
Connector categories
| Category | Examples | What the connector does |
|---|---|---|
| Cloud storage | S3, Google Cloud Storage, Azure Blob | Discover buckets, classify contents, surface exposure findings |
| Databases & warehouses | Popular relational databases, Snowflake, BigQuery, Redshift | Inventory schemas, classify columns, execute DSR deletions and exports |
| SaaS & CRM | Salesforce, HubSpot, Zendesk, Workday | Map stored personal data, propagate DSRs, sync preferences |
| Marketing | Mailchimp, Braze, Google Ads | Propagate consent and opt-outs, execute suppression |
| CMPs | Existing consent platforms | Import consent records during migration to TruePrivacy consent |
| Ticketing | Jira, ServiceNow, Linear | Push DSPM findings, DSR manual tasks, and assessment actions as tickets |
| E-signature | DocuSign, Adobe Sign | Send DPAs for signature from vendor records |
Connecting a system
Choose a connector
Under Settings → Integrations, pick the system and authentication method — OAuth where supported, scoped API keys otherwise.
Grant least-privilege access
Each connector documents the exact permissions it needs. Read-only scopes are sufficient for discovery; DSR execution requires write/delete scopes only on the systems you choose.
API-first
Everything in TruePrivacy is API-first. Anything a connector does, you can do with the REST API — and webhooks push events to your systems the moment they happen.Missing a connector? Requests via support@lowerplane.com feed the connector roadmap, and the REST API plus webhooks cover custom systems in the meantime.