§ Sub-processors
Sub-processors
The third parties we rely on to run our services, what each one does, where it holds data, and the safeguard covering any transfer outside the UK.
Confirm before publishing. The table below reflects the services the products are built against. Check every row against your actual contracts — hosting region, payment provider, support tooling — and correct it before this page goes live. A sub-processor list that is wrong is worse than one that is absent.
Why this page exists
Where we process personal data on a customer's behalf we are a processor, and the customer is the controller. Article 28 of the UK GDPR requires us to tell that customer who else is involved, and to flow our obligations down to them in writing. This page is how we do that in public rather than on request.
Every organisation listed here is engaged under a written contract that limits it to processing data on our instructions, binds it to confidentiality, requires appropriate technical and organisational measures, and obliges it to assist with data subject requests and breach notification.
Current sub-processors
| Provider | What it does for us | Data involved | Location and safeguard |
|---|---|---|---|
| Microsoft (Azure) | Hosting for the applications, databases and encrypted backups behind both products. | All customer data held in the products: accounts, templates, directory fields, domains, monitoring results, logs. | United Kingdom and EEA regions. Any onward transfer covered by the UK International Data Transfer Addendum to the EU Standard Contractual Clauses. |
| Microsoft (Entra ID) | Authenticates account holders. We receive an identity token; we never see a password. | Name, work email address, tenant and group membership, sign-in events. | The customer's own Entra ID tenant and region. Microsoft is the customer's provider as much as ours. |
| Transactional email provider | Delivers service notices, alerts and our replies to enquiries. | Recipient name and email address, subject and body of the message sent. | UK or EEA sending infrastructure. Safeguard: UK IDTA where the provider is outside the UK. |
| Payments and accounting | Takes subscription payments and keeps the statutory accounting record. | Billing contact name, email address, billing address, transaction records. Card details go to the payment provider and are never held by us. | UK or EEA. Safeguard: UK IDTA where applicable. |
| Error monitoring and support tooling | Captures application errors and holds support correspondence so a ticket can be answered and traced. | Diagnostic data, which may incidentally include an email address or a tenant identifier present in the request that failed. | UK or EEA where offered. Safeguard: UK IDTA where the provider is outside the UK. |
| MaxMind (GeoLite2 database) | Resolves an IP address found in a DMARC aggregate report to a country, so a sending source can be described usefully. | None transmitted. The database is downloaded and queried locally, so no lookup leaves our infrastructure. | Not applicable — no personal data is sent to MaxMind. |
Public DNS resolution carried out by MailAuthInspector is a query to the authoritative name servers for the domain you asked about. That is a public lookup, not a disclosure of personal data to a sub-processor, and it is the same query any receiving mail server makes.
This website
Only the hosting provider is involved in serving trustlayertechnologies.com. The site loads no scripts, fonts, styles or images from any other organisation, sets no analytics or advertising cookies, and has no chat widget or embed. Nothing about your visit is disclosed to a third party. See the cookie policy.
Notice of changes
Before we add a new sub-processor to a service, or materially change what an existing one does, we update this page. Customers who ask to be notified are emailed at least 30 days before the change takes effect, except where a provider must be engaged immediately to maintain security or availability — in which case we tell them as soon as we can.
To join that notification list, email privacy@trustlayertechnologies.com from your account's billing or administrative contact.
Objecting to a sub-processor
A customer may object, on reasonable data protection grounds, to a new sub-processor within 30 days of being notified. We will work with you to find an alternative arrangement. If no reasonable alternative exists, you may terminate the affected subscription without penalty and receive a pro-rata refund of fees paid for the unexpired term.
How we choose them
Before engaging a sub-processor we look at:
- whether we can do without it at all, which is the cheapest security control available;
- the data it would actually need, and whether that can be reduced or pseudonymised;
- its security posture, certifications and breach history;
- where it processes and stores data, and what transfer safeguard would apply;
- its own sub-processor list, since the chain does not stop at the first link;
- whether its contract terms let us meet our obligations to you;
- how hard it would be to leave.
We remain responsible to our customers for the acts and omissions of every organisation on this page. Naming them does not pass the responsibility along.
Questions about this document
Write to privacy@trustlayertechnologies.com for anything about data protection, or hello@trustlayertechnologies.com for everything else. Post reaches us at the registered office: to be confirmed.