Legal
Subprocessors
On this page
In short: Every third party that touches data we hold, what each one gets and what for. If we add one, this page changes before the change takes effect, and clients under a data processing addendum are told in advance.
1. What a subprocessor is
When a client engages us, they are the controller of their customers’ data and we are the processor. A subprocessor is a company we in turn rely on to deliver the service — a model provider, a messaging carrier, a host. They act on our instructions, under contract, for the purpose listed and no other.
This is not the same as a company we merely buy something from. Our accountant is not a subprocessor; Twilio is, because a client’s customer’s phone number passes through it.
2. The list
Current as of the effective date at the top of this page.
| Company | What we use it for | What it receives |
|---|---|---|
| Anthropic | The reasoning behind Erica — drafting, triage, summarizing. | The text of a prompt and the content it is asked to work on. |
| Google (Gemini) | A fallback model when the primary one is unavailable. | The text of a prompt and the content it is asked to work on. |
| ElevenLabs | Voice agents and spoken messages inside workflows. | The text to be spoken, and call audio where a voice agent is used. |
| Twilio | SMS, WhatsApp and voice. | Phone numbers, message content, call metadata. |
| Stripe | Subscription billing. | Billing contact and payment details. Card numbers go to Stripe directly and are never stored by us. |
| Elavon | Card-present payments at a point of sale, where a client uses one. | Transaction records. Card data is handled by the terminal and the processor. |
| n8n | The automation engine that runs client workflows. | Whatever a given workflow moves — typically lead and job records. |
| Meta | Advertising, for clients who buy ads through us. | Campaign and conversion data for that client's own ad account. |
| Google Ads | Advertising, for clients who buy ads through us. | Campaign and conversion data for that client's own ad account. |
| Google Analytics | Counting visits to this site and to client sites that use it. | Page views, referrer, coarse location, a device identifier. Only with consent. |
| RingCentral | Business telephony and SMS on a client's own number. | Phone numbers, call metadata, message content, call recordings where enabled. |
| Hostinger | The server the platform and client sites run on, and domain DNS. | Everything stored on the server, at rest. Hostinger does not access it in the ordinary course. |
| Neon | Managed PostgreSQL — the platform's primary database. | Client records, leads, jobs, invoices, configuration. |
| MongoDB Atlas | Managed database for certain client applications. | That client's operational records — leads, orders, applicants. |
| Sentry | Error reporting, so a fault is found before a customer reports it. | Stack traces and request context. Configured to scrub personal data from payloads. |
3. The model providers, specifically
The providers behind Erica are the ones clients ask about most, so: content sent to them is processed to produce a response and is not used to train a public model. That is a term of the API agreements we hold, not a preference we have expressed. If a provider changes it, we change provider — and this page changes with us.
See the AI use policy for what the models are allowed to do once they have the content.
4. Where the data sits
Primary storage is in the United States. Some subprocessors operate globally and may process data outside it in the course of delivering their service; each one’s own notice, linked above, states where. We do not move client data outside the United States as a matter of course, and a client who needs a contractual commitment to US-only processing should ask before signing — it is a reasonable requirement and it constrains which providers we can use for them.
5. How changes work
A client under a data processing addendum gets thirty days’ notice by email before a new subprocessor starts handling their data, and may object. If we cannot resolve an objection, the client may terminate the affected service without penalty and without losing what has already been built.
To be told when this list changes, email admin@inericasystems.com and ask to be added to the notification list.