RoPA Pilot

Paddle and GDPR: hosting, non-EU transfer and DPA

Paddle is published by Paddle.com Market Ltd. If your teams use it, it is a processor within the meaning of Article 28 GDPR and it must appear in your record of processing activities.

Vendor (processor)
Paddle.com Market Ltd
Headquarters
United Kingdom
EU hosting
EU optional (plan/config)
Non-EU transfer
Yes
Transfer mechanism
Adequate country
Category
Payments
Typical personal data
identity, contact details, financial data
Detected domains
vendors.paddle.com, paddle.com

Does using Paddle mean a non-EU transfer?

Yes, but to a country covered by an adequacy decision (United Kingdom): no additional safeguard is required, the destination country must still be named in your register.

What to write in your Article 30 record

Purpose: Payments. Categories of personal data: identity, contact details, financial data. Recipient: Paddle.com Market Ltd. Transfer: Adequate country. Retention: aligned with the contract or the account lifetime, whichever is shorter.

How RoPA Pilot handles it

RoPA Pilot detects Paddle from the domain name of the tab — never from page content — and pre-fills the record above in one click. The extension flags the record if the transfer mechanism is missing or unverified.

Indicative information from public sources. The transfer mechanism actually applicable to you is the one written in your contract.