Security

Your memories are sensitive. Here's how we protect them.

Encryption

• In Transit: TLS 1.3 for all connections
• At Rest: AES-256 encryption for all stored data
• Backups: Encrypted before storage

Data Isolation

• Row-Level Security: Complete tenant isolation at the database level
• API Keys: Scoped to single tenant, never shared
• Zero Cross-Contamination: Your memories are never visible to other users

API Key Security

• One-Time Display: Keys shown only once at creation
• Hashed Storage: We store bcrypt hashes, not plain text
• Instant Revocation: Delete compromised keys immediately
• Rate Limiting: Protection against brute force attacks

Infrastructure

• Self-Hosted: Full control over our infrastructure
• Regular Updates: Security patches applied promptly
• Monitoring: 24/7 security monitoring and alerts
• Backups: Automated daily backups with encryption

Responsible Disclosure

Found a security issue? We appreciate responsible disclosure.

Email us at security@memberberry.dev with details. We'll respond within 24 hours.

Best Practices for Users

✓ Store API keys securely (use environment variables, never commit to git)
✓ Rotate API keys if you suspect compromise
✓ Use different keys for different projects/environments
✓ Enable two-factor authentication (coming soon)