DevelopmentDocker Hub and the GDPR: agreement, role and data location.
Docker Hub is a development tool. Its role depends on the activity, it publishes its data processing agreement, and it usually keeps data in United States. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Development
- Usual role
- Depends on the activity
- Data location
- Usually United States
- Agreement
- Published by the vendor
What does Docker Hub do with personal data?
Manage source code, software development and deployment workflows. That is how Privacyboard describes a typical use of Docker Hub, as a starting point you can edit.
The data usually involved: developer names, work email addresses, contribution metadata and information included in repositories or issues.
Is Docker Hub a processor or a controller?
Docker states it acts as controller for some data, such as billing, legal compliance and cloud security.
Privacyboard does not prefill a role for this vendor on purpose. You are asked to choose, since the answer changes what your privacy policy says and which agreement matters.
Where does Docker Hub store personal data?
Docker Hub usually keeps data in United States for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs.
What Docker Hub says (read on 2026-11-05): Docker Hub hosting is only available in the United States (paraphrase) Source: https://www.docker.com/trust/privacy/
How to find yours: Check your account settings, the address you log in to, or the provider’s data processing terms. Support can tell you if you cannot find it.
If the data is processed outside the European Economic Area, Articles 44 to 49 require a transfer mechanism, such as standard contractual clauses, an adequacy decision or the EU-US Data Privacy Framework. Your privacy policy should name it.
Which legal basis usually applies to Docker Hub?
For the usual use of Docker Hub, companies most often rely on legitimate interests (GDPR Article 6(1)). Source code and deployment tools are needed to build and run the product.
The interest you would state: “Building, testing and deploying our software efficiently and securely.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
The balancing test is yours to do: the interest must be real, the processing necessary for it, and people’s rights must not outweigh it.
This is a starting point, not legal advice: the basis belongs to your activity, and you confirm it in your register.
Sources: GDPR Article 6, lawfulness of processing, EDPB Guidelines 1/2024 on legitimate interest
Does Docker Hub have a data processing agreement?
Checked on 5 November 2026. Vendors change their pages, so check the date.
Yes. Docker Hub publishes the text of its data processing agreement as a PDF on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep.
What we noted when we opened the page: Docker Data Processing Agreement for Docker Services, last updated 31 Oct 2023, entity as stated in the main Agreement. Relies on Docker's EU-US DPF certification, with EU SCCs or UK IDTA as fallback. Trust page says Hub is hosted only in the US.
A page that exists does not mean you are covered. Whether the agreement applies to you depends on your plan and on what you accepted, so record the decision yourself in your vendor list.
Read the Docker Hub agreementHow to declare Docker Hub
- 1
In your privacy policy
Name Docker Hub as a recipient, say what it is used for (manage source code, software development and deployment workflows) and mention any transfer outside the EEA. Articles 13 and 14 ask you to tell people who receives their data.
- 2
In your vendor list
Add Docker Hub with its purpose, the data involved, its role, its region and a link to the agreement. Privacyboard prefills all of this, you confirm or correct it.
- 3
In your processing register
Link Docker Hub to the activities that use it, so each record shows its recipients. Article 30 asks the register to list the categories of recipients.
What to check before relying on Docker Hub
- Keep secrets and customer data out of repositories and issues.
- Review who has access and how departures are handled.
- Check the retention of issues, logs and deleted repositories.
- Record the provider where personal data is processed through it.
Go online for free. Grow when you need to.
Free puts you online. Pro adds requests, domains and your team; Business, your brand only.
Free
$0 forever
No card, no time limit
For getting compliant and going online on your own.
Start for freeKey features:
- Privacy and cookie policies
- Vendor and processing registers
- Requests and breaches tracked
- Impact assessment screening
- Privacy center on privacyboard.io
- Cookie banner on 1 domain
- 1 person
No card needed
ProRecommended
$32 per month
Billed $384 a year Save $84
For taking requests, covering all your sites and working as a team.
Start with ProEverything in Free, plus:
- DPA for your clients
- PDF and Excel exports
- Email reminders
- Request form and replies
- Your own domain
- Banner on 3 domains, every choice logged
- Weekly site scan
- Complete DPIAs and TIAs
- AI assistant connector
- Up to 5 people, with roles
Cancel any time
Business
$109 per month
Billed $1,308 a year Save $240
For proving it to customers and auditors, under your brand only.
Start with BusinessEverything in Pro, plus:
- No Privacyboard mention
- Security section and vendor alerts
- Evidence pack in one click
- Banner on 10 domains, daily scan
- Up to 50 people
- Two-step verification required
- Activity log kept 3 years
Bank transfer on request
Questions, answered.
Is Docker Hub GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Docker Hub is configured and used, on the agreement you have with it and on your own practices. What can be checked is documented here: it publishes a data processing agreement, the usual role and the data location. Read the agreement itself before relying on it.
Does Docker Hub have a DPA?
Yes. Docker Hub publishes the text of its data processing agreement as a PDF on its own website. Article 28 of the GDPR requires a written contract with every processor, so this is the document to read and keep. You can read it at https://www.docker.com/wp-content/uploads/2022/03/2022-Docker-EU-UK-SCC-Data-Processing-Agreement.pdf.
Is Docker Hub a data processor?
It depends on the activity. Docker states it acts as controller for some data, such as billing, legal compliance and cloud security.
Which legal basis applies when I use Docker Hub?
For the usual use of Docker Hub, companies most often rely on legitimate interests (GDPR Article 6(1)). Source code and deployment tools are needed to build and run the product. The interest you would state: “Building, testing and deploying our software efficiently and securely.” The GDPR asks you to say which interest you pursue (Article 13(1)(d)).
Where does Docker Hub store data?
Docker Hub usually keeps data in United States for every customer on its standard service, so there is normally nothing to choose. Privacyboard prefills this and you can change it if your setup differs. What Docker Hub says (read on 2026-11-05): Docker Hub hosting is only available in the United States (paraphrase) Source: https://www.docker.com/trust/privacy/
Do I need to mention Docker Hub in my privacy policy?
Yes, if Docker Hub handles personal data for you. The GDPR asks you to tell people who receives their data (Articles 13 and 14). Name the vendor or its category, say what it is used for and mention any transfer outside the EEA.
How do I add Docker Hub to my vendor list?
In Privacyboard, pick Docker Hub from the catalog. The purpose, the data, the suggested role and a link to its agreement are prefilled, and you confirm each one. Creating a workspace is free.
Similar tools
Privacyboard is not affiliated with Docker Hub. Names and logos belong to their owners and are used only to identify the tool. This page summarises public documents as checked on 1 November 2026; it is guidance, not legal advice, and it does not certify any vendor.