Privacy Policy

Controller and scope

Cookie Build is operated by Guillaume Claverie, who is the controller for personal data processed by the Cookie Build Minecraft server, website, and companion app. Contact support@cookie-build.com for privacy questions or requests. This policy covers the app, website, and game services.

Data we process

• A pseudonymous Firebase identifier created by anonymous authentication.
• Technical authentication diagnostics automatically processed by Firebase, such as IP address, operating system, device model, brand, form factor, installer, SDK versions, and Firebase app identifier.
• Minecraft UUID, display name, Java or Bedrock edition, link status, and gameplay statistics.
• Personal seasonal rank, per-game match history and activity, aggregate minigame XP, achievements, earned coin balance, unlocked and selected kits, and daily and weekly goal progress. Goal resets use UTC.
• Skyblock island membership and role, progression, quests, workers, virtual storage quantities, marketplace quotes/listings/sales, and the state and timestamps of crash-safe inventory deposits.
• Structured friend requests, accepted friendships, blocks, report reason, parties, members, invitations, and fixed-format player calls. The app has no free-form chat.
• Friend suggestions calculated on demand from completed matches shared in the last 30 days. Suggestions do not expose the match, time, score, online state, or last-seen time, and exclude existing relationships, blocks, and reports.
• Presence derived from active game sessions. It is available only to accepted friends and current party members, subject to the player’s friends-and-party, friends-only, or hidden setting and all blocks.
• For opted-in notifications: installation ID, FCM token, platform, app version, locale, authorization state, quiet hours, daily/weekly reminder choices, and an optional online alert selected for an accepted friend. Cookie Build does not support silently following arbitrary players.
• A limited in-game app-reminder counter and last-display date, used to avoid repeatedly promoting the app to an unlinked player.
• While legacy version 1.2.3 remains available to older Android devices: Minecraft nickname, Google Play product and purchase history, purchase token and signature, and app-view interactions used by the former shop and Google App Indexing integration.
• Short-lived security information such as IP-based rate-limit counters and operational logs.
• For web commerce: the Minecraft player UUID and name used for the commerce session, a hash of the session token, order and product references, total price and currency, Stripe customer/Checkout/subscription/payment/invoice/charge/refund/dispute identifiers and statuses, entitlement source, purchase history, and the exact version and timestamps of terms, immediate-performance, withdrawal-waiver, cancellation, and withdrawal actions.

The current app does not use advertising identifiers, cross-app tracking, Firebase Analytics, Crashlytics, precise location, contacts, microphone, camera, or payment data. Legacy version 1.2.3 transmitted its shop requests over an unencrypted connection; the update replaces that implementation on compatible devices. This statement concerns the mobile app only. Web payments are hosted by Stripe: Stripe processes contact, billing and card/payment details. Cookie Build does not receive or store full card numbers or card security codes. Public Minecraft names and gameplay statistics can appear in leaderboards.

Purposes and legal bases

• Contract: authenticate the app, link the correct player, provide stats, history, rank, goal progression, Skyblock island/storage and earned-coin marketplace management, earned-coin kit unlocks and selections, privacy-scoped presence, friends and recent-player suggestions, parties, events, and requested account controls.
• Contract and pre-contractual steps: link the purchasing player, fulfil web orders and subscriptions, show purchase history, and provide cancellation and support.
• Legal obligations: retain transaction and consent evidence for applicable accounting, tax and consumer-law periods.
• Consent: send push notifications, including separately configurable player calls, goal reminders, and selected accepted-friend online alerts, only after the corresponding in-app opt-in. Consent can be withdrawn in Settings. Quiet hours suppress these notifications.
• Legitimate interests: secure accounts, prevent abuse, moderate reports, keep games fair, diagnose incidents, and protect service availability.
• Legitimate interests: reconcile Stripe events, prevent duplicate or fraudulent orders, secure sessions, handle payment disputes, and preserve minimal evidence needed to defend legal claims.

Cookie Build does not sell personal data or use it for targeted advertising.

Recipients and international transfers

Google Firebase provides anonymous authentication and push delivery. The legacy app also shared app-view interactions with Google App Indexing. Apple and Google distribute the app. Current website and companion source builds proxy public Minecraft avatars through Cookie Build using the public UUID, so mc-heads.net does not receive the requesting device's IP address or player display name. A legacy app build may still load avatars directly and disclose those values until it is removed from every store track. EU-based infrastructure providers host the website, API, database, monitoring, and Minecraft server. These providers process only the data needed for their services under their own terms and data-processing safeguards. Firebase or store services may process data outside the EEA using applicable transfer mechanisms such as adequacy decisions or standard contractual clauses.

Stripe provides hosted Checkout, billing, invoicing, refunds, disputes and the Customer Portal. Stripe acts under its own privacy information for payment data and may process data outside the EEA using its applicable transfer safeguards. Cookie Build sends Stripe the Minecraft player UUID and name, along with the order and product references needed to process and reconcile the transaction.

Retention

• One-time link codes expire after 10 minutes; challenge audit rows are removed after 7 days.
• Active mobile profile, player links, and notification data are kept while needed to provide the app or until mobile-account deletion.
• Friendships, blocks, and active parties are server records keyed to the Minecraft UUID. They remain until removed in the app or game, the party ends, or the published cleanup period applies.
• A friend-request timestamp prevents repeat contact for 30 days after a request is cancelled or declined; the timestamp is removed after 90 days.
• Revoked devices are removed after 30 days; revoked player links after 12 months.
• Declined/expired requests, invitations, and ended-party records are removed after 90 days.
• Reports are kept for up to 24 months, or longer while a safety case or legal obligation remains open.
• Delivered notification jobs and deleted-account tombstones are removed after 90 days and 30 days respectively.
• Match results and aggregate gameplay statistics remain for the life of the server for public leaderboards, fair-play, and match integrity, unless law requires earlier deletion.
• Daily/weekly goal progress, achievements, XP, coins, and the app-promotion limiter are Minecraft gameplay records and follow the game-statistics retention period.
• Access through a web commerce session is valid for up to 30 days and can be revoked earlier by the player. Expiry does not delete the associated transaction records.
• Orders, payment status, refunds, disputes, invoices and consent evidence may need to be retained for accounting, tax, consumer-protection and legal claims. Contact support to request a review or erasure of your commerce records. Requests are reviewed individually, taking account of applicable retention obligations.
• Skyblock island progress, storage, market transactions, and crash-recovery deposit records are Minecraft gameplay and integrity records and follow the game-statistics retention period.

Your choices and rights

The app works for status, news, events, and leaderboards without linking a player. You can disable notifications, unlink a player, copy your app-account data, and delete the mobile account from Settings. Deletion removes the pseudonymous mobile profile, devices, preferences, per-friend online-alert selections, and mobile player links. It does not erase the Minecraft name, friendships, blocks, party or safety records keyed to that player, or integrity records from public gameplay history. It also does not erase rank inputs, XP, coins, achievements, or daily/weekly goal progress, Skyblock island/storage, market, or deposit records, which are gameplay records rather than mobile-account data; those use their own controls and retention periods above.

Depending on your location, you may request access, correction, deletion, restriction, portability, or objection, and may withdraw consent. Contact the address above. You may also complain to your local data-protection authority; in France, this is the CNIL. The no-app deletion flow is available on the account-deletion page.

Deleting the mobile account does not delete the separate Minecraft-linked commerce history. A privacy request can cover it, subject to mandatory invoice, accounting, fraud-prevention and legal-claims retention.

Age and changes

The companion app is intended for players aged 13 or older. A player below the age at which they can consent to online services in their country must use Cookie Build only with a parent or guardian. We will post material policy changes here and update the effective date.