Privacy here is a threshold, not a posture.

Most of what this site remembers sits in a liminal place: not yet public, not yet gone. Settings, notes, visits, and drafts stay in this browser so a return can continue. That is ordinary human continuity. It is not a claim that every surface needs the same walls.

Integrity scales with the work. A casual reading visit can keep a theme and a checkpoint. A care note should stay small and local unless sharing is the point. Work with a higher-profile client needs a tighter scope: fewer traces, clearer handoff, and no casual projection of names or artifacts into public rooms.

This page exists because

people need to know what a return visit will remember, and what a client engagement should not leak.

Use this when

you are deciding how much state a visit, a note, or a commission actually needs.

What it can produce

a realistic scope: local continuity for ordinary use, tighter integrity when the stakes rise.

?"analytics_posture"

Analytics posture

Counting visitors is optional here, not a default. A page only loads an analytics script if it names an engine. If you do not see that declaration, nothing extra is being counted.

<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

Install prompts and offline files

Choosing “Later” on an install hint stores a local timestamp for up to 30 days. The service worker keeps the offline shell and recently used site files in Cache Storage.

spw-pwa-install-dismissed
spw-pwa-ios-hint-dismissed

Web fonts

JetBrains Mono and Newsreader load from this site under /public/fonts/. No font request leaves the browser for a third-party host. Offline visits use the cached local faces, then system fonts if those files are missing.

/public/fonts/

!"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 something stays local and when it is about to leave. That is enough for most visits. Client work may need a smaller surface than the public site: do not paste names, drafts, or artifacts into a tool just because the tool is convenient.

~"integrity_scopes"

Integrity has a scope

The same person can need different walls in the same week. Name the threshold before you treat every note as a secret or every page as a vault.

A visit

Theme, density, and a few return handles can stay in this browser. They make the site feel continuous. They are not a dossier.

A working note

Care cards, drafts, and local notes sit on the threshold between thinking and sharing. Keep them here until a person actually needs them. Share the smallest useful slice.

A public page

Published routes are meant to be found. Do not put a client’s unpublished work, a private name, or a midprocess artifact on a public route unless that handoff was the job.

A higher-stakes engagement

Higher-profile clients raise the cost of a leak, a screenshot, or a casual model prompt. Use a narrower channel, fewer copies, and a clearer end of the work. Integrity here is realistic necessity, not a brand of secrecy.