A task-first tool site
The site provides usable scanning, rule-conflict, reaction, memory, sustained-monitoring, and focus-routine tools, with an explicit account of what each page records.
Tools require no account and perform their core calculations in the browser. Completed results stay on the current device by default; ordinary visit analytics and advertising technology are separate third-party flows described in the Privacy Policy.
The site suits people who want to understand or repeat a specific task. It is not suitable for diagnosis, ranking people, or decisions about health, school, employment, or safety-critical fitness.
Tools cover ordered search, target detection, word/color conflict, simple reaction, position and sequence recall, n-back, low-frequency monitoring, motion tracking, timers, and pacing cues. Each page explains stimuli, responses, metric denominators, comparable settings, and known limitations.
The blog explains results, compares nearby tasks, and provides workflows centered on real study or work. It does not dress repeated keywords or unsupported benefit claims up as information.
A result describes page behavior under the current implementation, device, input, and settings. Personal comparison should preserve conditions, errors, and validity flags and use several recent sessions rather than one personal best.
The site provides no IQ, brain age, ADHD score, clinical cutoff, or age norm and does not guarantee transfer to academic work, employment, reading, health, or broad cognitive ability.
Local tool sessions use localStorage and can be cleared or exported by the user. The site has no login or score-upload API. Google Analytics, Google AdSense, and hosting logs can still process ordinary visit and device information; the Privacy Policy gives the full distinction.
Visible copy should match the real interaction. Research context links to verifiable papers, standards, or institutional sources where appropriate; strong claims that cannot be checked are removed. Article modified dates change only after substantive edits.
The repository currently contains no verifiable public email address, contact form, or public issue destination, so the site does not invent a Contact page. When the owner publishes a real channel, the Editorial Policy should be updated with a clear correction route.
Read supporting explainers and practical guides.