IMAGINEThis policy explains the cookie and browser-storage baseline for the corporate site. It is aligned to an explicit-consent model for non-essential technologies on consent-regulated surfaces and is written to stay consistent with the site's updated privacy program.
The current baseline of this site is designed to rely on essential functionality by default, together with an explicit consent choice for optional non-essential cookies where those technologies are introduced on a covered surface.
We do not rely on "continued browsing equals consent" for non-essential cookies on consent-regulated surfaces.
A live browser-technology inventory is published in this Cookie Policy experience and through /api/trust/browser-technologies so the declared storage baseline can be reviewed against the code-backed implementation.
Storage periods depend on the purpose of the technology. Session cookies are removed when the session ends. Persistent cookies or preference signals last for the period reasonably necessary for the disclosed purpose or until you clear them, subject to the technical limits of the browser and applicable law.
Where a consent preference is stored, we aim to retain that preference for a reasonable period so you are not repeatedly prompted, while still allowing periodic refresh where law or practice requires it.
If we use third-party technologies for analytics, embedded media, or campaign operations, those providers may receive technical data such as device, browser, IP, or event data depending on the integration. Before enabling consent-gated integrations, we should disclose the provider and relevant purpose in the applicable notice or live preference layer.
You can delete cookies, block storage, or use browser-based privacy tools. Some jurisdictions also recognize opt-out preference signals for particular types of processing, including sale, sharing, or targeted advertising workflows.
On the covered browser surfaces in this repository, we recognize a supported Global Privacy Control signal as a restrictive baseline and keep optional categories off unless you later make an explicit preference choice through the site controls.
Separate products, beta programs, or wallet surfaces such as Lucid may use different technical stacks. Where those stacks rely on additional cookies, browser storage, or routing providers, a supplemental cookie or privacy disclosure may apply.
For cookie and privacy questions, use the Privacy Request Center or contact privacy-requests@imagine-tech.org. For general support, contact support@imagine-tech.org.
These notes explain how the site cookie baseline should behave under different consent and advertising-control regimes. They sit on top of the main Cookie Policy.
Non-essential cookies and similar trackers should remain disabled until the user gives a valid affirmative choice on the covered surface.
Each card below is written as an operational supplement to the baseline document family, not as a standalone contract. It highlights where timing, appeal rights, complaint routes, or consent posture need to diverge by jurisdiction.
You can review and change your optional cookie categories here at any time. The control below is the same consent-management layer used across the covered corporate surfaces, and it now also recognizes a Global Privacy Control signal as a restrictive baseline on the covered browser layer until you make an explicit site choice.
Use this control center to allow only essential technologies, enable all optional categories, or choose a custom mix. We keep necessary security and session functions on, while optional categories stay behind your explicit choice.
To keep the cookie baseline auditable, the covered repository now exposes a live inventory of declared cookies, local storage keys, and browser-managed vendor integrations. This is meant to be the code-backed source of truth for the browser layer, not just a narrative policy paragraph.
This inventory is the browser-side source of truth for the covered repository. It lists the cookies and local-storage keys currently declared in code, together with the consent category they belong to and the purpose they serve.
The same governance layer also tracks browser-exposed vendor scripts or widgets. At the moment, this repository does not declare any optional third-party browser scripts on the covered surfaces. Future additions should be declared in the integration registry and gated through the consent layer before activation.
Stores the current consent level so the banner and preference center can honor the user choice.
Stores the category-level preference bits for essential, preferences, analytics, and marketing handling.
Provides a stable identifier for the consent record so server-side evidence can be updated without using raw network identifiers.
Records when the current consent choice was last updated.
Tracks the notice version associated with the stored cookie preference so refresh logic can be evaluated later.
Records that a browser-level opt-out signal, such as Global Privacy Control, was honored as a restrictive baseline until an explicit site choice is made.
Records when a browser-level opt-out signal was last honored by the consent layer.
Maintains authenticated customer access after a successful OTP login.
Maintains privileged admin access after successful primary authentication and MFA where required.
Remembers the selected interface language across sessions.
Preserves cart contents and line-item notes for quote and order continuity.
Remembers which public brand cards were liked in the portfolio browsing experience.