RoPA Pilot

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

Sage is published by Sage Group plc. 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)
Sage Group plc
Headquarters
United Kingdom
EU hosting
EU optional (plan/config)
Non-EU transfer
Yes
Transfer mechanism
Adequate country
Category
Accounting
Typical personal data
identity, contact details, financial data, HR data
Detected domains
sage.com, sageone.com

Does using Sage 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: Accounting. Categories of personal data: identity, contact details, financial data, HR data. Recipient: Sage Group plc. Transfer: Adequate country. Retention: aligned with the contract or the account lifetime, whichever is shorter.

How RoPA Pilot handles it

RoPA Pilot detects Sage 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.