This site sets one kind of cookie: the one that keeps you signed in. There is no advertising cookie, no analytics cookie and nothing that follows you to other sites. There is no consent banner because there is nothing here that needs consent.

When you sign in we set a cookie holding a session identifier. It is how the next page knows it is still you. Without it you would be asked for your password on every click.

It is marked HttpOnly, so JavaScript on the page cannot read it, and Secure, so it is only ever sent over HTTPS. It expires after thirty days, and signing out removes it immediately.

The cookie holds an identifier and nothing else. Your role, your package and whether your account is active are read from the database on every request rather than carried in the cookie, which is why removing an account's access takes effect at once.

The sign in and sign up forms load Google reCAPTCHA, which tells people apart from automated traffic. Google sets its own cookies when that script runs and their cookie policy governs them. It runs on those two forms and nowhere else on the site.

Nothing at present. The dashboard does not keep drafts or preferences in local storage. If that changes, this section changes with it.

Every browser can block cookies, for all sites or for this one. Blocking the session cookie means sign in cannot work, because there is no other way for the site to know the next request is from you. The rest of the public pages read normally without it.

Blocking Google means the reCAPTCHA check cannot run. The forms still submit when that happens, because refusing a person who blocks a third party script would be a worse outcome than the automated traffic it stops.

If we add a cookie, it is listed here before it ships. The date at the top of this page is when it was last changed.