What a visit sends#
Your browser requests static pages and assets from the site host. That host necessarily receives request information such as your IP address, request time and requested path. This project cannot establish its live retention policy before deployment.
This website code does not send requests to analytics, advertising, third-party font, search, chat or session-replay services. External documentation and GitHub links open only when you choose them.
What stays in your browser#
| Feature | Local handling |
|---|---|
| Appearance preferences | Theme, contrast and text preferences may be stored under the website’s local-storage key. The site still works if storage is blocked. |
| Search | The static local index is filtered in your browser. Queries are not submitted to a search service. |
| Checksum comparison | The selected file and expected hash are processed locally. They are not uploaded or stored by this website. |
| Interactive preview | The preview runs in a sandbox without same-origin access or network access. It uses synthetic state and has no access to the parent website’s storage. |
| Offline reading | When you explicitly save guides, a service worker caches a small, fixed set of public documents and required assets. Release artifacts, credentials and the prototype are excluded. You can remove the cache from Offline reading. |
| Cookies | This website code does not set cookies. Review host-added behaviour before publishing. |
Inspect the deployed files#
The build manifest lists the exact local files and their SHA-256 values. It is a way to inspect this website snapshot, not a signed software release or an independent privacy audit.
Open the website build manifestRead the deployed page and asset indexThe website source and build tools are available in the public repository.
Your controls#
Use Preferences to change or reset the local appearance preference. Browser site-data controls also remove it. The website does not require registration, marketing consent or a tracking-cookie choice.
Before a public deployment#
The operator must confirm its hosting/CDN logs, actual response headers, retention, legal identity and any additional policy required for its jurisdiction. No legal-compliance certification is asserted by this technical notice.