Cookie Policy
Last updated: 2026-10-23
Summary
China AI Hub does not set tracking, analytics, or advertising cookies. We run no Google Analytics, no Meta Pixel, no Hotjar, no Clarity, and no advertising or retargeting networks. The site is static content with no accounts, no personalization, and no optional features that would require consent. The only cookies involved are strictly necessary technical measures set by our hosting provider, Cloudflare, to keep the site secure and operational.
What a cookie is
A cookie is a small text file that a website asks your browser to store and send back with later requests. Cookies are how websites "remember" things between page loads — a login, a language choice, or an advertising identifier. Some cookies are set by the site you are visiting (first-party); others are set by a different domain, usually an analytics or advertising provider (third-party). Cookies are also classified by lifetime: session cookies are deleted when you close the browser, while persistent cookies survive for a set period.
China AI Hub itself sets no first-party cookies of any kind — not session, not persistent, and not third-party. The only cookies that can appear are technical measures set at the infrastructure layer by our hosting provider, Cloudflare.
Cookie classification
The table below classifies cookies by the standard four categories. Because we set no optional cookies, three of the four categories are empty.
| Category | Purpose | Status on this site |
|---|---|---|
| Strictly necessary | Required for the site to function and remain secure. | Set only by Cloudflare (hosting provider), not by us — see below. |
| Performance / statistics | Measure how visitors use the site. | None. We run no analytics or statistics cookies. |
| Functional / preferences | Remember choices such as language or layout. | None. The site has no preference or personalization features. |
| Marketing / advertising | Target or measure advertising. | None. We serve no ads and run no ad or retargeting networks. |
Technical cookies from our hosting provider
The site is served by Cloudflare Pages. Cloudflare may set strictly necessary technical measures at the infrastructure level, for example:
- Bot management / security — Cloudflare may set a security token (e.g.
__cf_bm) to distinguish humans from bots during the loading of protected resources and to mitigate abuse. This is a session-level measure tied to a specific request. - Email protection — our contact email link is obfuscated by Cloudflare's email-protection feature, which runs a small script to decode the address in your browser. It does not track you.
These technical cookies are used to keep the site operational and secure — not to profile visitors, serve ads, or build marketing audiences. We do not read or combine them to identify individuals. Because they are set by Cloudflare rather than by our own scripts, their precise names, lifetime and behavior are governed by Cloudflare; consult Cloudflare's documentation for the current technical details. These measures are within the "strictly necessary" category and therefore do not require consent under consent-based frameworks.
Other tracking technologies
Cookies are not the only tracking mechanism, so we state our position on the others as well:
- Local storage / session storage — we do not write to your browser's local or session storage.
- Web beacons / tracking pixels — we do not use them.
- Fingerprinting — we do not fingerprint browsers or devices.
- ETags or cache-based tracking — we do not use such techniques.
In short, there is no first-party tracking of any kind on this site.
What we do NOT use
- No first-party analytics cookies
- No advertising or retargeting cookies
- No social-media tracking pixels
- No third-party marketing or cross-site tracking cookies
- No fingerprinting or similar tracking techniques
Why this matters for your privacy
Cookies are the main mechanism by which sites build persistent profiles of visitors across sessions and, in the case of third-party cookies, across the web. Because China AI Hub sets no cookies itself and runs no analytics or advertising partners, there is no profile to build: no browsing history is associated with you, no cross-site trail is created by this site, and no third party is inserted into your visits to observe them. The practical result is that reading this site leaves essentially the same footprint as reading any static document — the only technically necessary exception being the infrastructure-level measures from our host.
Why there is no consent banner
We do not display a cookie-consent banner because we set no optional cookies and run no analytics, advertising or tracking. Under consent-based frameworks such as the GDPR and the ePrivacy Directive, strictly necessary technical measures do not require consent, and there are no other cookies to which a consent choice could attach. Similarly, the site does not "sell" or "share" personal information in the CCPA sense, so no opt-out link is required.
If our practices change — for example, if we were ever to introduce analytics or another optional cookie — we would update this page and provide the appropriate consent mechanism before such cookies were set. That commitment is part of our data-minimization approach described in the Privacy Policy.
Managing cookies
Because we set no optional cookies, there is nothing to opt out of on this site itself. You can still clear or block cookies at any time through your browser settings. Most browsers let you view, delete and block cookies by site, or block all third-party cookies. Blocking cookies does not affect your ability to read this site, which is a static website with no accounts or personalized features.
- Google Chrome — Settings → Privacy and security → Cookies and other site data.
- Mozilla Firefox — Settings → Privacy & Security → Cookies and Site Data.
- Safari — Preferences → Privacy → Manage Website Data.
- Microsoft Edge — Settings → Cookies and site permissions.
Note that the strictly necessary measures described above are set by Cloudflare, not by us; blocking them generally does not prevent the site from loading, but Cloudflare's abuse protections may occasionally re-challenge a request. Because these are not consent-required cookies, the site continues to function with cookies blocked.
Cookies when you follow external links
This policy covers only the site itself. If you click a link that leaves the site, the destination may set its own cookies. Two common cases:
- WhatsApp. The footer's WhatsApp button opens
wa.me. Meta (which operates WhatsApp) may set its own cookies and process your interaction under Meta's cookie and privacy policies, not ours. - Vendor and source websites. Throughout the site we link to official vendor documentation, model cards, pricing pages and third-party sources. Those sites have their own cookie practices; their policies apply once you follow the link.
Cookie law and how it applies
Different frameworks treat cookies differently, and we note how each applies here:
- GDPR / ePrivacy Directive (EEA and UK). Consent is required for non-essential cookies. We set no non-essential cookies, and the strictly necessary measures set by Cloudflare are exempt from the consent requirement, so no consent banner is needed.
- CCPA / CPRA (California). The CCPA's opt-out obligations concern the "sale" or "sharing" of personal information; we do neither, so no "Do Not Sell or Share" link is required.
- Other jurisdictions. Because we set no tracking cookies at all, the site's cookie footprint is minimal everywhere, and no region-specific consent banner is necessary.
Do Not Track and Global Privacy Control
Some browsers send a "Do Not Track" (DNT) signal or a Global Privacy Control (GPC) signal. Because we run no tracking or analytics at all, there is nothing for those signals to disable; the site's behavior is the same whether or not such a signal is set. GPC is honored by definition here, since we never sell, share or target based on browsing behavior.
Cookie retention
We set no first-party cookies, so there is no first-party cookie to expire or retain. The
strictly necessary measures set by Cloudflare are session-scoped in practice (for example,
__cf_bm is cleared shortly after the request it protects, typically within about
30 minutes), but their exact lifetime is determined by Cloudflare and may vary with its
security configuration. For the precise retention of any Cloudflare-set measure, consult
Cloudflare's documentation.
Relationship to the Privacy Policy
This Cookie Policy is a supplement to the Privacy Policy, which describes the full data-handling picture: no accounts, no forms, no tracking, the technical logs from our hosting provider, and your rights under GDPR and CCPA. The two pages should be read together.
Changes to this policy
We may update this page if our use of cookies changes. The "Last updated" date at the top reflects the current version. Because we maintain no mailing list, please review this page when you have concerns. If we were ever to introduce analytics, advertising or any optional cookie, this page would be revised to reflect it before the cookie was set.
Contact
Questions about cookies: Martin.W — [email protected]. Related pages: Privacy · Terms · Disclaimer · About.
Related disclosures
This Cookie Policy is one part of the site's operating disclosures. The Funding Disclosure explains that the site runs no advertising and no affiliate links — which is why no marketing or retargeting cookies exist here — and the Privacy Policy covers the broader data-handling picture beyond cookies, including the technical logs from our hosting provider. Read all three pages for the complete picture of how the site treats your information.