Section 8 · Rule 14
Integrations for your DPDP data map
Discovery, rights requests and retention rules work from the systems you connect. The connector catalog, system discovery and the API are how they get in.
Sample workspace
Connectors
- PostgreSQL · loans-dbConnected
- Amazon S3 · kyc-docsConnected
- ZendeskConnected
- SlackNot connected
- forms.example.comDetected
System discovery
- forms.example.com detected
- Reviewed by IT
- Connect with OAuth or an API key
Short answer
DPDP duties such as security safeguards (s.8(5)), erasure (s.8(7), s.12) and access summaries (s.11) reach every system that holds personal data. TruePrivacy connects to those systems through a catalog of pre-built connectors with OAuth or API-key setup, with scanner sources including PostgreSQL, MySQL, MongoDB, Amazon S3, Azure Blob Storage, Google Drive, Slack and Zendesk. All connectors are on every plan, with no per-source fee.
What integrations cover
Every duty that touches data in your systems needs a way into those systems. Integrations give discovery something to scan and rights requests somewhere to send their tasks. Systems you find but have not connected stay on the list, marked detected or reviewed.
Pre-built connectors with OAuth or API-key setup, on every plan.
PostgreSQL, MySQL, MongoDB, Amazon S3, Azure Blob Storage, Google Drive, Slack and Zendesk.
A list of the systems your organisation uses, added by website or domain with how you found them, each marked detected, reviewed or connected.
An API and webhooks to connect TruePrivacy with your own systems.
Single sign-on and multi-factor authentication for the people on your team who use TruePrivacy.
All connectors are on every plan. See pricing.
How a system gets connected
- 01Find your systems
Add the tools your organisation uses by website or domain, noting how you found them.
- 02Review shadow SaaS
Mark each system reviewed once someone has checked it, and connect the ones that hold personal data.
- 03Connect
Authorise a connector with OAuth or an API key, granting the access scanning needs.
- 04Put it to work
Connected systems are scanned by data discovery and receive tasks from rights requests. Retention rules can target a connected system.
Mapped to the Act and Rules
| Duty | Section or rule | What TruePrivacy does |
|---|---|---|
| Be responsible for processing, including processing by your Data Processors | s.8(1) | System discovery makes unlisted SaaS visible so it can be connected |
| Reasonable security safeguards | s.8(5), Rule 6 | Connected stores scanned for personal data and access issues in data security posture |
| Summary of personal data and its processing on request | s.11 | Connected systems scanned by discovery give you an inventory to prepare it from |
| Correction and erasure | s.12 | Request tasks fanned out to connected systems |
| Erase when consent is withdrawn or the purpose is no longer served | s.8(7) | Retention rules per connected system |
| Publish how to make requests | Rule 14 | Requests from the privacy center fan out to connected systems |
Before you connect a system
A connector works with the access you grant through OAuth or an API key, so grant what scanning needs and review it with your security team. Systems you have not connected stay outside scans and request tasks.
India data residency for customer personal data is available where offered. Read about access control, the audit trail and the subprocessor list on the trust page.
Works with
Which systems does TruePrivacy connect to?
Scanner sources include PostgreSQL, MySQL, MongoDB, Amazon S3, Azure Blob Storage, Google Drive, Slack and Zendesk. Connectors are set up with OAuth or an API key.
Is there a fee per connected source?
No. All connectors are on every plan, with no per-source fee. Priced on scope, never per seat. Unlimited users. Quotes in INR, GST extra.
What is system discovery?
A list of the systems your organisation uses, each marked detected, reviewed or connected, so shadow SaaS becomes visible and can be connected.
Does TruePrivacy have an API?
Yes. TruePrivacy has an API and webhooks.
Your DPDP plan, starting today
Core obligations for data fiduciaries begin on 13 May 2027.
Core obligations begin