Cookies supporting Steadiflow commerce
This policy explains how brizelonskyx.world uses cookies, HTML storage, and comparable technologies to keep Steadiflow product journeys understandable and secure. It supplements the Privacy Policy but focuses on browser identifiers only.
What cookies are
Cookies are small text files stored on your device when you visit Brizelonskyx. They may be first-party (set by Steadiflow) or third-party (set by analytics vendors we vet through data protection agreements).
Categories we employ
Strictly necessary
These tokens remember cookie banners, keep CSRF protections synchronised during checkout, and bind authenticated download sessions to logged browsers. They cannot be disabled without breaking cart flows.
Functional preferences
We remember typography size choices in product previews, preferred language for invoices, and whether you collapsed onboarding tips inside Guided Cadence portals.
Performance analytics
Optional scripts measure scroll depth on pace-playbook.html and conversion steps on steady-offerings.html. Activation requires your explicit opt-in via the banner managed by main.js localStorage keys.
Contextual media
Embedded maps pull framing data from Google servers that may issue their own cookies. Review Google’s policy separately; we load maps only on contact-us.html after you scroll near the frame.
Storage duration
Consent records stay twelve months, cart abandonment reminders last forty-eight hours, and analytics identifiers rotate monthly unless law demands longer proof of consent.
Managing cookies
Use browser controls to delete cookies or install blocking extensions. Our banner offers granular switches re-runable anytime by clearing localStorage key flow_cookie_ok_v1 and reloading.
Signals we honor
Where browsers transmit global privacy control signals recognised by Danish guidance, we treat them as refusal of non-essential cookies until you affirmatively opt in on brizelonskyx.ddd.
Children
We do not tailor cookie-based ads to children; parental devices should manage family profiles accordingly.
Updates to this list
When we add processors for limited-time pop-up retail events we publish a thirty-day table appendix listing new cookie names, host domains, and retention periods.
Experimental pilots
Occasionally Steadiflow trials heatmap overlays on brizelonskyx.world using ephemeral cookies deleted after forty-eight hours unless you join the pilot via signed consent.
Cookie banner mechanics
The banner stores flow_cookie_ok_v1 inside localStorage when you press accept. Clearing site data resets the banner; no server round trip is required for that memory.
Cross-device behaviour
Preferences do not synchronise across phones and laptops unless you authenticate a future Steadiflow account expressly offering synced settings.
Audit trail
Quarterly internal audits sample five percent of consent logs tied to product purchases to verify timestamps align with cookie policy disclosures.
Processor inventory
Analytics vendors must list their cookie names in annexes we can email upon request. The inventory differentiates checkout-critical cookies from optional heatmapping tools.
Contact
Questions about cookie logic may be sent through contact-us.html referencing Cookies in the subject line so routing stays efficient.
Effective: · Year · Brizelonskyx