Privacy

SafeDeposit is designed so operators cannot read deposit contents on the server. Encryption runs in your browser; only ciphertext and a sealed key envelope are stored.

What we store: encrypted payloads, sealed key material, proof-of-work hash, file counts, byte sizes, timestamps, and receipt identifiers. We do not require accounts or collect names, emails, or phone numbers for deposits.

Network data: infrastructure may log standard connection metadata (IP, user-agent, timing). Prefer Tor to reduce linkability. This demo may use ephemeral storage in preview environments.

Cookies: deposit flows do not require authentication cookies. Optional analytics are not used in this build.

Retention: operators may delete or archive ciphertext after processing. Receipts may remain for status checks until expiry policy applies.

This privacy summary is for the product demo and is not a legal contract for a production deployment.