Send sensitive files through encrypted temporary sessions. Links expire automatically and end-to-end encryption keeps plaintext off the server.
Every share is a session that expires. Files are not kept as permanent cloud objects after the session ends.
Files are encrypted in the browser before upload. RookFile stores ciphertext only. Joiners receive the session key via encrypted invite; compare the Key fingerprint out of band.
Encrypted File Sharing exists to share a file so the server holds ciphertext and the key stays with the browsers in the session. It is not a second copy of the tool homepage. The homepage introduces the whole product. This page stays on one job so a search for that job lands on instructions you can follow without hunting through other tabs. Read the result on this page against the input you actually used. A screenshot without the input is not evidence. If the result surprises you, change one thing and run it again before you change your VPN, browser, or server config.
Work through Encrypted File Sharing in order. 1. Start an encrypted session. 2. Read the fingerprint. 3. Compare that fingerprint with the other person on a second channel. 4. Upload only after the fingerprints match. Write down the input and the output together. When you ask someone for help, send both. Repeat the same input once. A stable tool returns the same answer. If it does not, the input changed or the page is talking to a different network path than you think.
Encryption does not choose the right recipient. A wrong person with the link and the key can read the file. The fingerprint check is manual. This does not scrub metadata inside the file. Treat the output as a measurement, then decide. RookVPN does not log the contents of a client-side tool, and a measurement is not a promise that every other app on the device behaves the same way. Compare a second path when the decision matters: a terminal command, another browser, or the matching guide linked below.
Example: both browsers show the same fingerprint over a voice call, then you upload. If the fingerprints differ, stop. You are not looking at the same session. Uploading anyway encrypts the file to a key the other person does not have, or worse, to a session you did not create.
After you finish Encrypted File Sharing, open the end-to-end session page for how keys are wrapped to joiners if the next question is different from the one this page answers. Stay here if you are still on the same job. Extra pages help only when they answer a new question, such as a different algorithm, a different leak channel, or a different file type. The documentation link on this page is the long form of the same workflow, including the checks that do not fit in the tool UI.
Up to 1 GB per session.
No. Sessions auto-expire and files are deleted.
It is how you know the key you see is the key they see.
No. Keys are not a fragment you can forward by accident in the same way as a legacy link hash.
The server stores ciphertext for an encrypted session.