Telesign: DPA, subprocessors and transfers

Links last opened 22 October 2026. Record confirmed by a person on 29 September 2026. 9 recorded changes, listed below.

Telesign contracts through Telesign Corporation, registered in United States. Transfers of personal data out of the EEA are covered by EU-US Data Privacy Framework (DPF). Its trust center is published at https://www.telesign.com/security. Its customer data processing agreement, also called a data processing addendum, is published by Telesign itself; the link is below. Its sub-processor list is published by Telesign itself; the link is below. We open those pages every day — last on 22 October 2026 — and a person last went through this record on 29 September 2026.

Contracting legal entity: Telesign Corporation
Country of registration: United States
Transfer mechanism: EU-US Data Privacy Framework (DPF)
A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope.
Data processing agreement: https://www.telesign.com/dpa
Subprocessor list: https://www.telesign.com/dpa
Security or trust page: https://www.telesign.com/security

What to put in your subprocessor list

A ready row. Replace the purpose with what your client actually uses Telesign for.

Subprocessor	Legal entity	Country	Purpose	Transfer	DPA
Telesign	Telesign Corporation	US	Communication	DPF	https://www.telesign.com/dpa

Questions people ask about Telesign

Where is Telesign's DPA?: Telesign publishes its customer data processing agreement at https://www.telesign.com/dpa. We last opened that link on 22 October 2026.
Is Telesign's DPA the same thing as a data processing addendum?: Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Telesign's is at https://www.telesign.com/dpa.
Where is Telesign's sub-processor list?: Telesign publishes the list of its own sub-processors at https://www.telesign.com/dpa. We last opened that link on 22 October 2026.
Which legal entity does Telesign contract through?: Telesign Corporation, registered in United States. That is the name to put in a record of processing or a sub-processor list, not the brand.
What covers a transfer of personal data to Telesign outside the EEA?: EU-US Data Privacy Framework (DPF). A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope. Whether that is enough for a particular processing operation is a judgement for the controller.
Where is Telesign's trust center?: Telesign publishes it at https://www.telesign.com/security. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Telesign's page, so we link to it rather than repeat what it says.

What has changed, and when

Changes we noticed on Telesign's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.

22 October 2026
I don't have enough information to write a meaningful change note. The detected facts show that 2 lines were removed, but they appear to be blank or contain only language codes (EN), without any substantive content about what changed in Telesign's data processing agreement. Please provide the actual text that was removed so I can describe what changed and why it matters.
Seen on https://www.telesign.com/dpa
21 October 2026
Telesign added new subprocessors operating in Colombia, Indonesia, India, United Kingdom, China, Serbia, and Singapore. These locations lack EU adequacy decisions, which means data transfers there require additional safeguards like Standard Contractual Clauses under the GDPR.
Seen on https://www.telesign.com/dpa
21 October 2026
Telesign's Data Processing Agreement now explicitly references standard contractual clauses and adequacy decisions as transfer mechanisms for personal data outside restricted territories. This matters because it clarifies the legal basis Telesign uses to legitimize international data transfers, which affects how you document their compliance obligations in your records of processing and subprocessor management.
Seen on https://www.telesign.com/dpa
20 October 2026
Telesign added Close as a subprocessor. The vendor's data processing agreement documentation was replaced with website error pages, removing the full list of subprocessors and detailed processing terms that should be reviewed in records of processing.
Seen on https://www.telesign.com/dpa
20 October 2026
Telesign removed its data processing agreement document that previously specified standard contractual clauses and adequacy decisions as transfer mechanisms for personal data. The vendor no longer provides documented legal transfer mechanisms for cross-border data transfers, which affects how data transfers outside restricted zones are contractually justified.
Seen on https://www.telesign.com/dpa
20 October 2026
The contracting legal entity previously identified as Telesign (a Proximus Global company) no longer appears in the current legal documentation. This affects the accuracy of the subprocessor list and record of processing, as the legal entity responsible for data processing activities may have changed.
Seen on https://www.telesign.com/dpa
2 October 2026
We recorded a change to the sub-processor list link.
30 September 2026
We recorded changes to the transfer mechanism, the UK transfer mechanism.
30 September 2026
We recorded a change to the trust or security page.

Building your own sub-processor list?

Enter your website: each service it loads, what it is for and links to its own DPA, in a minute or two. No sign-up.

Build my list

Worked out from the registry and what we have written: the country this vendor contracts from, the guides that answer the question this page raises, and the rest of the registry.

Other communication

Six of them. All communication in the registry · others that transfer the same way.

Subprocessor

Legal entity

Country

Purpose

Transfer

DPA

Telesign

Telesign Corporation

Communication

DPF

https://www.telesign.com/dpa

Questions people ask about Telesign

Where is Telesign's DPA?

Telesign publishes its customer data processing agreement at https://www.telesign.com/dpa. We last opened that link on 22 October 2026.

Is Telesign's DPA the same thing as a data processing addendum?

Yes. A data processing agreement and a data processing addendum are two names for the document Article 28 of the GDPR requires between a controller and a processor; vendors use both, and some call it processor terms. What it has to contain does not change with the name. Telesign's is at https://www.telesign.com/dpa.

Where is Telesign's sub-processor list?

Telesign publishes the list of its own sub-processors at https://www.telesign.com/dpa. We last opened that link on 22 October 2026.

Which legal entity does Telesign contract through?

Telesign Corporation, registered in United States. That is the name to put in a record of processing or a sub-processor list, not the brand.

What covers a transfer of personal data to Telesign outside the EEA?

EU-US Data Privacy Framework (DPF). A US certification scheme covered by an EU adequacy decision. Transfers to a certified US organisation need no further mechanism for the certified scope. Whether that is enough for a particular processing operation is a judgement for the controller.

Where is Telesign's trust center?

Telesign publishes it at https://www.telesign.com/security. A trust center, trust page or security page is the same thing under different names: the vendor's own account of how it protects data, and the place it keeps its certifications. It is Telesign's page, so we link to it rather than repeat what it says.

What has changed, and when

Changes we noticed on Telesign's own pages, each with the page we saw it on. The vendor does not publish this, and neither does anyone else.

22 October 2026

I don't have enough information to write a meaningful change note. The detected facts show that 2 lines were removed, but they appear to be blank or contain only language codes (EN), without any substantive content about what changed in Telesign's data processing agreement. Please provide the actual text that was removed so I can describe what changed and why it matters.

Seen on https://www.telesign.com/dpa

21 October 2026

Telesign added new subprocessors operating in Colombia, Indonesia, India, United Kingdom, China, Serbia, and Singapore. These locations lack EU adequacy decisions, which means data transfers there require additional safeguards like Standard Contractual Clauses under the GDPR.

Seen on https://www.telesign.com/dpa

21 October 2026

Telesign's Data Processing Agreement now explicitly references standard contractual clauses and adequacy decisions as transfer mechanisms for personal data outside restricted territories. This matters because it clarifies the legal basis Telesign uses to legitimize international data transfers, which affects how you document their compliance obligations in your records of processing and subprocessor management.

Seen on https://www.telesign.com/dpa

20 October 2026

Telesign added Close as a subprocessor. The vendor's data processing agreement documentation was replaced with website error pages, removing the full list of subprocessors and detailed processing terms that should be reviewed in records of processing.

Seen on https://www.telesign.com/dpa

20 October 2026

Telesign removed its data processing agreement document that previously specified standard contractual clauses and adequacy decisions as transfer mechanisms for personal data. The vendor no longer provides documented legal transfer mechanisms for cross-border data transfers, which affects how data transfers outside restricted zones are contractually justified.

Seen on https://www.telesign.com/dpa

20 October 2026

The contracting legal entity previously identified as Telesign (a Proximus Global company) no longer appears in the current legal documentation. This affects the accuracy of the subprocessor list and record of processing, as the legal entity responsible for data processing activities may have changed.

Seen on https://www.telesign.com/dpa

2 October 2026

We recorded a change to the sub-processor list link.

30 September 2026

We recorded changes to the transfer mechanism, the UK transfer mechanism.

30 September 2026

We recorded a change to the trust or security page.

Telesign: DPA, subprocessors and transfers

What to put in your subprocessor list

Questions people ask about Telesign

What has changed, and when

Building your own sub-processor list?

Where to go next

Other communication

Telesign: DPA, subprocessors and transfers

What to put in your subprocessor list

Questions people ask about Telesign

What has changed, and when

Building your own sub-processor list?

Where to go next

Other communication