Your customers' conversations, protected
Support data is some of the most sensitive data a business holds. ReplyX is built so isolation, encryption and least-privilege access are the default — not an add-on.
Tenant isolation with RLS
Every workspace's data is separated at the database level with PostgreSQL row-level security. The application connects as a restricted role, so one tenant can never read another's conversations — enforced by the database, not just app code.
Encryption at rest for secrets
Provider keys and channel access tokens (Anthropic, Stripe, Meta and more) are encrypted with AES-256-GCM before they touch the database. They're decrypted only in memory at the moment they're used, and never returned to the browser.
Least-privilege access
Owner / admin / agent roles scope what each teammate can do, and agents can be restricted to specific products. Support access to a workspace is read-only, time-limited and fully audit-logged.
Verified integrations
Inbound webhooks are signature-verified (Meta X-Hub-Signature, Stripe signed webhooks). Payments are only confirmed by server-to-server callbacks — never by a browser redirect that could be spoofed.
Auditability
Sensitive operator actions are recorded in an append-only audit log — who changed a subscription, a setting, or accessed a workspace, and when. Secret values are never logged.
Reliability
A fair-scheduling queue keeps one busy tenant from starving others, rate limits protect the public surface, and errors are tracked so issues surface fast.
Have a security question or need a data-processing agreement for enterprise procurement? Get in touch — we're happy to walk your team through the details.