Privacy and data

How This Site Handles Saved Results, Follow-Up Requests, and Analytics

This page explains the minimum data stored by the current product and the limits of that storage model.

Public trust asset Indexable Last updated 2026-03-08

Privacy and data

What is stored today

The current product stores a limited set of operational data so results can be reopened and follow-up requests can be reviewed.

Working rule

Saved results are stored as private snapshot files with a time limit instead of being published as indexable pages.

Working rule

Analytics events record route behavior such as public-page views, tool entry, result views, and CTA clicks.

Working rule

Lead requests store the contact details and page context the visitor explicitly submitted.

Privacy and data

What this storage model is for

The point of storage is to support decision continuity, not to silently create public profiles.

Working rule

Saved results exist so a household can reopen, share, or export a private decision snapshot.

Working rule

Analytics are used to understand which clusters lead to testing, compare clicks, and follow-up demand.

Working rule

Follow-up requests exist so high-intent visitors do not hit a dead end after a result.

Privacy and data

Current limits and handling rules

The current repo uses a lightweight storage model, so this page is intentionally explicit about its limits.

Working rule

Private result snapshots expire instead of staying available forever.

Working rule

Admin access should stay credential-protected and noindex.

Working rule

If Google Analytics or Search Console verification is configured, it should stay limited to low-sensitivity route metadata and avoid sending saved-result content, email fields, or follow-up notes into shared analytics surfaces.

Working rule

This product should avoid collecting more personal detail than is required for the follow-up or saved-result flow.