Set a deadline, limit access sessions, and start an optional self-destruction timer after first access. Share private files with a defined access window.
Some files are useful for an afternoon, not forever. A temporary document handoff or a private collection can have a clear endpoint. Revault’s controlled shares combine encryption with server-enforced limits on future access.
An expiry date from the start
Choose an expiry within 30 days when creating a controlled share. The service stops granting access after that deadline whether anyone has opened it or not. You can also revoke the share earlier. These controls apply to the shared snapshot, not the files in your personal vault.
A separate timer after first access
The optional self-destruction timer starts when the server first grants an access session, before successful decryption is confirmed. All recipients share the same deadline. Reopening does not reset it, and the earlier of this deadline and the original expiry ends access.
Limit sessions, not people
Set a maximum number of access sessions or leave sessions unlimited until expiry. The server counts granted sessions, rather than individual file views or identified recipients. Retrying with the same valid session token does not consume another access. A session lasts at most 15 minutes and never beyond the share’s deadline.
Decide whether exports are available
Allow recipients to save an encrypted .qvault copy, or disable the app’s export actions for a temporary viewing flow. Exported copies open with the share secret and can remain usable after the invitation expires. Disabling export does not prevent screen capture or a modified client from retaining data.
How to share with Revault
Choose a controlled server share when expiry or session limits matter, including between iPhones.
Set the expiry and optional first-access timer to match how long the recipient needs the files.
Review export permission before sending, then revoke the invitation when the handoff is complete.
Your vault pattern, recovery key, and vault master key are never included in a share. The service receives encrypted file data and operational metadata such as sizes, checksums, timestamps, and access-session counts. The separate decryption secret is not uploaded.