How it worksSecure sharing

Expiring file sharing with access limits

Share files that stop working on a deadline. Set an expiry, limit access sessions and add a timer after first open. Recipients need the app, no account.

Download RevaultSecurity model
Illustrative preview. Screens vary by platform.

Revault lets you share encrypted files that stop working at a deadline you choose, within 30 days, with an optional cap on access sessions and a timer that starts at first access. Your recipient needs the Revault app and the separate secret you send them, but not a Revault account or vault of their own. On desktop, the invitation page provides a QR code to continue in the mobile app.

Does the recipient need the Revault app?

Yes, for a controlled share. The recipient opens the invitation in Revault and enters the secret you send them separately. They do not need a Revault account, a personal vault or a pattern, and their own vaults stay locked while the shared vault is open.

A desktop visitor can scan the invitation page’s QR code with their phone. If Revault is not installed, use the download destination first and then reopen the invitation. The sender still needs to communicate the decryption secret privately; a QR code does not supply it.

When does an expiring share stop working?

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.

What does the timer after first access do?

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.

How do access-session limits work?

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.

Can recipients save a copy?

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 also enables supported capture safeguards: Android secure windows block screenshots and recordings; iOS hides recordings and closes after screenshots, which it cannot prevent. An external camera or modified client can still retain visible information.

What can’t an expiring share prevent?

Expiry and revocation stop future retrieval through Revault. They cannot erase screenshots, exported files, or copies retained by a recipient. Choose someone you trust, even when export is disabled.

Three controls answer three different questions

Fixed expiry answers when new access must stop, whether or not the share was opened. An access limit answers how many sessions the server may grant. The first-access timer answers how long the shared snapshot remains available after the first session is granted. Combine them for the actual task: the earliest applicable deadline ends access, and reopening does not restart the first-access timer.

Choose a session allowance that permits a real handoff

A granted session is not a verified person or one view of each file. A recipient may need to return after switching apps, losing connectivity or finishing an initial preview. A one-session allowance can therefore be less forgiving than expected. The first-access timer also starts before successful decryption is confirmed. Explain the secret and opening steps clearly before sending a tightly limited invitation.

Example: a short review window with a wider delivery deadline

A recipient can collect a document any time before tomorrow, but should only view the snapshot briefly after opening. Set a fixed deadline for tomorrow and add a first-access duration that fits the review. Decide separately whether an encrypted export is appropriate. If they need an enduring record, disabling export and choosing a short timer may conflict with the task; agree on the intended outcome first.

Practical checklist

  • Confirm whether the recipient needs temporary viewing or a retained copy.
  • Allow realistic retry and reopening needs when choosing the number of sessions.
  • Revoke the invitation itself when needed; deleting the source or changing its name does not revoke the share.

Frequently asked questions

Can I share between iPhone and Android?

Yes. Cross-platform shares use Revault’s server, with an expiry and optional access-session limits. Between iPhones you can also send a private, read-only CloudKit invitation, which has no automatic expiry or access counts.

What is the longest a share can last?

A controlled share can last up to 30 days. An optional first-access timer can end it sooner, and the owner can revoke the invitation before either deadline.

Does deleting my original file cancel the share?

No. A share is a separate snapshot, so removing the original file does not revoke it. Revoke the invitation itself when access should end.

Can Revault read what I share?

The service receives encrypted file data and operational metadata such as sizes, checksums, timestamps and access-session counts. Your vault pattern, recovery key and vault master key are never included in a share, and the separate decryption secret is never uploaded.

How big can a share be?

The server sharing service currently accepts snapshots with up to 1 GiB of file content. That capacity does not limit the files in your own vault.

Does a one-session limit mean only one person can open it?

No. An invitation is a capability: anyone holding the link and the secret can use an available session. Use separate invitations when different recipients need their own deadlines or counters.

Does the timer begin only after the recipient successfully decrypts?

No. It begins when the service first grants access, before decryption success is known. A wrong secret or interrupted transfer can therefore use time. Later opens share the same deadline rather than starting a new timer.

Can I guarantee a downloaded file self-destructs?

No. Expiry and revocation govern retrieval through the controlled service. A recipient’s earlier export, screenshot, external-camera photo or other retained copy cannot be remotely erased by that deadline.

Can one invitation give each recipient an independent timer?

The invitation’s limits are shared, including its first-access deadline. Create separate invitations when recipients need different opening windows, session counts or the ability to revoke one person’s future access independently.

Keep exploring

Put this into practice in your vault

Choose the settings that fit your files, and keep a recovery plan before you rely on a single device.

Download Revault

Secure sharing guides

How to share files securely between iPhone and AndroidExpiring file links and self-destructing shared vaults explained
Secure sharing

Share a file. Keep your vault private.