Isolation is structural
Every record carries its organisation’s identity and every query is scoped to it at the framework layer, not by a check each feature has to remember. Cross-tenant access exists only through explicit, audited administrative tooling.
Access is a capability, not a role
Each sensitive action maps to a named capability granted per member. The API enforces it and the interface only mirrors it, so hiding a button is never what keeps someone out.
Credentials and codes are hashed
Passwords and one-time codes are stored only as cryptographic hashes. One-time email codes protect signup, password reset and privileged logins, and the platform-owner console requires a second factor.
Card data never reaches us
Payments run through Razorpay. Card details are handled entirely on their side and are not stored on our servers.
Sensitive actions leave a trail
Append-only audit logs cover privileged actions, consent capture and rights-request handling — including who acted, and on whose behalf when a consultancy operates inside a client’s workspace.
Hosted in India, over TLS
The platform runs on infrastructure in India and every surface is served over TLS. Databases are backed up on a schedule and deployments are scripted rather than manual.