KILLBOX PROTOCOL: Bot Mayhem — Privacy Policy
Listed on Google Play as GRAFT: Build-a-Beast Arena · Published by Dizzywalk
This Privacy Policy explains how Dizzywalk ("we", "us") handles information in connection with the game
KILLBOX PROTOCOL: Bot Mayhem (listed on Google Play as GRAFT: Build-a-Beast Arena), package / bundle
com.dizzywalk.graft (the "Game"). Both names refer to the same app. Capabilities depend on the version you
have installed; a section that describes something your version does not contain does not apply to it.
- There is no account and no login. Your progress, settings and purchased items are stored on your device.
- The Game is free and supported by ads, served through AppLovin MAX and the ad networks it works with. They use your device's advertising ID and related data to show and measure ads.
- Tenjin measures which ad campaign led to an install, PostHog and Google Analytics for Firebase record how the Game is played, and our first-party diagnostic service (Fleet Replay) records low-rate masked in-game screen frames and gameplay events when analytics is allowed.
- In the EEA, the UK and Switzerland, Google's consent message asks for your choice before ads, attribution, analytics or session replay start, and the PRIVACY CHOICES button on the title screen lets you change it.
- Google Play (on Android) or the Apple App Store (where available on iOS) processes purchases. We verify each purchase with the store and never receive your payment-card details.
- We do not sell your name, email or contact details; the Game does not ask for them.
What we collect and who receives it
- Device and other identifiers: your device's resettable advertising ID and similar SDK identifiers (read by the advertising SDKs and Tenjin), and a random identifier the Game creates for this installation. The installation identifier is attached to analytics events, game-tuning requests and first-party diagnostic session replays, and is passed to AppLovin as the Game's user identifier. It persists until you clear the app's data or uninstall.
- App activity (app interactions and masked screen frames): gameplay events such as opening the Game, tutorial steps, starting and finishing a bout, revives, shop and offer views, ad and purchase outcomes, and — when analytics is allowed — low-rate in-game screen frames (approximately one 720 px JPEG frame every 3 seconds) captured by our first-party Fleet Replay diagnostic recorder, with Settings, consent forms, store purchase sheets and full-screen ads masked or paused.
- Purchase history: product, price, currency, transaction or order identifiers and the store's purchase token or signed transaction receipt.
- Approximate location: every service the Game connects to receives your IP address, and the advertising partners, Tenjin, Firebase, PostHog and our first-party services may use it to estimate your country or region. The Game does not request GPS or precise location.
- App info and performance: device model, operating-system and app version, language, connection type, first-party replay frame/session diagnostics, and crash logs and diagnostics collected by the advertising SDKs (for example, the AppLovin SDK includes its own crash reporter that sends crash information to AppLovin).
The Game does not collect your name, email address, phone number, contacts, photos, files, messages or precise location, and it does not include a third-party crash-reporting service of its own (such as Sentry or Firebase Crashlytics).
Recipients: AppLovin (MAX mediation) and the ad networks it mediates; Tenjin (install attribution and ad measurement); Meta (Facebook SDK app events, where switched on; see below); PostHog and Google Analytics for Firebase (gameplay analytics, processed on our behalf); Render (hosting for our first-party game-tuning service and our first-party Fleet Replay diagnostic service); Google Play, Apple App Store (where available) and Unity In-App Purchasing (purchases); Supabase (hosting for our stateless purchase verification service); and Google's User Messaging Platform (the consent tool).
Advertising
The Game uses AppLovin MAX to show ads: rewarded videos that you choose to watch for an in-game reward, a banner, full-screen ads at breaks between bouts, and a full-screen ad when the Game opens or when you return to it. Ads never interrupt a bout. Some purchases remove the forced ad formats as stated in the store.
The networks that can compete to serve an ad through MAX in this version are Google AdMob (Google bidding), Meta Audience Network, BIGO Ads, Pangle, Chartboost, DT Exchange, InMobi, ironSource, Mintegral, Moloco, Unity Ads and Liftoff Monetize (Vungle). Their SDKs start with AppLovin's and can receive the data below even when they do not serve an ad; which network serves a given ad depends on availability.
Advertising SDKs can process your advertising ID and other device identifiers, IP address and the approximate location derived from it, device and app information, ad interactions (requests, impressions, clicks and rewards) and diagnostics, for ad delivery, frequency control, measurement and fraud prevention. Unless you are in a consent region and did not consent (see "Your choices"), they may also use this information to personalise the ads you see, including based on your activity in other apps. Non-personalised ads may still use operational and device data. Ad-enabled Android builds declare the advertising-ID permission.
On iOS, the Game asks for permission through Apple's App Tracking Transparency prompt before the advertising SDKs can read your device's advertising identifier (IDFA). If you decline, or later turn off "Allow Apps to Request to Track" in Settings > Privacy & Security > Tracking, the IDFA is not available to the Game or its SDKs and ads are not personalised based on your activity in other companies' apps.
You can reset or delete your advertising ID in Android's settings (Settings → Privacy → Ads on most devices). Provider policies: AppLovin, Google AdMob, Meta Audience Network, BIGO Ads, Pangle, Chartboost, DT Exchange, InMobi, ironSource, Mintegral, Moloco, Unity Ads and Liftoff (Vungle).
Attribution and advertising measurement (Tenjin)
Tenjin measures installs and advertising performance for us, for example which ad campaign led to an install and how much revenue installs from that campaign produce. Tenjin can receive your advertising ID, device and app information, your IP address, a small set of named milestones, purchase details (product, price, currency, transaction identifier and Google Play's signed receipt) and ad-revenue details for ads shown in the Game. Tenjin may share attribution results with the ad networks we buy ads from so they can measure their campaigns.
Tenjin connects only after Google's consent tool has answered. In a consent region, Tenjin is set to opted-in mode only if you consented to storing or accessing information on your device, and to opted-out mode otherwise; changing your answer in PRIVACY CHOICES updates it.
Meta (Facebook SDK app events)
Android versions from 0.9.5 include Meta's Facebook SDK core (app events only: no Facebook login, no sharing, no Facebook account link). It is switched off by default and is started only for a share of installs that we choose remotely, and only after Google's consent tool has answered; in a consent region it starts only if you consented to storing or accessing information on your device and your choices allow Meta. When it runs, it sends Meta app-activation and session events (the Game opening and closing), device and app information, your IP address and, if ad personalisation is allowed, your advertising ID, so Meta can measure the ad campaigns we run on its platforms and show those ads to people likely to enjoy the Game. It sends no purchase, gameplay or custom events. If you opted out of the sale or sharing of personal information under a US state privacy law, it runs in Meta's Limited Data Use mode; withdrawing consent turns its event logging and advertising-ID collection off.
Gameplay analytics, Firebase and first-party session diagnostics (PostHog, Firebase, Fleet Replay)
We use PostHog and (on Android) Google Analytics for Firebase to understand how the Game is played. Events describe the app activity listed above, together with the app package, app version, platform and the random installation identifier. They do not contain your name, contact details or payment-card details. At launch the Game also asks PostHog and our first-party configuration service (hosted on Render) for game-tuning settings (for example difficulty bands, ad pacing, value-threshold rules and offer rules); requests carry the installation identifier only when analytics is allowed. PostHog, Firebase and Render receive the IP address used to connect and may use it to estimate an approximate location.
To find where screens or game flows are confusing or broken, the Game also includes our first-party diagnostic recorder, Fleet Replay (operated by Dizzywalk and hosted on Render). When analytics is allowed, Fleet Replay captures low-rate frames of the Game's own screen (720 px JPEG at quality 70, roughly one frame every 3 seconds) alongside a reviewed subset of gameplay and store events and technical session metadata (screen name, app version, build number, country tier and experiment arm), linked to the same random installation identifier. Capture automatically pauses or masks the screen completely while Settings, privacy/consent forms, store purchase sheets or full-screen ads are open, and never captures text entry, payment-card details or anything outside the Game. Stored replays are subject to bounded project quotas and retention and are used solely by Dizzywalk to debug and improve the Game.
Analytics events, Firebase collection and Fleet Replay wait on your device until Google's consent tool has answered. In a consent region, they run only if you consented to storing or accessing information on your device; otherwise queued events are discarded and no analytics events or replay frames are sent.
League rivals (squads other players face)
When you play the League, the Game uploads your squad to our first-party game server (Supabase) so it can appear as a rival in other players' League brackets: a one-way hash of the Game's installation identifier (never the advertising ID), a callsign the Game generates for you (you do not type a name), your chapter, and your bots' roles, star levels, lanes, cards and upgrade levels. Other players see the callsign and the squad. We use it only to run the League and keep it fair. It is deleted on request (see "Your rights and deleting your data").
Local notification reminders
On first launch (after any required privacy prompt finishes), the Game asks once for your device's notification permission so it can schedule optional local on-device reminders (for example daily rewards or garage build completion). These reminders are scheduled locally on your device and do not register a remote push-notification token. You can decline the prompt or turn notifications off at any time in your device's system settings.
Your choices
EEA, UK and Switzerland
Each time the Game starts, before the advertising SDK initialises, it asks Google's User Messaging Platform (UMP) whether a consent message is required where you are. Where it is (currently the European Economic Area, the United Kingdom and Switzerland), Google's consent message is shown, and your choices are recorded in the industry-standard IAB Transparency and Consent Framework format, which AppLovin, the ad networks and Tenjin read directly.
- No ad is requested, Tenjin does not connect and no analytics event or Fleet Replay frame is sent until the consent tool has answered.
- Personalised ads are shown only if your choices allow them; otherwise ads and rewards keep working with non-personalised ads.
- Attribution (Tenjin), analytics (PostHog and Firebase) and first-party session diagnostics (Fleet Replay) run only if you consent to storing or accessing information on your device.
- You can change or withdraw your consent at any time with the PRIVACY CHOICES button on the title screen, which reopens Google's privacy options form. Withdrawal stops future analytics and Fleet Replay recording; it does not undo processing that already took place with your consent.
Everywhere else
Outside those regions Google's consent tool reports that no message is required, so there is no privacy prompt: advertising (including personalised advertising), attribution, analytics and Fleet Replay diagnostics start once the tool has answered. You can limit ad personalisation by resetting or deleting your advertising ID in your device's settings, and you can contact us to exercise any rights you have under local law (see "Your rights").
Purchases
The Game offers optional one-time and consumable purchases (for example starter packs, a season pass, a piggy bank and a VIP pack that removes forced ads). Prices and contents are shown before you buy. Google Play (on Android) or the Apple App Store (where available on iOS) processes payment through Unity In-App Purchasing; we do not receive payment-card details. Unity In-App Purchasing can process device, purchase and diagnostic information as described in Unity's Game Player and App User Privacy Policy.
Before an item is granted, the Game sends the package/bundle name, product identifier and the store's purchase token or signed transaction over HTTPS to our verification service, hosted on Supabase, which verifies the purchase with Google Play or Apple and returns the result. The verification service does not store your purchase in a database; our hosting provider keeps routine request logs, including the IP address, for a limited period. Your purchase history and purchased items are recorded on your device (and durable non-consumable entitlements can be restored from the store after a reinstall), and purchase events are reported to PostHog, Firebase, Fleet Replay and Tenjin as described above.
Children's privacy
The Game is a robot-combat action game intended for a general audience aged 13 and older. It is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child under 13 has provided us information, contact us and we will delete it.
Data retention and security
Data on your device stays there until you clear the app's data or uninstall the Game (subject to platform backup). Analytics events and Fleet Replay diagnostic sessions are kept only as long as needed to understand, debug and improve the Game (Fleet Replay enforces bounded retention and storage quotas, after which old sessions and frames are automatically deleted). Providers retain the data they receive under their own policies, linked above. All data the Game transmits is encrypted in transit (HTTPS).
Your rights and deleting your data
Depending on where you live (for example under the GDPR, the UK GDPR or US state privacy laws such as the CCPA/CPRA), you may have rights to access, correct or delete information about you, to object to or restrict processing, and to opt out of the sale or sharing of personal information for targeted advertising. To make a request, including a request to delete data associated with your installation, email kristine@dizzywalk.com with the subject "KILLBOX privacy request". Because the Game has no account, include your device model and approximate install date so we can find the relevant records; we may ask for additional information to confirm the request. Clearing the app's data or uninstalling removes the data stored on your device and creates a new installation identifier the next time you play, but does not by itself erase records already held by us or by the providers above. You can also reset or delete your advertising ID in Android's settings. We honour the Google Play Data safety declaration for the released build.
Contact us
Questions about this policy or your data? Email us at kristine@dizzywalk.com.
Changes to this policy
If we change how the Game handles data, we will update this page and revise the "Last updated" date above. Material changes will be reflected here before they take effect.