Cookie Notice

Legal

Last updated: September 23, 2026

1. What Cookies Are

A cookie is a small text file that a website asks your browser to store and send back on later requests. Cookies are what let a site recognise that a series of requests comes from the same signed-in person, rather than treating each page load as a stranger.

Related technologies do a similar job without cookies. Local storage and session storage keep small values in your browser, but unlike cookies they are never automatically transmitted to a server.

2. Our Position on Cookies

We use cookies only where they are strictly necessary to provide the service you have explicitly requested. We do not use them to measure your behaviour, to build a profile, to recognise you across other websites, or to sell or share anything about you.

Because every cookie we set is strictly necessary, we do not ask for consent to set them, and you will not see a consent banner. This follows Article 5(3) of Directive 2002/58/EC and the corresponding national provisions, which exempt storage that is strictly necessary for a service the user has expressly requested.

3. Cookies We Set

Authentication and session

Session token Keeps you signed in after you authenticate with Discord, so you do not have to sign in again on every page. Strictly necessary. Set only after you sign in, and cleared when you sign out. HTTP-only, so page scripts cannot read it.

CSRF token Protects sign-in and account actions against cross-site request forgery, an attack where another site tries to make your browser perform an action on this one. Strictly necessary. Session lifetime.

Callback URL Remembers where to return you after the Discord sign-in flow completes, so you land back where you started. Strictly necessary. Session lifetime.

Invite flow

invite_code Carries the invitation code you entered across the redirect to Discord and back, so your invite can be applied when you return. Strictly necessary. HTTP-only and expires after five minutes.

All of the above are first-party cookies, set on isafemboy.gay, marked SameSite=Lax, and transmitted only over HTTPS in production.

4. Local and Session Storage

We store a few interface preferences in your browser rather than on our servers. These never leave your device and are not sent to us:

  • Theme preference (light or dark), so the interface does not flash the wrong theme on load
  • Accent colour and dashboard display preferences
  • Language preference
  • Acknowledgement of a content warning on a member page, remembered for the current browser session only

You can clear these at any time through your browser's site data settings. Clearing them resets your preferences but does not affect your account.

5. Third-Party Cookies

We do not embed third-party cookies on our own pages. However, two situations involve other parties:

Discord sign-in. When you authenticate, you are on Discord's own domain, and Discord sets its own cookies there under its own privacy policy. We neither control nor receive them.

Embedded and linked media on member pages. If a member embeds or links external media, your browser contacts that provider directly when the page loads. That provider may set its own cookies and will see your IP address. This is a direct connection between your browser and them, governed by their policy, not ours.

6. How to Control Cookies

Every major browser lets you view, block and delete cookies, usually under Settings, then Privacy. You can block all cookies, block third-party cookies only, or delete the cookies for a single site.

Some browsers send a Do Not Track or Global Privacy Control signal. We do not track you in the first place, so these signals do not change what we do.

7. Changes to This Notice

If we add, remove or change a cookie, we will update this notice and its date. If we ever introduced a cookie that was not strictly necessary, we would ask for your consent before setting it and give you a way to withdraw that consent.

8. Contact

Questions about this notice can be sent through our official Discord server or the contact form at /contact. Our Privacy Policy explains the wider picture of what personal data we process and why.