Every query and write carries the identifier of the Textra customer, and the application restricts them to that customer. It is an application control, not a separate database per customer.
Data isolation, roles and encrypted credentials: Textra's controls and their scope
This page lists the specific controls Textra has: data isolation per customer, three roles, encrypted provider credentials, short-lived access tokens, configurable message retention and consent history. Each one is explained with its scope and its limits.
The controls, one by one
Data isolated per customer
Every query, write and delete carries the identifier of the Textra customer. Scope: the application code applies it on each operation. Limit: it is not a separate database per customer.
Three roles
Each person on the team has a role: admin, editor or viewer. Scope: one administers, one edits and one only views. Limit: there are three roles per account, not custom permissions.
Encrypted provider credentials
The messaging providers' credentials are stored encrypted and decrypted only when needed to send. Limit: this describes the providers' credentials, not the content of the messages.
Short-lived access tokens
People's sessions use short-lived access tokens. Limit: it describes the token lifetime and nothing more.
Retention configurable per customer
Message-body retention is configurable per Textra customer. The conversation records are kept.
Consent history
Textra keeps the history of each contact's opt-in and opt-out, manual or by reply.
What this page is and is not
It describes application controls, written with the scope they have today. It is not a certification or a statement of regulatory compliance, and it makes no service-level commitments.
Nor does it describe the infrastructure Textra runs on. If your institution needs to assess something not listed here, ask for it in the demo and we will go through it.
Illustrative example
A cooperative's team and its access levels
- The person who administers the account loads the WhatsApp provider's credentials, which Textra stores encrypted.
- Another person on the team has the editor role.
- A third person has the viewer role and only views.
- The cooperative configures message-body retention for its account.
Frequently asked questions about these controls
It depends on the role: admin, editor or viewer. The viewer only views.
The credentials are stored encrypted and decrypted only when needed to send a message.
Yes. Each Textra customer sets how long the bodies of its messages are stored, and the conversation records are kept.
We do not claim any. This page describes only the application controls listed above.
Keep reading
Let's talk about what your institution needs
Tell us what you want to review and we will go through it in a Textra demo.