Local first. Cloud only by choice.

Calibration data and local profiles

MouseCalibration stores session identity, setup references, test results, excluded attempts and raw mouse-event evidence in your browser so you can resume and review a report. It also creates a local player profile that links your sessions, optional profile name, a versioned performance summary and your latest validated physical mouse setup. The saved setup includes its source session and measured movement reference so you can reuse it after confirming that the same mouse, DPI and pointer settings are still in use.

You can use the calibration, immediate report and local Advanced Lab without an account. Clearing this site’s browser data removes locally stored profiles and sessions. Download any report you need to retain.

Optional accounts and cloud history

You may create an account with a username, display name and passkey. MouseCalibration stores the passkey’s public credential and counter; your private passkey and device-unlock secret remain with your authenticator. Account creation alone does not upload calibration evidence. MouseCalibration does not currently provide email recovery, so you must retain access to the passkey.

Cloud history has a separate, explicit switch. If you enable it and sync, complete sessions—including raw movement events, setup and browser context, results, excluded attempts, source identity, algorithm/model versions and timestamps—are stored in the account. Cloud history is retained until you delete it or delete the account. The immutable session ID prevents a later upload from silently replacing different evidence. You can turn future syncing off, export cloud data, delete cloud history or delete the account from Advanced Lab. Turning sync off does not delete previously uploaded history; use the delete control for that.

Authenticated requests use a secure, HTTP-only session cookie and expire after 30 days. Cloudflare processes and stores the account and opted-in history to operate this service. A hosting provider may separately process ordinary technical logs such as IP address, requested page, browser type and request time for security and operation.

Analytics, advertising, cookies and consent

The public site may use Google Analytics to measure page use and product events such as starting or completing calibration. Analytics events deliberately exclude raw mouse movement, report identity, DPI and sensitivity results. The public site may also use Google AdSense. Google and other advertising vendors may use cookies, local storage or similar technologies to deliver, measure and limit ads.

Where required, a consent message supplied through a Google-certified consent management platform will let you manage analytics and advertising choices before eligible technology is used. Depending on those choices and your location, ads may be personalised or non-personalised. You can review personalised-ad choices in Google Ads Settings.

Learn how Google uses information from sites that use its services in Google’s partner-sites privacy information.

Current scope and changes

A local profile remains separate from an online account. There is no subscription in this release. Ranked training suggestions are computed from calibration evidence in the Lab; interactive daily drills and paid longitudinal features are not yet active.

Advertising is kept outside the active measurement, aiming-test and analytical chart controls. This policy may change as the service develops; the effective date above will be updated when material changes are published.