Privacy policy
Last updated: 29 October 2026
1. In brief
Lexiguesser. processes personal data to provide accounts, retain game progress, operate leaderboards, and offer social features such as friends, messages, duels, and multiplayer.
Lexiguesser. does not sell personal data. When advertising is enabled, the service uses Google AdSense. Google and approved advertising technology providers may process technical data and consent choices to deliver and measure ads, provide security and prevent fraud, and – where you consent – personalise ads.
You may play as a guest without an account. Guest play does not provide a stored account, public result, friends, or progress across devices.
2. What data is processed?
Account and sign-in: Email address, username, internal user ID, registration and sign-in times, session data, email confirmation, password recovery, and account-deletion events. Supabase Auth provides authentication. Lexiguesser. cannot access your password in plain text. Your email is shown only on your own account page.
Profile: Optional profile image, level, progress, any username effect the developer assigns manually, and content selected for your showcase. Uploaded profile images have a publicly accessible URL. When you change or remove the image, the old one is deleted.
Games and progress: Mode, language, times and duration, displayed and answered words, correct and incorrect answers, hints, attempts, scores, bonus events, results, XP, statistics, medals, achievements, word bank, species bank, and word history.
Social features: Friend requests and status, private messages and read status, duel opponent, settings, words, results, and timestamps. A declined friend request is stored with who and when, so the same person cannot ask again within 30 days. Reports of friends, or of someone who has sent you a friend request, store the reporter, reported user, reason, case status, and handling time. Developer mail stores published letters, audience, read status, and any claimed XP gift. Private messages are available to sender and recipient; reports are available to specially authorised developer accounts. Your username can be found through username search.
Multiplayer: In Approxilex, Party, and Tour de Word, the lobby is stored with its code, participants, host role, colour, language, when each participant joined and was last active, answers, votes, and scores. Signed-in players take part under their username. Guests give a guest name, and the server stores only a hash of the guest's key. Signed-in players also get multiplayer statistics such as rounds, wins, and best times.
Activity: When you open the app while signed in, the time and the language you use are stored, at most once a day. The time is not shown to you or anyone else and is used only to warn about and delete accounts that are no longer in use (see section 8).
Abuse prevention: If someone enters a wrong lobby code, a trace of the IP address is stored with the attempt so repeated attempts can be stopped. For guests, requests to the word bank, challenge links, Lexi-Mix, and Globetrotter are also counted per IP address and minute. The address is never stored as it is, only as a hash made with a secret key, which cannot be turned back into the address. The traces are deleted after 15 minutes.
Security and fair play: Focus loss, timing, guesses, hints, leaderboard eligibility, and discrepancies between local and server-calculated scores. This may affect leaderboard display but is not used for decisions with legal or similarly significant effects.
3. Public leaderboard and sharing
A registered user's best eligible rounds in both Classic and Basic may appear on separate public leaderboards with username, any manually assigned username effect, optional profile image, correct-answer count, score, total round time, and the round details shown on the result screen. Others can open your public profile, for example from a leaderboard. It shows your username, avatar, level, profile background, and the content you have selected for the showcase. Time Trial, Lightweight, Guess Five, and Lexi-Mix have no public leaderboard.
You can object by opting out of public leaderboard display on My Page. Enabling the reservation permanently deletes existing entries, blocks new records, and hides your public profile from others while enabled. Disabling it does not restore old entries.
What friends and fellow players see: Friends see the same profile card as the public profile, and whether you are a friend of Lexiguesser. Fellow players in a multiplayer lobby see your username or guest name, your profile image and level, and your answers and scores in the round.
For signed-in users, shared round data is stored in Supabase behind a random, non-listable link ID. It may contain a player name, words, scores, time, and results. Anyone with the link can open it, and the link works for 14 days. The preview image shows only player name, score, and number of words. Guest sharing continues to use a self-contained link carrying the same round data.
4. Local storage on your device
Browser storage is used for language and game settings, the sign-in session, recent words, a temporary registration name, and some local progress values.
Your chosen language is also stored in the cookie lexiguesser_sprak, which holds only the language code (for example en-GB or no) and lasts a year, so the front page can show the right edition without asking again. The first time you arrive at the front page without a stored choice, the site looks at which country the request comes from, as Netlify reads it from the IP address, and which languages your browser lists. If it comes from outside Norway and lists no Norwegian, you are sent to the English edition. The country and the language list are not stored.
Local progress mainly includes Time Trial settings, word history used to reduce repetition, local play time, and some achievement and medal counters used for guest play or as a temporary fallback. Passwords and private messages are not stored as local game progress.
Supabase stores access and refresh tokens for the sign-in session in the browser. Google AdSense and approved advertising providers may use cookies or local storage for ad delivery, measurement, security, and optional personalisation in accordance with your consent choice. In the EEA, choices are collected through Google's certified consent solution before purposes requiring consent are enabled. Clearing browser data may sign you out and reset local progress.
The technologies used for advertising are cookies, local storage, web beacons (pixel images) and your IP address. Third parties, including Google, use cookies to serve ads based on your prior visits to this and other websites; Google's advertising cookies enable Google and its partners to serve ads based on such visits. You can opt out of personalised advertising from Google in Google's Ads Settings and from other providers at aboutads.info/choices. The ad technology providers that may serve ads here are listed in Google's list of certified vendors.
In the EEA, the United Kingdom and Switzerland, your consent choice is collected through Google's certified consent solution and stored in your browser. You can change or withdraw it by reopening the consent choice from the site footer once ads are live, or by clearing the site's cookies so that you are asked again.
5. Why is the data processed?
Account, game, progress, friend, message, duel, multiplayer, and developer-mail data is processed where necessary to provide requested functions under GDPR Article 6(1)(b).
Technical logs, focus events, abuse prevention using IP addresses, result checks, handling of user reports, hidden retention of deleted and edited messages, and recording activity so that accounts no longer in use can be deleted are processed on the basis of the legitimate interest Lexiguesser. has in a secure and fair service that stores no more than necessary, under Article 6(1)(f).
Optional profile images and public showcase content are based on your voluntary choice under Article 6(1)(a) and can be removed. The leaderboard is operated for the legitimate interest of providing a shared competition feature.
Where consent is required for device storage, personalised advertising, or related measurement, consent is the legal basis. You may change or withdraw consent without affecting the lawfulness of earlier processing.
6. Providers and recipients
Supabase provides authentication, accounts, PostgreSQL database, profile-image storage, and sessions. The primary database and storage are in AWS region eu-central-1 in Frankfurt, Germany.
Resend provides email about your account: confirmations and password recovery on behalf of Supabase Auth, and notices before an account that is no longer in use is deleted.
Netlify provides hosting, content delivery, security and access logs, and sharing-preview functions.
Google AdSense provides advertising, a consent solution, ad measurement, security, and fraud prevention. Google and selected advertising technology providers may receive data including IP address, device and browser information, ad interactions, approximate location, and consent choices. See Google's Privacy Policy and advertising information.
Content requests may send ordinary technical data, including IP address, browser information, and time, to Ordbøkene.no, Wiktionary, Wikipedia, Wikimedia Commons, Wikidata, Store norske leksikon, GBIF (tile.gbif.org and api.gbif.org), api.wikimedia.org, and GitHub/Raw GitHub Content.
OpenAI, Anthropic, and their development tools do not receive accounts, messages, or game history through the published service. Data may be disclosed where legally required.
7. Transfers outside the EU/EEA
The primary Supabase database is in Germany. Supabase, Netlify, and their subprocessors may nevertheless process some technical or support data outside the EU/EEA under data-processing agreements and valid safeguards such as the EU Standard Contractual Clauses or adequacy decisions.
Supabase processes some data outside Frankfurt: account and billing, support on request, telemetry and logs (in EU centres), and content delivery (CDN) for stored files. Supabase Pte. Ltd. in Singapore is the main processor, with transfers to Singapore and the United States under the EU Standard Contractual Clauses. Resend keeps the recipient address in its e-mail log for 30 days.
8. Retention
- Account, profile, progress, statistics, word bank, friends, messages, completed duels, and developer-mail receipts remain while the account exists.
- An account that has not been used for two years is deleted automatically. You receive an email when the account has been unused for one year, and again 30 days before deletion. Opening the app while signed in counts as use.
- User reports are deleted 12 months after the case is decided. Cases not yet decided remain until they are. A report is also deleted if either the reporter or the reported account is deleted.
- Declined friend requests are deleted after 30 days.
- Senders can delete individual private messages, and they then disappear for both participants. The text of a deleted or edited message is still kept hidden for 90 days, so the recipient can report something offensive even after it has been removed. No player can see it; only the developer can retrieve it when needed. If a player is reported, a copy of the conversation between the two is kept with the report and deleted when the report is deleted. Messages and copies are also deleted when either participant deletes their account.
- Duels that are not finished are deleted after 14 days without activity.
- Round data on the server, meaning the words shown, answers, timing, and bonus events in a round, is deleted after seven days. The result, XP, and statistics from the round are kept.
- Short sharing links and their round data are deleted after 14 days, and earlier if the account that created them is deleted. Copies and previews may remain with external services and caches.
- Guest rounds in Lexi-Mix are stored briefly to run the round and are deleted automatically within two days.
- Multiplayer lobbies with participants, guest names, answers, and votes are deleted automatically within three days of last use. Signed-in players' multiplayer statistics remain while the account exists.
- The IP traces from wrong lobby codes and the guest counts are deleted after 15 minutes.
- Account-deletion tokens expire after 30 minutes and are removed from the database within a day after that.
- Diagnostic score-engine comparison data is retained for up to 90 days.
- Local browser data remains until overwritten or cleared.
- Provider logs, backups, and caches follow their ordinary security and deletion cycles.
- The developer also takes their own backups of the database before major updates. Only the two most recent are kept.
9. Account deletion
You may request deletion from My Page. A confirmation link is sent to the account email, and deletion happens only after confirmation. The account, all uploaded profile images, and related database data are deleted. This cannot be undone and stored progress is lost.
An account that has not been used for two years is deleted automatically in the same way, after notice by email (see section 8).
Information others already received through messages, screenshots, or shared links may not be retractable.
10. Security
Lexiguesser. uses HTTPS, Supabase authentication, row-level database access, restricted private-data access, and server-side result checks. No online service can guarantee complete security, but Lexiguesser. works to reduce unauthorised access, alteration, and loss.
11. Your rights
Where the conditions apply, you may request access, correction, deletion, restriction, portability, or object to processing based on legitimate interests. You may withdraw your choice to publish optional profile content and change or withdraw advertising choices through the site's consent settings. Contact post@lexiguesser.com. Lexiguesser. may request information needed to verify your identity.
You may also complain to the Norwegian Data Protection Authority.
12. Required data
Creating an account is voluntary. Email, password, and username are required for an account with stored progress and social features. Profile image, showcase content, friends, messages, duels, and sharing links are optional.
13. Children
Lexiguesser. is not intended for children under 13 to create an account on their own. Children under 13 must not register or publish profile content without parental consent.
14. Changes
This notice may be updated when features or processing change. The date above shows the latest update. Material changes will be made clear in the service.
15. Who is the controller?
Lexiguesser. is operated by Matias Willand, who is the controller for personal data processed through the service.
Privacy enquiries may be sent to post@lexiguesser.com.