Actual data-flow disclosure
Tool results stay in the current browser by default. Ordinary visits can still cause the host, Google Analytics, and Google AdSense to process visit, device, and advertising information.
focus-game.org is a static site that does not require an account. Interactive tasks run in the browser; local history and some settings use localStorage. The site has no account database that stores personal training results.
Pages use Google Analytics for aggregate visits and site interactions, and pages with publisher content load Google AdSense. These third-party data flows are separate from local tool results.
A completed session can contain tool ID, locale, start and completion times, duration, settings, aggregate metrics, and validity flags. Theme, checklist, recent-tool, and legacy history data can also use browser storage. Clearing site data, using private browsing, or changing browser or device removes or separates these records.
Task code does not upload the local session collection, trial-by-trial stimulus responses, names, or email addresses to a focus-game.org application database. Export features create a local file only after an explicit user action.
Google Analytics loads after the page becomes interactive. Depending on its configuration, Google may process page URL, referrer, browser and device information, IP address, approximate location, events, and cookies or similar identifiers such as _ga. Site event code does not put names, email addresses, user IDs, or local tool results into dataLayer.
Analytics is used to understand aggregate visits and interface use. Exact retention and deletion behavior depends on the owner's Google Analytics property settings and Google's service policies; it cannot be confirmed from the public repository alone.
The AdSense script can allow Google and its advertising-technology partners to read or set cookies, use web beacons, and process IP address, advertising identifiers, browser/device data, page URL, referrer, and ad interactions for delivery, frequency control, measurement, system protection, and—when required consent exists—personalization. Non-personalized ads can still use cookies or storage for frequency capping, aggregate reporting, and abuse prevention.
AdSense code is not loaded on this site's 404, Privacy, Terms, Disclaimer, Editorial Policy, About, or FAQ pages. Auto-ad formats, personalization state, and final display also depend on AdSense account settings, user region, and consent choices. The site does not ask users to click ads or disguise ads as Start, Continue, Retry, Result, or navigation controls.
For regions covered by Google's EU User Consent Policy, the page sets regional defaults for ad_storage, ad_user_data, ad_personalization, and analytics_storage to denied before Google tag configuration and waits for a consent solution to update them. The code never hard-codes consent granted for every visitor.
The publisher must still configure a Google-certified CMP integrated with IAB TCF v2.3 in AdSense Privacy & messaging or another supported solution, and verify that it displays across the EEA, UK, and Switzerland, records choices, and allows withdrawal. TC strings generated on or after March 1, 2026 must use v2.3. Account-level CMP activation is not stored in this repository and must be checked by the owner before serving ads in those regions.
Static files can be delivered by the host or CDN selected in the deployment configuration. Providers commonly process IP address, request time, path, response status, browser identifier, and network logs for security, reliability, and operations. The live hosting account, log retention, and access controls are outside the repository, so this policy does not invent an exact retention period.
Opening an external link is governed by the destination's privacy policy. Article-source links do not send local tool history, though the browser normally sends ordinary request information.
The site is intended for a general audience and does not request age, name, school, or parent information. The kids' Schulte and student-scenario pages explain tasks and study workflows; they do not diagnose and must not be used to build personalized-ad audiences from activity known to belong to users under 13.
If the owner determines that a page or traffic is child-directed under applicable law, the corresponding child-directed treatment must be enabled in Google and deployment settings and prohibited personalization must be disabled. That account-level determination cannot be confirmed automatically from this repository.
Use a tool's clear-history control or browser site settings to remove localStorage and cookies. Tracking protection, ad blocking, script blocking, and private browsing may limit third-party tags or local saving. The CMP for applicable regions should provide consent choices and a withdrawal route.
Local records persist until the user, browser, or storage policy clears them. Google and hosting-provider data follow their own policies and account configuration. The site does not sell local task results and has no user score-account profile.
Use these links to check the research context, measurement limits, and original definitions discussed above.
Google AdSense Help
Google AdSense Help