Sub-processors
Last updated 1 August 2026
Every third party involved in running TyrrexAgent, and what each can see. This list is short, and the reason is worth stating: speech recognition, language understanding, and speech synthesis all run on our own servers. The contents of a call are not sent to an AI provider, because there is no AI provider.
Always involved
| Who | What for | What they can see | Where |
|---|---|---|---|
| Hostinger | The server everything runs on | Everything stored, as any hosting provider does | India |
| Cloudflare | DNS and traffic in front of the site | Requests to the website; not call audio, which never crosses it | Global edge |
Only if a customer chooses
| Who | What for | What they can see | Where |
|---|---|---|---|
| Sign in with Google, if a customer chooses it | Email address and account identifier, to confirm who they are | Global | |
| GitHub | Sign in with GitHub, if a customer chooses it | Email address and account identifier | Global |
Chosen by the customer, not by us
Two things sit outside this list because the customer picks them and holds the relationship:
- Their telephony provider — Twilio, Vobiz, Plivo, or any SIP carrier. They carry the call and see it as they would any other call on that number. They bill the customer directly; we never touch it.
- Any endpoint a customer connects as a tool. If they build one that looks up an order, we send it whatever that lookup needs. That is their integration, on their infrastructure.
Not on this list, deliberately
No analytics provider, no advertising network, no error-tracking service, no customer-messaging widget. Nothing on the product reports to a third party about what a customer is doing.
Changes
We will update this page before adding a sub-processor, not after, and note the date at the top. If you want to be told directly, write to [email protected].
Questions about either document go to [email protected].