Security
How we protect your customers’ data
Texa Desk is built for banks and regulated businesses. This is how data is kept apart, protected and deleted, and how every reply is checked.
Photo: Roberto Hund
The controls
Each control below is written down in our security pack with the code and the test that show it, so your team can check it.
Businesses kept apart
- Every table of customer records is protected by database row-level security, so one business can never read another’s data.
- The application’s own database login cannot switch that protection off.
- A test checks every protected table automatically, including new ones.
Secrets sealed
- API keys and tokens you give us are sealed with AES-256-GCM, under keys kept outside the database.
- Keys rotate without downtime, and a secret can never reach a log line.
- Your API keys for Texa are shown once, and only a hash is kept.
Sensitive numbers masked
- Card numbers, PINs, BVN and NIN are masked before anything is stored, and Texa never repeats them.
- Photos of cards and IDs stay in Texa Desk, visible only to the roles you choose.
- Card data is never stored, so your card scope stays where it is.
Your customers’ rights
- Texa acts as your data processor under a data processing agreement, as the Nigeria Data Protection Act requires.
- Delete a customer across Texa Desk and Texa in one action, or download everything held about them.
- Data is kept only as long as you set.
Sign-in and access
- Two-step sign-in for anyone who wants it, and always for Texa’s own staff.
- Single sign-on with Microsoft Entra ID, Google Workspace or SAML, which you can enforce.
- Roles limit what each person sees, and an audit log records changes.
Connections and network
- Everything that leaves a server is encrypted with TLS.
- Connections reach only the addresses you registered. Internal and private addresses are blocked.
- Texa Relay connects out over mutual TLS, and webhooks are signed in both directions.
Replies that are safe
- Every reply is checked before it is sent: no unchecked facts, no figures from nowhere, no private details before verification.
- Instructions hidden in messages, documents, images or lookup results are treated as text, never obeyed.
- Actions that change something need the customer’s clear yes and stay within your limits.
Running the service
- Daily backups, with restores tested.
- A public status page that checks every part each minute, with the last 90 days.
- Health checks and monitoring on every part, with internal metrics kept off the internet.
- Switches to hand every conversation to people at once, for a business, an inbox or a conversation.
Measured
Tested, not assumed
Results from our own test suite, run against the real system with test data.
- 0 duplicate replies across 1,000 redelivered messages
- 0 Texa messages across 1,000 conversations a person had taken over
- 0 reads of one business’s data by another
- 0 of 16 attempts to reach internal addresses through a connection got through
- 1 refund sent across 1,000 retries of the same request
- 0 rule breaks across 11,006 simulated campaign sends
Data questions
For hosting in Nigeria, a dedicated instance or Texa Relay, see the enterprise page.
EnterpriseCan our data stay in Nigeria?
Yes. Texa Desk can run on Texa’s standard hosting, on Texa’s hosting in Nigeria, or as a dedicated instance in the country you choose, on your own domains. The Safety page shows where each part runs, including where the AI model processes messages. You can require a country, and the go-live checklist then fails, in plain words, while any part is elsewhere.
Is Texa Desk built for the Nigeria Data Protection Act?
Yes. Texa acts as your data processor under a data processing agreement. You can download everything held about one customer, or delete them across Texa Desk and Texa in one action. Card numbers, PINs, BVN and NIN are masked before anything is stored, and Texa never repeats them.
Does it work with core banking systems behind a firewall?
Yes, through Texa Relay, a small program your team runs inside your network. It connects out to Texa over mutual TLS, so you don’t open an inbound firewall port. It runs only the named read queries you approve, with row limits and column masking, keeps its own audit log, and can be switched off from either side.
Send us your security questionnaire
We’ll answer it and share our security pack, which names the code and test behind every control.
Photo: Edmond Dantès