What we mean by cookies and parallel storage
Cookies are short text strings your browser stores per site. They can be session-scoped (deleted when the browser session ends) or persistent (surviving restarts until expiry). Local storage and IndexedDB allow larger records. Pixel tags and software development kits may synchronise identifiers across sessions when marketing tools load with your consent.
We describe everything generically as “cookie technologies” when we talk about consent banners, even if the underlying mechanism is not strictly an HTTP cookie.
Strictly necessary storage
This layer keeps the site secure and usable. Examples include routing you to the correct language variant, remembering that you closed a safety notice, storing CSRF tokens for forms, maintaining shopping cart integrity while you check out, and recording the fact that you opened granular cookie settings so we do not nag during the same session.
Under many EU interpretations these technologies fall outside consent requirements because they are essential to provide an explicitly requested service. They still process data, which is why the Privacy Policy references them under Article 6(1)(f) or-implementations with appropriate transparency.
Analytics storage
When you opt in, we may activate privacy-oriented analytics that aggregate page views, scroll milestones, and acquisition channels. Personal identifiers are shortened or rotated to reduce re-identification risk. Heatmaps, if ever enabled, operate on masked coordinates.
You may withdraw analytics consent through the cookie banner’s “Cookie Settings” or by clearing site data and revisiting.
Marketing and attribution storage
Marketing cookies help measure whether campaigns bring readers to informational articles or paid programs. They may record click identifiers, creative variants, and approximate conversion steps. We do not use them to sell your data; we use them to understand performance of our own advertising spend.
A
Analytics opt-in only after granular approval
M
Marketing tags gated separately
N
Necessary storage always disclosed
Expiry and rotation cadence
Session cookies expire when you close the browser tab where they were set (depending on browser implementation). Persistent cookies range from a few hours to thirteen months for mainstream vendors; we ask suppliers to honour the GDPR principle of storage limitation and to delete data on our workspace when contracts end.
Consent logs themselves may persist up to thirteen months to demonstrate compliance during regulatory inquiries.
Illustrative first-party keys
The exact names rotate with deployments, but our engineers aim for predictable prefixes such as tdde_consent_v1 for consent state and tdde_session for short-lived form protection. Do not treat this list as exhaustive; it demonstrates transparency intent.
Third-party controllers you might meet
Embedded videos, social previews, or map tiles can attempt to set their own cookies the moment they render. Because we cannot fully control their behavior, we delay loading those embeds behind a consent check where feasible or replace them with static previews until you click through.
Browser-level controls
Every major browser offers settings to block third-party cookies, delete existing ones, or alert you before storage. Mobile operating systems expose similar toggles at the web-view level. These tools complement, but do not replace our on-site preferences because some necessary cookies may still be required to submit encrypted forms.
How we notify you of updates
When we adopt a vendor that materially changes tracking capabilities, we bump this Policy’s revision stamp and may reset optional consents if regulators expect fresh consent.
Email service@floradynam.world with “Cookie inquiry” in the subject line. For broader data rights, consult the Privacy Policy.