The transfer path
The browser encrypts supported media, breaks it into chunks and sends those chunks through the application transport. The backend tracks transfer state and descriptors and can enforce quotas, expiry and authenticated access.
Client-side protection
Supported media is encrypted in the browser using AES-GCM and handled through authenticated transfer descriptors. The protected transfer path is designed so the application server does not need ordinary plaintext media to route and manage the transfer.
Why files are chunked
Chunking makes retries and progress reporting practical and avoids treating a very large file as one request. It also allows upload concurrency and request-size controls.
Temporary storage and expiry
The media architecture supports temporary storage, signed/expiring media tokens, manifest access, cleanup and deletion. Vault storage is intended for longer-lived retention subject to the plan and quota configuration actually enabled in production.
Workspace separation
Workspace uploads are intentionally separate from chat attachments, so working files can use the same protected transfer infrastructure without being silently published into the conversation timeline.
Safe-sharing practice
- Share only the file the recipient needs.
- Use expiry for temporary material where appropriate.
- Verify the recipient before sending sensitive documents.
- Remember that a recipient can make their own copy.
How an encrypted file transfer works
- Select: choose the file or media item in the browser.
- Protect: the supported client workflow encrypts content before transfer.
- Chunk: larger files are split into manageable transfer units.
- Authorise: transfer operations are tied to the authenticated context and transfer metadata.
- Store temporarily or in Workspace: supported storage classes can apply different retention and separation rules.
- Retrieve: the recipient reconstructs and decrypts the protected content in the supported client.
Expiry and deletion
Expiry controls are useful when a file should not remain available indefinitely. Deletion removes the stored transfer from the supported application path, but users should never treat expiry as a guarantee that a recipient has destroyed every local copy.
File-sharing safety checklist
- Check the recipient before sending.
- Use a short-lived transfer when long retention is unnecessary.
- Keep confidential files out of public links or unrelated rooms.
- Use Workspace when you want working files separated from the conversation.
- Review file names and metadata before sharing if those details are sensitive.