Chatline

Security and privacy

What the product does to keep clients apart, control who gets in, and limit how long chat data is kept. This page describes features, not certifications.

Keeping clients apart

Separate accounts
Each client is its own account. Its agents, chats, contacts, settings and reports are not visible to any other client.
Visitors
A visitor can only reach their own conversation. The public chat page shows no internal identifiers and checks on every visit whether the client is still active.
Operator access
The operator manages clients and can read their reports. People are added to a client only through that client's own invite link.

Getting in

Invite links
Shown once, usable once, and valid for seven days. Only a fingerprint of each link is stored, so a leaked database does not leak working links.
Single sign-on
SAML 2.0 per client, with signature, audience, expiry and replay checks. Administrators keep password sign-in as a way back.
One sign-in at a time
An account is active in one place at a time, which stops a seat being shared between two people.
Roles
Administrators, agents and custom roles with narrower permissions.
Rate limits
Sign-in, public forms and the offline message form are rate limited.

What is kept, and for how long

Twelve months
Chats, their messages and attachments, ratings, offline messages and availability history older than twelve months are deleted automatically every day.
Deletion on request
Given a visitor's email address, the operator can delete that person's contact, chats, messages, attachments, ratings and offline messages inside one client. The record of the deletion keeps a fingerprint of the address, never the address.
Audit log
Changes to people, roles, limits and settings, and sign-ins, are recorded with who and when. Secrets are never written to it.
Expired tokens
Expired invitations, reset links and sign-in sessions are cleaned up on a schedule.

What this page does not claim

No compliance certifications and no uptime guarantee. Hosting, backups and encryption at rest are handled by whoever runs your installation; ask about them in a demo.

Questions about your setup?

Bring your list. We will answer it against a running installation.