Less data.
Less exposure.
BlockBox is designed to collect the minimum metadata needed to deliver an encrypted file to an authorized Solana wallet. You do not need to provide a name, email address, phone number, password, or social account.
What BlockBox stores
- Encrypted file objects. Plaintext files are never intentionally sent to or stored by BlockBox.
- The creator wallet, authorized recipient wallets, access policy, sanitized filename, file type, size, timestamps, and optional title or note.
- One-time authentication challenges, hashed session tokens, and minimal access outcomes used to enforce authorization.
- A file key encrypted at rest under the service key-encryption-key.
What stays in your browser
File encryption and decryption happen locally with the Web Crypto API and AES-256-GCM. The unencrypted file and decrypted preview remain on your device. BlockBox does not add advertising or behavioral analytics trackers.
Important limitation
Common Solana wallets expose signing, not standardized encryption. BlockBox therefore uses signatures for identity and a server-assisted key-release design. A service compromise alone does not reveal stored files without the key-encryption-key, but a simultaneous compromise of the application service and that key could expose file keys. See the project threat model for operational controls.
Deletion
Creators can permanently delete encrypted objects from their dashboard. Minimal access records may be retained for abuse prevention and security response.