1. What cookies are
Cookies are small text files stored on your device when a site loads. They can remember preferences, keep you signed in on other sites (not typically used here), or help analytics tools distinguish returning visitors from one-off hits in an privacy-preserving way depending on configuration.
2. Cookies we use
We use cookies and similar technologies associated with Google Analytics 4 to measure traffic and engagement. GA4 may set first-party cookies under our domain and communicate with Google’s servers. Google’s documentation describes data retention, IP handling options, and regional controls.
3. What we do not intentionally use this policy to cover
We do not run first-party login sessions on this static site. We do not intentionally deploy advertising pixels beyond analytics as described. If we add tools (e.g., embedded video or comment widgets), we will update this policy.
4. Managing cookies
You can block or delete cookies through your browser settings. Major browsers (Chrome, Edge, Firefox, Safari, Brave) provide “clear browsing data” and per-site controls. Blocking analytics cookies may not remove all network requests; some measurement may still occur at the network layer in aggregated forms depending on implementation.
5. Google Analytics opt-out
Google offers a browser add-on to disable Google Analytics on participating sites. Search for “Google Analytics Opt-out Browser Add-on” for the official download. Mobile browsers may offer reduced support for add-ons; use in-app privacy settings where available.
6. Do Not Track
There is no uniform global standard for “Do Not Track” signals. We do not promise specific behavior in response to DNT headers beyond what our analytics vendor automatically applies.
7. Local storage and similar APIs
Some scripts may use browser storage APIs for performance or measurement. Treat them like cookies for management purposes; clearing site data removes them in most browsers.
8. Changes
If we change analytics providers or add new storage categories, we will revise this page and bump the effective date.
9. More detail on privacy
See our Privacy Policy for categories of data and contact information.
10. Similar technologies
In addition to classic cookies, vendors may use pixels, SDKs in embedded content, or bounce tracking via link redirects. We minimize embeds, but if we embed a video or map in the future, that provider may set its own cookies. Review their policies before interacting.
11. Frequency of review
We review this cookie policy when we materially change measurement tools or add interactive widgets. Minor vendor updates may not trigger a rewrite; the effective date still signals the last human review pass.
12. European ePrivacy reminder
EEA readers may encounter consent banners on other sites; our static pages may still load analytics subject to Google’s regional configuration. Use browser controls and Google’s opt-out add-on in combination for defense in depth.
13. Mobile app WebViews
If you open our site inside an in-app browser, the app developer may inject additional tracking beyond what this policy lists. Prefer opening links in your standalone browser when you want clearer separation of tracking contexts.
14. Experimental features
If we ship beta widgets (search overlays, calculators), they may set temporary storage keys. We will document them when they graduate from experiment to default.
15. GitHub Pages and third-party repositories
Source code or issue trackers on GitHub may log your interactions under GitHub’s privacy policy when you contribute or star a repository. Reading static HTML pages on our custom domain still relies on GitHub’s CDN; consult GitHub documentation for technical logging detail.
16. “Strictly necessary” vs analytics
Some jurisdictions distinguish strictly necessary cookies from analytics. Our static HTML does not require cookies to render text. Analytics cookies are non-essential for reading; block them if you prefer a cleaner privacy footprint, accepting that we lose signal to improve guides.
17. Education for household users
If you share a device, clear cookies after sessions on shared computers, especially if you logged into Amazon or email in the same browser profile. This site does not authenticate readers, but general hygiene still applies.
18. Version history
We do not publish a separate changelog file for cookies; the effective date above marks the last substantive edit. If Google renames GA4 features, we may adjust wording without changing practices materially. Thank you for reading this policy carefully.