What we store
Last updated 29 Sep 2026
The short version
Peekle has no accounts. You never give us a name, an email, or a password, because there is nowhere to put one. There are no cookies, no advertising, and no third-party fonts. Two things do leave: Peekle counts visits with Google Analytics, set up so that it stores nothing on your device, and a description you write is graded by an AI. Both are described under What leaves Peekle.
On your device
Nearly everything Peekle knows about you lives in your own browser, in two entries of its local storage:
-
peekle.playHistory— a random id your browser generates for itself, plus your last 400 days of play: the date, your score, what you wrote or which choices you picked, and the picture's description so you can read your results again later. -
peekle.inProgress— a note that you started today's puzzle, so refreshing mid-play returns you to the questions instead of handing you another twenty seconds with the picture. It's erased the moment you submit.
Your streak and your average are calculated from that history on your device. Nothing on our side knows or keeps them.
On our server
When you load a puzzle and when you submit one, we store a row in a database (Amazon
DynamoDB, in AWS's us-east-1 region) recording that the random id above visited
and played that day, and a row holding what you submitted: the text you wrote or the choices
you picked, your score, and the time. That's the whole list.
Those rows let us count how many people played on a given day and check that the scoring is fair. They have no expiry set, so assume they're kept as long as Peekle runs. They are never sold, shared, or used for advertising.
The id is a random number your browser made up. It isn't tied to a name, an email, an account, or your device's identity, and nothing in Peekle ever tries to work out who is behind it. It exists so a submission has somewhere to be filed.
What leaves Peekle
Counting visits
Peekle loads Google Analytics, which tells us how many people arrive, which links they arrived from, and how many of them go on to play. We added it to find out whether telling people about Peekle actually works; without it a link posted somewhere is indistinguishable from a link posted nowhere.
It is configured to store nothing on your device — no cookie, no identifier, nothing written into your browser. That is a deliberate trade: it means Google cannot tell one of your visits from another, so we cannot see returning visitors in it, and it also means there is no consent banner standing between you and the picture. Google receives your IP address, the address of the page, the site you followed a link from if there was one, and the general shape of your browser and device.
On top of the page load it records five things you do, and nothing else: which mode you chose, that the picture was shown, that you submitted — with the number of stars you earned, from zero to five — which button you used to share, and whether you came back on a day you had already played. What you wrote, which choices you picked, the day's picture and its list of facts are never sent to Google, and neither is the random id described above.
Grading what you wrote
If you play by writing what you saw, your description is sent to Anthropic's API, where a Claude model checks it against our list of things that were in the picture and reports which ones you mentioned. Only the picture's fact list and your text are sent — not your id, and nothing else about you.
If you play the quiz, nothing leaves our server at all: the answers are checked against the key directly, with no AI involved.
What we don't collect
No contacts, no device fingerprint, no advertising identifier, no cross-site tracking, and nothing sold or handed to advertisers. Google Analytics derives a rough location from your IP address, at about the level of a city; nothing else asks where you are. We haven't enabled request logging at our CDN or our API, so beyond the analytics described above we keep no record of individual page loads. As with every website, the servers delivering Peekle to you necessarily see your IP address in order to send you a response — we don't store it, look at it, or use it for anything.
Deleting it
Clearing your browser's site data for peekle.io erases all of it on your side: the history, the streak, and the random id itself. Your next visit mints a new id and starts a fresh history, with no way for us — or anyone — to connect it to the old one.
The rows already written on our side stay, attached to an id that by then exists nowhere. Since that id is the only thing they carry, there is no account to close and nothing to look you up by.
One honest note
The one-play-a-day limit is kept in your browser, not enforced on our server. That's a deliberate choice — enforcing it properly would require accounts, and Peekle would rather not have them. It means the limit works on the honour system, and clearing your site data will let you replay a day. We'd rather tell you that than pretend otherwise.
Changes
If what Peekle stores changes, this page changes with it and the date at the top moves. Peekle is a small side project rather than a company; this page describes what the code actually does today, in plain terms, and is not a lawyer's document.