Who is responsible
minecraftthesift.com is an independent Minecraft guide. For a privacy question or a request concerning your information, contact support@minecraftthesift.com. Please identify the relevant email address or page without sending passwords, login codes, identity documents or private mod files.
Files and browser tools
Files selected in FileChecker stay in your browser. The checker reads limited package metadata in a local browser Worker. It does not upload the filename, file contents or extracted declarations to this site or a scanning service, and it does not execute JAR code. Its result is not a malware scan or a guarantee of authenticity, safety or runtime compatibility. Clearing the file removes the displayed result and resets the tool; leaving the page ends its local session.
Catalog searches, filters, the compatibility finder, portal finder and note simulator run in your browser. We do not send search text or entered game-version text to Google Analytics. When optional analytics is allowed, fixed choices and result categories can be measured, such as which tool was used and whether its result was compatible, incompatible or unknown. The analytics section below explains that separate data flow.
Cloudflare RUM is not loaded. Content and tool pages include ExoClick advertising under the regional and saved-preference rules below. Site-information pages have no advertising placements. There are no public visitor accounts or payment forms.
Newsletter information
Subscribing is optional. A selected email-updates topic is a preference, not an activated subscription. Requesting the confirmation email starts the process; the active confirmation step is required before updates begin. A submitted request alone does not activate a subscription. We use the address to send the confirmation and, after confirmation, The Sift updates. Sender: subscriptions@minecraftthesift.com; replies and support: support@minecraftthesift.com.
Cloudflare Workers processes the request, and a dedicated Cloudflare D1 database stores your email address, normalized address, subscription status, form source label, consent version, request/confirmation/withdrawal times and mail-processing state. Confirmation secrets are stored as hashes. We keep delivery records to distinguish accepted, failed and uncertain sending attempts and prevent duplicate sends. We also keep stop-mail records for unsubscribed addresses and verified permanent bounces or complaints.
Lark handles outgoing confirmation/update emails and support correspondence. This necessarily shares recipient addresses and message content with the mail provider. Mail-server acceptance does not prove inbox delivery. We do not sell subscriber information or add an address to unrelated mailing lists.
Each newsletter includes an unsubscribe link. Open the link and submit its unsubscribe form to stop future updates. Already submitted or in-flight messages cannot be recalled. Unsubscribing does not automatically erase all records: a minimal stop-mail record prevents accidental resending. A later subscription requires a new confirmation. Bounce/complaint suppression must be reviewed by the maintainer before it can be cleared, and clearing it does not reactivate a subscription.
Security and administration
To limit abuse, the application uses a time-varying keyed hash of the connecting IP for platform rate limiting; it does not store raw IP addresses in the newsletter database. The host still processes the original request and may maintain its own security or access logs.
The private administrator area uses one-time email codes and an eight-hour, Secure, HttpOnly, SameSite session cookie. It stores hashed session tokens, short-lived code verifiers and rate-limit records. These are necessary access controls, not visitor tracking. Only configured administrators can view subscriber data. Security sign-in emails for those administrators are separate from marketing preferences.
To detect service failures, we keep anonymous API totals in five-minute groups for seven days: a fixed operation category, HTTP response class and response-time range. These totals contain no email address, IP, visitor identifier, request text or query string. Operational alerts go to the site’s support mailbox.
Retention and deletion
The database’s daily maintenance is designed to remove expired sign-in codes, expired sessions and expired rate-limit records; unconfirmed requests are removed after 30 days without a new request. Expired codes cannot be used while waiting for cleanup. Delivery records older than 180 days are removed, and affected campaigns are closed to further sending so removed records cannot cause repeat delivery.
Active subscriptions are retained until withdrawal. After withdrawal, daily maintenance reduces the subscription record to the information needed to remember the stop-mail choice and validate its link. Minimal unsubscribe and bounce/complaint suppression records remain until an ownership-verified deletion request is processed. Removing an address from these records does not subscribe it again.
To request access, correction or deletion, email support@minecraftthesift.com from the affected mailbox and describe your request. We verify ownership before changing or deleting personal data and will confirm the scope and any outstanding steps. The deletion process targets that exact address; it is separate from unsubscribing. We will explain the next step and any information needed to complete the request.
Support messages held by Lark and Cloudflare platform logs/backups have provider-controlled settings and may require separate action. Deleting a database record does not remove previously delivered messages from recipients’ mailboxes. We will explain which records can be removed directly and which require a provider request.
Hosting and external links
Cloudflare serves the site and processes connection/request information, including IP addresses, to deliver pages and protect the service. Local file processing does not mean the website has no hosting data. See Cloudflare’s Privacy Policy for its processing.
Following an author, source, download or GitHub link opens another provider’s service under its own policies. We host no mod downloads. Information posted in public issues or discussions may be visible to others. Contact messages you choose to send are handled through Lark; keep unnecessary sensitive information out of them.
Video demonstrations use a YouTube player from youtube-nocookie.com. Loading the player sends connection information to YouTube, and playing a video sends playback information. The direct video link opens YouTube under its own policies.
We update this notice when the site’s services or data handling change. The modification date identifies the current notice. You can ask us about a particular service or an earlier request through the support address above.
See where information goes
| Action | Information involved | Destination and purpose |
|---|---|---|
| Read a public page | Connection and request information | Cloudflare delivers and protects the page |
| Inspect a local package | Selected file and supported metadata | Your browser performs the inspection |
| Request email updates | Email address and request state | Workers and D1 manage confirmation; Lark delivers mail |
| Confirm or stop updates | A valid request and resulting subscription state | D1 records the business change |
| Contact support | Your email and the information you send | Lark holds the conversation for handling your request |
| Use a page or tool with analytics allowed | Clean public path and fixed interaction categories | Google Analytics measures use of the site |
| View an advertisement when advertising is allowed | Fixed page-topic words, connection and browser/device information | ExoClick and its advertising partners deliver and measure advertisements |
| Change privacy preferences | Separate analytics and advertising choices, policy version and decision/expiry times | Local browser storage controls these optional purposes |
The rows are separate data flows. A local file staying on your device does not mean that the host receives no page request. Sending a support email does not upload the package you inspected. A newsletter confirmation does not grant permission to use its secret link as an analytics identifier. Understanding the separate flows lets you choose the action that matches your intention.
Optional analytics and your choices
We use Google Analytics 4 to understand public-page visits and the use of site tools. It helps us see which guides readers use and where a tool returns an unresolved result. Google’s enhanced measurement is disabled; the site sends its own limited page and interaction events. Google Signals and advertising personalization are disabled. Cloudflare RUM is not loaded.
Visitors identified as being in the European Economic Area, the United Kingdom or Switzerland receive a choice before analytics loads. Accept and reject are equally available. Until you choose to allow analytics, it remains off. Reading, using tools, subscribing and unsubscribing work with either choice.
In other known regions, the site’s regional policy allows analytics without an automatic prompt. You can open Privacy choices in the footer and reject analytics at any time. This regional permission is recorded as a policy state, not as your explicit agreement. A valid saved rejection takes priority even if your location changes. An unknown region, a Global Privacy Control signal, or unavailable preference storage keeps analytics off. Unknown regions do not receive an automatic location-based prompt.
The site obtains only a coarse region category through its own service. The browser does not request location from a separate geolocation provider. The host uses request information to determine the category; the privacy interface does not receive your raw IP address or exact location.
Your explicit choice is stored in this browser’s localStorage with a policy version, decision time and expiry time. It is valid for 180 days, whether you accept or reject. After expiry the site ignores that saved choice and applies the regional policy again. Expiry does not physically delete the localStorage entry. You can remove it through browser site-data controls; a later choice replaces the saved setting. Preferences belong to this browser, so another browser or device can have a different choice.
Rejecting analytics disables future collection through the site’s analytics controls, clears its pending event queue and removes accessible Google Analytics cookies for this site. Events from a period when analytics was off are not saved for later replay. Withdrawal does not delete information already held by Google. To discuss an existing record or a deletion request, contact us using the support address above.
Analytics cookies are configured to expire after 180 days, without extending their lifetime on each activity. GA4 user- and event-level data retention is set to two months. This setting is separate from cookie lifetime and does not set the lifetime of aggregate reports. Clearing cookies, withdrawing permission and requesting deletion are distinct actions with different effects.
Keep measurement separate from private inputs
Optional usage measurement is limited to public page paths and fixed choices or outcomes, such as the selected project, tool category, and result type. A tool click describes an action in this site, not proof that a game download completed. An unknown compatibility result remains unknown rather than becoming a successful installation metric.
Email addresses, filenames, package bytes, extracted file declarations, free search text, arbitrary version text, support messages, confirmation secrets and administrator codes are excluded from analytics parameters. Page locations contain only the public site origin and path, with query strings and fragments removed. Page titles sent to analytics use a fixed page category rather than user-entered text. Administration, API, confirmation-token, unsubscribe-token, demo and missing-page routes do not load the analytics adapter.
Referrer information is restricted to the HTTPS origin of three recognized search services: Google, Bing and DuckDuckGo. Their search paths, query strings and fragments are discarded; other referrers are sent as an empty value. Only predefined source and medium labels may be read from campaign links. Arbitrary campaign names and other URL parameters are excluded. Google Analytics can use its own client and session identifiers when allowed, so this measurement is not anonymous.
Google processes the permitted analytics data through its service. Its handling of service data is explained in Google’s Privacy Policy. The site does not add a persistent visitor identifier, User-ID or device fingerprint of its own. A general newsletter-request event can describe a form response, but it does not identify the address or mean that a subscription was activated.
Advertising and your choices
ExoClick serves advertisements on content and tool pages; site-information pages have no placements. Advertising and analytics have separate preferences. Open the footer control, select Customize, choose either purpose, and save your choices. Allow all and Reject all apply to both purposes. These settings do not change newsletter subscriptions or access to tools. An eligible placement can remain empty when no advertisement is available.
In the EEA, United Kingdom and Switzerland, the site does not request advertisements until you allow advertising. In other known regions, advertising follows the approved regional policy without an automatic prompt; you can reject it in the footer. A valid refusal, Global Privacy Control signal, unknown region or unavailable preference storage keeps advertising off. An older saved analytics acceptance does not count as an advertising acceptance in regions that require a choice. Older refusals remain effective.
The site supplies fixed, broad page-topic words such as minecraft, games and mods. Advertising requests do not include search text, email addresses, filenames, file contents or tool results. Advertisements run in a sandboxed frame with a separate browser origin; the frame cannot read this site’s forms, tools or localStorage. The frame’s initial referrer is restricted to the site origin, without page queries or fragments.
ExoClick and its partners can process IP addresses, browser and device information, language, approximate location and advertising interactions. They may use cookies or identifiers for delivery, measurement and advertising selection. Their handling is described in ExoClick’s Privacy Policy and Cookies Policy. These requests are a separate data flow from Google Analytics.
Explicit analytics and advertising choices are saved together for 180 days. Saving your selected settings confirms both displayed purposes. On withdrawal, the site removes its advertising frames and prevents new ones while the refusal remains effective. This stops active frame scripts; it cannot recall a request already sent, remove data already held by a provider, or delete cookies on another domain. Browser site-data controls and the provider’s privacy channels handle those separate actions. Third-party cookie restrictions or unavailable advertising inventory may also prevent an ad from appearing.
Google Consent Mode controls Google Analytics separately: analytics storage starts denied, and its advertising-storage, advertising-user-data and advertising-personalization fields remain denied. It does not control ExoClick. Cloudflare RUM remains off.
Confirmed subscriptions and withdrawals are business records in D1, not GA4 conversions. Each real status change creates a ledger entry with a random transition identifier, an internal subscriber reference, previous and new status, reason, time, flow version and fixed form-location fields. The entry does not copy the email address or confirmation token. Because the internal reference connects it to a subscriber record, the ledger is not anonymous.
The state update and ledger entry are committed together. Reopening a confirmation page does not activate a subscription, and repeating a completed confirmation or withdrawal does not create another state change. Confirming a later subscription creates a new change. Daily maintenance removes ledger entries older than 180 days; an ownership-verified deletion request removes the associated entries as part of deleting that subscriber’s records. The ledger is used for internal subscription counts and is not forwarded to Google Analytics.
Use the control that matches your request
Stopping optional analytics changes future measurement under the site’s controls. Stopping newsletters changes future email delivery. Requesting deletion concerns stored information. These actions can be requested separately; choosing one does not silently perform the other two.
If you want to stop updates quickly, use the unsubscribe route. If you also want an address removed from retained records, contact support from that address and request deletion. If your concern is measurement, open Privacy choices in the footer or ask support about your saved setting. Identify the relevant action without sending a secret link, package file, or unnecessary personal documents.
When a request involves a provider-controlled copy, We will explain the remaining scope rather than treating a change in the site’s database as proof that every previously delivered email or backup has disappeared. Keep the support conversation together so the requested action, verification, and outcome can be understood as one request.
