RoPA Pilot

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

Outreach is published by Outreach Corporation. 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)
Outreach Corporation
Headquarters
United States
EU hosting
Non-EU
Non-EU transfer
Yes
Transfer mechanism
United States — EU-US DPF
Category
CRM / Sales
Typical personal data
identity, contact details, professional data, usage data
Detected domains
outreach.io

Does using Outreach mean a non-EU transfer?

Yes. Outreach Corporation is a US vendor listed under the EU-US Data Privacy Framework: the transfer is lawful as long as the certification is active — check it on dataprivacyframework.gov and record the date of your check.

What to write in your Article 30 record

Purpose: CRM / Sales. Categories of personal data: identity, contact details, professional data, usage data. Recipient: Outreach Corporation. Transfer: United States — EU-US DPF. Retention: aligned with the contract or the account lifetime, whichever is shorter.

How RoPA Pilot handles it

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