Privacy Policy

Policy Purpose

This policy explains how the current SEO Blitz analyzer processes submitted draft content, what it stores in the browser, what the August 2026 runtime verification observed, and which areas remain outside that test.

Analyzer Processing

SEO Blitz processes analyzer input with browser JavaScript. In an August 2026 Chromium test of the generated production build artifact, analysis rendered without a network request during draft entry or result calculation. Submitted draft canaries were not observed in captured request URLs, relevant headers, or request bodies during the tested workflow.

This is scoped observational evidence, not a guarantee for every browser, deployment, extension, or future version. Users should avoid pasting confidential, regulated, or client-sensitive material unless they are comfortable using this browser tool on their device.

Local Draft Autosave and Persistence

The working draft is intentionally stored in browser localStorage under seoblitz-draft. In the tested browser, the draft fields and analysis results returned after reload and after navigation away from the analyzer and back.

Local storage is persistent browser-controlled storage. The working draft remains according to browser storage behavior until it is overwritten, cleared with the analyzer controls, or removed through browser storage controls. Clearing the current input removes the autosaved working draft. Named drafts use a separate local browser store and remain until they are deleted.

August 2026 Test Results

Third-Party Resources and Analytics

The tested build requested font resources from fonts.googleapis.com and fonts.gstatic.com. No submitted draft canary appeared in the captured Google Fonts requests. No analytics request was observed during the tested analyzer workflow. These observations do not prove that every deployment environment or future version has the same network behavior.

How the Verification Was Run

The August 2026 check used SEO Blitz Scoring Model v2.0 in Chromium against the generated production build artifact. Unique canary values were entered in each supported analyzer field. The test inspected network requests, request data available to the browser test, local and session storage, IndexedDB, cookies, Cache Storage, service workers, reload behavior, route navigation, console errors, page errors, and request failures.

The check did not inspect the deployed production host, hosting-provider logs, other browsers, browser extensions, or behavior after future analytics, telemetry, or third-party integrations change.

Information You Choose to Send

If you email support, request a correction, or report a scoring bug, the message may include your email address, the issue description, and any sample text you choose to provide. Do not send passwords, private analytics exports, confidential client drafts, or regulated personal information.

Hosting and Technical Data

The runtime test could not inspect hosting-provider access logs. Hosting, security, or delivery providers may process standard request information such as IP address, browser type, device type, referring page, and request logs for reliability and abuse prevention.

Google Advertising and Cookie Disclosure

If advertising is introduced, third-party vendors, including Google, may use cookies to serve ads based on prior visits to this or other websites. Users can learn about Google advertising controls through Google ad settings and browser cookie controls.

No Ranking or Professional Advice Guarantee

Privacy disclosures do not change the tool's limitations. SEO Blitz provides general content-scoring feedback and does not guarantee rankings, traffic, revenue, AdSense approval, or professional SEO outcomes.

Contact Path

Privacy questions can be sent through Contact. Include the page URL, browser, and a concise description of the concern so the issue can be reviewed.