Security at Chirp

Our Commitment to Your Security and Privacy

At Chirp, we understand that trust is the foundation of any meaningful relationship. When you entrust us with your conversations, memories, and business data, we take that responsibility seriously. This document outlines our comprehensive approach to security, privacy, and transparency.

Privacy Policy​
Trust Centre - coming soon.

🔒 Data Security

End-to-End Encryption
In Transit: All data is encrypted using TLS 1.3 during transmission
‍At Rest: Data is encrypted using AES-256 encryption in our databases
‍Application Level: Sensitive data fields are encrypted with additional layers of protection

Infrastructure Security
‍Cloud Provider: Hosted on enterprise-grade infrastructure (Supabase/AWS)
‍Network Security: Protected by firewalls, intrusion detection, and DDoS protection
‍Regular Security Audits: Quarterly penetration testing and vulnerability assessments
‍Zero Trust Architecture: Every request is authenticated and authorised

💬 Chat Security

Data Minimisation
We only collect and store data necessary for providing our services
Personal information is automatically anonymised where possible
Conversation data is processed with privacy-preserving techniques

Memory System Privacy
‍User Control: You own and control all your memories and data
‍Selective Sharing: Choose what information to share with different contexts
‍Automatic Expiration: Set retention periods for different types of memories
‍Granular Deletion: Delete specific memories or entire conversation histories

No Training on Your Data
Your conversations and deal data are private to your AI model’s memory and are used to provide custom recommendations for your account. It will never be used to train AI memory outside your account.
Your information remains private and is not shared with AI model providers
We use isolated processing environments for each user

🔐 Access Controls

Multi-Factor Authentication (MFA)
Required for all support user accounts
Support for SMS, authenticator apps, and hardware keys
Administrative accounts require additional security measures

Role-Based Access Control

• Employees have access only to data necessary for their role
• All access is logged and monitored
• Regular access reviews and least privilege principles

API Security

Secure API keys with automatic rotation
Rate limiting and abuse detection
Comprehensive logging of all API request

Last Updated: July 2025
Next Review: September 2025

For questions about this security document or our security practices, contact us at techops@trychirp.com.