PaymentsCheckout.com and the GDPR: agreement, role and data location.
Checkout.com is a payments tool. Its role depends on the activity, it publishes its data processing agreement, and the data location depends on your account. Below: what to check and how to declare it.
Prefilled for you · Free to set up · No credit card
In short
- Category
- Payments
- Usual role
- Depends on the activity
- Data location
- Set per account or project
- Agreement
- Published by the vendor
What does Checkout.com do with personal data?
Manage customer payments, subscriptions where applicable, invoicing and billing. That is how Privacyboard describes a typical use of Checkout.com, as a starting point you can edit.
The data usually involved: customer names, email addresses, billing addresses, transaction identifiers and payment information handled by the provider.
Is Checkout.com a processor or a controller?
Checkout.com acts as acquirer/payment processor and is often an independent controller for transaction data, with processor terms for some data.
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 Checkout.com store personal data?
Checkout.com does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable.
How to find yours: Check your account settings or Checkout.com’s data processing terms for where your data is stored.
Even when the main location is in the EU, ask whether subprocessors or support access involve a transfer outside the EEA, and record it if so.
Does Checkout.com have a data processing agreement?
Checked on 1 November 2026. Vendors change their pages, so check the date.
Yes. Checkout.com publishes the text of its data processing agreement 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: Service Terms with a section E 'Data Protection Terms' plus annexes on processing details and security. No date or contracting entity visible in the part read; no storage location stated. Sub-processors referenced on its trust site.
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 Checkout.com agreementHow to declare Checkout.com
- 1
In your privacy policy
Name Checkout.com as a recipient, say what it is used for (manage customer payments, subscriptions where applicable, invoicing and billing) 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 Checkout.com 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 Checkout.com 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 Checkout.com
- Work out whether the provider acts as your processor, as an independent controller, or as both for different activities.
- Say in your privacy policy that payment data is handled by the provider and for what purpose.
- Record the provider as a recipient of customer names, emails and transaction data.
- Check retention rules the provider applies for legal and fraud reasons.
Questions, answered.
Is Checkout.com GDPR compliant?
Privacyboard does not certify vendors. Compliance depends on how Checkout.com 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 Checkout.com have a DPA?
Yes. Checkout.com publishes the text of its data processing agreement 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.checkout.com/legal/service-terms.
Is Checkout.com a data processor?
It depends on the activity. Checkout.com acts as acquirer/payment processor and is often an independent controller for transaction data, with processor terms for some data.
Where does Checkout.com store data?
Checkout.com does not have one fixed location for every customer. The location depends on the plan, the account and the services you enable. How to find yours: Check your account settings or Checkout.com’s data processing terms for where your data is stored.
Do I need to mention Checkout.com in my privacy policy?
Yes, if Checkout.com 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 Checkout.com to my vendor list?
In Privacyboard, pick Checkout.com 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.
Privacyboard is not affiliated with Checkout.com. 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.