1. Introduction
Crivvi ("we," "our," or "us") is committed to protecting your privacy. This Privacy Policy explains how we collect, use, and safeguard your information when you use our secure secret sharing service.
2. Zero-Knowledge Security Model
Crivvi is built on a zero-knowledge architecture, which means:
- We cannot see your secrets: All encryption happens client-side in your browser using AES-256-GCM
- We never receive encryption keys: Keys are stored in URL fragments (after the #) which browsers never send to servers
- We cannot decrypt your data: Even if compelled by law, we cannot provide plaintext content of secrets
- Your data is encrypted at rest: All secrets are stored encrypted in our database
API Exception: When using our REST API with plain text input, encryption can optionally occur server-side for convenience. The encryption key is immediately returned in the API response and is NOT stored by our servers. After the API response, we cannot decrypt your data. For maximum privacy, we recommend using client-side encryption even when using the API.
Large File Exception: For files larger than 2GB, decryption occurs on our servers during download to ensure compatibility across all devices and browsers. In this case, your encryption key is temporarily transmitted to our server to decrypt and stream the file to you. The key is used only for that single download session and is never stored. The file data passes through our server during streaming but is not retained. This is necessary because browser-based decryption of very large files would cause performance issues or failures on most devices.
3. Information We Collect
Account Information
- Email address (for authentication and account recovery)
- Password (hashed and never stored in plaintext)
- Account creation date
Secret Metadata (Not Content)
- Secret creation timestamp
- Expiration time and view limits
- File size (for quota enforcement)
- Whether secret is text or file (type only)
- Number of times viewed
- Team association (if applicable)
Usage Data
- IP addresses (for security and abuse prevention)
- Browser type and version
- Access timestamps
- API usage statistics
Payment Information
- Stripe customer ID (we do not store credit card numbers)
- Subscription plan and status
- Billing history
4. Information We DO NOT Store
- Secret content: We do not store the plaintext of your secrets (see Large File Exception above)
- Encryption keys: Keys are not stored on our servers
- Passcodes: Only bcrypt hashes are stored, never plaintext
- File contents: Files are stored encrypted; we do not retain decrypted content
5. How We Use Your Information
- Service delivery: To provide secure secret sharing functionality
- Account management: To authenticate users and manage subscriptions
- Quota enforcement: To track usage against plan limits
- Security: To prevent abuse, fraud, and unauthorized access
- Compliance: To comply with legal obligations
- Service improvement: To analyze usage patterns and improve features
6. Data Retention
We automatically delete data according to these policies:
- Secrets: Deleted immediately when viewed (if view limit reached) or when expired
- Files: Deleted along with secret metadata
- Activity logs: Retained for security and debugging purposes
- Account data: Retained while account is active, deleted upon account deletion
- Billing data: Retained as required by law for tax and accounting purposes
7. Data Sharing and Third Parties
We share limited data with these third-party services:
- Supabase: Database and authentication provider (encrypted data storage)
- Cloudflare R2: Encrypted file storage for large files
- Stripe: Payment processing (PCI-compliant, we don't store card details)
- Vercel: Hosting, deployment infrastructure, and analytics
We do NOT sell, rent, or trade your personal information to third parties for marketing purposes.
8. Security Measures
- HTTPS only: All communications are encrypted in transit
- Client-side encryption: Data encrypted before leaving your browser
- Encrypted at rest: Database encryption for stored data
- Row-Level Security: Database policies enforce access control
- Bcrypt password hashing: Passwords never stored in plaintext
- Regular security audits: Continuous monitoring and updates
9. Your Rights
You have the right to:
- Access: Request a copy of your personal data
- Correction: Update or correct your account information
- Deletion: Delete your account and all associated data
- Export: Download your data in a portable format
- Object: Object to processing of your personal data
- Withdraw consent: Cancel your subscription at any time
10. Cookies and Tracking
We use essential cookies for:
- Authentication and session management
- Security and fraud prevention
- Remembering user preferences
We do NOT use tracking cookies or third-party analytics that collect personal data.
11. Children's Privacy
Crivvi is not intended for use by children under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately.
12. International Data Transfers
Your data may be transferred to and processed in countries other than your country of residence. We ensure appropriate safeguards are in place to protect your data in accordance with this Privacy Policy.
13. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. We will notify you of significant changes via email or through the Service. Continued use of the Service after changes constitutes acceptance of the updated policy.
14. Contact Us
If you have questions about this Privacy Policy or wish to exercise your data rights, please contact us through our support channels.
đź”’ Our Privacy Commitment
For text secrets and files under 2GB, we use a zero-knowledge architecture where decryption happens entirely in your browser—we cannot access your content even if legally compelled. For larger files, we use server-side decryption for compatibility, but we never store encryption keys or decrypted data. All files remain encrypted at rest in our storage.