Security Policy
Last Updated: March 1, 2026
1. Security Commitment
View Market applies layered security controls intended to protect platform availability, account integrity, and data confidentiality. Security is treated as an ongoing process that includes prevention, detection, response, and recovery measures. Our controls are reviewed as features evolve and as threat patterns change across infrastructure and application layers. While no system can be guaranteed fully secure, we aim to reduce risk through operational discipline and timely remediation practices. Users also play a critical role by protecting their credentials, devices, and broker account access.
2. Technical Safeguards
We use transport encryption for data in transit and apply access restrictions around production systems to reduce exposure. Security logging, monitoring signals, and alerting workflows support early detection of suspicious behavior or service anomalies. Sensitive operations are restricted by role-based access patterns and are reviewed under least- privilege principles. Infrastructure and application layers are updated regularly to address known vulnerabilities and dependency issues. Development and deployment workflows are designed to reduce accidental misconfiguration and unauthorized changes.
3. Account and Credential Security
Account access depends on user credential hygiene and secure authentication behavior, including strong unique passwords and prompt response to suspicious login activity. Session protections are used to reduce unauthorized reuse and to limit risk from inactive sessions. Broker API keys and related broker credentials should be managed in accordance with your broker’s security guidance and local device controls. You should never share account access and should immediately rotate compromised secrets. If a compromise is suspected, contact support without delay so mitigation steps can begin.
4. Vulnerability and Patch Management
We perform ongoing vulnerability management through a combination of automated checks, dependency monitoring, and targeted reviews of high-risk components. Identified issues are prioritized according to severity, exploitability, and user impact, then remediated under internal response targets. Security patches may be deployed on an accelerated schedule when active threats are detected. Operational change control is applied to balance rapid mitigation with service stability. Continuous improvement from incident lessons and post-remediation analysis is incorporated into future hardening work.
5. Incident Response
Security events are handled through a response workflow that includes triage, containment, investigation, remediation, and post-incident review. When required by law or operational necessity, affected users may be notified with relevant details and recommended actions. Incident handling focuses on reducing user impact, restoring safe operations, and preventing recurrence where feasible. Records of security incidents are maintained to support compliance, auditing, and process improvements. Not all anomalies indicate compromise, but every credible report is evaluated with urgency.
6. Responsible Disclosure
We encourage responsible disclosure of potential security issues by researchers and users acting in good faith. Please include clear reproduction steps, affected scope, and impact context so reports can be validated efficiently. Do not attempt data exfiltration, destructive testing, or privacy- invasive behavior while researching possible vulnerabilities. We aim to acknowledge valid reports promptly and communicate next steps as triage progresses. Security reports can be submitted to security@viewmarket.in.
7. Limitations and User Responsibilities
Security controls reduce risk but cannot eliminate all threats, especially those arising from third-party systems, compromised endpoints, or user credential misuse. You are responsible for maintaining secure local environments, applying device updates, and protecting broker access tokens used with automation workflows. Third-party integrations remain subject to their own security posture and downtime risks, which can affect end-to-end reliability. Use of the platform indicates acceptance of these limitations and shared responsibility for safe operation.
8. Contact
For security concerns, email security@viewmarket.in. For general support, contact support@viewmarket.in.