Peripheral test data
Test engines keep recent events and calculated results in browser memory or session storage so a result survives the optional advertising transition. Closing the tab clears session data. InputAnalyzer does not intentionally transmit raw peripheral inputs to its servers, advertising partners or analytics.
Technical and aggregate data
The hosting provider may process standard request logs such as IP address, requested URL, browser information and timestamps for security and delivery. If you consent to analytics, InputAnalyzer may record aggregate events such as which test started, completed or encountered an unsupported browser.
Advertising and consent
On free anonymous tool pages, InputAnalyzer can load Monetag In-Page Push and Vignette advertising only after you explicitly accept advertising, a diagnostic report has completed and you choose to continue with free ad-supported access. No Monetag tag starts while the tool is collecting peripheral input or before that free-access action. Monetag may process the page URL and referrer, IP-derived location, browser and device information, identifiers and cookies for ad delivery, frequency control, measurement and fraud prevention. InputAnalyzer does not enable Monetag MultiTag, popunder, direct-link or browser-push formats. Declining advertising or an unavailable ad never blocks a test or report.
Monetag is not loaded on the home, Premium, account, authentication, checkout or legal-information pages, or after the tab confirms an account session. Revoking consent after a provider tag started reloads the page so the stored denial applies to a clean document. The codebase also supports Google analytics or advertising only in a separate release configured with the required Google consent platform; Google and Monetag advertising are not activated together.
Premium account and payments
If you start a Premium purchase, InputAnalyzer stores the email address and a short-lived secure browser session in its own database before redirecting to Stripe. Existing accounts must instead use a one-time sign-in link. For those links, the token table retains only a cryptographic digest and the delivery outbox temporarily contains the link and recipient until delivery, cancellation, expiry or terminal failure, then redacts both.
Stripe processes checkout, payment, fraud-prevention and any tax or billing details shown there. InputAnalyzer receives identifiers and payment status needed to grant or revoke Premium, but never receives full card details. The mail service processes the address only to deliver account messages.
Retention and your choices
Expired sign-in tokens, sessions, rate-limit records and mail-delivery data are removed on a rolling schedule. An unverified email identity is removed after its short-lived session expires when no checkout or payment relation requiring retention exists. A verified account remains available for restoration until you delete it from the account panel or through the published privacy contact. Deletion from the panel requires a recent sign-in link. The financial ledger is then pseudonymised, but checkout and transaction records may be retained where required for accounting, fraud prevention, disputes or other legal duties.
You can decline optional advertising or analytics storage through the consent interface, clear local browser data, and request access, correction, portability or deletion where applicable.
Contact
InputAnalyzer[email protected]