Cookies
This site sets three cookies. They keep you signed in, protect forms against cross-site request forgery and remember your cookie choice. There is no advertising, no analytics, no tracking pixel and no third-party script of any kind. The site's Content-Security-Policy forbids loading one, with one exception: when you choose to pay for a coffee, the payment window loads Stripe's script, on that page only and only once you click.
What is stored
| Name | Purpose | Expires | Set by |
|---|---|---|---|
| tjb | Holds your sign-in session and the anti-CSRF token. Without it you cannot stay logged in or submit a form. | When you close your browser | This site (first-party) |
| tjb_remember | Keeps you signed in after you close your browser. Set when you sign in, deleted when you sign out. It holds a random token, never your password. | 60 days | This site (first-party) |
| tjb_consent | Remembers the choice you make below, so you are not asked on every page. Set only once you answer. It holds your answer and its date, nothing that identifies you. | 6 months | This site (first-party) |
Flags actually set on the first two: HttpOnly (unreadable to JavaScript), SameSite=Lax, Secure (HTTPS only). The choice cookie is SameSite=Lax and Secure but not HttpOnly: it holds no secret.
Paying for a coffee. Only if you open the payment window on /coffee, Stripe's script sets its own fraud-prevention cookies (__stripe_mid, one year, and __stripe_sid, 30 minutes), which are strictly necessary to take a card payment you asked for. They are Stripe's, under Stripe's cookie policy; we do not read them. Nobody who does not open the payment window gets them.
Your choice
The strictly necessary cookies above are set without asking, which the ePrivacy Directive and the GDPR allow: a cookie required to deliver a service you requested is exempt, and a sign-in session is the standard example. Declining it could only mean the site does not work.
Everything else is yours to decide, and nothing optional runs until you decide it. Silence counts as no. You can change your mind here at any time, and refusing is one click, exactly like accepting.
What analytics would collect, if you allow it
Nothing, today. No analytics service is configured, so allowing the category currently changes nothing and no third-party script is loaded for anyone. It is offered because that is expected to change; when it does, your recorded answer already governs it and this page will name the service.
Related storage
The library itself stores nothing in localStorage, sessionStorage or IndexedDB. Model previews are decrypted in memory and discarded; nothing about them is written to your device.
The Experiences are the exception, only once you open one: a game such as Cozy Isle keeps your progress (coins, fish journal, settings) in your browser's localStorage so it is still there next time. It never leaves your device and we never see it; clearing the site's data in your browser resets it.
Signing in with Google sends you to Google, who set their own cookies under their own policy while you are on their page. We receive only your email address, name and a Google account identifier, never a Google cookie. No Google script runs on this site as part of signing in.
Paying for a coffee happens in Stripe's payment window, described above. Card details go straight to Stripe and never reach this server. We store only the references Stripe gives us for your coffees, so a monthly coffee can be stopped from your account.
Refusing or removing them
Every browser can block or delete cookies for a single site, and doing so here is safe: you will be signed out and unable to sign back in, but nothing is lost. Browsing and previewing models works signed out.