Data Processing Agreement

Last updated: November 6, 2026

This Data Processing Agreement ("DPA") forms part of the Terms of Service between the customer ("Customer", the controller) and Eryk Andruszkiewicz, Spain ("we", the processor), for the RepPod service. It applies when we process personal data on the Customer's behalf under the EU General Data Protection Regulation (GDPR), the UK GDPR or similar laws. If you need a signed copy, ask through our contact form.

1. Scope and roles

  • Customer is the controller of personal data in its workspace. We are the processor.
  • Subject matter: providing RepPod, where AI agents research, draft and update records for the Customer's sales and marketing team.
  • Duration: the term of the Customer's subscription, plus the deletion period in section 9.
  • Data subjects: the Customer's users, and the Customer's prospects, customers and contacts whose data the Customer adds or connects.
  • Personal data: names, business email addresses, job titles, company details, CRM records, message and email text, and usage data. We don't ask for special categories of data, and the Customer agrees not to add them.

2. Instructions

We process personal data only on the Customer's documented instructions, which are this DPA, the Terms and the Customer's use of the product (for example, running an agent or approving an action). We tell the Customer if we think an instruction breaks data protection law.

3. Confidentiality

Everyone we authorise to process the data is bound by confidentiality.

4. Security

We keep appropriate technical and organisational measures, described in Annex 2, and update them as risks change.

5. Subprocessors

The Customer gives general authorisation for the subprocessors on our Subprocessors page. We give 30 days' notice before adding or replacing one, and the Customer may object on reasonable data protection grounds; if we can't resolve the objection, the Customer may end the affected service and get a refund of prepaid fees for it. We put data protection terms in place with each subprocessor that are at least as protective as this DPA, and we remain responsible for them.

6. International transfers

Workspace data is stored in the EU (Stockholm). Some subprocessors, such as Anthropic, process data in the United States. Such transfers rely on the EU-US Data Privacy Framework where the recipient is certified, or on the European Commission's Standard Contractual Clauses (and the UK Addendum where relevant), with supplementary measures such as encryption in transit.

7. Helping the Customer

  • We help the Customer answer data subject requests (access, correction, deletion, export), mainly through the product and on request.
  • We help with data protection impact assessments and consultations with authorities where reasonably needed.

8. Personal data breaches

We notify the Customer without undue delay, and within 48 hours, after becoming aware of a personal data breach affecting the Customer's data, with the information the Customer needs to meet its own obligations.

9. Deletion and return

When the subscription ends, the Customer can export its data for 30 days. After that we delete it, including from backups within a further 30 days, unless law requires us to keep it.

10. Audits

We make available the information needed to show compliance with this DPA, including our security documentation. Where that isn't enough, the Customer may audit once a year with 30 days' notice, at its own cost, during business hours and under confidentiality.

11. Order of precedence

If this DPA conflicts with the Terms, this DPA wins for the processing of personal data.

Annex 1: Processing details

  • Nature and purpose: storing workspace content, sending it to AI models to produce results, and carrying out actions the Customer approves.
  • Frequency: continuous while the Customer uses the service.
  • Retention: as section 9; run history stays until the Customer deletes it or the workspace closes.

Annex 2: Security measures

  • Encryption in transit (TLS 1.2+) everywhere, and at rest for the database. Connector keys and tokens are additionally encrypted with AES-256-GCM.
  • Workspace isolation enforced in the database with row-level security, so one customer can't read another's data.
  • Sign-in with Google (and SSO where enabled). No passwords stored by us.
  • Role-based access inside each workspace (owner, admin, member).
  • Agents can only propose emails, messages and CRM changes. A person approves each one. Gmail access is limited to creating drafts.
  • Access to production systems is limited to the people who run the service.
  • Error monitoring and alerting, and daily backups on the database plan that supports them.
  • AI providers are used under terms that don't allow training on customer data.