Data processing agreement (DPA)
This English version is a convenience translation. Only the German version is legally binding.
Parties
This agreement is concluded between the customer as specified at registration on app.aimarage.com, hereinafter the "Controller" (controller within the meaning of Art. 4(7) GDPR or, where it itself processes the data on behalf of a third party, that party's processor, clause 5.3),
and Dr. Peter Mayer, Webservice Mayer (sole proprietorship), Würzburgerweg 18, 4840 Vöcklabruck, Austria, email mail@aimarage.com, VAT ID ATU37463801, hereinafter the "Processor" (processor within the meaning of Art. 4(8) GDPR),
together the "Parties".
Preamble
The Processor operates the AI-assisted marketing service Aimarage at app.aimarage.com (the "Service"). To the extent the Processor processes personal data on behalf of the Controller, this agreement governs the data protection rights and obligations of the Parties under Article 28 of Regulation (EU) 2016/679 (General Data Protection Regulation, "GDPR") and the Austrian Data Protection Act (DSG).
This agreement supplements the General Terms and Conditions of Aimarage (the "Main Contract"). In case of conflict, the provisions of this agreement prevail with regard to the protection of personal data.
1. Conclusion
1.1 This agreement is concluded as soon as the Controller ticks the box "I conclude the data processing agreement (DPA)." at registration on app.aimarage.com; the agreement is linked there. The time of consent and the version (version identifier at the top of this page) are stored in the Controller's account.
1.2 The agreement is concluded in electronic form (Art. 28(9) GDPR). The current version is available at app.aimarage.com/avv and can be saved and printed by the Controller at any time.
1.3 A separate signature is not required. On request, the Processor provides a signed copy.
1.4 Existing workspaces: If the owner of a workspace has not yet accepted the current version, they are asked after their next login to accept the Terms and this agreement in the current version; until then, they cannot continue to use the Service except for export and logout. The time of consent and the version are stored in accordance with section 1.1.
2. Subject matter and duration
2.1 Subject matter is the provision of the Service under the Main Contract: planning marketing activities per project, reading the Controller's websites and documents, research, creating drafts using AI language models, approval and publication via connected accounts, receiving and replying to messages in connected mailboxes, and evaluating results.
2.2 Duration: The agreement begins with consent under section 1.1, runs for an indefinite period and ends with the Main Contract without separate termination. Section 12 (deletion) and all obligations that by their nature survive continue to apply after the end of the contract.
3. Nature, purpose and location of processing
3.1 Nature of processing (Art. 4(2) GDPR): collection, recording, storage, organisation, adaptation, retrieval, consultation, use, transmission to sub-processors under Annex 2, publication on the Controller's instruction, erasure.
3.2 Purposes:
- Project knowledge: retrieving the websites specified by the Controller, processing uploaded documents and media, storing the project profile, goals, strategy and rules.
- Creating drafts: transmitting the respective task and the project content required for it to an AI language model (Annex 2), storing the generated drafts and the conversation history with the agent.
- Research: web search with search terms derived from the project, retrieval of publicly available pages.
- Publishing and sending: transmitting approved content to the accounts connected by the Controller (directly or via a posting service); sending approved email replies via the Controller's mailbox.
- Incoming messages: retrieving emails, comments or messages from connected mailboxes and accounts, where set up by the Controller, and creating reply drafts.
- Evaluation: retrieving and storing metrics from connected accounts and services (e.g. reach, clicks, search statistics), figures entered by the Controller.
- Aimarage counter: counting page views of the Controller's website with UTM parameters via the Aimarage counter, stored only as totals per day, source, medium, campaign, content and page path; IP address and browser user agent are used only briefly in memory to prevent misuse and are not stored.
- Collaboration: team members and client links with the rights granted by the Controller.
- Operation: recording consumption (type of task, model, token counts, cost, time) to enforce plan limits, troubleshooting, backups.
3.3 No processing for own purposes: The Processor processes the data exclusively for the purposes listed in section 3.2. It does not use the data to train AI models or for advertising and does not disclose it to third parties. It only uses AI providers as sub-processors (Annex 2) if they are prohibited, by contract or by a chosen setting, from using the data to train their own models. Disclosure takes place only to the sub-processors under Annex 2 and to the recipients connected by the Controller itself (section 3.5). To the extent the Main Contract grants the Processor rights of use in the Controller's content, these do not cover personal data.
The contract terms listed in Annex 4 apply to the provider of the language model (Annex 2 No. 2). Under these terms, it may not use the data submitted via the API to train its models. Retention beyond the usual deletion period may take place under these terms to enforce its usage policy or due to legal obligations.
3.4 Location of processing: Database, file storage and backups are located at the hosting provider in Germany (Annex 2 No. 1). For individual services, sub-processors based or processing outside the EU are used (Annex 2); transfers take place only if the requirements of Art. 44 et seq. GDPR are met (adequacy decision or standard contractual clauses). Any further relocation to a third country requires prior notice under section 10.2 and may only take place if the requirements of Art. 44 et seq. GDPR are met.
3.5 Recipients connected by the Controller: Social media platforms, blogs, mailboxes, Google Search Console and other services that the Controller connects with its own credentials, as well as programs it connects via the interfaces (MCP, API), are not sub-processors of the Processor. Transmission to them takes place on the Controller's instruction; the contractual relationship with these providers exists between them and the Controller. Whether they act as controllers or as the Controller's processors depends on that contract and the actual processing; the Controller clarifies this itself. The Processor remains responsible for the security of the transfer up to these recipients and for compliance with the instruction.
3.6 Own AI key: If the Controller stores its own access to an AI provider, the Processor transmits the data for generating drafts to that provider on the Controller's instruction instead of to the AI provider in Annex 2. The chosen AI provider is not a sub-processor of the Processor because the Controller selects and engages it itself; the contractual relationship, including any required data processing agreement and safeguards for transfers to third countries, exists between it and the Controller. The Processor remains responsible for the secure transfer to this provider and the encrypted storage of the key. If an own key with Mistral AI is stored, the same applies to voice input in the chat; the recording is not stored.
4. Types of data and categories of data subjects
4.1 Categories of data subjects:
- employees and agents of the Controller whom it invites as team members or to whom it gives client links;
- customers, prospects, business partners and contacts of the Controller, in particular senders of incoming emails and authors of comments or messages;
- persons whose data is contained in the Controller's websites, documents, media and content;
- persons named in publicly available research sources;
- visitors to the Controller's websites, to the extent it uses the Aimarage counter.
4.2 Types of data:
- contact data (name, email address, platform username, possibly phone number and company);
- content of messages, emails and comments;
- content of documents, websites, images and videos;
- drafts, published posts and conversation histories with the agent;
- credentials for connected accounts and mailboxes (stored encrypted);
- metrics and statistics from connected services;
- for the Aimarage counter: page path, UTM parameters and host of the referring page (referrer), stored only as totals;
- usage data of team members (actions, approvals, times).
4.3 Special categories: Processing of special categories of personal data (Art. 9 GDPR) and of data relating to criminal convictions (Art. 10 GDPR) is not the purpose of the Service. The Controller does not deliberately bring such data into the Service and does not connect mailboxes or accounts through which such data regularly arrives (e.g. from patients, clients or applicants) without itself ensuring a legal basis under Art. 9 or 10 GDPR; this agreement does not create such a legal basis. If such data nevertheless enters the Service, for example in an incoming message, the Processor processes it only within the agreed purposes (in particular display and reply draft), does not access it outside section 8.2 and does not evaluate it separately. The Controller can delete such content in the Service at any time; on instruction, the Processor supports it in doing so.
4.4 End device: The Service sets only the technically necessary cookies ma_session (login), ma_project (last opened project, 30 days) and ma_chat and ma_chat_task (chat open or closed, 365 days) for the Controller's users; no analytics, tracking or advertising cookies. The Aimarage counter sets no cookies for visitors to the Controller's websites and does not access storage on their end device.
4.5 Logs: Independently of the project data, operation produces logs of the services (application, background worker, web server, database), which in individual cases may contain IP addresses or email addresses; the web server writes no access logs. They are deleted after no more than 14 days (Annex 3). Calls via the interfaces (MCP, API) are logged for 90 days with time, key, person, program, shortened IP address, tool, project and a summary of the arguments without content; the log is visible to owners and admins of the workspace.
4.6 Retention period: Project data, including retrieved emails, contacts and conversation histories, is not deleted automatically after a fixed period. It remains stored until the Controller deletes it or the project (section 12.1) or the Main Contract ends (section 12.2). The Controller sets appropriate deletion periods for its use and implements them with the deletion functions of the Service.
5. Responsibility and role of the Controller
5.1 The Controller is responsible for the lawfulness of processing, in particular for the existence of a legal basis, and for informing data subjects (Art. 13, 14 GDPR). For the Aimarage counter, the Processor provides a sample sentence for the Controller's privacy policy in the help; reviewing and adapting it is the Controller's responsibility.
5.2 The Controller ensures that it is entitled to process the content it brings in and to connect the mailboxes and accounts, and that advertising is sent only with the required consents (see Main Contract).
5.3 Controller acting as a processor (in particular agencies): If the Controller itself processes the data in the Service on behalf of a third party, for example an agency for its clients (hereinafter "End Client"), the End Client is the controller, the Controller is its processor and the Processor is a further processor (sub-processor) of the Controller within the meaning of Art. 28(2) and (4) GDPR. The term "Controller" in this agreement continues to refer to the customer. This agreement is concluded only between the Controller and the Processor in this case as well. There is no contractual relationship between the Processor and the End Client; the Processor does not conclude a separate data processing agreement with End Clients. The Controller exercises the rights and obligations assigned to it by this agreement itself vis-à-vis the Processor in this case as well; clause 5.1 applies with the proviso that the Controller ensures that the End Client can fulfil its obligations as controller.
5.4 Obligations of the Controller towards the End Client: In the cases of clause 5.3, the Controller ensures that
- it has itself concluded a contract under Art. 28(3) GDPR with each End Client before bringing data of the End Client into the Service;
- the End Client has authorised the use of the Processor and of the sub-processors listed in Annex 2 in advance in writing (specific or general authorisation, Art. 28(2) GDPR);
- it passes on changes to the sub-processors notified to it under clause 10.2 to the End Client in good time for the End Client to object; it notifies the Processor of an objection by the End Client within the period under clause 10.2, otherwise the change is deemed approved for it as well;
- the obligations under its contract with the End Client are compatible with this agreement. This agreement contains the data protection obligations that the Controller imposes on its sub-processor under the first sentence of Art. 28(4) GDPR; the Controller checks that they correspond to the obligations under its contract with the End Client. Further obligations bind the Processor only if it agrees to them in text form.
5.5 Instructions and requests via the Controller: The Controller passes on instructions of the End Client to the Processor via the settings in the Service or in text form (clause 6); the Processor does not carry out instructions that the End Client addresses directly to it but forwards them to the Controller. The same applies to requests from data subjects (clause 11.2) and other requests from the End Client. Notifications under clauses 10.2 and 13 and evidence under clause 14 are received by the Controller; it forwards them to the End Client without undue delay to the extent the End Client needs them for its obligations. Notifications to the supervisory authority and to data subjects (clause 13.3) are then incumbent on the End Client; the Controller assists it, and the Processor assists the Controller. The Controller exercises the End Client's audit rights under clause 14; audits by the End Client itself or by an auditor it engages are only possible via the Controller and on the terms of clause 14.
5.6 Liability along the chain: Towards the End Client, the Controller is liable for the Processor's compliance with its obligations as for its own (second sentence of Art. 28(4) GDPR). The Processor is liable only towards the Controller under clauses 10.3 and 15; contractual claims of the End Client are directed solely against the Controller. Statutory liability towards data subjects under Art. 82 GDPR remains unaffected.
6. Instructions
6.1 The Processor processes personal data only on documented instructions from the Controller, including with regard to transfers to a third country, unless required to do so by Union or Member State law (Art. 28(3)(a) GDPR). In such a case, the Processor informs the Controller of that legal requirement before processing, unless that law prohibits such information on important grounds of public interest.
6.2 The instructions are set out in the Main Contract and this agreement. Settings and actions of the Controller and its team members in the Service (e.g. creating projects, uploading documents, connecting accounts and mailboxes, approving, enabling sending, deleting) are also deemed documented instructions. The Controller gives individual instructions in text form to mail@aimarage.com.
6.3 The Processor informs the Controller without delay if, in its opinion, an instruction infringes the GDPR or other data protection provisions (Art. 28(3), second subparagraph, GDPR). It suspends the processing concerned until the legal concerns have been resolved and a lawful instruction has been given. Mere confirmation of an unlawful instruction does not oblige the Processor to carry it out.
6.4 Instructions going beyond the agreed scope of services are treated as a request for a change of services.
7. Obligations of the Processor
The Processor undertakes
- to process the data only within the instructions and for the purposes under section 3;
- to implement the technical and organisational measures under Annex 3 (section 9);
- to maintain confidentiality under section 8;
- to engage sub-processors only under section 10;
- to assist the Controller in safeguarding data subject rights (section 11) and with the obligations under Art. 32 to 36 GDPR, taking into account the nature of processing and the information available to it;
- to delete the data under section 12;
- to make available to the Controller all information necessary to demonstrate compliance with Art. 28 GDPR and to allow audits under section 14;
- to maintain a record of processing activities under Art. 30(2) GDPR;
- to inform the Controller without delay if a supervisory authority takes action in connection with this processing;
- to make copies only to the extent necessary for operation; this includes backups (section 12.3, Annex 3).
Contact for data protection matters at the Processor: Dr. Peter Mayer, mail@aimarage.com.
8. Confidentiality and access
8.1 The processing is carried out by the Processor personally; only the Processor himself (Dr. Peter Mayer, Webservice Mayer) has administrative access to the Controller's data. Persons at the Processor who obtain access in the future to the Controller's data are bound to confidentiality beforehand unless they are under an appropriate statutory obligation of confidentiality (Art. 28(3)(b) GDPR, § 6 DSG); the obligation continues after their activity ends. They process the data only on the Controller's instructions unless required to do so by Union or Member State law (Art. 29, 32(4) GDPR). The Processor keeps confidential all data and information of the Controller that becomes known to it in the course of the engagement, including where it is subject to professional secrecy of the Controller; this obligation continues after the end of the contract.
8.2 As operator, the Processor has technical access to the Controller's data. It accesses the data only if the Controller requests it (e.g. in a support request), to the extent necessary for troubleshooting or preventing misuse, or where legally required. The operator view of the Service shows only administrative data (workspace, plan, consumption), no project content, and is accessible only with a passkey. Access via the server or database is currently not logged automatically; on request, the Processor states whether and on what occasion it has accessed the Controller's project content.
8.3 Otherwise, only the Controller and the team members, client links and programs authorised by it have access to the projects, within the scope of the rights granted.
8.4 If a data subject or a third party requests data from the Controller's projects from the Processor, the Processor does not provide any information but proceeds in accordance with section 11.2.
9. Technical and organisational measures
9.1 Taking into account the state of the art, the costs of implementation, the nature, scope, context and purposes of processing and the risk to the rights and freedoms of data subjects, the Processor takes appropriate technical and organisational measures (Art. 32 GDPR). They are described in Annex 3.
9.2 The measures may be adapted to technical progress provided the level of protection does not decrease. Material changes are documented in an updated Annex 3 and made available to the Controller.
9.3 If the Controller carries out a data protection impact assessment or consults the supervisory authority (Art. 35, 36 GDPR), the Processor assists it, taking into account the nature of processing and the information available to it, in particular with information on the processing, the sub-processors (Annex 2) and the measures (Annex 3).
10. Sub-processors
10.1 The Controller grants general authorisation to engage sub-processors (Art. 28(2) GDPR). The sub-processors engaged at conclusion are listed exhaustively in Annex 2 and are deemed approved.
10.2 Notice of changes: The Processor informs the Controller of any intended addition or replacement of a sub-processor at least four weeks in advance by email to the address of the workspace owner. The Controller may object in text form on data protection grounds within this period. If no agreement is reached, the Controller may terminate the Main Contract with effect from the date the change takes effect. If no objection is made, the change is deemed approved. A new sub-processor does not receive any of the Controller's data before this period has expired. If a sub-processor fails or its further use is not justifiable due to a security incident, the Processor, until the period expires, only switches to a provider already approved in Annex 2, provided this complies with the Controller's settings, or temporarily suspends the affected function. The Controller is informed of this without delay.
10.3 The Processor contractually imposes on each sub-processor the same data protection obligations as set out in this agreement, in particular sufficient guarantees of appropriate technical and organisational measures (Art. 28(4), first sentence, GDPR). For providers with uniform contract terms, a data processing agreement meeting these requirements is sufficient. If a sub-processor fails to fulfil its obligations, the Processor remains liable to the Controller (Art. 28(4), second sentence, GDPR).
10.4 Service providers that do not process data within the meaning of this agreement are not sub-processors, in particular the payment provider Stripe (receives only contract and payment data of the Controller under the Processor's own responsibility) and telecommunications providers, as well as the recipients and AI providers connected by the Controller under sections 3.5 and 3.6.
11. Assistance with data subject rights
11.1 Taking into account the nature of processing, the Processor assists the Controller, as far as possible, with appropriate technical and organisational measures in responding to requests from data subjects (Art. 12 to 22 GDPR, Art. 28(3)(e) GDPR).
11.2 If a data subject contacts the Processor directly, the Processor forwards the request to the Controller without delay, where attribution is possible, and does not respond itself except on the Controller's instruction.
11.3 The Controller can view, rectify and delete the data of its projects in the Service itself.
11.4 In addition, the Processor deletes individual content within 14 days at the Controller's request in text form.
11.5 The owner of the workspace can export the data itself at any time in a common, machine-readable format (ZIP with JSON files and the uploaded files in their original format, Terms clause 15.1).
11.6 For assistance going beyond the functions available in the Service and not caused by a breach by the Processor, reasonable remuneration may be agreed.
12. Deletion and return
12.1 Deleting a project: If the Controller deletes individual content or a project in the Service, they are removed immediately and permanently from the database and file storage, in the case of a project including all associated drafts, tasks, emails, contacts, documents, media and conversation histories. Only a record that and when a project was deleted remains, without content. If a user deletes their user account, it is deleted immediately; workspaces in which they are the only member are deleted under section 12.2.
12.2 End of contract, return or deletion: After the end of the Main Contract, the Controller may choose between return and deletion of the personal data processed on its behalf (Art. 28(3)(g) GDPR). Return takes place by the Controller downloading the data via the export function of the Service for another 30 days (format see Terms clause 15). After these 30 days, the Processor deletes all personal data of the workspace processed on behalf of the Controller, including files and remaining copies, unless Union or Member State law requires storage. On the Controller's instruction in text form, it deletes the data before the 30 days have expired. The same applies if the Controller deletes the workspace in the Service; the workspace is then blocked immediately. Seven days before final deletion, the Processor informs the owner by email so that they can export the data in good time.
12.3 Backups: The database and the file storage are backed up daily in encrypted form (Annex 3). The backups of the last 7 days and one for each of the last 4 weeks are kept, older ones are deleted automatically; the additional database backup on the server is deleted after 14 days. Deleted data is therefore no longer contained in any backup about 5 weeks after its deletion at the latest. Restoration takes place only to remedy disruptions; data deleted since the time of the backup is deleted again afterwards and not put back into operation. If the Processor changes the backup concept, section 9.2 applies; a longer retention is announced in advance in Annex 3.
12.4 Content published on connected accounts and messages sent to third parties are outside the Processor's control and are not covered by this deletion. When the workspace is finally deleted (section 12.2), the Processor disconnects all of the workspace's accounts at the posting service Zernio (Annex 2 No. 4) and deletes its profile; when a project is deleted, it disconnects the accounts connected there that no other project uses. If this fails because of a disruption at Zernio, it is retried automatically.
12.5 The Processor confirms deletion in text form on request.
12.6 Data that the Processor processes as an independent controller (contract, account and billing data of the Controller) is not covered by this section; statutory retention periods apply to it.
13. Notification of personal data breaches
13.1 The Processor notifies the Controller of a personal data breach affecting the Controller's data without undue delay, at the latest within 48 hours of becoming aware of it, by email to the address of the workspace owner (Art. 33(2) GDPR).
13.2 The notification contains, as far as known, a description of the nature of the breach including the categories and approximate number of data subjects and records concerned, the contact details of a contact point, the likely consequences and the measures taken or proposed. Missing information is provided without delay.
13.3 The Processor takes the necessary measures without delay to secure the data and mitigate possible consequences. Notification of the supervisory authority and communication to data subjects (Art. 33, 34 GDPR) are the responsibility of the Controller; the Processor assists.
14. Audit rights
14.1 The Controller is entitled to verify compliance with this agreement (Art. 28(3)(h) GDPR). Evidence is primarily provided through information from the Processor, the current Annex 3 and documentation of the sub-processors (data processing agreements, certificates).
14.2 If the Controller considers this evidence insufficient in an individual case, it may carry out audits, including inspections, itself or through an independent auditor bound to confidentiality who is not a competitor of the Processor. Audits are generally to be announced at least 14 days in advance, take place during normal business hours and must not disproportionately affect operations or the confidentiality of other customers' data. In the case of a justified suspicion of a breach of this agreement, after a personal data breach or where a supervisory authority requires it, a reasonable shorter notice is sufficient.
14.3 For sub-processors, control takes place primarily via their audit reports, certificates and information. If these are insufficient in an individual case, the Processor obtains further information or exercises the control rights it has vis-a-vis the sub-processor on behalf of the Controller, or enables the Controller to exercise them, insofar as the contract with the sub-processor permits.
14.4 Each Party bears its own costs. If the Processor's effort exceeds one working day per contract year, it may request reasonable remuneration, which it states before the audit. No remuneration is due if the audit reveals a breach by the Processor of this agreement or of data protection law, or if it is required by a supervisory authority.
15. Liability
Liability is governed by Art. 82 GDPR and the statutory provisions. This agreement contains no separate limitation of liability.
16. Final provisions
16.1 The Processor may amend this agreement where necessary due to changes in law, regulatory requirements, a change of sub-processors (section 10.2) or of the measures (section 9.2). Changes are communicated by email to the address of the workspace owner at least four weeks before they take effect; if the Controller does not object within this period, they are deemed accepted. The notice will point out this consequence. If the Controller objects, the previous version continues to apply; if continuing on the previous version is unreasonable for the Processor (e.g. because it would violate amended legislation), either Party may terminate the Main Contract with effect from the date the change takes effect; prepaid fees are refunded pro rata. Section 10.2 takes precedence for changes of sub-processors. The Service may also ask the owner after login to accept a new version; the acceptance is stored with person, time and version. The level of protection must not decrease as a result of changes.
16.2 Should individual provisions be invalid, the validity of the remaining provisions remains unaffected. They are replaced by the requirements of Art. 28 GDPR and otherwise applicable law.
16.3 Austrian law applies, excluding conflict-of-law rules and the UN Convention on Contracts for the International Sale of Goods. The place of jurisdiction is Vöcklabruck, unless mandatory statutory provisions provide otherwise.
16.4 Annexes: Annex 1 Service description (summary); Annex 2 Sub-processors; Annex 3 Technical and organisational measures; Annex 4 Sources.
Annex 1: Service description (summary)
- Project knowledge: retrieving the website specified by the Controller, uploading documents and media, project profile, goals, strategy and rules. Personal data: data contained in the Controller's content.
- Drafts and chat: creating posts, articles, replies and strategies with the language model (Annex 2 No. 2), conversation with the agent, also by voice input if the Controller stores its own Mistral key (section 3.6); machine-readable labelling of AI-generated content. Personal data: task, input, required project content, generated texts.
- Research: web search with search terms derived from the project (Annex 2 No. 5), retrieval of publicly available pages. Personal data: persons named in public sources.
- Approval and publication: individual approval by users or pre-authorised approval (Terms clause 3.3), publication on behalf of the Controller via its connected accounts, directly or via the posting service (Annex 2 No. 4). Personal data: content of posts, account identifiers.
- Mailbox: retrieving emails from mailboxes connected by the Controller, reply drafts, sending only after approval as a reply. Personal data: sender, recipients, content of emails, contacts.
- Evaluation: metrics from connected accounts and services, Aimarage counter (totals only). Personal data: none, or only those contained in the platforms' metrics.
- Collaboration: team members, client links, interfaces (MCP, API) with log, daily email, push notifications to the iPhone app (Annex 2 No. 6). Personal data: name, email address, role, actions.
- Consumption recording: type of task, model, token counts, cost, time, without content.
Annex 2: Sub-processors
The Processor gives notice of changes to this list under section 10.2 at least four weeks in advance by email.
- Hetzner Online GmbH, Industriestr. 25, 91710 Gunzenhausen, Germany - hosting of server and database, file storage (Object Storage, Falkenstein), backups. Location: Germany. Data: all data under section 4.
- AI provider Anthropic, Anthropic Ireland, Limited, 6th Floor, South Bank House, Barrow Street, Dublin 4, D04 TR29, Ireland, together with Anthropic, PBC, 548 Market St, PMB 90375, San Francisco, CA 94104, USA - language model Claude. Location: USA, safeguarded by standard contractual clauses (Decision (EU) 2021/914, Module 2 or 3) under the provider's data processing agreement, which forms part of its commercial terms. Under the provider's commercial terms, no use of the data for training; inputs and outputs deleted within 30 days according to the provider, except to enforce its usage policy or due to legal obligations. Data: task, input and the project content required for it, generated texts.
- Sendinblue SAS (Brevo), 106 boulevard Haussmann, 75008 Paris, France - sending system emails (e.g. login codes, team invitations). Location: storage in the EU; access by Brevo group companies and service providers in third countries (including the USA) possible, safeguarded by standard contractual clauses or the EU-US Data Privacy Framework. Data: name and email address of recipients, content of the system email; no project content.
- Zernio Software SL, Carrer de Mallorca 2A, 17230 Palamós (Girona), Spain - connecting social media accounts and publishing approved posts (separate profile per workspace). Location: database and application in London, United Kingdom (adequacy decision), media in Western Europe; some further Zernio sub-processors in the USA, safeguarded by the EU-US Data Privacy Framework or standard contractual clauses. Data: posts, media, publication times, identifiers and access tokens of connected accounts, metrics.
- Brave Software, Inc., San Francisco, USA - web search for research (Brave Search API). Location: USA, safeguarded by standard contractual clauses. Data: search terms derived from the project.
- Apple Inc., One Apple Park Way, Cupertino, CA 95014, USA - Apple Push Notification Service for notifications to the iPhone app, only if a user switches on notifications. Location: USA, transfer based on the EU-US Data Privacy Framework (adequacy decision, Art. 45 GDPR), under which Apple is certified; the contractual basis is the Apple Developer Program License Agreement (Annex 4). Data: device identifier for notifications, title of the task or number of waiting drafts.
Not on this list: the payment provider Stripe, the recipients connected by the Controller itself (sections 3.5 and 10.4), an AI provider chosen by the Controller via its own AI key (section 3.6) and services the Controller connects with its own key (e.g. Upload-Post, Bing Webmaster Tools, Google Search Console).
Annex 3: Technical and organisational measures (Art. 32 GDPR)
Date of the technical inventory: 04.11.2026. Only implemented measures are listed.
1. Confidentiality
Physical access control
- Server, database, file storage and backups are located at Hetzner Online GmbH in data centres in Germany; physical access is controlled by the hosting provider (certified to ISO/IEC 27001).
- The Processor does not operate its own servers holding the Controller's data.
System access control
- Login without a password: by passkey (WebAuthn with user verification, bound to the Service's domain) or by a six-digit one-time code sent to the stored email address.
- One-time codes are valid for 10 minutes, locked after 5 failed attempts and stored only as an HMAC hash; a new code invalidates older ones.
- Limits on login and registration attempts per email address and per IP address (stored as a hash).
- Session keys are stored only as a hash; session cookie with HttpOnly, Secure and SameSite=Lax; new session on every login and every workspace switch; users can view and end active sessions.
- Re-confirmation (step-up) before sensitive actions such as changing the email address.
- Server access only via SSH key, password login disabled.
Data access control
- Roles per workspace (owner, admin, member, viewer) and permissions per project; every interface checks authorisation on the server.
- Interface keys (MCP, API) are stored only as a hash, expire (default 90 days) and can be restricted to permissions and projects; exporting the data is only possible for the owner after re-confirmation.
- Main switch for publishing and sending, switched off for new workspaces; sending only after approval.
- Operator view only for registered operators and only with a passkey; it shows no project content.
- Credentials for connected accounts and mailboxes and API keys are stored encrypted with AES-256-GCM; the key is kept separately from the database.
- Application credentials are not stored in the source code repository, only in configuration files on the server.
Separation control (tenant separation)
- All data is assigned to a workspace; queries filter on the server by the session's workspace.
- Files are stored with the workspace as prefix.
- Automated tests check that interfaces do not grant access with foreign identifiers.
- Separate environments and databases for development and production.
- Fair processing of background tasks per workspace.
Data minimisation
- No analytics, tracking or advertising cookies, no third-party captcha, no externally loaded fonts.
- Consent records and misuse protection store IP addresses only as a hash.
- The log of MCP and API calls stores IP addresses only in shortened form and no content.
- Push notifications to the iPhone app contain only the title of a task or the number of waiting drafts.
- AI consumption logs contain no content, only type of task, model, token counts and cost.
- The counter stores no IP addresses, identifiers or cookies, only aggregated figures.
2. Integrity
- Transmission between browser and server exclusively via HTTPS (TLS) with HTTP Strict Transport Security; transmission to sub-processors encrypted.
- Protection against requests to internal networks when retrieving websites and connecting mailboxes (SSRF protection).
- Notifications from the payment provider (webhooks) are verified by signature and processed only once.
- Time and version of consents are stored; approvals and agent actions are logged.
3. Availability, resilience and recovery
- Daily backup (03:30) of the database (pg_dump), the files from the Object Storage, the data directories and the configuration with restic, encrypted (AES-256) before upload, to a separate private bucket in Hetzner Object Storage in Falkenstein, Germany. Retention: 7 daily and 4 weekly states, older ones are deleted automatically (about 5 weeks at most). The key is held only on the server and by the operator.
- In addition, a daily database backup to a separate directory on the server, readable only by the operating user; automatic deletion after 14 days.
- Files (media, documents) are stored in Hetzner Object Storage in Falkenstein, Germany, in a private bucket.
- Failed backups are reported to the operator automatically; restoration can be tested with a check script in an isolated environment.
- Automatic restart of services after failures; limit on parallel background tasks.
- Deployment of new versions separately for development and production, rollback to the previous version possible.
4. Deletion
- Real deletion: deleting content and projects removes the data immediately from the database and file storage, not merely marking it as deleted.
- Deleted workspaces and workspaces after the end of the contract are blocked immediately and permanently removed including files after 30 days; the owner receives an email 7 days beforehand, and export is possible until then. Completed exports are deleted after 7 days.
- One-time codes, expired sessions and login counters are deleted automatically on a regular basis; the log of MCP and API calls after 90 days.
- Backups are deleted automatically after about 5 weeks at most, the database backups on the server after 14 days.
- Logs of the services (application, background worker, web server, database) and the list of error messages are deleted automatically after no more than 14 days; the web server writes no access logs.
5. Review and privacy by default (Art. 25, Art. 32(1)(d) GDPR)
- Security review of the source code before deploying material changes; automated tests.
- Privacy-friendly defaults: outbound sending switched off (main switch), individual approval per channel as default, AI reviewer switched off for new workspaces; automatic approvals only with an objection period and daily limit.
Annex 4: Sources
Contract terms of the sub-processors, kept on file by the Processor with the date of acceptance:
- Hetzner Online GmbH: data processing agreement of 29.10.2026, concluded in the customer account (accounts.hetzner.com/account/dpa).
- Anthropic: Commercial Terms (effective 17.06.2025) with Data Processing Addendum (anthropic.com/legal/commercial-terms, anthropic.com/legal/data-processing-addendum); "Anthropic may not train models on Customer Content from Services".
- Brevo: terms of use with data processing agreement as an annex (brevo.com/legal/termsofuse).
- Zernio: Data Processing Agreement, version 19.10.2026 (zernio.com/dpa), list of sub-processors (zernio.com/subprocessors).
- Brave: Data Processing Addendum of the Brave Search API from the Trust Center (trust.brave.app/resources).
- Stripe (not a sub-processor, section 10.4): Data Processing Agreement (stripe.com/legal/dpa).
- Apple: Apple Developer Program License Agreement (developer.apple.com/support/terms).