frisk

No. The uploader on the front page works with no signup at all. An account is optional and only adds a dashboard for tracking and deleting your own uploads.

No. Your address is hashed the moment a request arrives, and only the result is used. It is never written to the database, never written to the logs, and is discarded before anything else in the application sees it.

Being straight about what that does and does not mean: the hash is a stable pseudonym, so two uploads from the same connection produce the same value and can be recognised as the same client. That is what makes quotas and bans work. What it cannot do is be turned back into an address — it is keyed with a secret that is not in the database, so someone holding a copy of the database cannot reverse it or test a guess against it.

• The client pseudonym described above.
• A random frisk_client cookie, set on your first upload and kept for 7 days. It contains no personal data; it exists to count usage against the quota and to avoid counting one visitor repeatedly.
• The file's name, size and type, and a checksum of its contents.

All of it is attached to the upload and deleted with it. The counters behind the quota are dropped after 24 hours and the visit markers after two days.

Yes. Files are compressed and then encrypted with AES-256-GCM before they touch the disk. Every file gets its own key, and that key is itself stored encrypted under a master key held in the server's configuration rather than in the database.

So a stolen disk, a leaked backup or a copy of the database on its own yields nothing readable. Deleting a file destroys its key along with it, which makes any stray copy of the stored bytes permanently undecryptable.

The encryption is also authenticated: if stored bytes are altered, reading fails outright rather than returning something subtly wrong.

Yes, and it would be dishonest to imply otherwise. The server holds the keys, because it has to decrypt files to serve them. The encryption protects your files from anyone who gets at the storage; it does not protect them from whoever runs the service.

This is not end-to-end encryption. If a file needs to be private from us as well, encrypt it yourself before uploading — we will happily store bytes we cannot read.

None. No analytics, no advertising, no tracking scripts, and no embedded third-party content of any kind.

Fonts are served from this site rather than from Google Fonts, so loading a page contacts nobody but us. A content security policy blocks the page from making outside requests even if something later tried to.

The time, the method, the response status, how long the request took, and the client pseudonym. No addresses.

File identifiers are stripped out of logged paths as well, so the logs cannot be used to work out which client downloaded which file. They also rotate on a size limit rather than being kept forever.

For an anonymous upload: the file, its name and size, when it was uploaded, and an opaque pseudonym. There is no address to hand over, because none was ever written down. Nothing in our records points at a person, a location or a network.

For an upload made while signed in, the account's username is attached to it. We hold no email address, so the account carries no identity beyond the name you chose.

No. Registration is a username and a password, nothing else — no email field, no verification, no mailing list.

The trade-off is that there is no password reset. With no email on file there is no way to prove an account is yours, so a lost password means a lost account.

There is no automated scanning, classification or content matching of any kind.

One thing worth knowing: a checksum of each file's contents is stored so that identical uploads can share a single copy on disk instead of being stored twice. A side effect is that identical files are recognisable as identical.

Every upload gets a random 11-character identifier. Links are not listed anywhere, and there is no way to browse or search what has been uploaded.

They are unlisted rather than protected: anyone holding the link can download the file, and there is no password on it. Pages also send no referrer, so following a link from a Frisk page does not tell the destination where you came from.

If you uploaded it while signed in, yes — from your dashboard, at any time. The file and its encryption key are both destroyed.

Anonymous uploads have no owner attached, so there is nobody a deletion request can be verified against. Those come down on their own schedule. If something needs removing urgently, email abuse@frisk.page.

Up to 2 GB per file, and 4 GB in total per 24 hours. The rolling allowance applies whether or not you are signed in.

A file that is never downloaded is removed after 24 hours. After its first download it keeps a window that grows with how many people visit it in its first 14 days:

A visitor counts once per hour, so refreshing your own link will not extend it.

No. Compression uses Zstandard, which is lossless, and encryption is applied after it. What you download is byte-for-byte what you uploaded, and downloads support resuming and seeking.

Any file type, within the size limit. The one exception is uploading by URL, which rejects HTML pages and streaming playlists — that feature is for fetching a file, not mirroring a page.

Email abuse@frisk.page with the link and what is wrong with it.