Data Processing Agreement (GDPR / CCPA)

A description of how personal data is handled on this platform, in the structure of a Data Processing Agreement, so it is easy for your legal counsel to turn into a signed agreement with your customers.

Draft for legal review. The roles, rights, and security measures described below reflect what the platform actually does today. It has not yet been reviewed by legal counsel or formally executed as a binding DPA with any customer. Treat the factual claims as accurate and the legal framing as a starting point.

1. Roles of the parties

For personal data submitted by a lead through your intake forms or API integration, you (the account holder) act as the Data Controller, you decide why the data is collected and what happens to it. This platform acts as the Data Processor, processing that data only on your instructions, as expressed through your use of the API, the portal, and the automated bots.

2. What personal data is processed

Data categoryWhere it comes from
Lead contact detailsName, email, phone number, company, and role, submitted through your lead capture form or API.
Lead message contentThe free-text message or inquiry submitted with a lead.
Account holder detailsThe name and email of the person who created and manages the account.
Usage and access metadataIP address of API requests, timestamps, and which API key or user performed an action, kept in the audit log.

3. Data subject rights

RightCurrent support
Access / portabilityFully supported today. An account holder can export their leads, financial ledger history, workflow history, and audit trail as a self-service download at any time, without needing to contact support.
DeletionPartially supported today. Deleting an individual lead record is a real, immediate operation. Deleting an entire account removes it and its related records. What is not yet in place is a documented turnaround-time commitment for a formal deletion request (for example, "within 30 days"), and a defined process for a lead's own data-subject-request to be routed to the correct account holder rather than handled ad hoc.
RectificationSupported by editing a lead's record directly, no dedicated correction workflow exists separately from ordinary record editing.
Objection to processingHandled by removing the lead's data via the deletion capability above. There is no separate "opt out but retain a suppression record" mechanism today, which some businesses prefer for compliance purposes (so a contact isn't re-imported later). That is worth a decision before formalizing this section.

4. Security measures in place today

  • Encryption at rest: a lead's email, phone number, and message are individually encrypted with AES-256-GCM before being stored, not left to rely on whole-disk encryption alone. This currently covers those three fields specifically, not every field on every record in the system.
  • Encryption in transit: the platform enforces HTTPS going forward via a Strict-Transport-Security header. The underlying TLS certificate and cipher configuration sits at the infrastructure layer in front of the application.
  • Access control: every account's data is isolated from every other account's at the database query level, and API keys can be scoped to only the parts of the system they need.
  • Audit trail: sensitive actions are logged with who performed them, from where, and when.
  • Two-factor authentication: required on every account sign-in, not optional.

For the fuller security picture, including the parts that are honestly still gaps (a formal retention policy, encrypted backups, centralized access review), see the SOC 2 Overview.

5. Sub-processors

The vendors who process data on this platform's behalf are listed on the Compliance page, and kept matched to the real production infrastructure rather than a static list.

6. Data breach notification

Should a data breach affecting personal data occur, it would be identified through the platform's audit logging and monitoring. A formal, written breach-notification commitment, specifying a maximum notification window to affected account holders, has not yet been defined and is a business/legal decision that should be made and published here before this page is presented as a signed agreement.

7. International data transfer

Where the platform's hosting provider or sub-processors are located in a different jurisdiction than your customers, an appropriate transfer mechanism (such as Standard Contractual Clauses) may be required depending on your customers' locations. Confirming your hosting region and which transfer mechanism applies is a business decision that should be finalized with legal counsel, and then recorded here.

Was this page helpful?