Data processing agreement
Last updated: October 30, 2026
This agreement covers the personal data in what your organization lets Shipmate process: messages, code, tickets and runs. It meets article 28 of the GDPR and is part of the terms of service, so it applies without a signature as soon as your organization uses Shipmate.
1.Parties and roles
The customer (the organization that uses Shipmate) is the controller. The provider of Shipmate, Alex Gillard, Roodborstlaan 3, 2660 Hoboken, enterprise number 1005.281.868, is the processor. For its own customer relationship (accounts, billing, the website) the provider is a controller itself, as the privacy policy describes.
2.What is processed
- Purpose and nature: running Shipmate for the customer: reading requests in Slack and from the Claude connector, making tickets, code changes and pull requests, answering questions, showing the work, and the notifications that go with it.
- Types of personal data: names, Slack names and IDs, email addresses and profile pictures of members and Slack users; the content of messages, tickets, code, commit and pull request texts, screenshots and logs, which can contain any personal data the customer puts in them.
- Data subjects: the customer's members, the people in its Slack workspace, and anyone named in its tickets, code or messages.
- Duration: as long as the customer uses Shipmate, and after that until the data is deleted as set out below.
3.Instructions
The processor only processes the personal data on the customer's documented instructions: these terms, the settings and connections admins choose in Shipmate, and the requests members make. It tells the customer at once if it thinks an instruction breaks data protection law. If the law requires processing the processor did not get instructions for, it tells the customer first, unless the law forbids that.
4.Confidentiality
Only people who need access to run, support or fix Shipmate can access the data, and they are bound to confidentiality.
5.Security
The processor takes appropriate technical and organizational measures (article 32 GDPR), including:
- Encryption in transit (HTTPS) and of tokens, keys and project settings at rest (AES-256-GCM).
- Access per organization and role on every request; secrets are never sent to a browser.
- Code changes run in an isolated workspace per run, with the customer's own tokens.
- Only what is needed is stored; run sessions are deleted after 365 days.
- Strong authentication for administrative access, and access for as few people as possible.
- Software kept up to date, with dependencies checked for known weaknesses.
6.Subprocessors
The customer gives general permission to use the subprocessors listed in the privacy policy (hosting, email delivery and the like). The processor tells the admins by email at least 30 days before it adds or replaces one. The customer may object for reasonable data protection reasons; if no solution is found, the customer may end the agreement and get back the unused part of what it prepaid. The processor gives each subprocessor the same data protection obligations and remains responsible for them.
The services the customer connects itself (Anthropic, Slack, GitHub, Azure DevOps, Jira, DatoCMS) are not subprocessors of the processor: the customer chooses them, has its own agreement with them, and instructs Shipmate to send them data.
7.Transfers outside the EEA
Personal data is only transferred outside the European Economic Area with a safeguard of chapter V GDPR, such as an adequacy decision or the EU Standard Contractual Clauses.
8.Helping the customer
- The processor helps the customer answer requests of data subjects (access, correction, deletion, portability, objection), mostly through the export and delete functions in Shipmate, and passes on requests it receives directly.
- It helps with data protection impact assessments and prior consultations, as far as they concern Shipmate.
- It tells the customer without undue delay, and at the latest within 48 hours after becoming aware, of a personal data breach that concerns the customer's data, with what it knows and what it does about it.
9.At the end
When the customer deletes its organization, the processor deletes the customer's data at once from Shipmate, and from backups within 30 days, unless the law requires keeping it. Before that, admins can export what they need. Invoices are not part of this agreement: the provider keeps them as the law requires.
10.Information and audits
The processor gives the customer the information needed to show it meets this agreement. The customer may have an audit done once a year, at its own cost, by an independent auditor bound to confidentiality, with 30 days' notice, without disturbing the service or other customers' data.
11.Liability and precedence
The liability rules of the terms of service apply, insofar as the GDPR allows. Where this agreement and the terms of service differ about personal data, this agreement goes first. Belgian law applies.
