Security

Practical controls for customer conversations

Learn about Connext workspace isolation, account recovery, session controls and deployment responsibilities.

Boundaries between workspaces

Tenant-scoped database operations use PostgreSQL row-level security and organization context. Workspace membership and role checks are enforced by the API. Platform administration uses separate authorization.

Passwords and sessions

Passwords are hashed with Argon2id. Session cookies are HttpOnly, and production cookies are secure. Account security lets users inspect active sessions, revoke a specific session and sign out other sessions after confirming their password.

Recovery links with a limited lifetime

Recovery tokens are random, stored as hashes, single-use and time-limited. A successful password reset revokes existing sessions. Queued email payloads are encrypted at rest and removed after delivery or terminal failure.

Keep deployment responsibilities visible

Operators must maintain TLS, patches, credentials, database backups and monitoring. The current project has no claimed third-party security certification or independent penetration-test report.

Make your next step count.

Explore the product, understand your options, and get your team ready.

01 / EXPLORE

See how chat works

Connect your website to a shared inbox with clear ownership and private team collaboration.

Explore live chat →
02 / PLAN

Start with Free

Understand available policies, included capabilities and the responsibilities of self-hosting.

Explore pricing →
03 / LAUNCH

Set up your workspace

Follow the setup guide from creating an inbox to receiving your first website conversation.

Get started →