Data Processing Agreement (DPA)
In this article
Last updated: 17 November 2026
This agreement governs the processing of personal data that Clautia carries out on behalf of the customer when providing the service, in accordance with Article 28 of Regulation (EU) 2016/679 (GDPR) and Spanish Organic Law 3/2018 (LOPDGDD). It forms part of the Terms and conditions and is accepted with them. In case of conflict on data protection matters, this agreement prevails.
Parties
- Controller ("the customer"): the person or entity that owns the organization subscribing to Clautia.
- Processor: the self-employed owner identified in the Legal notice; contact: info@clautia.com.
1. Subject matter and scope
1.1. Clautia processes personal data on behalf of the customer only to provide the contracted service: connecting the customer's social media and Google Business Profile accounts, publishing and scheduling content and, when the inbox feature is active, receiving and displaying comments, messages and reviews, suggesting replies with artificial intelligence and sending the replies the customer decides on. Measuring results is also in preparation and is not included until launch. Details are in Annex I.
1.2. This agreement does not cover data Clautia processes as controller (user account, billing, security and support), which is governed by the Privacy policy.
2. Duration
This agreement lasts for as long as Clautia provides the service to the customer and, afterwards, for the time needed to return or delete the data under clause 10.
3. Customer instructions
3.1. Clautia will process the data only on the customer's documented instructions. Instructions include these terms, the settings the customer configures in the app (such as connected accounts) and the actions it carries out, including through the API or MCP.
3.2. If Clautia considers that an instruction infringes data protection law, it will inform the customer immediately.
3.3. If the law requires Clautia to process the data otherwise, it will inform the customer beforehand, unless the law prohibits it.
4. Confidentiality
Clautia ensures that persons authorised to process the data have committed to confidentiality or are under a statutory obligation of confidentiality. Access to the systems is currently limited to the owner.
5. Security
Clautia applies the technical and organisational measures in Annex II, appropriate to the risk (Art. 32 GDPR). It may update them provided the level of protection is not reduced.
6. Sub-processors
6.1. The customer gives general authorisation for Clautia to engage the sub-processors listed in Annex III.
6.2. Clautia will notify the customer, by email or in the app, at least 15 days in advance of any new or replacement sub-processor. The customer may object on reasonable data protection grounds; if no solution is found, it may cancel its subscription before the change takes effect.
6.3. Clautia will contractually impose on each sub-processor data protection obligations equivalent to those in this agreement, and remains liable to the customer for their performance under Art. 28.4 GDPR.
7. International transfers
Some sub-processors may process data outside the European Economic Area. In that case, Clautia will ensure the transfer is covered by a Chapter V GDPR safeguard: an adequacy decision (including the EU-US Data Privacy Framework for certified providers) or Standard Contractual Clauses. The safeguard for each one is shown in Annex III.
8. Data subject rights
Taking into account the nature of the processing, Clautia will assist the customer in responding to data subject requests. If a data subject contacts Clautia directly about data processed on the customer's behalf, Clautia will forward the request to the customer without undue delay and will not respond on its own unless instructed by the customer.
9. Security breaches and other obligations
9.1. Clautia will notify the customer without undue delay and in any case within 48 hours of becoming aware of a personal data breach affecting the customer's data, with the information available: nature of the breach, categories and approximate number of data subjects and records concerned, likely consequences and measures taken or proposed. It will provide further information as it becomes available.
9.2. Clautia will reasonably assist the customer in meeting its obligations on security, breach notification, impact assessments and prior consultation (Arts. 32 to 36 GDPR).
10. End of service: return and deletion
10.1. If the customer deletes its account or organization, its data is deleted at that time; automatic backups retain it until their rotation cycle is complete. If the customer only cancels, Clautia keeps its workspace so it can reactivate it and deletes it when the customer asks at info@clautia.com. The customer can request the return of its data in a commonly used format at that address. If the law requires data to be kept, it will remain blocked.
10.2. When the customer deletes a brand, Clautia also deletes its profile group at the publishing provider (Postproxy).
10.3. Backups are deleted according to their rotation cycle.
11. Information and audits
Clautia will make available to the customer the information needed to demonstrate compliance with this agreement, by answering reasonable questionnaires. The customer may carry out an audit, directly or through an auditor bound by confidentiality, once a year, with at least 30 days' notice, without disrupting the service and at its own cost, unless there are well-founded indications of non-compliance or an authority requires it. Clautia does not hold external certifications (such as ISO 27001 or SOC 2).
12. Customer obligations
The customer undertakes to:
- Have a legal basis for the processing it commissions, and inform data subjects where required.
- Connect only accounts it legitimately manages and comply with the terms of each social network and of Google.
- Review AI-suggested replies before sending them and configure any automatic rule carefully.
- Not enter special category data or data about minors into Clautia unless strictly necessary and lawful.
- Keep its credentials and API keys secure.
13. Liability
Each party's liability is governed by the GDPR and by the limitation of liability clause in the Terms and conditions, except where the law does not allow limitation.
Annex I. Description of the processing
| Item | Details |
|---|---|
| Nature | Collection through platform APIs, storage, consultation, organisation, generation of AI suggestions, transmission of posts and replies, deletion |
| Purpose | Providing the social media and review management service contracted by the customer |
| Categories of data subjects | Followers, customers and other people who comment, send messages or post reviews on the accounts connected by the customer; people appearing in content the customer publishes; members of the customer's team |
| Types of data | Name and username, profile picture where the platform provides it, text of comments, messages and reviews, rating, dates, platform identifiers, replies sent and content (texts, images, videos) uploaded by the customer |
| Special categories | Not processed intentionally. They may appear if a third party includes them in a comment, message or review |
| Frequency | Continuous, while accounts are connected |
| Duration | The term of the service, plus the time needed to delete the data under clause 10 |
Annex II. Technical and organisational measures
Data isolation and access control
- Every record is linked to an organization. The database enforces forced row-level security (RLS) policies, so every query only sees the data of the active organization.
- The app connects through a database user without administrative privileges and unable to bypass RLS. System operations use narrowly scoped, audited functions.
- After every schema change, hardening and an automated check are run to confirm that no tables, views or functions are exposed to the database's public API.
- Role-based permissions within each organization (owner, admin, member).
Authentication
- Passwords stored using a hash function; mandatory email verification; two-factor authentication and passkeys available; sessions expiring after 30 days that users can review and revoke.
- Rate limiting on authentication and the API.
API keys and MCP
- Keys are stored only as a SHA-256 hash and shown in full only once. They have scopes, expiry, revocation and per-key usage limits (requests, publications and AI credits). Sensitive actions may require confirmation.
Communications and integrations
- Encryption in transit (HTTPS with HSTS) for the website, the app and the API.
- Stripe and Postproxy webhooks are verified with an HMAC signature and a time tolerance, and de-duplicated by event ID.
- Each customer brand uses its own profile group at Postproxy, with a key limited to that group.
Files
- Files uploaded for publishing are stored under random, non-guessable names; storage only allows reading a specific file (not listing contents); uploads are authorised with signatures that expire after 60 seconds.
Artificial intelligence
- Only the text needed for each task is sent to the models. System instructions require third-party messages to be treated as material, never as commands, and forbid inventing facts.
- The inbox and suggested replies are in preparation and are not included until launch.
Infrastructure and organisation
- Database and app functions in Frankfurt (EU). Uploaded media in the United States (AWS us-east-2 through InsForge), subject to Annex III safeguards.
- Secrets and credentials stored as hosting provider environment variables, never in the code.
- Security reviews of the code before each significant release.
Annex III. Authorised sub-processors
| Provider | Purpose | Processing location | Transfer safeguard |
|---|---|---|---|
| InsForge | Database and files | Database: eu-central, Frankfurt; support: US / global | SCC (Decision 2021/914) under provider DPA |
| InsForge Storage → AWS | Media and avatars | AWS us-east-2, US; global CDN | SCC (Decision 2021/914) under provider DPA |
| Vercel | Hosting | fra1 (EU); CDN and support global / US | SCC (Decision 2021/914) under provider DPA |
| Resend | Service email | eu-west-1 (Ireland); US entity and support | SCC (Decision 2021/914) under provider DPA |
| Postproxy | Publishing and social tokens | International infrastructure; no exclusive EU residency commitment | SCC (Decision 2021/914) under provider DPA |
| OpenRouter → model provider | AI text | US and model provider regions | SCC (Decision 2021/914) under provider DPA |
| OpenRouter → Mistral AI | Dictation: turning your voice into text, only when you press the microphone | No guaranteed region: OpenRouter doesn't let us choose it | Zero data retention required on every request (OpenRouter only routes to services that neither retain nor train, per its public policy). DPA: OpenRouter publishes a DPA with EU standard contractual clauses. The model provider (Mistral AI) is not listed as a subprocessor in that DPA: OpenRouter requires zero retention from it, but does not guarantee its compliance. |
| Just One API / JustSerpAPI | Only when the trends feature is active | International; no guaranteed EU residency | SCC (Decision 2021/914) under provider DPA |
| SocialFetch | Only when enabled as a fallback for the trends feature | International; no guaranteed EU residency | SCC (Decision 2021/914) under provider DPA |
Stripe is not listed as a sub-processor under this agreement because it only processes the customer's own billing data, which Clautia processes as controller.