Cookie Policy

That is why you have not been shown a cookie banner. It is not an oversight: consent is required for cookies that are not strictly necessary, and Reisle does not set any.

All of these are first-party, and all of them are HttpOnly — readable by the server, never by scripts running in the page. Over HTTPS they are also marked Secure, so the browser will not send them over an unencrypted connection.

__Secure-authjs.session-token

Keeps you signed in. Holds your signed session token — the site reads it on every request to work out who you are.
Lasts: 30 days, extended each time you use the site

__Host-authjs.csrf-token

Protects against cross-site request forgery: it proves a form submission came from Reisle and not from another site acting as you.
Lasts: Until you close your browser

__Secure-authjs.callback-url

Remembers the page you were heading for, so signing in returns you there.
Lasts: Until you close your browser

__Secure-authjs.state

Set only if you sign in with Google or Apple. Ties the response coming back from them to the request you started, so someone else's sign-in cannot be substituted for yours.
Lasts: 15 minutes

__Secure-authjs.pkce.code_verifier

Set only if you sign in with Google or Apple. Proves the code returned by them is being redeemed by the same browser that asked for it.
Lasts: 15 minutes

__Secure-authjs.nonce

Set only if you sign in with Google or Apple. Stops a sign-in response being replayed.
Lasts: Until you close your browser

If you never sign in, the only cookie you are likely to meet is the CSRF token. The rest are set as part of signing in.

Your light/dark theme preference is stored in your browser’s local storage under reisle-theme. It is not a cookie and is never sent to us — it exists so the page does not flash the wrong colour scheme while it loads. Clearing your browser’s site data removes it, and the theme falls back to your device setting.

Reisle itself sets no third-party cookies. There is one place another company’s cookies appear: the checkout page, where PayPal’s payment buttons and approval window are loaded from PayPal and run inside their own frame.

PayPal sets its own cookies there, on paypal.com, to run the payment and to detect fraud. We cannot read them and they are not under our control — PayPal is responsible for them under its own cookie statement. You will only meet them if you go to checkout.

Signing in with Google or Apple sends you to their sign-in pages, where their cookie policies apply in the same way.

Every browser lets you see, block and delete cookies — usually under Settings, then Privacy. aboutcookies.org has instructions for the common ones.

• Blocking Reisle’s cookies will stop you signing in. Because they are the mechanism that keeps you signed in and protects your session, there is no version of the site that works without them.
• Deleting them signs you out. Nothing else is lost — your account, listings and orders are on our server, not in the cookie.
• Signing out clears the session cookie. To clear it everywhere at once, use sign out of all devices.

If we ever add a cookie that is not strictly necessary, we will ask for your consent before setting it, and this page will say what it is and what it does. The date at the top tells you when it last changed.

Questions about anything here: hello@reisle.je. See also the Privacy Policy for what we do with personal data generally.