Privacy Policy
This policy explains, in a practical way, how Hidden Theme handles information required to operate the game, protect the experience, and keep the service running.
1. Overview
Hidden Theme is a browser-based game. Most of the experience happens directly on your device, with data sent only when needed to deliver puzzles, receive guesses, calculate proximity, prevent abuse, and show results.
This policy describes information handling based on the product's current behavior. It does not cover features that are not implemented today, such as behavioral advertising or marketing analytics.
2. Data that may be processed while you play
When you use the game, the service may process information such as the match date, selected difficulty, revealed hints, submitted guesses, score, elapsed time, and round status. This data is used to power the game loop and preserve session continuity.
Basic technical request data may also be processed, including client identifiers derived from network headers, browser language, and information required to answer and protect the API.
3. Local browser storage
The game uses local browser storage, including the `tema-oculto-storage` key, to keep progress, history, stats, and already loaded puzzle state. This helps preserve the experience without relying only on the server.
Interface preferences may also be stored locally, such as whether the help modal has already been shown. That data stays in your browser until you clear it manually or use your browser tools to remove the site's storage.
4. Abuse prevention and security
To protect the game and its APIs, the service applies rate limiting and may use technical client identifiers to detect excessive requests within short time windows.
When additional protection is enabled, the game may require verification through Cloudflare Turnstile before accepting new guesses. In those cases, data necessary to validate the challenge may be processed by Cloudflare according to that service's own routines.
5. Processing required to operate the game
Submitted guesses are processed to validate allowed content, avoid duplicates, calculate correctness, and estimate proximity to the correct theme. This processing is a core part of the game experience.
When applicable to the current logic, the service may also use embeddings to improve semantic proximity calculations between guesses and themes. That may involve technical providers used to support the feature, always for the operational purpose of the game.
6. Operational backend storage
The product uses backend storage to keep puzzles, technical caches, rate-limit keys, and other operational records required to deliver the daily experience.
Those storage layers support availability, performance, game integrity, and abuse prevention. Based on the app's current behavior, they are not used to build advertising profiles of players.
7. Sharing with third parties
Hidden Theme may rely on third parties strictly connected to service operation, such as hosting infrastructure, anti-abuse protection, CAPTCHA verification, and technical providers needed for processing features.
Outside those operational scenarios, this version of the product does not describe data sharing for marketing purposes, ad networks, or the sale of personal information.
8. Retention and updates
Local data stays in your browser until you remove it or it is replaced through normal app usage. Operational backend records may follow technical expiration, cache, and retention policies that fit security and service continuity needs.
This policy may be updated as the product evolves. If new features materially change how data is handled, this page may be revised to reflect that state.
9. Rights and transparency
If you want to limit local game data, you can clear the site's storage in your browser. You can also stop using optional features, such as native sharing, simply by not triggering them.
Official contact channels and specific request paths may be published later on the product's institutional pages. Until then, this policy exists to document Hidden Theme's current behavior as transparently as possible.