Security & trust
Boring where it counts.
You are trusting Textent with your customer conversations: sales, support, and payments. Here is exactly how that trust is handled, in plain language.
- AES-256-GCM at rest
- Workspace isolation
- EU hosting
- Daily backups
Every connection to Textent, and from Textent to the platforms, is encrypted in transit.
Platform tokens and session credentials are encrypted with AES-256-GCM before they touch the database.
Every record belongs to exactly one workspace, and every query is scoped to it. Your conversations are not visible to any other business.
Payment pages are hosted by Stripe. Card numbers never touch Textent servers, and payouts go directly to your connected Stripe account.
Server-side sessions with modern password hashing, and two-factor authentication available on every account.
AI features send only the thread context needed to draft or summarize. We do not train models on your conversations.
The platform runs on EU-based servers, with media on distributed object storage encrypted at rest.
The database is backed up daily to separate off-site storage, so a bad day stays a bad day, not a lost one.
Enterprise workspaces add single sign-on (SSO/SAML), advanced roles and permissions, and audit logs. Talk to us about rollout for your organization.
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; see also our legal hub.