Connectors
Connectors push every consent change and erasure request into the tools you already use, so a withdrawal on your website also stops the next campaign in your CRM, store or WhatsApp list.
Growth and aboveWebhooks (Starter and above) let you build any integration yourself. Connectors are the ready-made version for common tools: you sign in to the tool, map a few fields, and OptProof keeps it in step.
Catalogue#
| Connector | On withdrawal | On erasure | Status |
|---|---|---|---|
| Zoho CRM | Sets Email Opt Out, and your SMS or WhatsApp opt-out fields, on matching Contacts and Leads. | Deletes or anonymises the record. | Available |
| HubSpot | Unsubscribes the contact from email. Re-subscribes on a new grant if you allow it. | Permanently deletes the contact. | Available |
| Shopify | Updates the customer’s email and SMS marketing consent. | Requests customer data erasure through Shopify, which completes it on its own schedule. | Available |
| Google Sheets | Keeps a suppression list: one row per person, updated on every change. | Anonymises the row. | Available |
| Brevo | Blocks the contact for email and SMS. | Deletes the contact. | Available |
| Mailchimp | Unsubscribes the person from your audiences. | Permanently deletes them. | Available |
| WhatsApp opt-out list | Sends a signed opt-out or opt-in event to your WhatsApp provider or your own endpoint. | Forwards the erasure request to that endpoint. | Available |
| WhatsApp Cloud API | Connects your WhatsApp Business number. OptProof enforces opt-outs before sending, because Meta has no opt-out API. | Manual. | Preview, phase 3 |
| Zoho Books | Flags customers who withdrew consent. | Manual, because accounting records usually have to be kept. | Planned, phase 3 |
| Zoho Desk | Suppresses helpdesk contacts. | Planned. | Planned, phase 3 |
| Freshworks | Unsubscribes Freshsales and Freshdesk contacts. | Planned. | Planned, phase 3 |
| LeadSquared | Sets Do Not Email and Do Not SMS on leads. | Planned. | Planned, phase 3 |
Planned connectors appear in the console so you can see what is coming, but they do nothing yet. Until they ship, erasure requests list those systems on the manual checklist described below.
How a change reaches your tools#
- Someone withdraws consent: in the preference centre, through the widget's Privacy choices link, by replying on WhatsApp, or through your own app via the API.
- OptProof records a
withdrawevent in the ledger and issues a receipt. - Each connected tool gets a sync job. The job finds the person by the contact details stored for them (encrypted) and applies the change.
- The result is recorded per tool: done, skipped (for example "contact not found"), or failed.
Our target is for a withdrawal to reach every connected tool within five minutes. If a tool is down or rate-limits us, the job retries with backoff for about 24 hours, the same schedule as webhooks. Failures show on the Integrations page with the tool's error message, and you can retry from there.
Choose which purposes drive each tool#
For each connector you pick the purposes that matter to that tool, usually the marketing ones such as marketing_offers or whatsapp_updates. Events for other purposes are skipped by that connector.
- A withdrawal, refusal or expiry of any chosen purpose suppresses the contact in the tool (unsubscribe or opt-out). This is deliberately cautious: one chosen purpose being withdrawn is enough, even if another is still granted.
- A new grant re-subscribes the contact only if you turn on Re-subscribe on grant. It is off by default, because some tools (Mailchimp, for example) send a confirmation email when you re-subscribe someone.
- Some tools let you name the fields to set. In Zoho CRM, for example, you can add your own SMS or WhatsApp opt-out fields next to Email Opt Out.
Erasure fan-out#
When you approve an erasure request in the request desk:
- every connected tool that supports erasure receives it, and each result is added to the request's timeline;
- tools that cannot erase automatically, and systems OptProof cannot reach at all (your clinic software, an Excel sheet, a paper register), appear on a checklist in the request. Someone on your team ticks each one off with a note;
- if the law requires you to keep some records, such as medical or tax records, you record a retention exception with the reason instead of deleting them. The person is told which records are kept and why.
Close the request once every item on the checklist has an outcome; the timeline is your record of what happened where. See Rights requests and SLAs.
Connect a tool#
- Open Integrations in the console and choose the tool.
- Sign in with the tool (OAuth) or paste an API key, depending on the tool.
- Map your purposes to the tool's fields and save.
- Run Test connection. OptProof checks it can reach the tool with the permissions it needs.
Credentials are stored encrypted (envelope encryption with AWS KMS), and you can disconnect a tool at any time.