Privacy

What stays on your device

The site sets no cookies, and its pages keep nothing in your browser — except, if you turn measurement off, the fact that you did.

The player keeps your copy of a game in your browser’s private storage on your machine, along with your saves, your settings and enhancement switches, whether you have answered the copy-protection question, and the text read from your Adventurer’s Journal if you gave it one. None of it is sent anywhere. If you choose a folder for backups, the player copies your saves into it as the game makes them: the browser writes them to your own disk, and the folder’s handle is kept with the rest so it can do so next time. The one way pictures and text of a running game can leave your browser is the assistant prototype, and only if you use it. The site never receives your files, so it has nothing about them to keep, share or lose. Clearing this site’s data in your browser removes all of it, except the backups already in a folder you chose, which are yours to keep or delete.

What leaves your browser

Two measurement scripts from Vercel load on every page: Vercel Web Analytics and Vercel Speed Insights. They record that a page was viewed and how fast it loaded. Vercel receives what any request carries — the page’s address and the one you came from, your browser and device type, your approximate location and the time — and Web Analytics tells visits apart with a short-lived identifier derived from the request, not a cookie. What we see is counts and timings, never a profile of you. Vercel describes each in its own words: Web Analytics (opens in a new tab) and Speed Insights (opens in a new tab).

On the player, Web Analytics also records that a game started running, and whether it was picking up where you left off after your browser brought the page back, that it was still running after each five minutes of play, and that a session ended. The end carries how many minutes the session lasted, how many of them the game was running, a length category, and whether you left, the machine stopped, the player failed, or you swapped or forgot the game. It also records that you gave the player a game or a journal it recognised, and whether that came as a folder, an archive, a file or a link, and that a recognised game was launched, and whether it came from this browser’s storage. Each of those carries the name of the game and nothing about your copy of it: no file names, no hashes, no saves, no text from the game.

If the player stops with an error, it offers to send an error report. Only if you press that button does it send, through Web Analytics, which build of the emulator you were running, whether the player or the site failed, the kind of error, and up to 200 characters of the error’s own message. Before it goes, links and email addresses are taken out of the message, and so are the folders of any path, leaving the file name at its end. The report attaches no game files and no saves, and What the report sends shows it to you before you decide.

Beside it, Report it on GitHub opens a bug form in our public feedback repository with the same details filled in, plus your browser’s user-agent string (its name, version and operating system). Opening that link sends those details to GitHub in its address, even if you never submit the form. Bug reports you do file, like anything you write or attach there, are public, and GitHub’s privacy policy applies.

The site is hosted by Vercel, whose servers see each request in order to answer it. Vercel handles that under its own privacy policy (opens in a new tab). This site keeps no logs of its own.

If you give the player a share link to your game or your journal, your browser downloads it straight from that host (Dropbox, say): the host sees the link and the ordinary details of a connection, such as your IP address, but the request carries no cookies and no referrer, and the file never passes through this site.

Nothing else is loaded: no advertising, no social embeds, no session recording, no third-party fonts. Links to shops are plain links with no tracking parameters.

Your choices

You can turn measurement off in this browser. It then sends nothing to Vercel Analytics or Speed Insights — no page views, no timings, no player sessions, and no error reports — and the site and the player work exactly the same. The choice is kept in this browser under one entry, and if your browser sends Global Privacy Control, measurement is already off.

Blocking the two scripts has the same effect. Clearing the site’s storage removes everything it has put on your device. It does not reach what has already left it: measurements Vercel has recorded, an error report you sent, a bug you filed on GitHub, what the assistant sent to Anthropic or OpenAI on your key, or an email you wrote to us. We can delete an issue in our feedback repository or an email on request; Vercel’s measurements and error reports carry nothing we could find you by.

The assistant prototype

The player has an experimental assistant: an AI model you can ask to do things in the game, which it does by reading the screen, and where the party stands, and pressing keys. It is off unless the player’s address has ?agent in it, and nothing on the site links to it.

It runs on your own Anthropic or OpenAI API key, which is kept in this browser, sent only to that provider, and billed for every request. Using it sends the game’s screen — its text and screenshots — and where the party stands, with the map it has explored and, in a fight, who stands where and what you are aiming at, to that provider, along with what you type and our instructions to the model, straight from your browser and never through this site. Your game files and saves are never sent. What the provider keeps is under the terms of your key (requests to OpenAI are sent with store: false). The conversation ends when you reload, and the assistant sends nothing to Web Analytics.

What changes next

Accounts, cloud-backed saves and advertising are planned. Each would mean collecting something this page does not describe today, and this page will be updated before any of them ships. Last updated 12 October 2026.

Getting in touch

If you email us, your address, your message and anything attached reach us through our mail forwarding provider and the inbox it delivers to. We use them only to answer you, keep them only as long as that takes, and delete them on request.

Questions go to hello@amberfolio.org.