Hosting
Where your data lives
Texa's three ways of hosting Texa Desk, what lives where, and how each account sees it.
Texa Desk is a hosted service: you don't install or run it. What you choose is where it runs.
| Option | What it is | For |
|---|---|---|
| Standard hosting | Texa's shared deployment at texadesk.com |
most companies |
| In-country hosting | Texa's deployment in Nigeria, shared by the companies that need it. Servers, databases, files and backups stay in the country | companies with a residency rule, such as payments data under the CBN's circular |
| A dedicated instance | one company's own Texa Desk, databases and backups, on servers in the country it chooses, on its own domains | banks and others who need their own instance |
In-country hosting and dedicated instances are set up on request: write to [email protected]. See dedicated instances.
What lives where
| Part | Keeps |
|---|---|
| Texa Desk | conversations, contacts, files, tickets, your team's work |
| Texa's service layer (the API, connectors, billing) | references and facts rather than copies of conversations; sealed secrets; logs of what it did; 24 hours of API answers for idempotency |
| Texa AI | transcripts, what it remembers about each customer, call recordings |
| The AI models | nothing kept: they read each message to answer it |
Every account sees the exact map for its own deployment in Texa Desk, under Texa AI → Safety → Where your data lives: where each part runs, and where the AI models process. An account can require a country; its go-live checklist then fails, in plain words, while any part is elsewhere.
The outside services Texa uses, and what each receives, are listed in the privacy notice.
Data that never leaves your network
For lookups in systems whose data may not leave your network at all (a core banking database), the Texa Relay runs inside it and answers only signed, read-only, masked operations, with no inbound port.