What a cookie is
A cookie is a small value a website can ask a browser to retain. Similar local-storage technologies can remember a session or preference. The name does not explain the purpose, so this policy groups technologies by what they actually do.
The public editorial pages do not require a gambling account and do not use advertising or affiliate tracking.
Necessary functions
WordPress can set session and preference cookies for signed-in administrators. Security or hosting layers may use a short-lived value to protect requests and distinguish abusive traffic. The contact form uses a server-generated nonce and a five-minute server-side rate-limit token; the form does not require an optional analytics cookie.
Necessary technology should be limited to delivery, security and requested form processing. It is not presented as a marketing preference.
Cloudflare performance analytics require action
A clean-browser network check on 13 July 2026 found that Cloudflare injects its Real User Monitoring performance beacon at the edge for supported browsers. The script loads from static.cloudflareinsights.com and sends performance measurements to Cloudflare. This is infrastructure behaviour, not an analytics choice implemented by the WordPress theme.
The current site has no prior-consent control for that beacon, so its injection does not meet this publisher’s rule that optional analytics load only after consent. It must be disabled in Cloudflare configuration before indexing, or a documented legal and consent review must prevent it from loading until consent. See Cloudflare’s Disable Real User Monitoring documentation.
Rejecting an optional purpose must not block access to the editorial information. Withdrawing consent should be as straightforward as giving it.
Current cookie and storage table
| Technology | Purpose | Status |
|---|---|---|
| WordPress administrator/session cookies | Signed-in administration and preferences | Necessary for administrators only |
| Contact rate-limit transient | Reduce repeated spam submissions | Server-side, five minutes |
| Cloudflare RUM beacon | Browser performance measurement | Edge-injected; must be disabled or placed behind valid consent before indexing |
| Advertising/affiliate tracking | Commercial attribution | Not used |
Choice, withdrawal and updates
Browser settings or privacy tools may block optional scripts, although the publisher must not rely on visitors to provide that protection. The Cloudflare RUM configuration needs to be disabled or placed behind a valid consent state before the indexing gate is removed.
The policy and consent choices need to be updated before any new vendor, purpose, cookie or retention period is enabled. Questions can be sent through the publisher contact form.
Return to the BCGAME.WIKI information hub.
Limits of the current storage record
The storage table has not yet been confirmed through a complete clean-browser review. A reliable check compares cookies, local storage and network requests before and after consent and after submitting the editorial contact form, while signed out of WordPress.
Administrator cookies are not evidence that every public visitor receives the same value. Conversely, absence in one short session does not prove a plugin or hosting layer can never set a security cookie. The table records the observed purpose; uncertain infrastructure details remain undisclosed because they have not been verified.
Changes require a new check
Activating analytics, a consent tool, embedded media or a new security service can change browser storage. Any such change requires an updated policy, any legally required consent and a fresh clean-profile review on desktop and mobile before the optional purpose is enabled.