AI Chatbot Security: How Chatsy Protects Your Data
Inside our security practices, encryption, and data privacy commitment. Multiple layers protecting your customer conversations.
Chatsy Team
Security
November 15, 2024Updated: January 15, 2026
Inside our security practices, encryption, and data privacy commitment. Multiple layers protecting your customer conversations.
When you entrust your customer conversations and business data to Chatsy, security isn't just a feature, it's a foundational principle that shapes every decision we make. From the encryption algorithms protecting your data to the access controls governing who can see it, security is woven into every layer of our platform.
TL;DR:
- Chatsy encrypts all data at rest (AES-256) and in transit (TLS 1.3), with encryption keys managed in AWS KMS and rotated every 90 days.
- Multi-tenant isolation is enforced at the code and database level via row-level security, ensuring customers can never access each other's data.
- AI-specific protections include prompt injection sanitization, PII redaction in logs, hallucination prevention through grounded generation, and configurable content boundaries.
- Chatsy is GDPR and CCPA compliant, with SOC 2 Type II in progress, and offers data residency options in the US and EU.
In this comprehensive guide, we'll pull back the curtain on our security practices, explain our technical implementations, and help you understand exactly how we protect your most sensitive information.
This guide synthesizes operational specifics from three categories of sources:
We avoided pure marketing claims and prioritized examples that ship in real codebases. Where we cite latency or accuracy numbers, the methodology, dataset, or test conditions are noted alongside. Last reviewed: April 2026.
Before diving into technical details, it's important to understand the principles that guide our security decisions:
Following the OWASP Application Security framework, we never rely on a single security measure. Multiple overlapping controls ensure that if one fails, others provide protection.
Every system, user, and process has only the minimum access required to function.
We verify every request, even from internal systems. Trust is earned through authentication and authorization, not assumed based on network location or previous access. Every API call is validated, every database query is scoped.
We believe you should understand how your data is protected. This document is part of that commitment, demystifying security practices so you can make informed decisions about your data.
All data stored in Chatsy systems is encrypted using industry-standard AES-256 encryption:
Database Encryption: Our PostgreSQL databases use Transparent Data Encryption (TDE). This means data is automatically encrypted when written to disk and decrypted when read into memory. Even if someone obtained physical access to our storage devices, the data would be unreadable.
File Storage: Documents, images, and other files are stored in S3 with server-side encryption (SSE-S3). AWS manages the encryption keys, providing automatic encryption without any performance impact.
Backup Encryption: All backups are encrypted with customer-specific keys. This ensures that even backup files, often overlooked in security discussions, maintain the same protection level as live data.
Vector Embeddings: Your knowledge base embeddings, which power AI search capabilities, are encrypted alongside other data. The mathematical representations of your content receive the same protection as the content itself.
All communications use TLS 1.3, the latest and most secure transport layer protocol:
API Traffic: All API endpoints require HTTPS. HTTP requests are automatically redirected. We enforce HTTP Strict Transport Security (HSTS) to prevent downgrade attacks.
Internal Services: Communication between our microservices uses mutual TLS (mTLS). Both the client and server authenticate each other, preventing man-in-the-middle attacks even within our internal network.
Database Connections: All database connections require SSL with certificate validation. Unencrypted connections are rejected at the network level.
Third-Party Integrations: When your chatbot connects to external services (via tool calling or webhooks), we use encrypted connections and validate certificates.
Proper key management is often the weakest link in encryption systems. We take it seriously:
Chatsy is a multi-tenant platform, meaning multiple customers share infrastructure. Ensuring complete data isolation is critical:
typescript// Every database query includes tenant validation const documents = await prisma.document.findMany({ where: { chatbotId, chatbot: { organizationId: session.organization.id // Always scoped to organization } } });
This pattern is enforced throughout our codebase. It's not possible to accidentally query another customer's data because the scope is always present.
We also implement row-level security in PostgreSQL as an additional safeguard:
sql-- Row-level security policy CREATE POLICY tenant_isolation ON documents FOR ALL USING (organization_id = current_setting('app.current_organization_id')::uuid);
Team members have different access levels based on their roles:
| Role | Capabilities |
|---|---|
| Owner | Full access including billing, team management, and deletion |
| Admin | Full access except billing and ownership transfer |
| Member | Create/edit chatbots, view analytics, manage conversations |
| Viewer | Read-only access to chatbots and conversations |
Roles are enforced at the API level, attempting to access functionality beyond your role returns an authorization error.
Password Storage: Passwords are hashed using bcrypt with a cost factor of 12. We never store plaintext passwords, and the hashing algorithm is computationally expensive enough to resist brute-force attacks.
Session Management: Sessions use secure, HttpOnly cookies that can't be accessed by JavaScript. Sessions expire after 24 hours of inactivity, and users can view and revoke active sessions from their account settings.
OAuth Integration: We support Google and GitHub SSO for organizations that prefer centralized identity management. OAuth tokens are stored encrypted and scoped to minimum required permissions.
API Key Security: API keys are scoped to specific capabilities (read, write, admin), rotatable at any time, and rate-limited to prevent abuse. Keys can be restricted by IP address for additional security.
AI systems introduce unique security challenges. We address them proactively:
Malicious users might try to manipulate AI behavior through crafted inputs. We sanitize all user inputs before they reach the LLM:
typescriptfunction sanitizeInput(input: string): string { // Remove potential injection patterns return input .replace(/\b(ignore|disregard|forget)\s+(previous|above|all)\b/gi, '') .replace(/\bsystem\s*:/gi, '') .replace(/\buser\s*:/gi, '') .replace(/\bassistant\s*:/gi, '') .trim(); }
We also use structured prompt templates that separate user input from system instructions, making injection attacks significantly harder.
AI hallucinations are a significant concern in customer support. Our mitigations include:
Our infrastructure follows defense-in-depth principles:
┌─────────────────────────────────────────────┐
│ Cloudflare │
│ (DDoS Protection) │
└─────────────────────────────────────────────┘
│
┌─────────────────────────────────────────────┐
│ WAF Rules │
│ (OWASP Top 10, Custom) │
└─────────────────────────────────────────────┘
│
┌─────────────────────────────────────────────┐
│ Load Balancer │
│ (SSL Termination) │
└─────────────────────────────────────────────┘
│
┌─────────────────────────────────────────────┐
│ Private VPC │
│ ┌─────────┐ ┌─────────┐ ┌─────────┐ │
│ │ App Pod │ │ App Pod │ │ App Pod │ │
│ └─────────┘ └─────────┘ └─────────┘ │
│ │ │
│ ┌─────────────────────────────────────┐ │
│ │ Database (Private Subnet) │ │
│ └─────────────────────────────────────┘ │
└─────────────────────────────────────────────┘
Key security features:
We maintain comprehensive security monitoring:
| Framework | Status | Notes |
|---|---|---|
| SOC 2 Type II | In Progress | Expected completion Q2 2026 |
| GDPR | Compliant | Data processing agreement available |
| CCPA | Compliant | Consumer rights honored |
| HIPAA | Available | Enterprise tier with BAA |
When you delete your account or request data deletion, we don't just mark records as deleted, we cryptographically shred the data, rendering it unrecoverable.
We maintain an active bug bounty program to encourage responsible disclosure:
| Severity | Reward Range |
|---|---|
| Critical | $1,000 - $5,000 |
| High | $500 - $1,000 |
| Medium | $100 - $500 |
| Low | Recognition |
Security is a shared responsibility. While we protect the platform, you control access to it:
Use strong, unique passwords: At least 12 characters, combining letters, numbers, and symbols. Use a password manager.
Enable two-factor authentication: Available in account settings. We strongly recommend enabling it.
Review team access regularly: Remove access for departed team members promptly. Audit permissions quarterly.
Protect API keys: Never commit API keys to version control. Rotate keys periodically. Use IP restrictions where possible.
Report concerns immediately: If you notice suspicious activity, contact security@chatsy.app right away.
Security is an ongoing conversation, not a checkbox. If you have questions about our practices, need specific compliance documentation, or want to discuss your organization's security requirements, we're here to help.
Security Team: security@chatsy.app Bug Reports: security@chatsy.app (please include reproduction steps) Compliance Requests: Contact sales for SOC 2 reports and other documentation
Your trust is our most valuable asset. We work every day to deserve it.
Skip Chatsy if your data classification requires FedRAMP High, IL5/IL6 DoD authorization, or specific Five-Eyes data-residency constraints we have not yet certified: your procurement team will rightly fail us on the SIG questionnaire and you will need a vendor with the matching attestation. Skip us if your privacy posture forbids any third-party LLM provider regardless of contractual safeguards: the underlying models we use today live with major foundation-model vendors, and that is a structural fact, not a feature flag. And skip us if you need a fully on-prem deployment for regulatory reasons: we currently operate as a multi-tenant SaaS with optional regional hosting, not a self-managed package. We will tell you so before you sign anything.
Chatsy uses defense-in-depth with multiple overlapping controls: AES-256 encryption at rest, TLS 1.3 in transit, row-level security for multi-tenant isolation, and role-based access control. Every API request is validated, and database queries are always scoped to your organization so other customers cannot access your data.
Yes. All data is encrypted at rest with AES-256 (database, file storage, backups, and vector embeddings) and in transit with TLS 1.3. Encryption keys are managed in AWS KMS, rotated every 90 days, and Enterprise customers receive dedicated keys for complete cryptographic isolation.
Chatsy is GDPR and CCPA compliant with data processing agreements available. SOC 2 Type II is in progress (expected Q2 2026), and HIPAA is available on the Enterprise tier with a BAA. Contact sales for SOC 2 reports and other compliance documentation.
Yes. You can request data deletion at any time, and all data is deleted within 30 days. When you delete your account or request deletion, we cryptographically shred the data rather than just marking it deleted, rendering it unrecoverable.
Default data residency is the United States (AWS us-east-1). EU customers can choose Frankfurt, Germany (AWS eu-central-1). Enterprise customers can request custom regions. All data stays within your selected region.
How government agencies use AI chatbots to automate citizen services, permit inquiries, and public information --- reducing call center wait times by 50-70%.