What memory-only storage means for your files
Reiven uses the server’s process memory as a temporary place to hold encrypted uploads. This has a direct effect on how long a link can remain available.
Where an upload goes
Your browser encrypts the content before uploading. The server holds the resulting encrypted byte buffers in RAM along with the information needed to deliver the share. The application does not save those payloads to application-managed files or a disk database.
For the hosted service, process swapping and core dumps are disabled. These host settings matter because an operating system can otherwise persist memory outside the application's own storage logic.
Why a share may disappear early
Shares have a 24-hour expiry measured from upload initialization. That is an upper availability window, not a durability promise. A service restart, deployment, crash, or machine reboot clears all stored shares immediately.
If you upload a file in the morning and the service restarts in the afternoon, the link will stop working even though its scheduled expiry is still in the future. You will need to create a new share.
Deletion and copies
Using a deletion link removes the live metadata record and encrypted buffers from the application's store. Memory is subsequently managed by the runtime and operating system; logical deletion is not the same as certified physical memory erasure.
Deleting a share cannot remove the sender's original, a recipient's saved download, clipboard contents, or screenshots. Memory-only server storage also does not mean there are no operational logs. The privacy page describes those separately.
When this model is useful
Use Reiven for an active handover where you can confirm receipt, such as sending a document to a colleague or moving a file to another device. Keep your original until the recipient has saved their copy.
Use a suitable backup or durable storage system for anything you need to recover later. Reiven provides temporary file sharing and private notes, not archival storage.