What is kept, and why

The short version

The daily puzzle is worked out in your browser from the date, so the whole game runs without an account. Sign in and a handful of rows are kept so a streak can follow you between devices. That is the entire purpose of the data described here.

Playing without an account

No account is needed. The board, the clock, your streak and your practice results are written to this browser and stay there.

One exception, stated plainly: when you finish the daily, the app posts the result to the server without first checking whether you are signed in — the play pages are served from a CDN and the sign-in cookie is deliberately unreadable by page scripts, so the page genuinely cannot tell. If you are signed out, the server refuses that request and keeps nothing from it.

Who is responsible, and how to reach them

This policy covers beFoQuSed, the site at befoqused.com. For anything on this page — a copy of your data, an erasure, a correction, or a question about how any of it works — write to contact@befoqused.com. That address is the controller’s contact point for privacy requests, and it is read by a person.

You can exercise the copy and erasure rights yourself, immediately, in account settings — you do not need to write to anyone first, and doing it yourself is faster. The address is there for everything the controls do not cover.

If you think this site has handled your data wrongly, you have the right to complain to your national data protection authority, and you can do that without contacting us first.

What the server keeps once you sign in

• Your email address as Google reports it, and whether Google says it is verified. It has one job: recognising which account is yours the next time you sign in. It is never displayed to anyone, and no email is ever sent to it.
• Your display name — the one name the product actually shows. It starts as the generated pseudonym below, but account settings lets you switch it to your Google name or to one you type; which of the three you are currently using is stored alongside it, so settings can show the right option selected.
• The pseudonym generated for you when the account was created — two words and a number, in the shape of SwiftHeron42. It is kept even after you switch to a different name, so switching back returns the name you started with rather than a new one.
• The name and profile-picture address Google returns with the sign-in, which the sign-in library records on the account row. Both are shown — the name as your display name, the picture on your account page — if and only if you choose your Google name in settings; otherwise neither appears anywhere in the product. They appear in your data export regardless, because they are held whether or not they are in use.
• The Google account identifier and the sign-in tokens that come with it, which are what let a session be established without asking you to sign in again.
• One row per live sign-in session: an opaque token, which account it belongs to, and when it expires. The cookie in your browser carries that token and nothing else.
• One row for every daily puzzle you solve: which game, which day in UTC, which difficulty, how long the solve took, how the row reached the server, and when it was written. At most one row per game per day.
• Your current and longest streak for each game, and the last day you solved.
• The date the account was created.

What other players can see

Today, nothing. No other player can see your display name, your Google name, your streak, or anything else about your account — there is no leaderboard, no profile page, and no way for one account to look up another.

That changes once leaderboards arrive: a display name is shown next to a rank, visible to anyone. That is why which name shows is the player’s choice to make — the generated pseudonym, your Google name, or a name you type, in account settings.

Signing in after playing as a guest

If you played on this browser without an account and then sign in, the daily history saved here is offered to your account once: up to the last thirty solves plus the streak counters. Anything a browser reports is marked as such, and marked rows may add a day the account lacks or raise a streak, never overwrite a day already recorded — nor will they ever count towards a ranked board. A browser’s history belongs to one account only, so if somebody else signs in on the same browser nothing is offered.

What stays on this device

These live in this browser’s local storage, under keys beginning game:v1:. The daily history in the section above shares that prefix and is the one exception — it is offered to your account at sign-in. Everything in this list is not, and never leaves the device:

• Unfinished daily boards — the grid you are part-way through, and its clock.
• Practice: the run in progress, and your best time and solve count per difficulty. Practice is unranked and the server never hears about it.
• The difficulty you last chose, for each game.
• Your light or dark theme choice.
• Your analytics preference.

Clearing this site’s data in your browser removes all of it, including the daily history.

Analytics

Visits are counted with Vercel Web Analytics, which is cookieless: it stores nothing on your device, and it cannot recognise you on any other site.

It is not merely a tally, and it would be an understatement to call it one. Vercel documents that each page view records which page was opened and which site referred you, alongside facts read off the request itself — country, operating system, browser and device type. Returning visits within a day are recognised through a hash Vercel computes on its own servers from the request and a salt it changes daily, so nothing is written to your device and one day’s figures cannot be joined to the next.

It runs unless you switch it off. The switch is here, and the same one is in account settings. The preference belongs to this browser rather than to an account, and it is honoured whether or not you are signed in, so you do not need one to use it.

Using it reloads the page. That is the point rather than an inconvenience: switching it off has to stop the script loading at all rather than load it and ask it to stay quiet, and a script already on a page cannot be taken back off it.

Cookies

A visitor who never goes near sign-in is given none at all. Signing in involves four, and every one of them is strictly necessary to sign you in or to protect the sign-in from abuse. None is used for analytics, advertising or measurement of any kind; all four are unreadable by page scripts and are sent only to this site.

• authjs.csrf-token — proves a sign-in or sign-out request came from this site rather than another one. Written the moment you reach the sign-in page.
• authjs.callback-url — where to return you once Google sends you back. Written at the same moment.
• authjs.pkce.code_verifier — a one-time secret binding the code Google returns to the request that asked for it. Added when you are sent to Google, lasts fifteen minutes, and is thrown away the moment you return.
• authjs.session-token — written once you are signed in, and the only one that outlives the sign-in. It carries the token for the session row listed above. Signing out ends both.

On the live site the first three reach you with a __Host- or __Secure- prefix, which is a browser-enforced restriction on how they may be sent. Analytics adds nothing to this list.

Taking a copy of everything

“Download your data” in account settings gives you a JSON file containing everything the server holds about you: your profile, the linked Google account, every solve and every streak. Two things are left out deliberately — the sign-in and session tokens, which are secrets rather than facts about you, and anything from the device list above, which never reached the server in the first place.

Erasing your account

The delete control in account settings removes the account row and, by cascade, the linked Google account, every session, every solve and every streak. It is one statement, it takes effect immediately, and it cannot be undone or recovered. You are signed out as part of it. Anything still in this browser is yours to clear.

Your display name is your choice, changeable at any time in account settings — the generated pseudonym, your Google name, or one you type. Switching back to the generated name returns the one you started with, not a new one.

How long it is kept

Server rows are kept until the account is erased — solves and streaks have no automatic expiry, because carrying a streak forward is what they are for. A sign-in session lapses after twenty-four hours without a visit, and signing out ends it at once. What is on this device lasts until you clear it.

Who else is involved

• Google — sign-in only. Google tells this site who you are; this site tells Google nothing about your play.
• Neon — the hosted PostgreSQL database the rows above live in.
• Vercel — hosting, delivery, and the analytics described above. Serving a page necessarily means Vercel handles the connection it arrives on, including your IP address.

That is the whole list. Nothing is sold. Nothing is shared with advertisers or data brokers, and no advertising or tracking script runs on any page.