Cookie Policy

Cookie Policy

Effective date: August 07, 2026

CryptoForumHub uses cookies and similar storage needed to operate accounts, sessions, security, preferences, and the Discourse forum.

Essential uses

• keep portal/forum users signed in;
• protect forms and sessions;
• remember basic preferences;
• prevent abuse and verify requests;
• support administrator TOTP and session security.

Cloudflare Turnstile

Application and selected security-sensitive forms use Cloudflare Turnstile. Turnstile may process technical information needed to determine whether a request is legitimate under Cloudflare's own policies. CryptoForumHub does not use Cloudflare as CDN/proxy in MVP.

Analytics

CryptoForumHub uses Google Analytics 4 across both cryptoforumhub.com and access.cryptoforumhub.com. Both sites report to the same Google Analytics property and use the same measurement identifier, so that a visit that moves between the forum and the access portal is counted as one visit rather than two.

Google Analytics 4 sets its own cookies to distinguish visitors and sessions and to record which pages were viewed and which source a visit arrived from.

CryptoForumHub does not send personal data to Google Analytics. In particular, it does not send your name, email address, social media profile, website, wallet address, token contract or explorer link, transaction details, or the free-text content of any form. Where an event needs to identify an application, it uses a random identifier generated for analytics only, which has no meaning outside CryptoForumHub's own systems and is not shown in any page address.

Advertising

CryptoForumHub does not use advertising cookies, advertising networks, or cross-site advertising profiles. If that changes, this Policy and the applicable consent controls will be updated first.

You can control cookies in your browser, but blocking essential cookies may prevent login or form submission.

Analytics cookies and your choice

Analytics is off until you choose it. When you first arrive we ask, and until you accept:

• the Google Analytics script is not loaded;
• no Google Analytics cookies are set;
• no analytics events are sent from your browser;
• no analytics events are sent about your activity.

We use Google Consent Mode v2 with analytics denied by default. Advertising signals (ad_storage, ad_user_data, ad_personalization) stay denied at all times, including after you accept analytics, because CryptoForumHub runs no advertising analytics.

The choice is shared, and it lasts 180 days

Your answer is stored in a first-party preference cookie (cfh_consent) scoped to cryptoforumhub.com, so one choice covers both the forum and the access portal. It is kept for 180 days, after which we ask again.

Changing your mind

Use Manage cookies in the footer of any page — on the forum and on the access portal. Rejecting takes effect immediately for everything sent from that point on, and nothing suppressed while you had refused is sent later if you change your mind.

Rejecting analytics does not affect reading the forum, submitting an application, verification, invitations, your account, the Publishing API, or anything else.

Rejecting analytics changes nothing else

Reading the forum, applying, confirming your email, signing in, verification, invitations, forum-account linking, your account dashboard and the Publishing API all work exactly the same either way. Analytics is never a condition of access.

Analytics is limited to your browsing

Google Analytics sees pages you view and a small set of interactions on our own site — which plan you looked at, that you began an application, and that a submission succeeded. It does not receive what happens afterwards: the review of your application, the verification decision, your invitation, your account, your subscription, or your use of the Publishing API. Those stay in our own records.

What analytics records

Only controlled codes: which page group you landed on, broad audience type (provider, project, expert), plan code, stage of the application lifecycle, duration buckets, and device class. It never contains your name, email address, organisation, links you submitted, application reference, forum username, API key, or anything you typed into a form.