Support

Privacy

This privacy page is written for Dont Wordle specifically. It explains the small set of data flows that matter on this site: browser-side gameplay state, analytics used to understand how the site performs, and the limited situations where information may be shared with infrastructure or measurement providers.

The site is built to be playable without an account

Dont Wordle does not require you to create a user account in order to play the daily board. The site is designed around a lightweight browser experience: load the page, make your guesses, and read the public guides if you want more context. That means the project does not operate like a profile-driven app with public handles, friend lists, or private dashboards.

That design choice matters for privacy because it keeps the site focused on basic functionality rather than identity. When you open the homepage or the blog hub, the project is trying to serve the page and measure broad usage patterns, not build a personal dossier about a logged-in account.

What data is used to run the site

The game uses browser-side state so the current puzzle, your local progress, and related interface behavior can work smoothly during a session. That kind of local state is part of making the game playable and is different from a system that stores public account history on a remote server.

The site may also use basic request and infrastructure logs through hosting and delivery providers so the pages can be served, errors can be investigated, and the project can tell whether the site is actually working. These operational data flows are a normal part of running a web property and are separate from editorial or marketing use.

Analytics and measurement

When configuration is enabled for the live site, Dont Wordle uses analytics tools to understand page performance and user flow. The current codebase includes Microsoft Clarity and Google Analytics for Firebase integrations. Those tools help answer product questions such as whether people reach the rules page from the homepage, whether the blog hub is clear enough, whether players start and finish games, how often people open the share flow, and whether archive navigation makes it easier to find more puzzles.

The purpose of that measurement is site improvement, not personal targeting. It helps the project see where users drop off, which pages deserve clearer internal links, and whether content updates are genuinely useful. If you want to understand why pages like About or Contact exist at all, analytics is part of the answer: it helps confirm whether the site is becoming easier to navigate and more trustworthy.

The analytics setup is intentionally narrow. The site measures page views, high-level game actions such as start, valid or invalid submit, undo, completion, share clicks, and archive navigation. It does not send the exact words you type, the hidden answer, your display name, or other direct personal identifiers to those analytics events.

Cookies, local storage, and third-party services

Browser technologies such as cookies or local storage may be used where needed to keep sessions functional, remember basic state, or support analytics. Some of those technologies are first-party to the site experience, and some may be set or read by third-party services involved in analytics, hosting, or delivery.

The important point is that this project does not pretend to be a blank static page if it is actually using measurement tools. This page exists so the site can describe those tools plainly and give readers a route to ask questions instead of hiding that information in generic boilerplate.

How to ask questions or request changes

If you have a privacy-specific question, the best route is to use the Contact page or email hello@dontwordle.top. If your question is really about how the project is structured or why the site publishes content alongside the game, the About page is the better first stop.

This page may be updated when the site changes its analytics setup, adds new infrastructure, or introduces a meaningful data flow that deserves public explanation. The goal is to keep the page specific to Dont Wordle, not to grow it into a generic legal wall that says very little about the actual project.

Quick answers

Privacy FAQ

Does Dont Wordle collect personal account data?
The site is designed to be playable without an account. It focuses on basic analytics and local gameplay state rather than user profiles.
Why mention Microsoft Clarity and Firebase here?
Because the site includes those analytics integrations when the relevant configuration is enabled, and the privacy page should describe the tools the project actually uses.
Does the game store my guesses on the server?
The gameplay experience is built around browser-side state and analytics rather than a user login system or a public account history.
How do I ask a privacy question?
Use the Contact page or email the project at the listed address if you have a question that is not covered here.