Privacy Policy
Privacy is not a feature; it is our foundation.
1. We Cannot See Your Data
SendCrypted is a "Zero-Knowledge" service. Because all encryption and decryption happen entirely within your browser using the Web Crypto API, your plaintext information and your decryption keys are never transmitted to our server. We do not have the technical ability to read your secrets.
2. Information We Collect
To provide the service, we only store the following for active secrets:
- Encrypted Payload: A versioned, encrypted blob containing your data.
- Unique Salt & IV: Randomly generated cryptographic values needed for your browser to perform decryption.
- Timestamps: Creation and expiration dates used for automated cleanup.
We do not use cookies, tracking pixels, or third-party analytics. We do not log your IP address in our database.
3. Data Lifecycle & Deletion
We believe data should not exist longer than necessary:
- Auto-Burn: By default, secrets are permanently deleted from our database the moment they are successfully retrieved by the recipient.
- Expiration: Secrets that are never viewed are automatically purged after their configured lifespan (between 1 and 7 days).
- Metadata Receipts: Depending on server configuration, we may retain a "receipt" (metadata showing when a secret was viewed or burned) for a limited time, but the sensitive encrypted payload is always destroyed immediately.
4. Understanding the Risks
While our cryptographic model is robust, no system is perfectly immune to all threats. Users should be aware of the following:
- Compromised Infrastructure / MITM: Because the encryption logic is delivered as JavaScript, the only way a compromised server or a "Man-in-the-Middle" (MITM) attack would be harmful is if the attacker managed to serve a compromised version of our frontend code designed to exfiltrate keys. We mitigate this by using strict HTTPS and CSP headers.
- Local Malware: If your device or the recipient's device is infected with malware (such as a keylogger or screen scraper), the security of the application can be bypassed at the source.
We encourage security-conscious users to audit the source code directly in their browser's developer tools.