Cookie declarations and technical consent disclosure stack specify storage tokens, advertising parameters, and user preference controls.
Amelune organizes all client-side storage keys into a collapsible disclosure stack. Expand individual clauses below or utilize master controls to inspect our Consent Mode v2 implementation.
This Cookie Policy and technical storage disclosure took effect on 2026-10-17.
This notice was formally ratified on 2026-10-17 by Amelune management in Tampa, Florida. It details all browser storage mechanics, HTTP cookie flags, LocalStorage keys, and advertising click identifier handshakes operational on amelune.click.
Our commercial operations are strictly inquiry-based; we store no shopping cart sessions, payment credentials, or personal banking profiles on client devices.
Client-side storage is segmented into strictly necessary, functional, and advertising categories.
Amelune classifies client-side storage tokens into three distinct operational tiers:
- Strictly Necessary Storage: Local storage items essential for storing your explicit cookie consent state (site_consent_v2) and maintaining CSRF form verification tokens. These operate without requiring opt-in consent and cannot be turned off without breaking website security.
- Functional Support Storage: Client storage used by our Tampa live desk widget (cavue50.php) to maintain your conversation token across page reloads so you do not lose active inquiry dialogues.
- Advertising & Analytics Storage: Storage keys that evaluate conversion effectiveness for campaigns directed through Google Ads, Microsoft Advertising, and Meta Ads. These keys are held in a strict “denied” state until affirmative opt-in is granted.
The comprehensive inventory ledger specifies token names, hosting origins, purposes, and retention clocks.
Every client-side storage key and HTTP cookie active on amelune.click is documented in the technical inventory table below:
Paid search campaigns associate inbound clicks with platform identifiers including gclid, msclkid, and fbclid.
Amelune advertises on major search and social discovery platforms in the present tense. Paid commercial campaigns direct wholesale and retail inquiries to our catalogue pages from:
- Google Ads: Inbound campaign URLs carry the gclid (Google Click Identifier) query parameter. This allows our servers and advertising tags to substantiate click origin and optimize landing page bids.
- Microsoft Advertising: Inbound clicks from Bing search results carry the msclkid (Microsoft Click Identifier) parameter for conversion attribution.
- Meta Ads: Targeted commercial posts and ads append the fbclid parameter to incoming landing page links.
No advertising network has reviewed, certified, or endorsed our website or dietary supplement catalogue products. All product descriptions are authored solely by Amelune under Florida regulatory frameworks.
Google Consent Mode v2 holds four security signals denied until explicit opt-in is registered.
Our front-end architecture enforces Google Consent Mode v2 by issuing explicit default commands prior to loading any advertising tag libraries. The four statutory parameters are initialized as:
| Consent Parameter | Default Pre-Consent State | Post-Acceptance State | Post-Decline State |
|---|---|---|---|
| ad_storage | denied | granted | denied |
| ad_user_data | denied | granted | denied |
| ad_personalization | denied | granted | denied |
| analytics_storage | denied | granted | denied |
When a visitor declines storage, tags transmit only cookieless aggregate pings without reading or writing persistent device identifiers.
Visitors exercise sovereign consent choices upon arrival and may alter preferences at any time.
When you first land on amelune.click, a prominent, non-blocking footer consent banner presents clear choices: “Allow Storage” or “Decline”.
To modify or withdraw your consent at any point in the future, simply click the “Cookie Preferences” button permanently anchored in our website footer or activate the interactive control below:
Additionally, Amelune honours the browser-level Global Privacy Control (GPC) header (Sec-GPC). If your browser transmits this signal, advertising storage is permanently suppressed without prompting.
Declining cookies does not restrict access to our catalogue, formulations, price estimator, or inquiry forms.
We do not implement cookie walls or degrade catalogue features for visitors who choose to decline tracking. If you select “Decline”:
- What Still Works: Full access to all product descriptions, milligram breakdown tables, ingredient origins, the interactive batch price estimator, support chat desk, and commercial inquiry forms.
- What Is Suppressed: Third-party ad attribution scripts, cross-session remarketing cookies, personalized ad delivery signals, and persistent Google Analytics client IDs.
Third-party platform privacy policies govern external tag infrastructure and data processing.
For complete technical transparency, we encourage commercial visitors to review the independent privacy documentation of the advertising and cloud platforms integrated into our workflows:
- Google Advertising & Analytics Policies: Consult policies.google.com for full disclosures on Google Tag Manager, Consent Mode v2, and conversion tracking mechanics.
- Microsoft Advertising Privacy Statement: Review privacy.microsoft.com for Microsoft Universal Event Tracking (UET) and search ad privacy policies.
- Meta Platforms Data Policy: Review Meta’s privacy frameworks governing commercial conversion measurement.
Inquiries concerning technical storage keys and browser cookies reach our Tampa administrative office directly.
If you require clarification on any cookie identifier, storage script, or data retention clock listed in this stack, contact our technical data officer:
Location: 1005 West Platt Street, Tampa, Florida 33606, United States
Telephone: +1 (464) 555-7461
Direct Inquiry Email: office@amelune.click
All cookie and technical storage inquiries receive a formal written reply within 14 days of intake.