What technologies we use
Cookies are small text strings your browser stores after our server—or a partner’s server—sends a Set-Cookie header. Similar technologies include LocalStorage for lightweight preference caching, session storage for ephemeral forms, and invisible pixel requests that confirm whether an email newsletter rendered. We describe everything in aggregate first, then split details by category.
Some wellness landing pages embed third-party media players or map widgets; those vendors may set their own identifiers even if you only watch a muted preview. When feasible we defer loading such embeds until you click “Load map,” reducing passive tracking.
Strictly necessary stack
These technologies keep consent choices remembered, prevent duplicate submissions of the same order inquiry within seconds, maintain secure session tokens for staff tools, and distribute traffic across healthy infrastructure nodes. EU regulators generally exempt them from opt-in banners because the site cannot function safely otherwise. You cannot disable this tier without breaking transactional flows.
Analytics & performance
When you opt in, we measure scroll depth on education sections, click-through rates on ingredient accordions, and error codes returned by failing shipments. Identifiers are hashed or truncated so analysts see cohort trends rather than household-level browsing histories. Heatmap tools may capture anonymised pointer coordinates on secure pages—never password fields.
You can revoke analytics consent through the footer link that reopens the cookie modal. Revocation takes effect on the next page load; in-flight beacons already dispatched cannot be retracted retroactively.
Marketing & social pixels
Marketing cookies help us attribute visits back to newsletters, influencer collaborations, or restrained paid social experiments. They may sync with partners such as advertising networks that require hashed email submissions. We only fire marketing pixels when the marketing toggle is on; rejecting optional cookies keeps these scripts dormant.
Duration & storage layers
Session cookies expire when you close the browser. Persistent consent logs last up to five years for evidentiary reasons. Analytics identifiers typically rotate within thirteen months to follow platform defaults. Localization preferences may persist twelve months unless you clear site data manually.
Your granular controls
Beyond our modal, every major browser ships settings to block third-party cookies, delete storage nightly, or run in private modes. Industry opt-outs such as the EDAA interest-based advertising tools remain available. If conflicting settings confuse our banner state, we default to the stricter interpretation to safeguard privacy.
Third-party responsibilities
Each vendor publishes its own cookie list. We review those quarterly and remove partners who fall below our security bar. Subprocessors sign DPAs mirroring the commitments in our Privacy Policy, including assistance during data subject requests.
Policy updates
When we launch new optional trackers or retire outdated ones, we bump the effective date above and highlight changes in the doc-callout section of our release notes page when one exists. Silent housekeeping—such as shortening TTL values—may not trigger a fresh banner.
Contact
Questions about how cookies interplay with supplement marketing belong in the same inbox as other privacy topics: talk@grozelonkroz.world. Include screenshots if a deprecated tag persists unexpectedly so engineering can trace the template revision.