The third parties involved in running Tephlo, what each one is used for, which data reaches it, and where it operates. This list is part of the Data Processing Agreement.
Running an AI assistant on WhatsApp and Telegram means other companies are involved: one generates the answers, two carry the messages, one hosts the database, one sends email, one stores files. Each is listed below with what it does, what it receives, where it operates and in what role, as configured on the live deployment on 9 October 2026.
These describe supported and documented configurations, not proof that each provider is active for every workspace. Endpoint settings and the operator’s provider agreements determine the actual recipients.
| Provider | Purpose | Data categories | Location |
|---|---|---|---|
| OpenRouter | Generating the assistant’s replies. Every AI answer goes through this provider, which routes the request on to the selected model provider. | The customer’s message and recent conversation, the passages retrieved from the workspace’s knowledge base, and the workspace’s instructions to the assistant.Whatever a customer writes in a message can therefore reach this provider. | United States, and the country of whichever model provider it routes to. |
| OpenAI | Turning knowledge base text and customer questions into search vectors, so an answer can be found in the right document. | Knowledge base text uploaded by the workspace, and the text of customer questions used to search it.On the live deployment these requests travel through OpenRouter (the row above) to OpenAI’s embedding model. | United States. |
| Meta Platforms (WhatsApp Business Cloud API) | Receiving and delivering WhatsApp messages. Required for the WhatsApp channel. | Customer phone numbers and the full content of messages in both directions. | Global infrastructure operated by Meta.See the note on channels below — with your own WhatsApp number, Meta is your provider, not our sub-processor. |
| Telegram | Receiving and delivering Telegram messages. Required for the Telegram channel. | Telegram user identifiers and the full content of messages in both directions. | Global infrastructure operated by Telegram. |
| Cloudflare | Object storage for files customers send and for brand assets; hosting for the public marketing, documentation and legal sites. | Uploaded files and their extracted text; brand images. The public sites involve only ordinary connection data. | Storage region set when the bucket was created: Cloudflare R2, automatic placement. Site hosting is distributed. |
| Heroku (Salesforce) | Application hosting, the managed PostgreSQL database, and the managed key-value store used for queues and short-lived state. | All application data at rest, including conversations, knowledge bases and accounts. | Region chosen at provisioning: Europe (Ireland).The platform can also be self-hosted, in which case this row is replaced by the operator’s own infrastructure. |
| Mailtrap | Delivering operational email: signup verification, team invitations, password resets and escalation alerts. | Staff names and email addresses, and the content of those emails.Escalation alerts carry no customer message content — they say a conversation needs a person and link to the console. | Operated by Railsware Products Studio, LLC (United States), with infrastructure in the European Union and the United States. A workspace deployment may instead use its own SMTP provider. |
These are disabled by default. Each requires the platform to be configured for it and, where it affects conversations, the workspace to opt in. If they are off for your workspace, no data reaches them.
| Provider | Purpose | Data categories | Location |
|---|---|---|---|
| OpenAI (speech to text) | Transcribing voice notes so the assistant can answer them. | The audio of a voice note, and the resulting transcript. | United States. The request travels through OpenRouter to OpenAI’s Whisper model. |
| Paystack (workspace plan billing) | Hosted checkout, payment verification and supported renewals for workspace plans, where billing is enabled. This does not process payment for a customer’s saved cart. | Payer email, amount, currency, payment references and transaction metadata. Payment details are entered directly with the provider; the platform can retain a reusable authorization reference and limited payment-method display details returned by it. | Nigeria: Paystack Payments Limited, Lagos. Paystack is an independent controller for the payment itself, which the payer completes on Paystack’s own page; we receive the reference, status, amount, fee and the display details above. |
| OpenRouter, routing to Deepgram (spoken replies) | Turning an approved assistant reply into audio, where spoken replies and a compatible speech endpoint are enabled. | The approved reply text, selected voice and language-related settings, and the resulting audio. This can contain customer information already present in the reply. | United States. The request goes to OpenRouter, which routes it to Deepgram’s speech model; both operate in the United States. |
| OpenRouter, routing to OpenAI (image reading) | Interpreting customer images and, when separately enabled, reading scanned PDF pages without selectable text. | Customer images or rendered pages of a customer document. | United States. The request goes to OpenRouter, which routes it to an OpenAI vision model. |
| Tavily | Web search, for question types a workspace has allowed the assistant to look up. | A search query derived from the customer’s question. | United States. |
| Sentry | Error monitoring — collecting crash reports so faults get fixed. | Error type, stack trace and technical context. Message content, identifiers, tokens and addresses are redacted before logging. | No error-monitoring project is configured on the live deployment, so nothing reaches Sentry today. If one is configured, this row will say where before it starts. |
| Telegram Gateway | Delivering password-reset codes to a staff member’s phone, where they have chosen that method. | A staff phone number and a short one-time code. | Global infrastructure operated by Telegram. |
Before a new sub-processor begins processing customer data, this page is updated and workspace administrators are notified by email, with 30 days’ notice. If you object on reasonable data protection grounds, section 7 of the Data Processing Agreement sets out what happens next.
General questions about this document go to hello@tephlo.com. Questions about personal data, including requests from individuals, should go to the data protection contact at hello@tephlo.com. A request about your own data — access, erasure, correction, objection or a complaint — can also be sent through the privacy request form, which puts it in front of the team as a tracked request rather than a message in a mailbox.
Postal address: TEPHLO AI VANGUARD SYSTEMS LTD, 9A Kenneth Lekara Luka Street, Lokogoma, FCT, Nigeria.