Cookie Policy

Cookies are small text files placed on your browser or device when you visit a website. They help websites remember your actions and preferences and support security, analytics, and performance.

We may also use similar technologies such as local storage, SDK identifiers, and pixels for related purposes.

These are the cookies and browser storage keys the Services actually set, and what each is for.

Strictly necessary — always set

• Session and authentication cookies: keep you signed in and protect your session against request forgery. Set by our authentication provider (Neon Auth).
• ch_consent:records the cookie choice you made on the bar, so we do not have to ask again on every page. Its value is one of two words — "granted" or "denied" — and it contains no identifier. Kept for 180 days.
• th_referral_code and th_first_touch: attribute a sign-up to the referral link or landing page that brought you, so referral rewards can be paid correctly. Set server-side and not readable by scripts.

Functional — always set

• Interface preferencesstored in your browser's local storage, such as the display theme. These never leave your device.

Analytics and advertising — only after you accept

• Google Analytics 4 and Google Ads (_ga, _ga_*, _gcl_au and related): usage measurement and advertising campaign measurement. The gtag.js script loads on every page, but it runs under Google Consent Mode: until you accept, every storage signal is set to denied, so none of these cookies is written or read and no identifier is created. What Google receives in that state is a cookieless ping it uses to estimate traffic in aggregate.
• ch_analytics_sid and ch_analytics_ref: a session identifier and a snapshot of the site that referred you, held in session storage for our own product analytics. Created only after you accept, cleared when you decline, and gone when you close the tab.

• Keep the platform secure and help detect malicious or unauthorized activity.
• Enable sign-in, account protection, and stable sessions.
• Remember your cookie choice, and your interface preferences.
• Credit the right referrer when someone you invited signs up.
• Understand product usage and improve reliability and user experience.
• Measure advertising campaigns, where you have consented.

The only third party that sets cookies through the Services is Google, via the shared gtag.js library used for Google Analytics 4 and Google Ads. It sets none of them until you accept: before that, Consent Mode holds analytics storage, advertising storage, ad user data and ad personalisation atdenied, and ad-click identifiers are redacted. Google acts as an independent controller for some of that processing; its own privacy documentation applies in addition to ours.

Separately, and not a cookie: where you accept analytics cookies, your IP address is sent to ipwho.is so that we can show an approximate city. If you decline, no IP address is sent for that purpose, and the country is resolved on our own servers from an offline table instead. Our Privacy Policy names every service provider we use.

In the product. The first time you visit, a bar at the bottom of the page offers Accept and Decline. Nothing optional is stored on your device until you accept — closing the bar without choosing has the same effect as declining.

You can change your answer at any time. The Cookie settings link in the footer of any page reopens the bar.

What declining actually does. It is a real refusal, not a way to hide the bar. No Google Analytics or Google Ads cookie is written or read, no advertising identifier is sent, no session identifier is created for you, and your IP address, city, region, referring site and browser user-agent string are discarded on our server before anything is written to the database. If you decline after having accepted, the session identifier already created is deleted from your browser and the consent signals sent to Google flip back to denied.

What we still record without consent. A count: which page was opened, for how long, and which country from, plus a cookieless ping to Google carrying no identifier. So that the count is of people rather than of page loads, each visit is grouped under a key our server derives from your connection and rotates every day. It is a one-way value: it cannot be turned back into your IP address, it cannot be joined to yesterday or tomorrow, and it is not linked back to a person. We rely on legitimate interests for that, and a tracker-blocking extension will stop it if you would rather it did not happen.

In your browser. You can also block or delete cookies through your browser settings, by site and by category. If you block strictly necessary cookies, parts of the Services will stop working, including sign-in and account security features.

Some browsers transmit "Do Not Track" (DNT) signals. Because no common industry standard governs DNT signals, our Services do not respond to DNT signals at this time. The consent bar described in section 5 is the control we do offer, and it is honoured on the server as well as in your browser.

If you access our Services from outside the United States, your information may be processed in the U.S. and other countries where our providers operate, subject to applicable legal safeguards.

We may update this Cookie Policy from time to time to reflect operational, legal, or regulatory changes. Updates will be posted on this page with a revised effective date.

Company name: THECRYPTOHUB LLC

Mailing address: South Governors Avenue, Dover, Delaware, US

Privacy email: hello@thecryptohub.io