Cookies and similar technology · effective October 11, 2026
Cookie Policy
This policy describes the current code package. The actual behavior also depends on the PHP session and Apache configuration on the deployed host.
01 / FIELD NOTE
Contact session cookie
The contact-token endpoint starts a PHP session for a CSRF token used when the form is submitted. The session cookie is first-party, HttpOnly, SameSite=Lax, and Secure on HTTPS; its configured lifetime is the browser session. The session can also hold the successful-send cooldown. The cookie is not used to track browsing across unrelated websites.
02 / FIELD NOTE
No optional analytics or ad cookies
No Google Analytics, Google Ads conversion, remarketing, social media, heat-map, or third-party font script is included in this build. The calculator inputs remain in the page and are not persisted in local storage. The application does not intentionally set advertising or analytics cookies.
03 / FIELD NOTE
Blocking storage
A browser setting that blocks session cookies may prevent the contact token from being associated with the form and cause the submission to fail. The calculator does not depend on a cookie. Browser history and cached assets are controlled by the browser. Server logs and PHP session files are host-side storage and are not browser cookies.
04 / FIELD NOTE
Consent and future tracking
Because no optional tags are configured, this build does not display a tracking consent banner or load Google tags. If the owner adds non-essential tags, it must first determine applicable consent obligations, implement choices that actually gate the tags, update this policy, and test the resulting behavior, including applicable privacy signals.