Analytics notice

Analytics preferences

Google Analytics 4 is enabled by default on the public pages listed below. It starts when you visit an eligible page, without a consent popup or an approval click. A browser that previously turned analytics off stays off. Turning analytics off does not prevent browsing, creating, downloading or using checkout when purchases are available.

Use Analytics preferences in a public page's footer and choose Turn off analytics to stop future analytics collection immediately in that browser, including purchase and registration source tracking. Choose Enable analytics there if you want to turn it on again. If saving a request to turn analytics off fails, collection remains off in the browser and the website retries that request. Turning analytics off cannot cancel a request already sent or automatically erase earlier records held by Google or our servers. Other browsers have separate preferences.

What analytics uses

We use analytics to understand visits, referral sources and which visits lead to confirmed purchases. While analytics is enabled, the following may be processed:

• Visits to a fixed set of public pages, such as the homepage, pricing and information pages. We remove URL query parameters and fragments from the page address sent to analytics.
• A safe external referring domain and short, screened utm_source, utm_medium, utm_campaign and utm_content campaign labels. We do not send referring-page paths or searches, utm_term, gclid or fbclid.
• Successful account creation and sign-in, with the method (email, Google or GitHub); these events are sent by the server only after the account or session is committed. Registration counts account creation, including an email account awaiting verification. Repeated sign-ins do not count as new registrations.
• Creation acceptance and completion observed in the public studio, the creation category, download requests and the file format. A download request does not prove the file finished downloading. No creation names, private download URLs or contents are sent.
• Google Analytics browser and session identifiers, cookie information and technical browser, device, language and network information. Requests to Google expose your IP address; Google may derive a general location from it.
• When production purchases are available, a server-confirmed purchase summary: an order reference, paid amount, currency, applicable tax, product package and payment time, linked to the browser and safe checkout source. Test payments, free credits and administrator credit adjustments are excluded. Before sending purchase information, we check that analytics has not been turned off and that the visit record is still valid.

When you create an account while analytics is enabled and a valid visit record is available, we also save the earliest collected referral domain, public landing page and screened campaign labels with your account to understand which visits lead to registration. This account-side record does not contain Google browser or session identifiers, and we do not send your account identity to Google.

Our analytics events do not include your email, name, account identifier, prompts, reference images, creation files, generated source or support messages. Account, administrator, sign-in and private creation routes are excluded. Automatic enhanced measurement, Google signals and advertising personalization are disabled for this integration. We do not send an advertising user identifier.

Google processes the information under its terms, including on infrastructure outside your country or region. See How Google uses information from sites or apps that use its services and Google's Privacy Policy. Analytics reports are for understanding the service; they are not the billing ledger and may not reflect subsequent refunds.

We also keep daily first-party counters for pricing views, package selections, checkout errors and redirects, creation acceptance, saved models and download requests while analytics is enabled. Events contain only fixed categories and package/file-format codes, never prompts, filenames, payment details or account identifiers. These counters use a 30-day reporting window and a pseudonymous analytics context. Browser-reported events are not proof of a payment, completed download or successful Minecraft installation.

Cookies, preference records and retention

The website uses a cookie to remember analytics settings for up to 180 days. While analytics is enabled, we configure Google Analytics identifiers for a 180-day expiry without extending it on each page load. Browser restrictions or clearing site data may shorten this period. Existing analytics cookies may remain after you turn analytics off until they expire or you clear them; the website disables future analytics collection.

The browser also remembers your preference locally and may hold a short campaign snapshot for the current browser session. We record whether analytics started automatically or you explicitly turned it on or off, together with the notice version, time, expiry and safe source information. This automatic record does not mean you clicked an agreement. Public-page analytics does not wait for this record to be saved; if saving it fails, we cannot link purchase or registration sources. Google sign-in and accepting account terms do not count as an analytics choice.

We retain the notice text that applies to each visit record. Expired records or records for an older notice cannot be reused for purchase reporting. Updating this notice does not reopen an explicit refusal or restore previously excluded purchase reports.

The 180-day period limits the settings and identifiers; it is not a promise that all server records, backups or previously sent Google data are physically deleted after 180 days. Retention also depends on Google's settings and terms and on our privacy, security and recordkeeping needs.

Privacy requests

This notice supplements the Privacy Policy. Choose Privacy or account data in Contact and support, or email support@mcmodmaker.com, to ask about access, correction, export or deletion of analytics-related data. Include the approximate visit dates and browser information if helpful; do not send passwords or payment details. We may need information to locate a browser-based record and will explain any verification requirements or deletion limits.