Discovery queue open Typical turnaround: one working day The register Method Talk to a reviewer
subprocessor.org
Have us do it →

discovery

Find your sub-processorssix sources, read for youRead your own listsCSV, DPA or procurementDecide the scopewhat touches customer data

publish

Your register pagecurrent to the dayEmbed on your siteor in your trust centreCustomer noticessent in your name

prove

Evidence packsdated and exportableDecision logaccepted, objected, escalatedLedger verificationhash-chained record
and later
Watch your vendors too

Every vendor found in your discovery, monitored daily.

See monitoring →
Six sources. One reviewed list. Re-checked daily.See how the work flows →

by role

In-house privacyyou signed the DPAsGRC & securityyou answer the auditorDPO firmsyou carry it for clients

by situation

Selling into the EUyour first Article 28 annexFinancial servicesDORA subcontracting chains100+ SaaS vendorstoo many to watch by hand

by stage

First DPA annexget it right first timeScaling privacy teamretire the spreadsheetMulti-client practiceone workspace each
for dpo firms
One workspace per client

Cross-client rollups, white-labelled exports, reseller terms.

Compare tiers →
Same engine, different job to be done.Compare the tiers →

european union

GDPR Article 28notice and objection windowsEDPB Opinion 22/2024what “current” now meansDORAregister of informationNIS2supply-chain duties

transfers & elsewhere

SCCs & transferswhere each entity processesUK GDPRsame duty, own regulatorCCPA / CPRAservice provider duties

what we publish

Our methodhow detection worksFalse-positive policywhy we stay quietCoverage and gapswhat we cannot reach yet
annual cycle
The DORA register window

Subcontracting chains, produced as a by-product of discovery.

Talk about DORA →
We publish observations and dated records, never legal conclusions.Read the method →

browse, free

All businesses1,284 with a dated historyLive changesevery list that movedSub-processor indexwho is named, by whom

go deeper

By countrywhere processing happensFourth-party chainsyour suppliers’ suppliersCoverage and gapswhat we cannot reach yet

if you are listed

Claim your pageverify and take it overSuggest a correctionwe log every onePublishing guidehow to keep it right
free to read
No account needed

The register stays open whether or not you buy anything.

Open the register →
Free to read. No account.Open the register →

Sub-processor index › Measures to be taken by third-party sub-processors

Measures to be taken by third-party sub-processors

Named on 1 published list. This is a record of who names them, not a statement about the company itself.

named by 1
0 countries

Named by

1
twilio.com Where Twilio engages a sub-processor under Section 6.1 (Authorization for Sub-Processing), Twilio and the sub-processor enter into an agreement with data protection obligations substantially similar to those set forth in this Addendum. Each sub-processor agreement must ensure that Twilio is able to meet its obligations to Customer. In addition to implementing technical and organizational measures to protect personal data, sub-processors must (a) notify Twilio in the event of a Security Incident, so Twilio may notify Customer; (b) delete personal data where instructed by Twilio in accordance with Customer’s instructions to Twilio; (c) not engage additional sub-processors without Twilio’s authorization; (d) not change the location where personal data is processed; or (e) not process personal data in a manner which conflicts with Customer’s instructions to Twilio. v1