Your data
Your files are locked on your device before they are uploaded, and only your key can unlock them. FKN’s servers keep the locked file, with its name and size. They can’t open it.
Who holds the key
Section titled “Who holds the key”You hold the key. It stays on your devices. FKN stores only locked copies of it, which your password, a passkey or your recovery code can open.
This is called end-to-end encryption. Every account has it, and no setting turns it off.
Encryption protects your files on FKN’s servers. It doesn’t hide a file from the app that saved it, because the app works with the file unlocked in your browser. An app sees only its own files in your FKN storage, so choose apps you trust.
What is encrypted
Section titled “What is encrypted”- Files apps save to your FKN storage. Each file is locked on your device before it is uploaded.
- Room messages. Messages are encrypted on your device, and fkn.app never sends the room’s key to FKN’s servers. An app can set rules for a room, and those rules can add a short readable part to each message, such as the message type.
- Files an app publishes for you. The file is locked in your browser, and the key stays with the app. Anyone with both the file’s address and the key can read it.
- Cookies of sites you open through FKN. Cookies are encrypted and stored on your device only.
What FKN’s servers see
Section titled “What FKN’s servers see”FKN’s servers can’t see:
- Your password or your key.
- What is inside your stored files.
- The locked part of a room message, as long as the room’s key stays a secret among its members.
- What is inside your HTTPS traffic through the relay.
FKN’s servers can see:
- Your email, your account name and your plan.
- Your IP address while you are connected. It isn’t stored.
- The names, sizes and folders of your files, and which app they belong to.
- Who is in a room, who sent each message, when, and how large it was.
- Which server your relay traffic reaches, and how much data passes.
- A short label for each sign-in, such as “Chrome on Windows”.
- Everything an app sends through the HTTP proxy, and the answers.
Two paths through FKN
Section titled “Two paths through FKN”An app can send traffic through FKN in two ways, and they are different. Any app can use either one without asking you.
- The relay carries traffic between your browser and a server. HTTPS is the encrypted connection websites use. On an HTTPS connection your browser encrypts the traffic end to end, so the relay can’t read your HTTPS traffic.
- The HTTP proxy makes a request for the app and hands back the answer. It reads what the app sends through it, and it keeps copies of answers in a cache, including answers to requests carrying sign-in details. This path is not end-to-end encrypted.
FKN doesn’t keep a log of the sites reached through either path. It doesn’t store your IP address, sell your data, or use ads or trackers.
Parts of FKN run on Cloudflare: the app pages, the package sandbox, file delivery and rooms. Cloudflare can see the requests that reach those parts, including your IP address. The privacy page has the full account.
Where your files are
Section titled “Where your files are”The locked copies are in FKN’s cloud storage, which runs on Cloudflare. To see them, go to Usage on fkn.app. Storage by app lists each app with its size. Press Files to browse an app’s folders, open a file or download it.
An app can also keep copies in your browser, on that one device. Those copies are not in your account, so Usage doesn’t show them, and they stay when you delete your account. To remove them, use the app, or clear that site’s data in your browser.
Files an app published appear as one Public files row, with their total size.
Download your data
Section titled “Download your data”You can download your data in two forms:
- Readable is an ordinary zip of your files, with no encryption. For one app, press Download readable on Usage. For everything, press Download readable files on Security, under Your data.
- Encrypted is one locked file, and a code shown once. For one app, press Export on Usage. For everything, press Download my encrypted data on Security, under Your data.
A readable download needs your key on this browser. If FKN says this browser doesn’t hold your key, unlock on the Security page first.
Keep an encrypted file together with its code. On an account with no password, use the readable form, because an encrypted file can’t come back after a key reset.
To put a file back, unlock your key on Security, go to Bring a file back, and press Restore from this file. A zip needs nothing else. An encrypted file needs its code and the password you had when you made it.
Remove your data
Section titled “Remove your data”- One file. Delete it in the app that saved it. fkn.app has no delete button for a single file.
- A published file. Delete it in the app that published it. A copy someone already downloaded stays with them.
- Room messages. Go to Rooms, then press Clear to remove a room’s kept messages, or Unclaim to give up the room.
- A site’s cookies and data. On a site you opened through FKN, use Reset site data in the options menu of the bar that names the site.
- Everything. Delete your account.
Optional: How this works
Section titled “Optional: How this works”Your browser creates your key when you create your account. Code from fkn.app then locks each file with it, in your browser, before the file is uploaded. FKN needs a file’s name and size to store it and count it toward your storage, so those stay readable.
A room has its own key. Everyone who has that key can read the room’s messages. An app decides how the key is shared. If it builds the key from the room’s name, anyone who knows the name can work the key out.
FKN’s relay works like a courier with a sealed box: it sees the delivery address and the size, not the contents. The HTTP proxy works more like an assistant who makes the request for you, so it sees the request and the answer.
The proxy keeps answers in a cache so it can serve the same request again, for about an hour, less for an error. That includes answers to requests carrying sign-in details, such as cookies an app sends through it, and such an answer can hold your details on that site. Each answer is sealed: it is encrypted with a key made from the whole request, sign-in details included, and filed under a digest of that request, a short fingerprint of it, not under who sent it. Only an identical request can find and open it.