Data Processing Agreement
Effective date: July 13, 2026·Last updated: November 15, 2026
This Data Processing Agreement (“DPA”) forms part of the Terms of Service between Column Seven LLC, 8 The Green, Ste B, Dover, DE 19901, United States, operating ECHOdrop (the “Processor”), and the customer / Drop Owner who creates drops and receives lead data (the “Controller”). It reflects the mandatory content of Article 28(3) of the GDPR. Where this DPA and the Terms of Service conflict on a data-protection matter, this DPA prevails.
Electronic acceptance and signed copies
This DPA is entered into electronically when the Drop Owner, or an authorized representative acting for the Drop Owner, accepts the Terms of Service when creating the account. The contracting customer is the person or organization on whose behalf that account is created. No separate signature is required for this electronic acceptance.
If your organization requires a separately signed copy, request one at privacy@echodrop.social before submitting lead data under that requirement. You may print or save this DPA for your records.
1. Parties and roles
This DPA governs ECHOdrop’s processing on the Drop Owner’s instructions. ECHOdrop’s separate marketing to people who have explicitly opted in is undertaken as an independent controller, subject to applicable law, and is described in section 4.1 of the Terms and the Privacy Policy, not as processor activity authorized by this DPA. This distinction does not extend Social marketing use to professional sealed-handoff recipient data.
- Controller: the customer (Drop Owner) who creates drops and receives lead data.
- Processor: Column Seven LLC, operating ECHOdrop.
- This DPA prevails over the Terms of Service for data-protection matters.
2. Subject matter, duration, nature and purpose
- Subject matter: processing of lead data submitted through the Controller’s drop pages.
- Duration: the term of the Controller’s account.
- Nature and purpose: collection, storage, display, export, and webhook delivery of lead submissions on the Controller’s instructions.
- Categories of data subjects: visitors who submit details through the Controller’s drop pages.
- Categories of personal data: email address; any additional form fields the Controller configures; submission timestamp and associated drop. The Controller must not configure forms to collect special-category data (e.g., health, political, religious, or biometric data).
3. Processor obligations
- Documented instructions only. The Processor processes lead data under this DPA only to provide the Service as configured by the Controller (dashboard, CSV export, webhooks). The Controller’s configuration is the instruction.
- Confidentiality. Persons authorized to process lead data are bound by confidentiality.
- Security (Art. 32). TLS in transit, encryption at rest, hashed credentials, HMAC-signed webhooks, and per-account access isolation, as further described in Annex II.
- Sub-processors. The Controller grants general written authorization for the Processor to engage the sub-processors listed in Annex III. The Processor will give at least 30 days’ notice (by email or in-app notice) before adding or replacing a sub-processor; the Controller may object on reasonable data-protection grounds and, if the matter is not resolved, terminate the affected service.
- Data subject rights assistance. The Processor provides the tooling (view, export, and delete individual leads) that lets the Controller answer access and erasure requests. Requests received directly by the Processor are forwarded to the Controller.
- Breach notification. The Processor will notify the Controller without undue delay, and in any event within 72 hours of becoming aware of a personal data breach affecting lead data.
- Deletion or return. On account deletion, all lead data is deleted within 30 days; the Controller can export CSV at any time before deletion. Backups purge on a rolling 30-day cycle.
- Audit. Audit rights are satisfied primarily through documentation and self-service reports. On-site audits are limited to once per year, on reasonable prior notice, at the Controller’s cost, and subject to confidentiality.
4. International transfers
The Processor and its sub-processors are located in the United States. Where lead data is transferred from the EU/UK to the United States, the parties incorporate the EU Standard Contractual Clauses (Module Two: controller to processor) by reference, together with the UK Addendum where applicable.
5. Liability
Liability under this DPA is subject to, and does not increase, the aggregate liability cap set out in the Terms of Service.
6. Annexes
Annex I - Description of processing
The subject matter, duration, nature, purpose, categories of data subjects, and categories of personal data are as set out in Section 2 above.
Annex II - Technical and organisational measures
- TLS encryption for data in transit;
- encryption at rest via our hosting providers;
- hashed authentication credentials;
- HMAC-signed webhook payloads;
- per-account access isolation so lead data is accessible only to the owning account;
- access controls and least-privilege administration;
- backups with a rolling 30-day purge cycle;
- incident response and breach-notification procedures.
Annex III - Approved sub-processors
| Name | Purpose | Region | Safeguard |
|---|---|---|---|
| Replit (Replit Deployments) | Application hosting and server logs; runs on Google Cloud infrastructure | United States | Data processing terms; SCCs |
| Replit (Postgres database) | Database storage of account, drop, and lead data | United States | Data processing terms; SCCs |
| Supabase | Authentication (Drop Owner login credentials and email) | United States | Supabase DPA; SCCs |
| Resend | Transactional email delivery (verification codes, access codes, gated-content links) | United States | Resend DPA; SCCs |
Public website assistant: outside lead-processing scope
OpenRouter and its model providers power the optional public ECHO website assistant. That service receives visitor chat messages, a temporary random session ID and the public site guide; it is not connected to campaign lead records or reward files. This is processing for ECHOdrop's own website service, not lead processing on a Drop Owner's instructions under this DPA. These providers are therefore not appointed as lead-data sub-processors under this DPA. Do not submit lead records or sensitive information to the public assistant.
The Privacy Policy explains the assistant's data handling, requested ZDR routing and provider-policy limitations. Billing through Stripe is also separate from lead processing under this DPA.
Contact
For any question about this DPA, to exercise data-protection rights, or to notify the Processor of a data incident, contact Column Seven LLC, 8 The Green, Ste B, Dover, DE 19901, United States, at privacy@echodrop.social.