Boring where it counts.
You are trusting Textent with your client conversations. Here is exactly how that trust is handled, in plain language, and only where the code backs it.
The ledger,
area by area.
What we do, where, and what it means for your data. No badges, no claims the code does not support.
- In transitTLS everywhere
Every connection to Textent, and from Textent to the platforms, is encrypted in transit.
- At restAES-256-GCM for credentials
Platform tokens and session credentials are encrypted with AES-256-GCM before they touch the database.
- IsolationWorkspace-scoped data
Every record belongs to exactly one workspace, and every query is scoped to it. Your conversations are not visible to any other business.
- Sign-inSessions + two-factor
Server-side sessions with modern password hashing, and two-factor authentication available on every account.
- AIAI runs on Google Gemini
AI drafting and search send message text to Google Gemini, listed as a subprocessor. Textent currently uses Gemini on Google’s unpaid tier, under whose terms Google may use that text to improve its products.
- HostingEU infrastructure
The platform runs on EU-based servers, with media on distributed object storage encrypted at rest.
- BackupsDaily, off-site
The database is backed up daily to separate off-site storage, so a bad day stays a bad day, not a lost one.
Least drama
Security is a practice, not a page of badges. We prefer boring, provable measures over impressive-sounding ones.
Least data
We store what the product needs to work and nothing speculative. What we hold, we can explain.
Honest limits
If you need a control we do not have yet, we will say so plainly rather than sell around it. Ask us anything below.
Security researchers
are welcome here.
Report privately and we respond fast. Please do not test against workspaces you do not own.
[email protected] · see also the legal center.
Client work needs
client trust.
Encrypted tokens at rest, isolated workspaces, and any channel's history deleted when you choose. Only the claims the code supports.
- Encrypted at rest
- Isolated per workspace
- Delete any channel's history