Draft for legal review. Highlighted items must be confirmed by RUSH before publishing.

Legal · Security

Security

Last updated: 20 October 2026

Samvrik is built for companies that handle sensitive and regulated data. This page explains how the platform is designed to protect it, and how to tell us about a security issue.

How Samvrik protects data

  • Runs in your environment. Samvrik is deployed on-premises, in your private cloud, or air-gapped. Your data stays inside infrastructure you control.
  • Access by role. Access can be limited down to the row and column, with masking for personal data.
  • Everything logged. Changes, approvals and data access are recorded in an audit trail.
  • Checked before use. Data that fails quality rules is held for a person to review before it is published.
  • Open formats. Data is stored in open table formats, so you keep control of it.

The exact controls in each deployment are agreed in the customer contract and security documentation. [To confirm: certifications or audits held, e.g. ISO 27001, SOC 2 - list only those actually held]

How we work

  • People at RUSH get access only to what their role needs, and access is reviewed.
  • When RUSH operates a deployment as a managed service, it does so under the customer's instructions and the agreed security controls.
  • We report personal data breaches to customers and authorities as the law and our contracts require.

Report a vulnerability

If you think you have found a security issue in Samvrik or this website, please email [To confirm: security contact email, e.g. security@rush.tech] with details and steps to reproduce it. Please:

  • give us reasonable time to fix the issue before sharing it publicly,
  • avoid accessing or changing data that is not yours,
  • not run tests that could harm availability, such as denial of service.

We will acknowledge your report, keep you updated, and will not take legal action against good-faith research that follows these guidelines.