Cookie Notice

Last updated: November 13, 2026

This notice explains the cookies and similar technologies Bit Models uses. Cookies are small files a website saves in your browser; your browser’s local storage, session storage and IndexedDB work in a similar way.

We use only what Bit Models needs to work. We don’t use analytics, advertising or tracking cookies, so we don’t ask for your consent. How we handle personal data is explained in our Privacy Policy.

What we use

1. Cookies and storage set by Bit Models

  • bit-models-session · cookie · 24 hours
    Keeps you signed in. It is sealed, so only our server can read it. For a few minutes it also remembers a step in progress, such as setting up an authenticator app, or why a sign-in was refused.
  • sign_in_code · cookie · 15 minutes
    Links the sign-in code we emailed you to this browser, so the code works only here.
  • age_confirmed · cookie · 1 year
    Remembers that you confirmed you are 18 or older, so this browser is asked only once.
  • payout_draft · cookie · 2 minutes
    Creators only: if a payout address you entered is refused, puts it back in the form so you don’t have to paste it again.
  • report_already · cookie · 30 seconds
    Tells the next page that you have already reported this.
  • wallet-sign-in · session storage · used for 5 minutes, deleted when you close the tab
    Remembers that you chose to sign in with a wallet, so the sign-in continues when you come back from your wallet app.
  • wallet-top-up · session storage · used for up to 15 minutes, deleted when you close the tab
    Shows a top-up you sent from your wallet while the network confirms it.

2. When you connect a crypto wallet

Nothing in this section is loaded until you choose to sign in or top up with a crypto wallet (or, if you used a wallet here before, until you sign out: then it loads to disconnect your wallet). Then the code that connects wallets is loaded and keeps, in your browser’s local storage and IndexedDB, which wallet you connected and the connection, so it keeps working from page to page:

  • wagmi and RainbowKit, which connect wallets to Bit Models: entries whose names start with wagmi. and rk-.
  • WalletConnect, which connects a wallet on your phone: the WALLET_CONNECT_V2_INDEXED_DB database.
  • The code of Coinbase Wallet (entries starting with cbwsdk) and, if you choose MetaMask, of MetaMask (entries such as .sdk-comm).

Some of these are created as soon as the code loads, before you pick a wallet. They stay until you clear your browser’s data; signing out of Bit Models disconnects your wallet. We have turned off the usage statistics this code can send to its makers. The wallet you pick may keep its own data, and Coinbase Wallet opens a window on Coinbase’s website, which uses Coinbase’s cookies (Privacy Policy, section 6).

3. Videos

Videos play in a player from Cloudflare Stream, the service that stores our videos. [whether the player stores anything in your browser]

4. The sign-in check

On the sign-in page, a check from Cloudflare (Cloudflare Turnstile) tells people from bots. Its script is not loaded when you open the page. It loads only when you send your email, when a wallet signs in for the first time, or each time a smart wallet (a wallet run by a contract, such as a Safe) signs in. Then your browser talks to Cloudflare, which receives signals from your browser and device and your network (IP) address (Privacy Policy, section 6). If you have already signed in here with an ordinary wallet, you don’t see this check. Cloudflare says the check relies on cookies and local storage in your browser to keep its state, and that what it collects is strictly necessary to tell people from bots. Cloudflare doesn’t publish the names of what the check stores or how long it keeps them. [names and lifetimes, if Cloudflare gives them]

5. Your choices

You can block or delete cookies and other site data in your browser’s settings. If you block ours, you can’t sign in, and you’ll be asked to confirm your age on every page.

6. Changes

If we ever want to use cookies that Bit Models doesn’t need to work, such as analytics, we’ll ask for your consent first and update this notice.

Contact us

Questions about cookies or your data: [privacy email address].