Security enforced in code, not just in a policy PDF.
Every control below is implemented in the platform and exercised by tests — not a promise we ask you to trust. Here is exactly how your data is isolated, encrypted, audited, and, when the time comes, destroyed.
Role-based access control
Granular RBAC governs what every role can see and do across the platform.
Privileged access
Only designated Ektasi administrators hold platform-level access, and they use it only for support you ask for, a security investigation, or where the law requires it.
TOTP two-factor
Standards-based TOTP 2FA protects accounts, with enforcement options for admins.
OIDC single sign-on
Act as an OIDC issuer so teams can sign in with a central identity.
Per-tenant AES vault
Stored credentials — integration passwords, OAuth tokens, AI-provider keys — are encrypted with AES-256-GCM using per-tenant, HKDF-derived keys; the derived key is never stored. Ordinary workspace rows are protected by row-level isolation, not by per-tenant encryption.
Row-level isolation
PostgreSQL row-level security prevents one tenant’s query from reaching another tenant’s data.
Servers in India
Our application and database servers are in India. Some sub-processors, including the AI model providers, operate outside India — see the sub-processor list.
Workspace erasure
Decommissioning deletes every table that carries the tenant’s identifier from the live database, in one transaction, and destroys its per-tenant salt. Two records are kept for eight financial years because tax and company law require them (CGST Act s.36; Companies Act, 2013 s.128(5), permitted by DPDP Act s.8(7)): the GST tax invoices we issued, and the record of the acceptance behind each charge. Copies in backups expire on a rolling retention schedule.
Append-only audit ledger
A database-enforced, append-only trail records key administrative actions for forensic review.
Per-tenant kill-switches
Lock or decommission a tenant instantly if something goes wrong.
Backups & restore
The production database is backed up every six hours on a fixed schedule, with a documented restore procedure.
Self-hosted observability
Error and usage telemetry can run on your own stack, not a third party’s.
Honest about where we are.
DPDP readiness. The platform is built for DPDP work — servers in India, per-tenant encryption of stored credentials, row-level isolation, and an append-only audit ledger. Compliance is a shared responsibility that also depends on how you deploy and operate it.
SOC 2. We hold no SOC 2 attestation and no audit is in progress. We maintain internal control playbooks, and we will publish attestation status here if that changes.
Sub-processors & data flows. When you self-host, third-party processors can be reduced to those you choose. The current list for the hosted service — what each one receives and where — is published at /legal/subprocessors.
We run our own business — billing, support, and a production license server — on this platform. Uptime is public.
Send us your security questionnaire.
We would rather answer hard questions than dodge them. Request a security review and we will walk your team through the architecture.