DialectGuessr
← Back to the map

DialectGuessr

Privacy

Last updated 4 September 2026.

What is stored

When you contribute, we store your quiz answers, the submission time, completion duration, and a random browser identifier that is irreversibly hashed on the server. We do not ask for your name, email address, exact street address, precise current location, birth date, or an account.

A hometown is optional. If you give one, we store the town or city you selected as where you grew up and a coarse H3 map cell derived from it. If you choose “Get my result without adding a map pin”, no hometown is stored and none is guessed or filled in on your behalf: the contribution is recorded as having no location, and it is excluded from the map, from the pin count, from area coverage, from head-to-head comparisons, and from the Guessr rounds.

At the final quiz step you may optionally share the town or city where you live now. We store its label, country, town/city coordinates and a coarse H3 cell with your answers to help improve future results. You can leave it blank. It is not shown on the public map or public result, and it is never used to work out your accent match today.

Why it is used

Your answers alone produce your accent result: where you grew up is used for the map, comparisons, and area coverage, and never changes which profiles you match. If you tell us which of the closest profiles fits you best, that answer and a snapshot of what was predicted are stored with the contribution so accuracy can be measured over time. If none of them fit and you name the accent yourself, that short piece of text is stored with it and read only to decide which profiles are missing. A functional draft is stored for up to 30 days so an interrupted quiz can be resumed.

Optional accounts and email

You can play without an account. If you choose to create one, we store your email address, account sessions, saved results, streak and private game history so they can follow you to another device. You can sign in with Google or ask for a passwordless email link. Google supplies the account identifier and email address; Resend delivers requested sign-in links and any daily-puzzle emails you separately opt in to receive. Session and email-link tokens are stored only as hashes. Email links expire after 15 minutes, and browser sessions expire after 90 days.

Requesting a sign-in link does not subscribe you to anything. Daily-puzzle email requires a separate opt-in and can be stopped from the account page or the unsubscribe link in every message. Deleting the account removes its email address, sessions, saved results and game history. It severs the link to an anonymous map contribution rather than deleting that contribution; the private deletion control on your result dashboard removes the contribution itself.

Full Dialect Profile

The optional paid profile stores your extra answers, report, progress and any family hometowns, age band and self-description you choose to give. These details stay in your private profile and do not appear on the community map or free result. A signed browser cookie lets you return without an account. The browser that owns your free result can restore this access.

Stripe processes the one-off payment. We store purchase identifiers, amount, currency and payment status; card details are handled by Stripe. Profile sharing downloads only the selected card: it does not publish your report, age, family towns or access token. We compare age groups only with at least 30 other completed, comparable local profiles; smaller groups receive documented local markers without a generational comparison.

“Delete my paid profile” removes its context, answers, report, purchase access and related profile events. “Remove my data” on your free result dashboard also removes the paid profile. Paid data expires with the underlying contribution after 365 days. Deletion does not issue a refund or erase Stripe’s own payment records. Contact us using the address below for payment support.

Optional analytics

With your permission, pseudonymous events such as quiz starts, completed shares, referral visits, game starts, and completions are recorded to measure which parts of the site people use and whether the sharing experience works. The random browser identifier is hashed before storage. Refusing analytics does not change the quiz or games.

Vercel Web Analytics is used across the site to count page views, visitors, and referring sites. PostHog records page paths, time on site, heatmaps, rage clicks, and session replay so we can see how the quiz and games are used. Separately, completed Classic and Elimination games contribute an identifier-free aggregate row containing the mode, date, and score. Signed-in players also receive private game history attached to their account.

Sharing and public results

If you added a pin, map visitors can see it near your selected city along with aggregated answer patterns, and a shared result exposes that city label and the calculated matches. A contribution with no location has no pin and no city label to expose. In both cases the public result API does not expose your raw answers, browser identifier, completion time, or legacy profile fields. Share links are public to anyone who receives them.

Retention and deletion

Contributions are automatically removed after 365 days, drafts after 30 days, and optional analytics and identifier-free game completion rows after 395 days. The browser that submitted a result receives a private deletion token; use “Remove my data” at the foot of that result’s dashboard to delete the contribution and related events immediately, whether or not it has a location attached. The same token is what authorises adding or clearing the optional current country. Keep the token private—it is not recoverable if browser storage is cleared.

Contact

Privacy contact: louisforster208@gmail.com.