Cookie Policy
Last updated: October 22, 2026
We Don't Use Analytics or Advertising Cookies
Unlike most websites, Sharp AI Hub does not set cookies for analytics or advertising, and does not load Google Analytics' gtag.js, Google Tag Manager, or the Meta Pixel in your browser. There is no client-side tracking script to block, and no consent-management platform overlay is needed for that purpose.
The Equivalent Mechanism We Use Instead
To measure traffic and understand our content's performance without cookies, we use a server-side, cookieless architecture:
- Client ID in local storage. Only after you choose "Accept all" or "Analytics only", a small script generates a random identifier (not a cookie — it lives in your browser's
localStorage, a different browser storage mechanism) and stores it locally. Before you choose, or if you reject, no identifier is created. It stays until you reject (via "Privacy preferences" in the footer) or clear your browser storage. This ID contains no personal information and cannot be linked to your identity by us or by Google. - Consent widget. The consent pop-up you see on your first visit lets you choose "Accept all", "Analytics only", or "Reject". Your choice is stored alongside the client ID and reported once to our own server. You can change it at any time through the "Privacy preferences" link in the footer.
- Server-side forwarding. When you interact with the site (page views, scrolling, clicks), your browser sends these anonymous events to our own automation server — never directly to Google or Meta.
- Consent Mode v2, enforced server-side. Before forwarding any event to Google Analytics 4's Measurement Protocol, our server checks your stored consent choice:
- Accept all — full event sent, eligible for audience export to Google Ads / Meta.
- Analytics only — full event sent to GA4 for internal analytics, explicitly flagged as not eligible for advertising export.
- Reject — only a minimal, aggregated ping is sent, with no identifier attached. If you had accepted before and later reject, your old client ID is sent one last time with the refusal, so our server marks it as refused (it is then no longer eligible for any export), and it is deleted from your browser.
Why local storage and not a cookie?
Cookies are automatically sent with every request to our server and can be read by any script running in the page. Local storage is not automatically transmitted anywhere — our own script reads it and decides, explicitly, what to send and to whom. This gives us server-side control over what leaves your browser and complies with the legal basis described in our Privacy Policy.
How to Opt Out
You can change your consent choice at any time by clearing your browser's local storage for sharpaihub.com, which will show the consent widget again on your next visit. You can also request deletion of any associated records by contacting us — see our Privacy Policy for the process.
Third-Party Cookies
Outbound affiliate links may set their own cookies once you leave our site and land on the affiliate's website. We have no control over those cookies; refer to each affiliate's own cookie policy.