What this page sends
This site is built to send nothing about you anywhere. Every page — all 231 generated state pages across 51 jurisdictions, both product tiers, plus the 20 fixed pages — sets zero cookies, writes zero browser storage, and makes zero third-party requests. The table below says so per surface, and the sources line below it names the machine checks that re-prove each value on every change.
| Surface | Pages | Cookies | Storage | Third-party requests |
|---|---|---|---|---|
| The fixed pages (home, directories, legal, compare, about, contact, security) | 20 | 0 | 0 | None |
| State landings | 51 | 0 | 0 | None |
| How-it-works pages | 51 | 0 | 0 | None |
| Statute listings | 51 | 0 | 0 | None |
| Eligibility checks | 1 | 0 | 0 | None |
| Eligibility results | 1 | 0 | 0 | None |
| Pricing pages | 1 | 0 | 0 | None |
| FAQ pages | 1 | 0 | 0 | None |
| Process explainers | 2 | 0 | 0 | None |
| County listings | 1 | 0 | 0 | None |
| County pages | 67 | 0 | 0 | None |
| Statute pages | 4 | 0 | 0 | None |
How each value is proven: a static scan of every source and built file rejects storage APIs (our content-model gate 2); a real browser loads a sample of built pages on every change and asserts zero cookie, localStorage, sessionStorage, indexedDB, and CacheStorage writes at runtime; and a full-site scan rejects any script loaded from another origin — backed by a Content Security Policy that only permits our own. These checks run before any change ships.
Check it yourself
You don't have to take our word for it — your browser can show you, on this page, right now:
- Open your browser's developer tools (F12, or right-click → Inspect).
- Open the Application tab (Chrome/Edge) or Storage tab (Firefox).
- Look at Cookies, Local Storage, and Session Storage for expeal.com — each is empty.
- Open the Network tab and reload: every request goes to expeal.com. No analytics, no ad networks, no trackers.
The same is true on every page of this site. The Expeal application at its own domain sets only the essential cookies sign-in requires — its posture is described in the Application Privacy Policy and on the security page.
Change log
- 2026-08-18 — Initial publication (Story 1.7.2). The per-surface table derives from the route matrix at build — coverage is computed, never typed — and every value is machine-proven on each change by the checks the sources line cites.