Legal
Data Processing Addendum
Last updated: May 10, 2026.
1. Definitions
Terms used here have the meanings given in EU Regulation 2016/679 (“GDPR”) and, where applicable, the UK Data Protection Act 2018 and California Consumer Privacy Act of 2018 as amended (“CCPA/CPRA”). “Personal Data”, “Processing”, “Controller”, and “Processor” carry their GDPR meanings. “Customer Personal Data” is Personal Data Customer makes available to QuickPly via the service.
2. Roles
3. Subject matter, duration, nature, purpose
- Subject matter. Drafting customer-support reply variants from inbound email content.
- Duration. For the term of the Customer's subscription, plus the export window described in our Terms.
- Nature & purpose. Storage, retrieval, AI inference, transmission to Customer; no profiling, no automated decisions with legal effect.
- Categories of data subject. Customer's end-customers (i.e., the people who emailed Customer's support inbox) and Customer's authorized users.
- Categories of personal data. Names, email addresses, free-text email content, OAuth tokens for Customer's own mailbox, IP addresses, browser metadata.
4. Customer obligations
5. QuickPly obligations
QuickPly will:
- Process Customer Personal Data only on documented instructions.
- Ensure personnel with access are bound by confidentiality.
- Implement and maintain the technical & organizational measures listed in Annex II below.
- Engage sub-processors only under written terms providing materially equivalent protections.
- Notify Customer of any Personal Data Breach without undue delay and in any event within 72 hours of becoming aware.
- Assist Customer with data-subject requests, security reviews, DPIAs, and supervisory-authority cooperation, on a commercially reasonable basis.
6. Sub-processors
Customer authorizes QuickPly to engage the sub-processors listed in our Privacy Policy Section 4 (Sub-processors). We'll give 30 days' notice before adding a new sub-processor that handles Customer Personal Data. If Customer objects on reasonable data-protection grounds, we will work in good faith to provide an alternative or, failing that, allow Customer to terminate the affected service for refund of unused fees.
7. International transfers
8. CCPA / CPRA
9. Deletion and return
10. Audits
Annex I — Processing details
Annex II — Technical & organizational measures
- Encryption. TLS 1.2+ in transit; pgcrypto AES-encryption of OAuth refresh tokens at rest; Supabase-managed AES-256 disk encryption for the rest of the row store.
- Access control. Postgres row-level security per workspace. Production console access is two-person, MFA-required, audited.
- Authentication. Bcrypt passwords (Supabase Auth). TOTP MFA available to every user. SSO via OAuth providers.
- Network. All endpoints HTTPS with HSTS. Sliding-window rate limiting on auth, write, and AI-generation endpoints. Origin/Referer guards on cookie-authed mutations.
- Logging. Structured server logs with request IDs; security-relevant events recorded in an immutable audit_log table.
- Backups. Encrypted, 7-day rolling, restored quarterly to a staging environment as part of disaster-recovery testing.
- Vulnerability management. Dependency scanning on every CI run. Security reports accepted at security@quickply.com.
- Incident response. 72-hour breach notification commitment. Postmortem published to affected customers within 30 days.