Privacy, metadata, and logging
No account is needed to use Reiven. Payload contents are encrypted on your device, but operating a sharing service still involves metadata and network information.
Uploads and share metadata
The application receives encrypted content and metadata needed to deliver a share: its filename, encrypted size, identifier, expiry, deletion token, receiver-deletion setting, note flag, access-code hash, and download count. Filenames are not hidden from the service. Passwords and decryption keys are not submitted by the normal upload or download flow.
Encrypted payloads and their live share records are held in server process memory. Shares expire after 24 hours from upload initialization, can be deleted earlier, and disappear if the service restarts. Abandoned upload sessions are cleaned up after two hours. Cleanup runs periodically; deletion removes the live record but is not a guarantee of immediate forensic erasure from RAM.
These settings describe the hosted service. A self-hosted deployment can configure different limits. Read the storage guide.
Operational and network logs
The server and its hosting infrastructure receive client IP addresses to handle connections. Routine successful web requests and successful upload completions are not currently written to a dedicated access log. Application errors, reverse-proxy errors, and operating-system events may be logged.
Error records can include timestamps, IP addresses, request paths or queries, and request headers, depending on the component. They are separate from the RAM-only upload store and may persist on disk across restarts. There is currently no application-enforced fixed retention period for these operational logs. Reiven therefore does not claim to keep “no logs”.
Analytics on public information pages
The homepage, product information, documentation, and guides use Google Analytics to understand visits. Google receives network information and may use analytics cookies or browser identifiers. The local initializer supplies the canonical public page URL and an empty referrer, disables Google Signals and advertising-personalization signals, and does not intentionally report share identifiers or content.
Google Analytics is not loaded on the sharing workspace, receive-by-code page, private download pages, or deletion pages. It is also skipped on public-page requests containing a query or fragment. No custom upload-completion events are sent. Browser privacy tools can block analytics requests.
Read Google's privacy policy for how Google handles its services. The remote analytics script remains third-party code on the public pages where it loads.
Information on your device
The sharing tool caches an Argon2 performance estimate in local storage so later visits can prepare encryption more quickly. This cache does not contain a password or payload. Your browser may retain downloaded files, history, QR links, or data copied to the clipboard independently of Reiven's server.
Clear site data through your browser to remove local storage and cookies. Anyone who receives and decrypts content may keep a copy; deleting the server share cannot erase those copies.
Questions and project information
Reiven is maintained through the Reiven.io project repository. You can raise general privacy questions in its public issue tracker; do not include private links, passwords, IP addresses, or confidential files.
Read the security model for encryption details and limitations.