GDPR-compliant Git hosting
with the paperwork in public.
Give security and privacy reviewers concrete answers about where repositories live, who processes them, and what the contract says.
CodeTrunk is operated by a Dutch company on EU infrastructure. Repositories, collaboration data, and backups remain in the European Union, and the DPA and infrastructure details are available before signup.
GDPR-compliant Git hosting
EU jurisdiction from the start
The provider, primary infrastructure, and backups are European. EU data protection law applies directly rather than through a transfer framework or a region setting inside a global cloud.
A DPA you can read first
Business and Enterprise plans include a data processing agreement covering processor obligations, subprocessors, retention, deletion, and breach notification.
Subprocessors are documented
The infrastructure page identifies the hosting, backup, email, and payment providers involved in operating the service, including their roles and locations.
The details behind the summary
The decisions, definitions, and trade-offs that a short guide cannot show.
Controller, processor, and subprocessor
Under the GDPR, your organisation is usually the controller and CodeTrunk is the processor. That distinction decides who answers a data subject request, who signs the DPA, and who is liable when something goes wrong. A subprocessor is a third party the processor uses, such as the hosting or email provider. The DPA and infrastructure page should name them, describe their role, and explain how changes are announced.
Data residency is not jurisdiction
Storing data in an EU datacenter is not the same as being subject to EU law. A US parent company, a US cloud provider, or a support team outside the EU can still create a transfer or a disclosure path. The stronger claim is a European legal entity, EU infrastructure, and no US parent in the chain. That is why the contracting entity matters as much as the region dropdown.
What a DPA should answer
A DPA is useful when it is specific: the subject matter, duration, nature and purpose of processing, the categories of data, the subprocessors, the security measures, the deletion and return terms, and the breach notification window. A one-page document that repeats the GDPR articles is not a substitute. Read the DPA before you sign up, not after procurement asks for it.
Backups, deletion, and retention
The GDPR does not require instant deletion from every backup, but it does require a defined retention period and a process that eventually removes the data. Ask how long backups are kept, how a deletion request propagates, and what happens to logs. The answer should be in the DPA or a public retention policy, with a named owner.
The documents to request
At minimum: the DPA, the subprocessor list, the infrastructure description, the privacy policy, and the security measures. For a larger buyer, add the penetration test summary, the incident response process, and the data processing register. If a provider cannot produce these before signature, that is the finding.
Frequently asked questions
Is CodeTrunk GDPR compliant?
The service is designed and operated for GDPR compliance: data is hosted in the EU, a DPA is available for Business and Enterprise customers, and processing details are documented publicly.
Is a DPA included?
A DPA is included with the Business and Enterprise plans and is available to review before signup.
Is a DPA enough to make us GDPR compliant?
No. A DPA is one piece of the puzzle. Your organisation still needs a lawful basis, a record of processing, appropriate security, and a process for data subject requests. The DPA tells you what the processor does and how it helps you meet those obligations; it does not transfer your accountability.
How long are backups retained?
The DPA and privacy policy define the retention window and the deletion process. Backups rotate on a schedule rather than being deleted instantly, so a deletion request propagates as the backup set ages out. Ask for the current window before you sign, especially if your own retention policy is stricter.
Are repositories transferred outside the EU?
No repository data is stored or replicated outside the EU or EEA. The privacy and infrastructure pages document the limited non-repository hash-prefix security check separately.
Sources and further reading
Primary sources for the claims in this guide, last checked 20 October 2026. Product terms change; check the source before you decide.
-
Regulation (EU) 2016/679 (GDPR)
EUR-Lex · The full legal text
-
Guidelines 07/2020 on controller and processor
EDPB · Who is controller, processor, or subprocessor
-
EU-US Data Privacy Framework
European Commission · The transfer framework and its limits
-
Data protection in the EU
European Commission · The rules, rights, and enforcement
Keep exploring
Start with the plan that fits.
Create an account with no credit card. Upgrade when your repositories or team need more.
Start Building