Skip to content

Data Processing Agreement

Version and last updated 2026-11-10

1. Parties

This Data Processing Agreement ("DPA") is between the SuperPost customer ("Controller") and SuperPost ("Processor") when a customer on any paid plan, or in its free first week, executes it under §7.

2. Subject matter

Processor processes personal data only to provide the SuperPost desk: account data, workspace content, connection metadata, and mail delivery logs as described in the Privacy Policy.

3. Processor obligations

Processor will process personal data only on documented instructions, ensure confidentiality, implement appropriate technical and organisational measures, assist with data-subject requests within 30 days, assist with Articles 32–36 including DPIAs, notify Controller of personal-data breaches without undue delay, and delete or return data within 30 days of termination except where law requires retention (including billing records). Controller warrants that its instructions are lawful.

4. Sub-processors

Controller authorises the sub-processors listed at /sub-processors (Annex III). Processor will give at least 14 days' notice before adding a sub-processor. Controller may object on reasonable grounds; if the parties cannot resolve the objection, Controller may terminate the affected processing.

5. International transfers — Standard Contractual Clauses

Where personal data is transferred outside the EEA/UK, the parties enter into the Standard Contractual Clauses annexed to Commission Implementing Decision (EU) 2021/914 of 4 June 2021 (the "SCCs"), which form part of this DPA on the terms below. Module. MODULE TWO (transfer controller to processor) applies: Controller is the data exporter and Processor is the data importer. Modules One, Three and Four are not used. Where Controller is itself a processor for its own clients, Controller warrants that its client has authorised the onward engagement of Processor and Module Two is read accordingly. Options selected. Clause 7 (docking clause) — included. Clause 9(a) — Option 2, general written authorisation, with the 14-day notice period in §4 of this DPA. Clause 11(a) — the optional independent dispute-resolution body is not selected. Clause 13 and Annex I.C — the competent supervisory authority is the one identified in Annex I.C of this DPA. Clause 17 (governing law) and Clause 18 (forum) — the law and courts of the EU Member State recorded in the execution block of this DPA (the member state the Controller enters when accepting in Settings → Data, or names by email); a Controller established outside the EEA names the Member State of its Art. 27 representative or, failing one, Ireland. Annexes I and II of the SCCs are completed by §8 and §9 of this DPA; Annex III (sub-processors) is /sub-processors. United Kingdom. For transfers subject to UK GDPR, the International Data Transfer Addendum to the EU SCCs issued by the Information Commissioner under s.119A of the Data Protection Act 2018 (version B1.0, in force 21 March 2022) is incorporated. Tables 1 to 3 of the Addendum are completed by the parties, Module Two and Annexes I to III above; for Table 4, either party may end the Addendum as set out in section 19 of the Addendum. Switzerland. For transfers subject to the Swiss FADP, the SCCs apply with the adaptations the Federal Data Protection and Information Commissioner requires: references to the GDPR are read as references to the FADP, the FDPIC is the competent authority in Annex I.C for Swiss data subjects, and data subjects in Switzerland may enforce their rights in their place of habitual residence. Signature path. The SCCs and the Addendum take effect when this DPA is executed under §7. The execution block — your legal entity, address, signatory and the Member State for Clauses 13, 17 and 18 — is stored with the acceptance and completes Annex I; that record, together with this text at its accepted version, is the signed instrument. A copy of the SCC text is available from legal@superpost.io on request.

6. Audits

Upon reasonable request, Processor will provide information necessary to demonstrate compliance and allow audits no more than once per year with 30 days' notice.

7. Execution

Workspace owners on any paid plan, or in their free first week, execute this DPA in Settings → Data by entering the Controller's legal entity name, address, signatory and the EU Member State in which it is established (or "non-EEA"). SuperPost records those four fields with the acceptance, the version of this text and the time; that row is the execution block referred to in §5. You may instead email the same four details to legal@superpost.io; we record them the same way and confirm by reply.

8. Annex I — Parties and processing

A. Parties. Controller: the customer entity on the order. Processor: SuperPost. B. Description of processing. Data subjects: the customer's staff and the authors of public posts the Inbox pulls. Categories of data: account, workspace content (the repo map, extracted facts with their quote spans, drafts, posts and metrics; never full repository text), connection metadata, mail logs (recipient hashed). Frequency: continuous during the subscription. Duration: the subscription and the retention periods in the Privacy Policy. C. Competent supervisory authority: the supervisory authority of the EU Member State in which the Controller is established (Clause 13(a) of the SCCs). Where the Controller is not established in an EU Member State, the authority is determined under Clause 13(a): that of the Member State of the Controller's Art. 27 representative or, failing one, of the Member State where the data subjects concerned are located.

9. Annex II — Technical and organisational measures

TLS 1.2+ in transit. AES-256-GCM sealing of network tokens at rest (sp2: envelope with a key id and per-row additional data). __Host- HttpOnly Secure SameSite=Lax session cookies with a 60-second cookie cache. Sessions revoked on password reset. DB-backed per-endpoint auth rate limits. CSP default-src 'self' with frame-ancestors 'none', HSTS with preload, X-Content-Type-Options, X-Frame-Options: DENY, Referrer-Policy, Permissions-Policy. Least-privilege OAuth scopes. Audit log. Secret scanning (known key formats plus an entropy check) on every repository file before it is stored or sent to a model; a match is replaced with a placeholder and only the count is kept. Repository file text is not stored: only the repo map, cited quote spans and their git blob SHAs. SSRF-refusing outbound fetch with private-IP denial.

10. Annex III — Sub-processors

The current list, entity names, countries and change log live at /sub-processors.

11. Term

This DPA remains in effect while Processor processes personal data on Controller's behalf under the Terms of Service.