Privacy policy

Last updated: August 25, 2026

Beamcode (“we”) provides temporary encrypted file transfer at beamcode.vjyas.online.

What we process

• Encrypted file objects stored briefly in edge object storage until expiry, revoke, or auto-delete.
• Transfer metadata such as transfer id, sizes, filenames (may be hidden when password-protected), TTLs, and download counters needed to run the service.
• Security signals like rate-limit counters, optional CAPTCHA tokens, and optional policy webhooks that receive only metadata (not file bytes).
• Nearby signaling (optional): short WebRTC connection messages so devices can send the file directly. Nearby file bytes are not stored in object storage.

End-to-end encryption

Client-side AES-256-GCM encryption is required. Encryption keys are generated in your browser and are intended to live only in the share link fragment or compact QR. We design the service so plaintext content is not needed on the server for normal operation.

Accounts and cookies

Beamcode does not require accounts. Sender session state is kept in browser session storage for live beams. Essential operational cookies or similar technology may be used by the network edge for security.

Retention

Transfers expire by lifetime or download limits. Senders can revoke early. Optional auto-delete removes stored ciphertext after the last allowed download package attempt.

Contact

For privacy questions, feedback, or feature requests about Beamcode, email support@vjyas.online.