The privacy model should be easy to inspect.

Spwashi is mostly a static site with progressive browser features. Some features remember preferences, visits, notes, checkpoints, or drafts in this browser so the surface can feel continuous across visits. Those records are local unless a specific feature says otherwise.

?"analytics_posture"

Analytics posture

Plausible is no longer emitted by the shared template and legacy Plausible tags have been removed from source pages. The head template now requires analytics to be declared explicitly with an engine and script source. If no engine is configured, no analytics script is rendered.

<spw-page
  analytics_engine="custom"
  analytics_src="/public/js/runtime/example-analytics.js">
</spw-page>

^"local_state"

Local state inventory

Settings

Theme, density, typography, runtime display, and accessibility preferences live under the site settings key.

spw-site-settings

Notes

Footer and settings notes are stored in this browser and can be cleared from the settings page.

spw-local-notes

Guide and visit state

Collected handles, grounded visits, pins, and checkpoints make repeated browsing easier.

spw:guide-collection

Tool state

Some tools, such as care, budgeting, RPG Wednesday, and seed cards, keep working data locally.

tool-specific localStorage keys

!"reset_paths"

Reset paths

Use settings presets or the deviation register to reset appearance and runtime preferences.
Use local notes to review or clear browser notes.
Use saved data and app status to inspect service worker and cache state.
Use browser storage tools when you want to clear every local trace for this origin.

Sensitive working surfaces should say when data stays local. If a future feature sends data off-device, that should be visible in the route copy, not hidden in implementation.