Labs / Browser verification
Browser Privacy Verification
A controlled Chromium study of where submitted analyzer state appears during the tested production-artifact workflow.
01 / Research question
Where does analyzer state appear in a controlled browser workflow?
We tested whether submitted canary content appeared in observed outbound requests during analysis, then inspected browser storage and persistence across reload and navigation.
Scope: Chromium against the generated reports/site/ artifact, using the shipped v2.0 analyzer workflow.
02 / Method
Observe the real interface.
- Load the production artifact in a fresh Chromium context.
- Enter fixed canaries in title, body, and supported brief fields.
- Record request URLs, relevant headers, bodies, host classification, and analytics observations.
- Inspect localStorage, sessionStorage, IndexedDB, cookies, Cache Storage, and service workers.
- Reload and navigate away, then inspect restored state and new requests.
- Repeat the normalized run and compare research-relevant fields.
03 / Evidence
Retained browser observations.
The result traces to a fixed canary fixture, two isolated Chromium executions, normalized request records, storage snapshots, persistence checks, and derived claim statuses. Result checksum: 9f07b078129e4e498473f90d524502ff163d7103d2b3db37eb231e30d00adae5.
The canary values are not published here. The retained evidence records their checksums and observed storage and request surfaces.
04 / Results
Observed behavior in this test scope.
| Observation | Result |
|---|---|
| Submitted canary in request URLs, relevant headers, or bodies | Not observed |
| Analytics request during tested workflow | Not observed |
| Draft storage | localStorage, key seoblitz-draft |
| Reload and navigation persistence | Draft and results restored |
| sessionStorage, IndexedDB, cookies, Cache Storage | No submitted canary observed |
| Service worker | None registered |
| Third-party hosts | fonts.googleapis.com, fonts.gstatic.com |
The run retained 38 requests. The canaries were stored locally because the analyzer autosaves the current draft in browser local storage.
05 / Interpretation
The tested workflow kept analyzer canaries out of observed request data.
Within this controlled Chromium run, we did not observe submitted draft content in outbound request URLs, relevant headers, or request bodies. This is an observational result, not cryptographic proof and not a universal guarantee across all browsers, deployments, extensions, or future versions.
Google-hosted font requests occurred. Their presence does not by itself show that analyzer draft content was sent to those hosts.
06 / Limitations
Keep the scope explicit.
- The deployed production host and provider access logs were not tested.
- Only the controlled Chromium environment was tested.
- Browser extensions and network layers outside browser instrumentation were out of scope.
- Future analytics, integrations, or application versions may behave differently.
- Local storage persists according to browser behavior until overwritten or removed by the user or browser.
07 / Reproduction
Inspect the retained evidence.
The retained manifest, fixed canary fixture, normalized raw evidence, and derived claims are stored with the repository research contract. The study result checksum is 9f07b078129e4e498473f90d524502ff163d7103d2b3db37eb231e30d00adae5.
Review the Privacy Policy and Methodology limitations for the broader product boundaries.
Continue the work
Use the Analyzer for a draft, read the Methodology for scoring details, or return to the Labs index for the other study.