HomePrivacy Policy
Trust center

Privacy Policy

This policy describes the storage and tracking behavior found in the current SEOToolMatcher application code. It does not describe what third-party sites may do after you leave SEOToolMatcher.

Effective
June 24, 2026
Last updated
June 24, 2026

Browser storage used by the application

KeyStored categoriesPurposeTransmissionClear it
seoToolMatcherQuiz:v1Quiz answers, current question step, current quiz phase, and storage-version marker.Restore Tool Finder progress after refresh and let users continue or clear the quiz locally.Stored in the browser by the application. It is not sent by the quiz itself.Use the quiz Retake/Restart control or clear site data in the browser.

Affiliate redirect click-event handling

BehaviorFieldsDestinationNotes
Controlled commercial redirecteventName, eventId, toolSlug, redirectPath, sourcePath, outcome, targetHost, and occurredAt.A same-origin affiliate-click endpoint when configured by the deployment. The static app does not include a visible analytics vendor script.The redirect tracking call is designed not to include names, email addresses, payment data, quiz answers, or affiliate credentials. It may use navigator.sendBeacon with a fetch fallback.

Analytics, cookies, and consent status

External analytics
No external analytics provider is configured in the current application code.
dataLayer
The current application code does not push affiliate, quiz, or page events to window.dataLayer.
Cookies set by SEOToolMatcher
The audited application code does not set application cookies. Browser storage for quiz progress uses localStorage instead.
Cookie banner
No cookie banner is shown because no non-essential analytics or marketing cookies are enabled by the current application code.

Contact submissions

A public contact channel is not configured in the current build, so SEOToolMatcher does not publish a contact form that collects submissions.

Hosting and technical logs

The current repository is built as a prerendered static site. The application code does not identify a hosting provider in public policy text.

A production host may process ordinary technical logs such as request time, requested URL, user agent, referrer, IP address, and error information. Hosting-provider behavior should be confirmed before launch.

User controls and retention

Clear quiz progress
Use the quiz Retake/Restart control or clear site data for SEOToolMatcher in your browser.
Affiliate event retention
The static application does not define server-side retention. Any configured first-party endpoint should set and document its own retention policy before launch.
Security limitations
No website can guarantee absolute security. Avoid entering sensitive information into the Tool Finder or any future contact channel.