Sub-processors

01How to read this page

A sub-processor is a company we use to run Adoptiv that may handle personal data belonging to our customers. Every one of them is under a written contract that limits it to processing on our instructions, holds it to security obligations no less protective than our own, and is covered by the transfer clauses in /legal/dpa. We remain responsible to our customers for what they do.

The last column is the one to read carefully. Many of these are not on unless somebody turns them on.

One important scoping point about the AI section. That table lists every provider the platform is built to support, not a list of companies all receiving your data at once. Each AI job is bound to a single provider at a time, so the providers actually in use are a small subset. A customer can ask which providers are bound for its account and we will tell it.

This page covers sub-processors. It does not cover the services a customer chooses to connect for itself, such as another CRM or a video conferencing account. Those are the customer's own controllers and its own contracts, and we only move data at its instruction.

02Infrastructure

These run the platform. There is no version of Adoptiv that does not use them.

03Mailbox and calendar

Reached only when a user connects their own mailbox or calendar. If nobody connects one, none of these receive anything.

04AI and speech

This is the most sensitive category, because these providers can receive the content of calls and email rather than just metadata.

AI analysis is opt-in for each workspace and every switch starts off. Nothing here receives anything until an administrator turns a feature on. Providers are engaged under terms that prohibit them from training any model on the data.

Where analysis produces suggested corrections to a contact record, such as a corrected job title or postal address heard on a call, those suggested values pass through the language model as part of the same request. They are held as suggestions for a person to accept or reject, not applied automatically.

05Email delivery

Resend is the only one of these that is always on, because the platform has to be able to email you about your own account. A customer's own campaign and CRM mail never silently falls back to it: if the customer's chosen sender is unavailable, the send fails rather than going out from an Adoptiv address.

06Telephony numbers

Adoptiv runs its own voice infrastructure. Call media and recordings stay on our own servers and storage. The companies below sell and provision phone numbers.

None of these receives call audio, recordings, transcripts or call detail records from Adoptiv. They do not receive contact lists or CRM data. To be straight about one thing that is inherent rather than something our software sends: whoever is the carrier of record for a number carries the calls to and from it, so that provider's network sees the call the way any telephone carrier does.

Messaging runs on the same carrier that supplies the number. A text sent from Adoptiv goes out over that carrier, and the recipient number, the message body and the sending number reach it in order to be delivered. Nothing else about the record travels with it.

07Payments

There is no second payment processor. If you find another one named in an older Adoptiv document, that document is out of date and this page is correct.

08Compliance screening and business data

The five company lookup providers do the same job and only one is used at a time. They receive a company domain, not a person's contact details.

09Meetings

Reached only when a user connects that account to create meeting links from Adoptiv.

10Product telemetry and support

Sentry is the one to note if you are assessing us, because it is the only telemetry provider that receives an identifiable email address, and it is on by default. It exists so that when something breaks we can find the account it broke for.

11Website and browser services

These are small, but they are outbound connections and they belong on the list.

12What is deliberately not on this list

Naming a company we do not use would be as misleading as leaving out one we do, so here is what we checked and excluded.

• No second payment processor. Billing runs through Stripe alone.
• No IP geolocation service. We look up approximate location from a database file held on our own servers, so visitor IP addresses are not sent to a geolocation vendor.
• No advertising or data broker receives customer content, and we do not sell personal data.
• No AI provider receives anything from a workspace that has not switched AI features on.

Configuration keys for unused services sometimes survive in a codebase after a feature is removed. A leftover key is not a sub-processor. This page lists services that actually receive data.

13Changes, and how to be told about them

We give at least 30 days' notice before we add a new sub-processor or replace an existing one. The notice period runs from the day this page is updated.

• To subscribe, email subprocessors@adoptiv.com with the subject Subscribe and tell us which addresses to notify. We will confirm, and you can unsubscribe the same way.
• Notice goes to every subscribed address and to the account administrator on file.
• If you object on reasonable data protection grounds, write to legal@adoptiv.com within the 30 days and explain the grounds. We will work with you to resolve it.
• If it cannot be resolved, you may terminate the affected part of the service without penalty and receive a pro rata refund for the unused period, as set out at /legal/dpa.

We may occasionally have to replace a sub-processor faster than 30 days, for instance if one fails or a contract is terminated for cause. If that happens we will tell you as soon as we can and explain why, and your right to object still stands.

Questions about anything on this page go to privacy@adoptiv.com, or Adoptiv Inc, 2810 N Church St STE 88783, Wilmington, DE 19802, United States. Our phone number is +1 (636) 556 0022.