How we handle your data - and what we never do with it.
A plain-language page about community tickets, bot tokens, AI processing, and where data lives. No badges we have not earned. No promises we cannot keep.
- Document retention, deletion, and optional AI processing.
- Encrypt bot tokens, client secrets, and sensitive credentials before storage.
- Route OpenRouter AI requests with provider data collection denied.
- Delete bot and ticket data when you delete it or make a valid privacy request.
- Tell you when a material issue affects data we are responsible for protecting.
- Sell your data.
- Share ticket data with advertisers or data brokers.
- Use private tickets to train public or foundation AI models.
- Read tickets out of curiosity. Access is limited to support, debugging, security, abuse prevention, or legal duties.
Protected at rest and in transit.
Bot tokens and client secrets are encrypted before storage, and service connections use secure transport. Backups follow a normal rotation, while audit logs help us investigate sensitive dashboard actions.
A note on access: a small set of named staff can access data when you ask us to help, when we debug a concrete incident, or when security or legal duties require it.
Things we will answer without friction.
Email [email protected] with any of these, and we will respond as quickly as we can.
A copy of your data
Tickets, transcripts, bot configuration, and knowledge base entries exported in a readable format where technically available.
Deletion help
You can delete tickets and bots from the dashboard. For broader account or privacy deletion, email us and we will walk through the right scope.
What we store about you
A plain-language list of what we keep, why we keep it, and how long it normally stays.
Custom terms
On Enterprise, we can discuss custom data-handling terms with your legal team.
The AI systems that help draft replies.
Generated AI responses are routed through OpenRouter with provider data collection denied. Knowledge-base search uses OpenAI for embeddings. We do not use customer ticket content to train public AI models, and ZDR is used only where the selected endpoint supports it.
Want the full list of services we use under the hood? Read the privacy policy.
Got a question we have not answered?
Write to us. A member of the team reviews trust, security, and data questions.