Anonymous local draft
Private by default. Limited on purpose.
The free fixture scan does not ask for an email, create an account, track behavior, call AI, or contact a public storefront.
Local data flow
Controlled fixture in. Local evidence record out.
The working product stores only the state needed to demonstrate the deterministic report and local interactions.
Controlled fixture→Deterministic scan→Local report
What is stored locally
Evidence and product state—not merchant private data.
- Scan and eight stage states with timestamps.
- Controlled fixture page, asset, request, schema, and rule evidence.
- Metrics, findings, recommendations, report snapshots, and saved calculator scenarios.
- Optional local action intent, without a contact address.
- No production customer, order, analytics, credential, or private Shopify data.
Local deletion: run pnpm data:reset to remove local draft records.
Intentionally disabled
Production capabilities wait for their safety and consent boundaries.
- Live public scans
- Disabled until URL normalization, DNS/IP and redirect validation, budgets, rate limits, timeouts, response limits, cancellation, redaction, and adversarial fixtures pass review.
- AI
- The anonymous core has no enabled provider and displays zero calls. AI cannot create evidence, measurements, scores, or unsupported claims.
- Connected data
- Shopify Admin, GA4, Search Console, Merchant Center, authentication, and billing are not configured.
- Lead delivery
- Save, email, reminder, brief, booking, and help surfaces are local previews. No message, appointment, or request is sent.
What a public scan could never prove alone
Some answers require permission and re-measurement.
Indexing status, answer-engine visibility, conversion, revenue, order impact, private settings, source-code causes, and real-user performance require separate authorized evidence—and often a controlled before/after test.