Cookie Policy

Accept all, reject optional, or customize the four categories. Browsing works when you decline. We store the choice, policy version and date as vp_cookie_consent_v1 in local storage for up to 180 days; after expiry we ask again. If storage is unavailable the decision applies only to the current visit.

Saving changes reloads public pages to unload old tracking code and removes known optional first-party cookies/storage. Withdrawal stops future loads; it does not erase events already held by providers. Use Your data rights for a deletion request.

Consent choice, chunk-reload recovery flags (vp_chunk_reloaded, vp_admin_chunk_reloaded), and operator sign-in/session storage keep the service working and secure. Hosting and anti-abuse services receive network information needed to serve requests. Admin sign-in uses Firebase Auth and Google reCAPTCHA.

With permission, vp_calc_lang, vp_calc_last_* and vp_calc_recents remember language, inputs and recent calculations locally on your device. They remain until cleared or your consent expires/changes. Without permission calculators still work for the current visit. Share links contain your selected inputs; share them only with intended recipients.

With permission, GA4 measures visits and interactions using identifiers such as _ga and _ga_*. Google typically sets these for up to two years; settings and browser limits can shorten this. Network requests include IP/browser information. See Google’s partner-site privacy information.

This separate optional category records browsing interactions on public marketing pages to identify usability issues. Clarity uses _clck (typically one year), _clsk (typically one day), and session storage such as _cltk. See Clarity’s cookie list and Microsoft privacy.

With permission, Google Ads and Meta measure campaign conversions and advertising activity. Examples include _gcl_au, _gcl_*, _fbp and _fbc (commonly up to 90 days), and Google’s _gcl_ls local storage. If you also permit Clarity replay, marketing permission allows Clarity to share data with Microsoft Ads. Providers may set additional storage according to their policies. See Google cookies and Meta cookies.

Tracking stays blocked on admin, checkout, invite, calculator, contact and data-request routes, and on URLs containing query strings or fragments, even after you accept. Fonts are served locally. The contact page uses an outbound Maps link rather than an embedded map; Google receives information if you choose to open it. Static blog articles contain no optional tracking tags.

Choices here do not change native-app ads or tracking permissions. Our Privacy Policy covers those separately.