Trust · DPDP-compliant by design

Your employee data never reaches us

What “compliant by design” means in practice: what the architecture covers, and what stays with you as the data fiduciary. Written for your procurement and security teams to test.

What the design covers · Built in

Six things the architecture does for you

Where data lives
In your cloud account, in your region. Postgres, Airflow and the agents run inside it. Dattamsha holds named operator access that you can revoke.
What the model sees
Masked sentences built from aggregates, never an employee row. The model is pluggable: Claude API by default, a self-hosted model where policy requires.
Who sees what
Row-level access enforced in the application layer; an HRBP sees their zone, a manager their team. Teams under 10 are withheld everywhere.
Consent
A consent ledger in Sangam™ records purpose and status per employee, so a withdrawal propagates to every downstream metric.
Identity documents
Verified through Setu APIs at onboarding. Aadhaar and PAN numbers are never stored in the platform.
Audit
Every agent step, every approval and every nudge is logged in a case file you can reopen.

What stays with you · The fiduciary’s duties

Four things only you can do

Notice to employees
You issue the DPDP notice to your employees as the data fiduciary. We provide the template and the purpose list.
Grievance handling
Your grievance officer and your process. The platform surfaces requests; your team answers them.
Breach intimation
We alert you inside your account; the intimation to the Board and to employees is yours to make, within the timelines in the Rules.
Retention
You set the retention periods; Sangam enforces them.

Core duties under the DPDP Rules, 2025 apply from 13 May 2027. We help you comply before that date.

Practices · How we operate

Security practices

Deployment
Infrastructure as code, deployed only from CI, pinned dependencies, no secrets in repositories.
Access
Named accounts, two-factor everywhere, access reviewed quarterly and revoked on the day an engagement ends.
This website
Static pages hosted on GitHub Pages, with a strict content security policy. No cookies, no analytics, no third-party scripts. The only personal data it handles is what you send to book a session or ask a question, kept 90 days after the session.
Sub-processors
For this website: Google (email and booking calendar) and GitHub (hosting). For a deployment, only what you approve inside your own account.
Reporting a vulnerability
daksh@dattamsha.co.in, or /.well-known/security.txt. We acknowledge within two working days.

Send us your security questionnaire.

We answer it in full, in writing, before any session, so your security team is not the last to hear.

Request the answers