Wyrmjoust — Privacy Policy
Portrait dragon-rider duel roguelite — read the tell, shape your altitude, match the sigil.
Summary
This policy covers the Android and iOS editions of Wyrmjoust: Scalebreak (com.dizzywalk.wyrmjoust), distributed through Google Play and Apple's App Store. You can play without creating a game account; progress and settings are stored on your device. The game uses AppLovin MAX for banner, interstitial, app-open and optional rewarded ads; Google Play or Apple processes optional in-app purchases, with RevenueCat managing purchase records and entitlements. PostHog and Google Analytics for Firebase measure play, UXCam records session replays on Android (the screens you visit, taps and gestures, game events and, on some devices, a video of the app's screen) so we can find confusing screens and fix crashes, Tenjin measures install attribution and permitted purchase/ad revenue, and Sentry reports errors and crashes. Analytics, advertising and attribution follow the privacy choices described below. Google's consent service asks for consent where required. On iOS, Apple's separate tracking-permission choice controls access to the advertising identifier; refusing that permission does not stop purchases or all permitted measurement. The Android notification features described below do not apply to the current iOS edition.
The browser version at wyrmjoust.onrender.com is a separate, earlier build with its own privacy notice at wyrmjoust.onrender.com/privacy.html.
Data stored on your device
- Your game save: campaign and duel progress, dragons, upgrades, currencies, pass and event progress, and settings
- A random install identifier created on first launch (not derived from your device, account or advertising ID), the records the game keeps of purchases it has already delivered, and cached remote settings
- A short queue of analytics events waiting to be sent, and your consent answers as stored by Google's consent message
- Android only: reminder notifications you allowed, scheduled on the device itself
- On iOS, the game also keeps verified Apple transaction data and pending purchase-attribution records on the device. Product and transaction identifiers, purchase dates and revocation information support purchase recovery, dated pass or membership restoration, and prevention of duplicate delivery or reporting. These records are separate from gameplay progress.
- Android backup: the app does not opt out of Android Auto Backup. If backup is turned on for your Google account, Android may back up the save and the install identifier and restore them when you reinstall or move to a new phone. The backup is handled by Android and Google; we do not receive it.
Data we collect
Consent and privacy choices
In the European Economic Area, the United Kingdom and Switzerland, Google's consent message (Google User Messaging Platform) is shown after your first duel result, and again at later launches until you answer it. Until you answer, no ad is requested and no analytics, session replay, attribution or crash report is sent. If you consent to personalised advertising (storing and accessing information on your device, building and using an ads profile), ads may be personalised and analytics, session replay, attribution and crash reporting run; AppLovin and Tenjin also need your consent as individual providers in that message. If you decline, the game still shows ads, but non-personalised ones: AppLovin MAX is told you did not consent and not to sell your data, and no PostHog or Firebase analytics (events waiting in the game's queues are deleted), UXCam session replay (a replay already in progress is stopped and deleted), Tenjin attribution or Sentry crash reports are sent. If the consent check cannot reach Google, the game keeps your last recorded answer; with no answer on record it requests no personalised ads and sends no attribution data until the check succeeds. To change your answer, open the pause menu during a duel and tap PRIVACY OPTIONS; the button appears whenever Google's consent service says privacy options apply to you, and your new answer takes effect at once. If Google's consent message offers you a US state privacy choice and you opt out of the sale or sharing of your data or of targeted advertising, the game tells AppLovin MAX not to sell your data and reports ad personalisation as denied to Tenjin. In all regions you can reset or delete your advertising ID, or opt out of ads personalisation, in your Android settings. On iOS, Apple's App Tracking Transparency permission is separate from Google's consent message. If tracking permission is denied or restricted, the advertising identifier is unavailable. Where your other privacy choices allow it, the game can still perform measurement without that identifier. You can review Apple's tracking permission in iOS Settings. A refusal of analytics or attribution consent is applied to those services separately; making or restoring a purchase does not require advertising or analytics consent.
Advertising by platform
AppLovin MAX runs an auction among AppLovin and the ad networks it mediates in this game: Google AdMob, Meta Audience Network, Unity Ads and Liftoff Monetize (Vungle); Pangle, InMobi, Bigo Ads, ironSource (Unity LevelPlay) and Mintegral are added in the update after version 1.10.0. The Meta Audience Network SDK is removed starting with version 1.10.3; older installed versions may still contain it. MAX and the included networks may process your advertising ID, IP address (from which an approximate location can be estimated), device and app information, consent signals, ad interactions and ad-impression revenue, to serve and measure ads, limit how often they appear, prevent fraud and, subject to the choices above, personalise ads. The game gives MAX a user identifier made from the random install identifier. The network roster above describes the Android versions identified there. The current iOS configuration uses AppLovin ads and AppLovin Exchange through MAX, with Google AdMob bidding. These providers may process device and app information, IP address, permitted advertising identifiers, consent signals, ad interactions and impression revenue for ad delivery, measurement and fraud prevention, and for personalization where permitted. A provider present in an SDK or configured in mediation is not evidence that it serves every ad.
Google Analytics for Firebase (Android 1.10.3+ and iOS)
Android version 1.10.3 and later and the iOS edition use Google Analytics for Firebase. When analytics is permitted, Google receives SDK-generated app-instance identifiers, app and device information, app activity, tutorial and duel outcomes, and ad-impression revenue and currency. Store-purchase measurement is handled by the Firebase SDK where supported; the game does not manually duplicate those purchase events into Firebase. Advertising-storage, advertising-user-data and advertising-personalization signals follow the game's privacy choices. The game keeps pending-event and replay records on the device. This analytics integration does not collect a notification token; Android remote messaging is a separate feature.
Remote notifications (Android 1.10.4 and later)
If you opt in to remote reminders and news, Firebase Cloud Messaging processes an installation identifier and device-specific registration token, plus technical app and delivery information, to send notifications to this app. The token is managed by the Firebase SDK and is not sent to PostHog or a separate Dizzywalk token registry. Remote messages are separate from reminders scheduled locally on the device. Notification permission does not enable gameplay analytics; analytics follows its own privacy choice above. Android only: remote reminders and game news from version 1.10.4 require the separate opt-in and notification permission already described. The current iOS edition does not register for Firebase Cloud Messaging or collect an FCM registration token.
Product analytics (PostHog)
PostHog receives events about how the game is played: sessions, duels, progression, tutorial steps, store and offer views, purchase attempts and results (product, price, currency, transaction ID and Google Play order number), ad events with their impression revenue, reminder-prompt answers, your consent state, and stability diagnostics such as whether the save loaded and when the web page of an ad stops unexpectedly. Each event carries the random install identifier, a session identifier, the app version and build, a coarse device tier (low, mid or high), the experiment groups the install is in, the country of the connection as reported by AppLovin MAX, and, from Android version 1.10.13 and subject to attribution consent, the install source that Tenjin reports: whether the install is organic or the ad network, campaign, ad group, creative and publisher site it attributes the install to. The game does not send your advertising ID, device model, screen size or OS version to PostHog. When session replay runs, PostHog also receives one record per recorded session with the links to that session and user in UXCam. PostHog receives the IP address of the connection and may derive an approximate location from it.
Install attribution (Tenjin)
Subject to attribution consent, Tenjin receives device and app information, IP address and permitted advertising identifiers to attribute installs, together with app-open and progress milestones, permitted completed-purchase information and AppLovin MAX impression revenue. Purchase information includes product, amount, currency and transaction identifier. Android forwards the Google Play receipt; iOS forwards Apple-verified signed transaction data for permitted production purchase reporting. On iOS, access to the advertising identifier also depends on Apple's tracking permission. The game retains pending reporting and duplicate-prevention records on the device. Attribution permission does not determine whether a purchased benefit is delivered.
Purchases
Google Play handles Android payments and Apple handles iOS App Store payments. We do not receive your payment-card number or your Google or Apple password. RevenueCat processes the store purchase/transaction data, product and subscription status, and the app user ID derived from the random install identifier to load prices, verify purchases, manage entitlements and support restores. On iOS, the game also reads verified StoreKit transaction history to restore the correct dates and revocation state of non-renewing passes and memberships. A fresh purchase-status check may occur at launch; a player-requested restore can contact the store to recover eligible purchases. Purchases and restores are independent of advertising or analytics consent.
Crash reports (Sentry)
Sentry receives crash, error and app-not-responding reports and session health (whether a session ended normally or crashed): the error and stack trace, the app release and build, and device and OS details without your device's name. The game sends no user identifier, screenshot or view hierarchy to Sentry, and Sentry receives the IP address of the connection. When session replay runs, a report can also carry the link to the UXCam replay of that session (see Session replay). Crash reporting follows the analytics choice above: in the European Economic Area, the United Kingdom and Switzerland it runs only if you consented. We use these reports to find and fix crashes and to watch release stability. Crash and error reporting and session health apply to the configured Android and iOS editions, subject to analytics consent. Android app-not-responding reports are Android-specific. The configured reports exclude user-set device names, game user identifiers, screenshots and view hierarchies; network services still receive connection information such as IP address.
Session replay (UXCam, Android only)
On Android, to find confusing screens and fix crashes, the game records how it is used: the screens you visit, taps and gestures, game events such as tutorial steps, duel starts and results, offer views, purchase attempts and ad views, and, on some devices, a video replay of the app's screen, which can include ads shown in the game. This uses UXCam (UXCam Inc., our processor; data processed in the United States). Replays are linked to the random install identifier and to a device identifier that UXCam assigns, never to your name or store account. With each replay UXCam also receives the app version; device details (manufacturer and model, operating-system version, screen size and density, memory and storage size, language, mobile carrier, network type and whether the device is rooted); an approximate location (country and city, with coordinates estimated from the connection's IP address); and coarse game facts such as whether a purchase has been made, the country of the connection, the experiment groups the install is in and the campaign Tenjin attributes the install to. The game tells UXCam to hide the screen while you type a dragon name and while a purchase is in progress, and the Google Play and App Store purchase sheets are shown by the store, not by the game, so they are not part of a replay. A dragon name shown on other screens can appear in a replay. We do not sell this data or use it for advertising. Replays are kept only as long as we need them to find and fix problems, within UXCam's retention period for our account. In the European Economic Area, the United Kingdom and Switzerland, recording runs only if you agree in the consent message, and you can change that choice at any time with PRIVACY OPTIONS in the pause menu. Anywhere, you can ask us to delete your replays using the contact address below. The iOS edition does not record session replays.
Remote settings
At launch the game downloads a settings file from dizzywalk.com that tunes the game, its offers and its ads. The request carries no player data; the server receives the standard request information, such as your IP address, needed to answer it.
Reminder notifications (Android only)
After a won duel the game may ask whether you want reminders; if you say yes, Android asks for notification permission. Reminders (for example, a patrol ready to collect or a season about to end) are scheduled on your device and cancelled when you return to the game. Versions through 1.10.3 use local reminders only. In version 1.10.4 and later, remote reminders and game news require a new, separate opt-in as well as Android notification permission. An older local-reminder choice alone does not turn remote messages on. Declining remote messages preserves previously enabled local reminders. You can turn app notifications off in Android Settings. Your answers to the reminder prompt are recorded as analytics events. Android only: the local reminder scheduling and notification-permission flow described here. The current iOS edition does not schedule these reminder notifications.
Advertising
The game shows a banner ad at the bottom of the screen, interstitial ads at natural breaks such as after a duel result, app-open ads when the game starts or when you come back to it, and optional rewarded ads that you choose to watch for an in-game reward. The ads are served through AppLovin MAX and the networks listed above.
Third parties
We do not sell your data for money. Letting advertising partners use data to personalise ads can be a "sale" or "sharing" of personal information under some US state laws; the choices described above limit it. The providers below process data for the features described in this policy, and advertising partners also process data under their own privacy policies.
| Provider | What they do |
|---|---|
| AppLovin (MAX mediation and AppLovin ads) | ad delivery, measurement and fraud prevention, and personalised advertising subject to your choices |
| Android Ad networks mediated by MAX: Google AdMob, Meta Audience Network, Unity Ads, Liftoff Monetize (Vungle); from the update after 1.10.0 also Pangle, InMobi, Bigo Ads, ironSource (Unity LevelPlay) and Mintegral | bidding on and serving ads in the game, ad measurement, and personalised advertising subject to your choices; each under its own privacy policy |
| iOS networks mediated by MAX: AppLovin, AppLovin Exchange (ALX), and Google AdMob bidding | ad delivery, bidding, measurement and fraud prevention; personalization and identifiers subject to privacy choices and Apple tracking permission |
| Google (User Messaging Platform) | the consent message and privacy options in the European Economic Area, the United Kingdom and Switzerland, and any US state privacy message it shows |
| PostHog | product analytics (no advertising ID) |
| Google Analytics for Firebase (Android 1.10.3+ and iOS) | Android version 1.10.3 and later and the iOS edition use Google Analytics for Firebase. When analytics is permitted, Google receives SDK-generated app-instance identifiers, app and device information, app activity, tutorial and duel outcomes, and ad-impression revenue and currency. Store-purchase measurement is handled by the Firebase SDK where supported; the game does not manually duplicate those purchase events into Firebase. Advertising-storage, advertising-user-data and advertising-personalization signals follow the game's privacy choices. The game keeps pending-event and replay records on the device. This analytics integration does not collect a notification token; Android remote messaging is a separate feature. |
| Tenjin | install attribution, milestone and purchase measurement, and ad-revenue measurement |
| Google Play | payment, purchase verification, subscriptions, refunds, and in-app review and update flows |
| Apple (App Store and StoreKit) | iOS payments, verified purchase history, subscription and refund status, and tracking-permission controls |
| Google Firebase Cloud Messaging (Android 1.10.4 and later only) | optional remote reminders and game news after a separate opt-in and notification permission |
| RevenueCat | purchase records, subscription status, restores and entitlements |
| Sentry | crash, error and stability reporting |
| UXCam | session replay (Android only): screens visited, taps and gestures, game events and, on some devices, a video replay of the app's screen, with device details and an approximate location, linked to the random install identifier and a UXCam device identifier (processor; United States) |
| Dizzywalk (dizzywalk.com) | serving the remote settings file |
Children
Wyrmjoust: Scalebreak is not directed to children under 13 and does not knowingly collect personal data from children under 13. If you believe a child has provided personal data, contact us.
Your choices & data deletion
You can remove local game data using your device's app-storage controls or by deleting the app; operating-system backups or restored purchases can affect what returns after reinstalling. Removing the app does not cancel a subscription or erase store and provider records. Manage Google Play subscriptions in Google Play and App Store subscriptions in Apple's subscription settings. For privacy questions or deletion requests, contact the address below with the game name, your platform and enough information to identify the relevant record. If needed, provide a Google Play order number or an App Store transaction reference; do not send passwords, payment details or raw receipts. Stores and RevenueCat may retain purchase records needed for payments, refunds, recovery and applicable obligations.
Changes
We will update this policy as the game changes and revise the effective date above. Material changes will be reflected in the app and store listings where required.
Contact
Privacy questions and deletion requests: mtime88@gmail.com.
DIZZYWALK RECORDS LLC, 930 S 4th St Ste 209, Las Vegas, NV 89101-6845, US.