The checker remains fully available when analytics is disabled, rejected, or consent is withdrawn.
Your choice
When analytics is enabled through the reviewed build-time setting, you can opt in or reject before any analytics request is attempted. Rejecting does not limit the checker. You can reopen Analytics choices from the footer and withdraw consent; withdrawal removes the saved choice and returns analytics to zero-network behavior.
One first-party storage item
Optional analytics may store only subtitlepreflight.analytics_consent in first-party localStorage, with the value accepted or rejected. It does not use analytics cookies, sessionStorage, IndexedDB, Cache Storage, a service worker, visitor/session/device IDs, fingerprints, replay, or cross-site identifiers.
Allowlisted events
If enabled and accepted, analytics supports only these content-free categories: tool opened, input selected, analysis started, analysis finished, analysis cancelled, export finished, and reset confirmed. Properties are closed enum values for input method, safely detected format, default or modified profile state, coarse outcome and finding-count bucket, cancellation phase, export format/outcome, and reset kind.
Never included
Analytics must not include filenames or paths; subtitle, pasted, cue, header, speaker, sound-description, comment, or note content; cue text, sequence numbers, timecodes, timings, durations, gaps, CPS, WPM, line lengths, exact finding counts, exact thresholds, profile values, report or export contents; names, email addresses, company or contact data; account, payment, device, visitor, session, cross-site, fingerprint, or advertising identifiers; free text, raw errors, logs, browser location query or fragment, page title, or referrer.
Network metadata
If analytics is enabled and accepted, ordinary network metadata such as IP address, browser/user-agent, request date and time, destination, and the fixed sanitized checker route may be observable or processed by the self-hosted analytics infrastructure. The event body itself is restricted to the fixed site, allowlisted event and enum properties, and canonical checker URL.