Developers / Security

Security you can check for yourself

ChatterMate security starts with open code, so you do not have to take our word for it. This page says what is protected, what is not, and what you are responsible for.

Encrypted at rest

Encrypted in the app
  • Chat messages
  • AI-written handover and ticket summaries
  • AI memory for each chat
  • LLM API keys
  • Channel and CRM credentials
  • Database connector passwords and SSH secrets
Not encrypted by the app
  • Ticket titles, text and comments
  • Customer names, emails and phone numbers
  • Knowledge base content
  • Some other integration settings

Protect these with database and disk encryption on your host.

Sign-in and keys

Passwords

Stored as bcrypt hashes, with a strength check.

Sessions

Short-lived access tokens, with refresh tokens that last 7 days.

Widget keys

Stored as bcrypt hashes, not as plain text.

Safe defaults

A production install refuses to start with default secrets.

Slack

Every request is signature-checked, with a 5-minute replay window.

Widget limits

You can turn on a daily limit per visitor for each agent.

If you self-host

Your servers
Your data stays with you

Chats and knowledge live in your own database. Embeddings run locally.

Your TLS

The shipped web server listens on port 80. You add HTTPS in front of it.

Outside your servers
Your AI provider

Message text goes to the model provider you configure, so choose one you trust.

What leaves your servers

This is the self-hosted picture. On our cloud, we run the database and the servers for you.

DataWhere it goes
Message textThe AI model provider you configure
Embeddings for your knowledgeCreated locally on your install
AI framework telemetryOff by default
Your databaseStays on your infrastructure

Connecting a database safely

AI ticketing can read Postgres or MySQL, so the rules there are strict. It runs SELECT queries only, on tables you allow, with a row limit. You can mask columns and scope rows to the customer on the ticket. Use a read-only database user as well, so the database enforces it too.

What we do not have yet

Not yetNo certification

We are not SOC 2, ISO 27001 or HIPAA certified. If you need that today, choose a larger vendor.

Not yetDeleting data

Knowledge, users, channels and integrations can be deleted. There is no one-click delete for a single customer yet.

Advisories and reports

We publish security advisories on GitHub, including the ones that were our fault. If you find a problem, report it there privately.

Security questions

Is it end-to-end encrypted?

No. Messages are encrypted at rest in the database, and the app has to read them to answer.

Who sees my chat text?

Message text goes to the AI model provider in use, so its terms apply. On your own key or your own servers, you choose that provider.

Where can I read the code?

On GitHub. The core is Apache-2.0.

Plug it in

Add your website and start teaching your AI agent.

Start free