Data processing agreement
Last updated: 9 October 2026
1. Parties and scope
This data processing agreement ("DPA") is between the customer that accepts the Euthyne terms of service (the "customer", as controller) and Maxime Mansiet EI, 22 avenue Victor Hugo, 33120 Arcachon, France, SIREN 941 572 364, trading as Euthyne ("Euthyne", as processor). It forms part of the terms and applies to personal data Euthyne processes on the customer's behalf to provide the service ("customer personal data").
If the customer is itself a processor for a third party, Euthyne acts as its subprocessor and this DPA applies in the same way. Terms such as controller, processor, personal data, processing and personal data breach have the meaning given in Regulation (EU) 2016/679 ("GDPR").
Euthyne is the controller, not the processor, of the data it needs to run its own business, such as account sign-in, billing, support and security logs. Its privacy policy covers that data.
2. Subject matter and duration
Euthyne processes customer personal data to provide the service described in the terms. Processing lasts for the term of the terms and until the data is deleted or returned under section 11.
3. Nature and purpose of the processing
Euthyne receives signed receipts from the euthyne command-line tool and data from the customer's git host, verifies and stores them, links agent sessions to merged changes, displays them in the dashboard and verify pages, exports them, and deletes them. It does so for the sole purpose of letting the customer record, review and prove the work done by coding agents in its organization, and of supporting and securing that service.
4. Data subjects
- the customer's members: developers, reviewers, administrators and owners of its Euthyne organization
- auditors the customer invites
- people who appear in the customer's git host data, such as authors, committers, reviewers and mergers of pull requests, including people outside the customer's organization
5. Categories of personal data
- git host identifiers: user ID, username and email address, organization membership and role in Euthyne
- device data: device name, public key and fingerprint, the credential binding that key to a person and organization, status and revocation history
- receipt metadata: agent tool and version, model, the user ID of the person who ran the agent, repository, branch, commits, tool names, file paths, timestamps and outcomes
- change records: pull request numbers, authors, mergers, reviewers and review states, continuous integration results, and agent markers read from commit metadata, including author names and email addresses
- salted hashes of prompts, tool inputs and outputs, commands, file contents and diffs, computed on the customer's machines with a key Euthyne never receives
- if the customer turns on command retention: commands and tool arguments, redacted on the device before they are sent, which may still contain personal data
- auditor invitation email addresses, API key names and usage dates, and IP addresses used for rate limiting
The service is not designed to process special categories of personal data. The customer must not send them in clear, for example through retained commands.
6. Instructions
Euthyne processes customer personal data only on the customer's documented instructions. The terms, this DPA and the settings the customer chooses in the service are those instructions. Further instructions must be in writing and consistent with the terms. Euthyne will tell the customer if, in its opinion, an instruction infringes data protection law. If European Union or Member State law requires Euthyne to process customer personal data otherwise, Euthyne will tell the customer before processing, unless that law forbids it.
7. Confidentiality
Euthyne gives access to customer personal data only to people who need it to provide, support or secure the service, and who are bound by confidentiality.
8. Security
Euthyne implements the technical and organizational measures in the annex below, taking into account the state of the art, the cost of implementation and the risks of the processing (GDPR art. 32). It may update them, provided the overall level of protection does not decrease.
9. Subprocessors
The customer gives Euthyne general authorization to use subprocessors. The current list is on the subprocessors page.
- Euthyne will tell the owners of the customer's organization by email at least 30 days before a new subprocessor starts processing customer personal data, and update the list.
- The customer may object on reasonable data protection grounds within that period. The parties will then discuss it in good faith. If they find no solution, the customer may terminate the affected service and receive a refund of prepaid fees for the period after termination.
- Euthyne imposes on each subprocessor data protection obligations that offer the same level of protection as this DPA, and remains liable to the customer for its subprocessors.
10. Assistance
Taking into account the nature of the processing and the information available to it, Euthyne helps the customer:
- answer requests from data subjects exercising their rights, through the service's features (removing members, export, deletion) and, where needed, on request. Euthyne forwards to the customer, without undue delay, any request it receives about customer personal data, and does not answer it itself unless the customer asks it to.
- meet its obligations on security, breach notification, data protection impact assessments and prior consultation (GDPR art. 32 to 36), for example by describing how the service works and what it records.
11. Personal data breaches
Euthyne will notify the customer without undue delay, and where possible within 48 hours, after becoming aware of a personal data breach affecting customer personal data. The notice will give, as far as they are known, the nature of the breach, the categories and approximate number of data subjects and records concerned, the likely consequences, the measures taken or proposed, and a contact point. Euthyne will provide further information as it becomes available and take reasonable steps to contain the breach and limit its effects.
12. Deletion and return
During the term, the customer can export and delete its data using the service. When the terms end, the customer can ask for an export within 30 days. Euthyne then deletes customer personal data from its systems within 30 more days, and from backups as they expire, unless European Union or Member State law requires it to keep the data.
Deletion removes personal data fields and receipt contents from Euthyne's database. The customer acknowledges that each receipt also adds a hash to Euthyne's public, append-only transparency log, its public mirror and its timestamps. Those hashes contain no personal data in clear, cannot be removed without breaking the log, and remain after deletion without pointing to any record Euthyne holds.
13. Audits
Euthyne makes available to the customer the information needed to demonstrate compliance with GDPR article 28, including this DPA, the annex and answers to reasonable security questionnaires. If that is not enough, the customer, or an independent auditor bound by confidentiality, may audit Euthyne once a year, or after a personal data breach or at the request of a supervisory authority. The customer gives at least 30 days' written notice, bears the cost of the audit, and the audit is conducted during business hours without access to other customers' data or disrupting the service.
14. Transfers outside the European Economic Area
Euthyne hosts customer personal data in the European Union (Germany). A subprocessor may process some customer personal data outside the European Economic Area, as shown on the subprocessors page. Euthyne makes such transfers only with a safeguard required by chapter V of the GDPR, such as an adequacy decision, including the EU-US Data Privacy Framework for certified providers, or the European Commission's standard contractual clauses.
15. Customer obligations
- The customer has a lawful basis for the processing it instructs, and informs data subjects about it.
- The customer informs its members and, where required, consults employee representatives before it uses Euthyne to record who launched or approved agent work.
- The customer decides which verify links to share, which repositories to make public, and whether to turn on command retention, and is responsible for those choices.
16. Liability and precedence
Each party's liability under this DPA is subject to the limits in the terms, to the extent the law allows. If this DPA conflicts with the terms, this DPA prevails on the protection of personal data.
Annex: security measures
Data minimization by design
- Prompts, tool inputs and outputs, commands, file contents and diffs are committed as salted SHA-256 hashes on the customer's machine. The salts derive from a commitment key that stays in the device keychain, so Euthyne cannot recover the hashed content.
- Euthyne does not store source code or file contents, only file paths, commit identifiers and hashes.
- Command retention is off by default. When an organization turns it on, commands and tool arguments are redacted on the device before signing and encrypted at rest.
- An automated test checks that marker secrets in test inputs never reach the local queue or upload requests.
Keys and integrity
- Each device signs receipts with an Ed25519 key held in the operating system keychain. Private keys never leave the device.
- Key rotation and revocation are recorded in the transparency log, so a revoked key can no longer sign valid receipts.
- Receipts are added to an append-only transparency log with signed checkpoints, timestamped through OpenTimestamps and mirrored off the server, so later changes to a record are detectable.
- Euthyne's log and service signing keys are separate from each other, held as server secrets and backed up offline.
Access control and tenant isolation
- Members sign in through GitHub or GitLab. Each organization has owner, admin and member roles.
- Every query for customer data is scoped to the requesting organization.
- API keys are scoped (read, export, admin), bound to one organization, can expire, can be revoked, and are stored only as SHA-256 hashes. They are shown once, when created.
- Verify links use random 128-bit identifiers that cannot be enumerated, and are not public unless the customer chooses.
- Auditor access is limited to the repositories and period the customer chooses.
Network and infrastructure
- Traffic to the service is encrypted with TLS. Plain HTTP requests are redirected to HTTPS.
- Git host webhooks are authenticated by signature and deduplicated.
- Rate limits apply per device, per API key and per IP address on public endpoints.
- The service runs on a server operated by Euthyne in Hetzner's data center in Nuremberg, Germany. The database is not exposed to the internet.
- The GitHub integration requests read access to the minimum it needs, and the client is restricted to a published list of endpoints that excludes file contents.
Deletion
- Erasure clears personal data fields and deletes receipt contents, leaving only a hash in the transparency log that no longer points to any record.