How SnapSend Works
SnapSend is designed with a single goal: ephemeral, secure sharing without a trace. Here is how we protect your data from the moment it leaves your device.
1. Transient Storage
We store your data in a volatile key-value store (Redis) with strict Time-To-Live (TTL) policies. Once the time is up or the data is viewed, it is instantaneously evaporated from memory. We do not use long-term databases for secret content.
2. Encryption at Rest
While explicit client-side encryption is on our roadmap, current transfers are protected by TLS 1.3 in transit. On the server, your secrets are isolated and protected by the runtime environment before being ephemeralized.
3. No Logs Policy
We do not track IP addresses, user agents, or sharing metadata. Your sharing history is non-existent because we don't create it. Anonymity is the default, not a setting.
4. Self-Destruct Mechanics
When you select "Burn on View", we use an atomic verify-and-delete operation. The moment the secret is served to a valid requester, the key is scheduled for immediate deletion, ensuring it cannot be accessed twice.