sheet.guidePrivacy
Privacy policy
This policy explains how sheet.guide and its game subdomains (together, the “Sites”) use advertising, CDN and performance monitoring, privacy-friendly analytics, and error monitoring. Fan-made guides; not affiliated with any game publisher.
Effective date: 7 November 2026
1. Who we are
The Sites are operated as an unofficial reference for players. The primary domain is sheet.guide; individual games are hosted on subdomains such as wos.sheet.guide.
Questions about this policy: [email protected].
2. What this policy covers
When you visit the Sites, data may be processed for:
- Google AdSense — display advertising (and Google’s consent / CMP messages where required). This is our only intentional external advertising vendor for visitor traffic.
- Cloudflare — DNS, CDN, DDoS/bot protection, and Cloudflare Pages hosting for the Sites, including Cloudflare’s Real User Monitoring (RUM) / performance analytics that come with normal consumer use of their network
- Plausible Analytics — privacy-oriented site analytics, self-hosted on infrastructure we control for sheet.guide
- Sentry — application error and performance monitoring, self-hosted on infrastructure we control for sheet.guide
Self-hosting Plausible and Sentry keeps product analytics and error data isolated to the sheet.guide platform; we do not send that telemetry to Plausible Cloud or Sentry SaaS. External processors that necessarily see visitor traffic are Google AdSense (ads) and Cloudflare (edge delivery, security, and RUM).
We do not run user accounts on the Sites. Game tip checklists may be stored in your browser’s localStorage only on your device and are not sent to us.
3. Google AdSense (advertising)
We use Google AdSense (publisher ID ca-pub-8076339593698860) to show ads that help keep the Sites free. Google and its partners may use cookies or similar technologies to serve ads, measure delivery, and (where allowed) personalize ads.
In regions covered by Google’s EU user consent policy (and similar rules), we use Google’s Consent Management Platform (CMP) via AdSense Privacy & messaging, together with Google Consent Mode v2. Until you grant relevant consent (or Google determines consent is not required for your request), advertising-related consent signals default to denied. After you choose in the CMP, Google updates those signals for ad storage, ad user data, and ad personalization as configured.
You can learn more and manage ad preferences here:
- How Google uses information from sites that use its services
- Google Ads Settings
- Opt out of personalized ads (Google)
Ads are placed outside primary hero content (for example after a list of games, or between guide sections). Ad blockers may prevent ads from loading; that does not change the rest of this policy.
4. Plausible Analytics (private analytics)
We run a self-hosted instance of Plausible Analytics on sheet.guide’s own platform to understand aggregate traffic (for example page views and referrers). Analytics events stay on infrastructure we operate; they are not sent to Plausible’s commercial cloud. Plausible is designed to be privacy-friendly: it does not use cookies for analytics, does not collect personal identifiers for a marketing profile, and does not track you across unrelated websites.
Typical data includes the page URL, referrer, browser, device type, country (coarse), and timestamps needed for counts. We use this to improve content and performance—not to identify you as an individual.
Product design notes (open-source Plausible) are described in Plausible’s data policy; our deployment keeps the resulting datasets under sheet.guide’s control. plausible.io/data-policy
5. Sentry (error analytics)
We run a self-hosted instance of Sentry on sheet.guide’s own platform to detect crashes, JavaScript errors, and related performance issues so we can fix bugs. Error events stay on infrastructure we operate; they are not sent to Sentry’s SaaS cloud. When an error occurs, our Sentry instance may store technical details such as:
- Error message and stack trace
- Browser and operating system information
- URL or route where the error happened
- Release / environment metadata we configure
We configure Sentry for operational debugging, not advertising. We do not intentionally send form passwords or guide content typed into calculators as PII; event payloads may still include request context needed to reproduce a bug.
6. Cloudflare (CDN, hosting, and RUM)
We use Cloudflare to deliver the Sites: DNS, content delivery network (CDN) caching, TLS termination, DDoS and bot mitigation, and Cloudflare Pages hosting. Every request to the Sites typically passes through Cloudflare’s edge network as part of ordinary CDN use.
In that role, Cloudflare may process technical data needed to route, cache, secure, and measure the Sites, for example:
- IP address and approximate location derived from it (country / region)
- Requested URL, HTTP method, headers such as User-Agent and Referer, response status, and timing
- Edge PoP / data-center identifiers and network metadata used for routing and performance
- Security signals used for bot management, challenges, rate limits, and abuse prevention (which may involve short-lived cookies such as
__cf_bmor similar Cloudflare cookies)
Cloudflare may retain request and security logs for operational, security, and abuse-prevention purposes under its own retention practices. We use these capabilities to keep the Sites available and safe—not to build advertising profiles.
We also use Cloudflare’s Real User Monitoring (RUM) / browser performance analytics (as offered with Cloudflare’s consumer CDN and related products). RUM collects aggregated or sampled performance metrics from browsers—such as page load and Core Web Vitals–style timings, navigation paths, and coarse device or connection characteristics—so we can see how fast the Sites feel in the real world. RUM is for performance and reliability, not ad targeting.
Cloudflare acts as an infrastructure and analytics processor for these edge and RUM features. Details of Cloudflare’s processing are described in Cloudflare’s privacy policy. Cloudflare Privacy Policy
7. Cookies and similar technologies
- AdSense / Google CMP — may set or read cookies and similar storage when ads or consent messaging run, subject to your CMP choices and applicable law.
- Cloudflare — may set security or bot-management cookies (for example
__cf_bm) and similar storage required for CDN, challenge, or session integrity features; RUM measurement may also use limited browser storage or beacons as described by Cloudflare. - Plausible — does not use cookies for its analytics.
- Sentry (self-hosted) — primarily uses error reports from the running app on our own infrastructure; it may use limited storage for session or replay features if we enable them later (we will update this policy if that changes materially).
- Local preferences — theme and checklist ticks may use
localStorageon your device only.
8. Legal bases and your choices (EEA / UK / similar)
Where GDPR or similar rules apply, advertising that relies on consent is shown only after you agree via the CMP (or as otherwise allowed by law / Google policy). CDN delivery, security, RUM performance monitoring, privacy-friendly analytics, and error monitoring are used to operate and improve the Sites (legitimate interests in running a reliable free reference), balanced against your rights.
Depending on your location, you may have rights to access, correct, delete, or restrict certain processing, and to object or withdraw consent. For AdSense personalization, use Google’s ads settings linked above. For requests about data we control on the Sites, email [email protected].
9. Children
The Sites are general audience fan references. We do not knowingly collect personal information from children for accounts or profiles. If you believe a child has provided personal data to us directly, contact us and we will delete it where appropriate.
10. International transfers
Cloudflare’s global edge network, site hosting (Cloudflare Pages), our self-hosted Plausible and Sentry instances, and Google AdSense may process or store data in the United States or other countries depending on where those systems run. For AdSense and Cloudflare, their policies describe the transfer mechanisms that apply. Product analytics and error data we self-host remain under sheet.guide’s operational control rather than Plausible Cloud or Sentry SaaS.
11. Changes
We may update this policy when our tools or practices change. The effective date at the top will be revised. Continued use of the Sites after an update means you acknowledge the revised policy.
12. Contact
Privacy questions: [email protected]