RELEASE
Sign in

Cookies

Three cookies.
Every one of them does a job.

You will not find a consent banner with an “accept” and a “reject” on this site, and the reason is not that we skipped it. The cookies below are strictly necessary for something you asked for — signing in, keeping your work yours before you have an account, and remembering the language you chose. There is nothing here to reject: switching them off would not protect you from anything, it would just break the product.

rel_sidAnonymous session90 days

Set the first time you upload something. It is what lets you create and configure a payment link before you have an account — and, on the other side, what binds a client to the purchase they just made so their files stay reachable.

Without it: You would have to create an account before you could try anything, and a client who paid would lose access to their download on refresh.

first-partyhttpOnly — unreadable by any script, including ourssameSite=lax

rel_sessionSigned sign-in30 days

Holds your creator account id, cryptographically signed so it cannot be edited or forged. It is the cookie that keeps you signed in.

Without it: You would be signed out on every page you open.

first-partyhttpOnly — unreadable by any script, including ourssameSite=lax

rel_langThe language you chose1 year

Only written when you pick a language from the switcher yourself. Until you do, the language is guessed from what your browser asks for and nothing is stored — guessing is fine, recording a guess as your decision is not. It holds a language code and nothing else: no id, no name, nothing that identifies you.

Without it: The site would go back to guessing on every visit, and would override a choice you had already made.

first-partyhttpOnly — unreadable by any script, including ourssameSite=lax

What is not here

If you delete them

Nothing is lost. Clearing cookies for this site signs you out and detaches any draft you had not yet claimed with an account; everything already tied to your account is untouched, because it lives in the database rather than in your browser. Sign in again and it is all there.

If this ever changes

If RELEASE ever adds a cookie that is not strictly necessary — analytics, for instance — it will appear in the table above and it will ask first, with a real choice that is honoured.

This page said “exactly two” until the day the interface learned to speak other languages and a third arrived to remember which one you picked. It is listed above, on the same day it shipped. That is the whole point of writing the number down: a page that counts its cookies out loud cannot quietly grow one.

More on what we store and why: Privacy · Terms of use