Privacy

Last updated:

Blobbu is a small static website. It has no accounts, sets no cookies, and runs no tracking scripts or ads. Visit counts come from the host's server logs (see Netlify, below). This page explains what happens to the little bit of data it does touch. One small thing is stored on the server: the arena list of recent Blobbu codes, explained below.

Your Blobbu lives in the link

Your quiz answers, a random number (the "salt") and your Blobbu's name are put in the part of the web address after the #, for example #b=1govtnq4fcedgto2lxqac&n=Smokey (older links look like #a=0123&s=1x2y3z&n=Smokey). That part is called the fragment. Browsers don't include the fragment when they request a page, so it isn't sent to the server that hosts Blobbu. The Blobbu is drawn entirely in your browser.

The fragment does stay in the link itself. If you share the link, whoever receives it, and any app or service you use to send it, can see the answers and the name. Your browser may also keep the link in its history like any other page. The name is whatever you type, so don't use anything you wouldn't want in a link.

Saved Blobbus (only if you say yes)

Blobbu saves nothing in your browser unless you choose Allow in the storage notice. The notice doesn't pop up when you arrive: it appears when you first try to save a Blobbu, restore a backup or turn the sound off, or when you open Storage settings. If you choose Allow:

To delete it, use Clear my data in the Menu, or choose No thanks in Storage settings. Both remove the key completely. Clear my data also removes an arcade cabinet's local record (below) if this browser holds one. Clearing your browser's site data for Blobbu does the same. If you choose No thanks, nothing is stored, so your choice isn't remembered and you'll see the notice again the next time you try to save on a later visit.

The arena (the 20 latest Blobbus)

When you hatch a new Blobbu, the app sends its 21-character code to Blobbu's server, for example 1govtnq4fcedgto2lxqac. The code is your four quiz answers plus the random number (salt). It is the only thing sent and the only thing kept:

The list is kept with Netlify (Netlify Blobs, part of the hosting). As with any request, Netlify's server logs record the request itself (see Netlify, below).

Battle honors need no storage. When a Blobbu wins, Keep the honor adds the beaten Blobbu's code to the winner's link (w2=…; links made before October 14, 2026 use w=…). The browser re-runs the battle to check it, and the beaten Blobbu's code is visible to anyone you share that link with.

Ascension needs no storage either. Clearing the arcade's Gauntlet adds the day's date to the Blobbu's link (asc=2026-10-18), and any page that opens it re-runs that day's ladder to check it. If you save an ascended Blobbu, the date is saved with it, like an honor. A Gauntlet run itself lives only in the arcade page's memory and is wiped with the rest of the game.

The hatch API (for AI agents)

AI agents can hatch a Blobbu with one request to /api/hatch. The request carries the quiz answers and a name, if one is given, in the address. A small Netlify Function rolls the Blobbu and sends it back. It stores nothing, calls no other service, and doesn't add the Blobbu to the arena. Like any request, it may appear in Netlify's server logs (see Netlify, below), so names shouldn't contain personal details.

Sharing and downloads

Share opens your device's own share sheet if it has one; otherwise it copies the link, with a short intro and #MyBlobbu, to your clipboard. Challenge a friend (after a battle) copies the battle link and a one-line taunt. Either way, Blobbu hands the link to your device and nothing goes to us. What happens next depends on the app you pick. PNG and Card create their images in your browser and download them to your device. Downloaded images carry a small "blobbu.net" mark.

Share codes. The Share code pill, the trading card and the system card show a QR code for your Blobbu's share link, with the Blobbu in the middle. The code is made in your browser; nothing is sent anywhere to make it. Like the link itself, it contains the Blobbu's code and name, so anyone who scans a card you post can open that Blobbu.

Mini games. The arcade's mini games run in your browser. A run and its score exist only in the page's memory and on the sticker you print; nothing is saved or sent.

Stickers, badges and the arcade. Stickers, die-cut stickers, winner stickers, honor badges, the card back and the sticker sheet are drawn in your browser from your Blobbu's code. The sticker sheet uses the Blobbus you already saved on this device; nothing new is stored. The arcade page (blobbu.net/arcade) is the same app made into a cabinet: a splash screen, PRESS START and big buttons. A game exists only in the page's memory while someone plays; nothing is saved, the arcade never shows Blobbus saved on that device, and after the end screen or a minute without a touch (two during a battle) it wipes the game and goes back to the splash. Scanning a code there reads the picture on the device; it is never uploaded. Its print options, how long it waits and whether it starts muted are part of its link (set up at blobbu.net/arcade?setup). The operator can also press Save on this cabinet there: the same settings (no player data) are then kept in that browser's local storage under blobbu.arcade.v1, so opening blobbu.net/arcade on that machine starts with them; Forget saved settings or Clear my data removes them, and they are never sent anywhere. While it is open it asks the browser to keep the screen awake; nothing is recorded. The Advanced printing setting is remembered only if you allowed storage, like the Sound setting. The arcade's Dark/Light button lasts only for that session; its starting theme is part of its link. One opt-in exception: a cabinet's operator can switch on a local record at setup — per Blobbu, its battle wins and losses and Gauntlet best at that cabinet — stored in that browser's local storage under its own key, blobbu.records.v1 (keyed by each Blobbu's code; no names, no times), shown at the cabinet's hub, and cleared by the setup page's Clear button when it is opened on the cabinet itself, or by Clear my data in that browser. It is never sent anywhere, and it is off unless the operator turns it on in the link. The same goes for the cabinet's high-score table, a second opt-in at setup: each mini game's ten best runs at that cabinet — the Blobbu's name, the score and the date, nothing else — stored in that browser's local storage under blobbu.board.v1, shown on the cabinet's splash and score screen, cleared by the setup page's Clear button on the cabinet or by Clear my data in that browser, never sent anywhere, and off unless the operator turns it on in the link.

Seasonal costumes. For a few weeks a year (Halloween: October 15 to 31) some Blobbus wear a costume, picked from the date and the Blobbu's own code. Nothing about you is used, and a Blobbu's stats and battles never change.

Scan a code. In Battle, Scan a code lets you take a picture with your phone's camera app, pick one, drop one in or paste one. The picture is read in your browser to find the code, then thrown away. It is never uploaded or stored, and the site never gets live access to your camera.

Chat, status page and other extras

Other companies involved

The Inter font is served from this site itself, so loading the page doesn't contact any font service.

Changes

If any of this changes, this page will be updated and the date at the top will change.