A subprocessor is a company we engage that may process personal data on our customers' behalf. Each one below is bound by a written agreement imposing protections no less strict than our own Data Processing Addendum, and we remain fully responsible to you for what they do.
1. Current subprocessors
| Provider | What it does | Data it can touch | Location |
|---|---|---|---|
| Amazon Web Services, Inc. | Hosting for the application, the primary database, object storage for uploaded assets, load balancing, DNS, and content delivery. | All customer data | United States |
| Scaleway SAS | Hosting for the outbound mail server. The mail server is ours and we operate it; Scaleway provides the machine it runs on. No third party decides what is sent, and no email-delivery service handles your mail. | Recipient addresses and message content, while a message is being sent | France |
AI assists
No AI provider is engaged as a subprocessor today. The platform AI assists hold no credentials of their own, so no prompt you write leaves our systems to a model vendor. Before any AI provider begins processing customer data it is added to the table above with the 30 days' notice in section 3, exactly like any other subprocessor.
We previously declined to name a provider in advance. We are naming one now, because the notice period is worth more to you than our flexibility: we intend to use DeepSeek for the platform AI assists, and it is listed under “Planned, not yet in use” below so the clock starts today rather than on the day we switch it on. DeepSeek operates in China, which is a different jurisdiction from the rest of our infrastructure and has no European Commission adequacy decision. If that matters to you, section 4 explains how to object, and configuring your own AI provider keeps your prompts out of it entirely.
This is separate from bringing your own key. If you configure your own AI provider, your prompts go to that provider under your agreement with them, they bill you directly, and they are not our subprocessor.
Planned, not yet in use
These are listed early so the notice period in section 3 is never the first you hear of them. Neither is processing any customer data today.
| Provider | What it will do | Data it will touch | Location |
|---|---|---|---|
| Stripe, Inc. | Payment processing and subscription billing, once paid plans launch. Card details go to Stripe directly and are never stored by us. | Billing contact and payment details of account owners. No contact data. | United States |
| Twilio Inc. | Delivering one-time SMS codes for phone verification at signup. | The phone number of the person verifying. No contact data. | United States |
| DeepSeek | Running the platform AI assists: drafting and editing campaign copy and templates, and summarising send performance. Only when you use an AI assist, and only on the text of that request. | Whatever appears in the prompt: the copy or template you are working on, and the performance figures of the send you are analysing. Not your contact list. | China |
2. What we do not use
Worth stating plainly, because for most platforms the list below would be long:
- Google Analytics on the marketing site only, and only after the visitor allows it (Europe, the UK and Switzerland opt in; elsewhere it runs by default with a one-click off switch in every footer). It counts page views with a truncated IP address and never touches customer data or the application. No advertising pixels, no session recording. Google LLC, United States.
- No third-party email delivery provider. We run the mail server ourselves, so your recipient list and message content are not handed to a sending vendor such as SendGrid, Mailgun or Amazon SES. The machine that mail server runs on is hosted by Scaleway, which is why they are listed above.
- No data enrichment or list-brokerage provider. We do not append data to your contacts from outside sources, and we do not buy data about anyone.
- No AI training on your data, by us or by any provider above.
3. Notice of changes
Before a new subprocessor begins processing customer data we give at least 30 days' notice: we update this page and email account owners who have subscribed to subprocessor notifications.
To subscribe, write to privacy@sentientmail.com with the subject "subprocessor notifications". There is no charge and you do not need to be on a particular plan.
4. Objecting to a subprocessor
You may object to a new subprocessor on reasonable data-protection grounds within the 30-day notice period, by writing to legal@sentientmail.com and explaining the concern. We will work with you to find an alternative.
If we cannot resolve it, you may terminate the affected part of the Service and we will refund the unused portion of any prepaid fee, as set out in section 7 of the Data Processing Addendum.