Privacy, without the vague fog
The guide works without an account. This page identifies the production services that can receive data, explains Google advertising technology, and records the controls required before ads are activated.
Information this site can receive
You do not need to register, create a profile, or submit personal information to read this guide. Like most hosted websites, the infrastructure may process basic request information such as an IP address, browser type, requested page, approximate time, referrer, and security signals. These logs can be used to deliver the site, prevent abuse, investigate errors, and understand aggregate demand.
If you email the site operator, the message contains the address and information you choose to provide. It is used to answer the request, investigate a correction, or maintain a record of the conversation. Do not send passwords, account tokens, world files containing private information, or anything unrelated to the guide question.
Production services and data flows
At the date of this policy, the production configuration uses Cloudflare to deliver and secure the site and can use measurement services to understand aggregate traffic and site performance. When enabled, these services can receive the requested page, IP address, browser and device characteristics, approximate location, referral source, timestamps, interactions, and diagnostic or security signals. That information is used to deliver, secure, measure, or diagnose the site.
Measurement can include page views, navigation, aggregate interaction events, and technical performance signals. This guide has no reader accounts, checkout, profile fields, or public comment forms, and the operator must not place names, email addresses, or other personally identifiable information in analytics events, page URLs, or advertising requests.
- No account is required to read the site.
- Provider scripts whose deployment variables are empty are not loaded.
- Cloudflare can retain delivery, security, and abuse-prevention logs under its service settings.
- External links, including Modrinth, have their own privacy practices.
Google advertising, cookies, and identifiers
The site is prepared to use Google AdSense after site approval. When Google advertising is active, third-party vendors, including Google, use cookies to serve ads based on a visitor's prior visits to this site or other websites. Google's use of advertising cookies enables Google and its partners to serve personalized ads where permitted and consented, or non-personalized or limited ads where applicable.
As a result of ad serving, Google and other third parties may place and read cookies in a visitor's browser, or use web beacons, IP addresses, device information, and other identifiers to collect information. Google and its partners may collect, share, and use that information to select and deliver ads, limit how often ads appear, prevent fraud and abuse, measure ad performance, produce aggregate reporting, and personalize advertising when the required permission exists.
The operator does not receive a visitor's Google advertising cookie contents and must not send personally identifiable information to Google through an ad request. Visitors can learn how Google uses information from partner sites and can control personalized advertising through Google Ads Settings.
Consent and regional advertising controls
Automatic AdSense ad requests are disabled in the site's application configuration by default. The release procedure permits the operator to activate them only after AdSense approval and after the required consent controls have been configured. Merely setting a publisher ID publishes ownership-verification metadata and ads.txt; it does not activate automatic ads.
Before advertising is activated for visitors in the European Economic Area, the United Kingdom, or Switzerland, the operator must enable a Google-certified consent management platform that integrates with the IAB Transparency and Consent Framework version 2.3. The consent flow must make the required disclosures and collect the required choices for cookies or local storage and for the collection, sharing, and use of personal data. Google advertising tags must not be called where the required consent signal is absent.
When a consent message is available, visitors can accept, reject, or manage the purposes and vendors presented there. Browser cookie controls, tracking protection, and the advertising-choice links on this page provide additional controls, although blocking third-party technology can reduce measurement or advertising functionality without restricting access to the written guide.
Purpose, retention, and your choices
Information is used to operate and secure the site, measure which guides solve real questions, prioritize corrections, and evaluate whether the project is sustainable. The operator should keep identifiable support correspondence and raw logs only as long as reasonably necessary for those purposes, legal obligations, backups, and security. Aggregate statistics may be retained longer because they do not describe a specific visitor in ordinary use.
You can use browser controls to block or delete cookies, enable tracking protection, or prevent third-party scripts from loading. You may ask about personal information included in a message you sent by using the configured contact address in the footer. You may also ask which production measurement services are currently enabled. This policy will be revised when the hosting, analytics, consent, or advertising setup materially changes; the revised date at the top identifies the active version.