Security — T-Mobile

All API traffic uses TLS 1.2+ with HSTS enforcement. No unencrypted access paths.

Geo-routing and data residency options for EU, APAC, and US-based workloads.

Role-based access, API key scoping, SSO integration, and audit logging across all admin actions.

Subprocessor list, DPA, and security overview available for procurement and legal review.

Security review process

A structured path from initial questions to approved use.

For organisations with formal vendor approval workflows, T-Mobile provides supporting documentation and direct contact for security questions.

01

Review the security overview, subprocessor list, and available certifications.

02

Request a DPA, raise questions via the security contact, or initiate a formal vendor review.

03

Proceed to onboarding with documented controls and residency options in place.

Operational security

T-Mobile applies security controls at every layer — from API access to infrastructure placement and data residency.

Compliance & governance

Access the materials your legal and security teams need to complete a procurement review.