Boring, documented, and in writing.
What tenant isolation actually looks like
This is the shared plan, where clients sit on one platform. Choose a dedicated plan instead and the boxes below become entirely separate infrastructure — your own instance, not just your own row.
isolated database
isolated database
isolated database
Every box above is scoped by organisation. There is no query path from one client’s account into another’s data.
Data processing terms
Every client signs a Data Processing Addendum covering what we handle, where it is stored, how long we retain it, and what happens when the relationship ends.
DPDP Act 2023
You are the Data Fiduciary for your customers' personal data. Ophriel Systems acts as your Data Processor and operates under your written instruction.
Your data stays in India
Deployments run on DigitalOcean infrastructure in the Bangalore region (BLR1). The region is named in your Data Processing Addendum before you sign — in the contract, not in a footnote — and we will tell you in writing before it ever changes.
Tenant isolation
On a shared plan, every client's data is scoped by organisation at the database level. On a dedicated plan, it's a separate instance entirely. Either way, cross-client access is structurally prevented, not policy-prevented.
Encryption
Sensitive fields, identity documents in particular, are encrypted at the application layer — not only at rest on the disk.
Backups
Automated, stored separately from the primary hosting provider, and test-restored. A backup nobody has ever restored is a rumour, not a backup.
Payments
Card and payment data is handled entirely by Razorpay. Ophriel CRM does not store card details.
Want the details in writing?
Ask for the Data Processing Addendum when we scope your deployment — it names the region, the retention terms, and what happens if you leave.