Crown Out — Privacy Policy
Slide the blocks and guide the King to the exit across 175 puzzles in seven courts.
Crown Out for iOS — separate privacy notice
This section covers Crown Out: Block Escape for iPhone and iPad (com.dizzywalk.foursquare), published by DIZZYWALK RECORDS LLC. You can play without creating a game account. The Android notice and version history below apply to Android only; their Google Play purchase and Android partner descriptions do not describe iOS.
Device data and online services
The game stores progress, currency, inventory, purchase-delivery and entitlement records, preferences, privacy choices, cached configuration and random installation identifiers on your device. These identifiers are pseudonymous, not a promise of anonymity. Functional HTTPS requests download game configuration independently of optional analytics. The configuration request adds no player or advertising identifier, but receiving services still see connection information such as IP address. Online services use connection and technical information to deliver services, diagnose problems and prevent abuse.
Advertising and regional choices
AppLovin MAX supports banners, interstitials at gameplay breaks, optional rewarded ads and app-open ads. The iOS integration includes Google AdMob, Liftoff Monetize/Vungle, Unity Ads, Pangle, InMobi and BIGO Ads mediation libraries. Available ads depend on provider configuration and demand. These providers may process device and permitted advertising identifiers, IP address and approximate location inferred from it, app/device/OS information, ad impressions, clicks, rewards and diagnostics for delivery, measurement and fraud prevention. Their own advertising SDK diagnostics are separate from the game's Usage + diagnostics switch. Non-personalized or limited ads still involve data processing. Google User Messaging Platform (UMP) checks regional consent requirements and presents applicable choices; ad requests wait for the game's consent-readiness decision. In the EEA, UK and Switzerland, applicable consent choices govern personalization and measurement. Canada starts Personalized ads and Usage + diagnostics off. Where the region is unresolved, optional reporting remains restricted; elsewhere these switches default on and can be changed.
Apple tracking permission and attribution
Apple's App Tracking Transparency (ATT) choice controls permission for cross-company tracking and access to IDFA, the advertising identifier. It is separate from UMP and the game's Usage + diagnostics choice. Denying ATT does not prevent gameplay, purchases or permitted first-party usage measurement. Tenjin's full attribution forwarding requires ATT authorization plus the game's regional privacy conditions. In opt-in regions it also requires permitted usage reporting and personalized advertising; elsewhere it is enabled unless Do Not Sell or Share My Data is on. When allowed, Tenjin processes install, session, purchase and ad-revenue information, available identifiers, IP address and device/app details to measure campaigns, with configured advertising channels receiving attribution/conversion information.
Usage measurement and diagnostics
When Usage + diagnostics and the applicable regional decision permit reporting, PostHog receives gameplay, session, level, offer, purchase and ad events with technical information and a random installation identifier. Google Analytics for Firebase receives app-instance/device identifiers, app interactions, purchase product/value/currency/transaction information and ad-impression revenue. Firebase advertising-use signals additionally require ATT and the applicable advertising choices. Sentry receives crash/error reports, stack traces and technical context when diagnostic reporting is permitted. These services help us understand play, improve reliability and, where advertising permissions allow, measure campaign performance. We do not describe this information as unidentifiable.
Apple purchases, restoration and refunds
Apple processes payments through StoreKit and Unity In-App Purchasing. We do not receive your payment-card number or Apple Account password. The game handles product, transaction, receipt, price, currency and entitlement information to verify and deliver purchases, reconcile eligible restored purchases and subscriptions, prevent duplicate delivery and respond to verified refunds or revocations. Purchase measurement is sent to analytics/attribution services only when their respective conditions permit it; Tenjin may receive verified transaction information for revenue attribution. Restore purchases does not guarantee recovery of spent consumables or all local progress. Manage or cancel auto-renewing subscriptions through your Apple Account subscriptions settings; deleting the app does not cancel them.
Changing choices, deletion and children
Open Settings > Privacy choices to change Personalized ads and Usage + diagnostics, use Do Not Sell or Share My Data where displayed, and reopen advertising privacy options when available. Turning on Do Not Sell or Share disables personalization, attribution and usage reporting; a later explicit change to Usage + diagnostics can enable usage reporting again. ATT can be changed in iOS Settings. Follow any restart instruction after changing ad choices. Requests already in progress may finish; withdrawal does not erase provider-held records. Removing the app removes local app data, subject to device backups and purchase restoration. For access, correction or deletion requests, email mtime88@gmail.com with the game, platform/version and enough information to identify relevant records. Do not send passwords or card details. We may need verification and may retain records for purchased benefits, security, disputes or applicable obligations. Retention varies by purpose and provider; no fixed period or immediate deletion of every copy is promised. The game does not request a child's name or date of birth. If you believe a child supplied personal information, contact us. Any previously stored under-18 age choice suppresses advertising and optional tracking.
Android notice and Android version history
The following original notice applies to Android only. For iPhone and iPad, use the separate iOS notice above.
Summary
This notice covers the Android app com.dizzywalk.foursquare, also published as Four Square 2 Play. You can play without creating a game account. This notice distinguishes the earlier Android WebView edition (version code 101) from the native Crown Out edition (Google Play version code 249 / 1.0.52 and later native releases). Sections marked version code 285 and later describe the current release, which has no privacy screen of its own on the way to play: ads, install attribution and usage analytics are on by default and can be limited in Settings > Privacy choices, and in the EEA, the United Kingdom and Switzerland Google's consent form asks for your consent. The native-edition sections apply whenever a native Crown Out edition is installed, including an internal-test installation. Android releases after version code 301 can also record play sessions (screen video, screens visited, taps and gameplay events) with UXCam, under the same Usage + diagnostics choice as usage analytics. Gameplay progress and settings are stored on your device.
Android version code 101: this is the earlier WebView edition. Its packaged monetization features are disabled, and it does not include the native AppLovin MAX, Tenjin, Google Play Billing or RevenueCat libraries. It retains progress and settings in local WebView storage. If you explicitly grant its optional analytics choice, it can send gameplay/session events and a random installation identifier to PostHog over HTTPS; the service also receives network information such as IP address. Its analytics initialization is disabled unless that stored choice is granted. The native-edition privacy controls and native services described below are separate from version 101.
The native-edition sections describe version code 249 (1.0.52) and later native releases, including version code 283; they do not establish the behavior of earlier native test builds. The Google AdMob and Liftoff Monetize advertising libraries described under Advertising are included starting with version code 279; earlier native releases do not include them. A separately hosted browser edition may have different behavior and controls; this Android notice does not establish the browser edition's data use. Contact us with the edition's web address or app version if you need help identifying the relevant notice.
Data stored on your device
- Version 101: progress and settings in local WebView storage.
- Native edition: progress, board checkpoints, stars, crowns, coins, lives, daily and season progress, reward claims, cosmetics, settings and tutorial state.
- Native edition: your Personalized ads and Usage + diagnostics choices, whether DO NOT SELL OR SHARE MY DATA is on, and consent preferences (including the choices stored by Google's consent form where it is shown). Before version code 285 the game also stored an age range (unknown, under 13, 13-17 or 18+) and whether ads were allowed; version code 285 and later no longer asks for either, and keeps an age range an earlier version stored. We do not ask for or store a date of birth.
- Native edition: purchase receipts or transaction identifiers and entitlement/grant records used to deliver purchases; a random installation identifier and locally queued analytics events.
- Native edition, version code 283 and later: whether DO NOT SELL OR SHARE MY DATA is on, and (version code 283 only) whether the attribution notice was on screen when an adult chose ads.
Data we collect
Privacy choices — native edition
Version code 285 and later: the game does not ask you any privacy question before you play, does not ask your age, and has no option to switch ads off for free; the No Ads purchase removes the ads it covers (see Ads). Open Settings > Privacy choices from the main menu, or Pause > Settings > Privacy choices during a puzzle, to change: Personalized ads (ON by default; OFF by default in Canada), Usage + diagnostics (ON by default; OFF by default in Canada), DO NOT SELL OR SHARE MY DATA (outside the EEA, the United Kingdom, Switzerland and Canada), and Ad privacy choices, which opens Google's consent form where it applies. Tap SAVE to keep a change to Personalized ads or Usage + diagnostics. Choosing to buy or restore a purchase still involves Google Play. Earlier native versions (before version code 285) showed a privacy screen that asked for an age range and offered PLAY LOCALLY — ADS OFF; if you chose PLAY LOCALLY there, version code 285 and later shows ads to you and keeps your privacy choice as DO NOT SELL OR SHARE MY DATA, which you can turn off in Privacy choices. If you switched Usage + diagnostics OFF in version code 283, it stays OFF; other OFF settings saved by an earlier version's privacy screen, which started OFF there, now follow the defaults above. If an earlier version stored an under-13 or 13-17 age range for your installation, the game keeps advertising, install attribution and optional tracking off for it.
Your region and which choices apply — native edition, version code 283 and later
The game decides which rule applies on your device, without asking for location permission. It uses the answer of Google's consent service (User Messaging Platform) and AppLovin about whether a consent region applies, then the country of your SIM card or mobile network, then your device's language region. If Google's consent service or AppLovin says a consent region applies, or your SIM or network country is in the EEA, the United Kingdom, Switzerland or Canada, the opt-in rule applies to install attribution and usage analytics. If no country can be determined, the opt-in rule applies. The notice rule applies only when a country outside those regions is determined and neither Google's consent service nor AppLovin says a consent region applies; while Google's consent service is still being asked, the opt-in rule applies. If Google's consent service gives no answer (for example, it cannot be reached), your SIM, mobile network or language country decides as described above. Because a country code cannot identify a Canadian province, all of Canada is treated like Quebec. In version code 285 and later the game asks Google's consent service when it starts, for every installation; in the EEA, the United Kingdom and Switzerland, Google's consent form is shown when you first leave a finished puzzle for the next one (never before you play), and your answer there decides personalized ads, install attribution and usage analytics. In Canada, personalized ads, install attribution and usage analytics start OFF; Personalized ads and Usage + diagnostics in Privacy choices turn them on.
DO NOT SELL OR SHARE MY DATA — native edition, version code 283 and later
Open Settings > Privacy choices and turn on DO NOT SELL OR SHARE MY DATA. It takes effect immediately and stays on until you turn it off: Tenjin install attribution is opted out and stops receiving install, app-interaction, purchase and advertising-revenue information; Usage + diagnostics and Personalized ads are switched OFF (which also stops UXCam session recording in releases that include it); and AppLovin MAX is told not to sell or share your information (its do-not-sell setting), which it passes to the advertising partners that support it. Where Meta Audience Network is included in a version, Meta is told to apply Limited Data Use. Ads continue to be shown, as non-personalized ads. This is how you exercise the right to opt out of the sale or sharing of personal information and of targeted advertising under the California Consumer Privacy Act (as amended by the CPRA) and other US state privacy laws, and it is the opt-out for the notice rule described above wherever you live. The game has no web browser, so it does not receive a Global Privacy Control signal. Separately, if you delete your advertising ID in Android settings, Android stops providing it to the game and its SDKs. An installation for which an earlier version stored an under-13 or 13-17 age range is never included in install attribution, in any region.
Changing a choice — native edition
You can return to Privacy choices at any time. Ad privacy choices opens Google's consent form where it applies (the EEA, the United Kingdom and Switzerland); elsewhere your ad choices are the controls on the Privacy choices screen. Some changes after an advertising service has started require closing and reopening the game; follow the in-app instruction and use Save and close game when offered. The game discards its queued analytics events when a refusal or withdrawal is known, so a later grant covers new activity rather than that discarded history. Requests already in progress may finish, and changing a choice does not erase information previously received by a provider.
Advertising — native edition
AppLovin MAX and Google User Messaging Platform support ad delivery and consent choices. The game can show banners, interstitials between gameplay activities, and optional rewarded ads. AppLovin and its advertising partners may process device or advertising identifiers, IP address, approximate location inferred from IP, device/OS and app information, and ad impressions, clicks and reward interactions. These support ad delivery, measurement, frequency limits and fraud prevention. Starting with version code 279, AppLovin MAX can also request ads from Google AdMob (Google Mobile Ads SDK) and Liftoff Monetize (Vungle SDK), whose libraries are included in the game; neither sends ad requests or data until AppLovin MAX is initialized. Starting with version code 287, AppLovin MAX can also request ads from Unity Ads, Pangle, InMobi and BIGO Ads, whose libraries are included in the game from that version, and in version codes 287 through 293 from Meta Audience Network, whose library is included only in those versions; AppLovin MAX calls them only after it is initialized. Starting with version code 293 (1.0.96), AppLovin MAX can also request ads from ironSource / iSX (Unity), whose advertising library is included from that version. Its advertising requests follow the same AppLovin MAX consent and do-not-sell sequence described here. In version code 285 and later, AppLovin MAX is initialized when the game starts, for every installation, after Google's consent service has answered; in the EEA, the United Kingdom and Switzerland it is initialized after you answer Google's consent form, whichever answer you give, and if you do not consent, ads are non-personalized or limited. AppLovin MAX and the ad networks it mediates are not initialized for an installation for which an earlier version stored an under-13 or 13-17 age range. Before version code 285, AppLovin MAX was initialized only after an adult chose CONTINUE WITH ADS. When ads are shown, Google, Liftoff, (version codes 287 through 293) Meta, (version code 287 and later) Unity, Pangle, InMobi and BIGO, and (version code 293 and later) ironSource / iSX, may each receive device and advertising identifiers (such as the advertising ID and app set ID; for Google, also identifiers related to accounts signed in on the device), IP address and approximate location inferred from it, app and ad interactions such as app launches, taps, ad views and clicks, and diagnostic and performance information, for advertising, measurement, analytics and fraud prevention. Personalization requires the Personalized ads choice and the applicable consent decision; non-personalized or limited ads can still involve data processing. When Personalized ads is OFF, or DO NOT SELL OR SHARE MY DATA is on, the game sets AppLovin MAX's do-not-sell setting. AppLovin may also process SDK crash/error logs and technical diagnostics to operate and improve its advertising service; this processing is separate from the Sentry reporting controlled by Usage + diagnostics.
Purchases — native edition
Google Play Billing processes purchases through Unity In-App Purchasing. Google handles payment credentials. The game receives product, receipt or purchase-token, transaction, price, currency and entitlement information to validate and deliver purchases. Purchase/revenue events may be reported to PostHog, Tenjin or (version code 285 and later) Google Analytics for Firebase only when their respective choices and consent conditions allow it. Eligible entitlements may be restored through Google Play; consumable balances and local progress are not guaranteed to return after local data is removed.
Product analytics — PostHog
In the native edition, Usage + diagnostics must be ON and the current consent decision must permit reporting before the game forwards product analytics. In version code 285 and later, Usage + diagnostics is ON by default; outside the opt-in regions described under Your region and which choices apply, analytics is on unless you switch Usage + diagnostics OFF or turn on DO NOT SELL OR SHARE MY DATA; in the EEA, the United Kingdom and Switzerland it also requires your consent in Google's consent form; in Canada it is OFF until you switch Usage + diagnostics ON. Events may include sessions, level starts/results, store or offer views, reward claims and purchase/ad activity, with technical app information and a random installation identifier. That identifier is pseudonymous: it links activity from an installation over time. It is separate from the advertising identifier. Network requests also disclose IP address to the recipient. We use this information to understand use and improve the game.
Install attribution — Tenjin
Outside the opt-in regions (the EEA, the United Kingdom, Switzerland, Canada and wherever the region cannot be determined), in version code 285 and later Tenjin is on by default for every installation, independent of the Personalized ads and Usage + diagnostics choices, until DO NOT SELL OR SHARE MY DATA is turned on (in version code 283 it was on for an adult who chose CONTINUE WITH ADS or ACCEPT ALL after the attribution notice). Inside the opt-in regions, and in every version before 283, Tenjin forwarding requires permitted usage reporting and permitted ad personalization: in the EEA, the United Kingdom and Switzerland that means your consent in Google's consent form; in Canada, turning on both Personalized ads and Usage + diagnostics. It is never on for an installation for which an earlier version stored an under-13 or 13-17 age range. When enabled, install, app-interaction, purchase and advertising-revenue information helps measure campaign performance. Data may include available advertising/device identifiers, IP address, device/OS, locale, app version and attribution information. Configured advertising channels may receive attribution/conversion information. Before version code 283, the game's Tenjin Google DMA data-sharing settings are OFF. In version code 283 and later, inside the opt-in regions the game passes your actual ad personalization and ad user data consent to Tenjin's Google DMA settings; outside them Tenjin's Google DMA data sharing stays OFF.
Measurement for advertising — Google Analytics for Firebase, version code 285 and later
When Usage + diagnostics is ON and the current consent decision permits reporting (the same conditions as Product analytics), the game sends Google Analytics for Firebase an app-instance identifier, app interactions (sessions, level starts and results, tutorial completion), the product, purchase value, currency and transaction ID of each purchase, and the advertising revenue of each ad impression (ad network, ad format, ad unit and value). Google Analytics for Firebase may also collect the advertising ID, device and app information, and approximate location inferred from IP address. Google processes this for our analytics and, where your choices permit advertising measurement, to measure and optimize our Google Ads campaigns. In the EEA, the United Kingdom and Switzerland, advertising use follows your answer in Google's consent form; in Canada it stays off until you turn on Personalized ads; everywhere, DO NOT SELL OR SHARE MY DATA stops advertising use, and Usage + diagnostics OFF stops Google Analytics for Firebase entirely. Installations where an earlier version stored an age range under 18 are not measured.
Crash diagnostics — Sentry
In the native edition, when Usage + diagnostics is ON (ON by default in version code 285 and later; see Product analytics for the conditions), the current consent decision permits reporting and a reporting service is available, Sentry may receive crash/error information, stack traces, diagnostic context and technical app/device information. Network requests reveal IP address to the recipient. These reports help investigate reliability problems. Disabling reporting is not a promise that every request already in progress or every provider-held report disappears immediately.
Session recordings — UXCam, Android releases after version code 301
Releases after version code 301 can record play sessions with UXCam, so we can see where the game is confusing, too hard or broken. UXCam runs only under the same conditions as Product analytics: Usage + diagnostics must be ON and the current consent decision must permit reporting. In the EEA, the United Kingdom and Switzerland nothing is recorded until you consent in Google's consent form; in Canada nothing is recorded until you switch Usage + diagnostics ON; nothing is recorded for an installation for which an earlier version stored an under-13 or 13-17 age range. When it runs, UXCam receives: a video recording of the game's screen during the session, which can include ads shown in the game (Google Play's purchase sheet and Android's share sheet are other apps and are not recorded); the names of the game screens you visit; your taps and gestures; the gameplay events also sent to PostHog, such as level starts and results, boosters, store and offer views, and purchase attempts and results with the product and its price tier (never a payment-card number, purchase token, receipt or transaction ID); the random installation identifier that PostHog also uses, as the UXCam user; properties of the installation, such as its graphics tier, whether it has made a purchase, the highest level reached, the advertising campaign and campaign type that led to the install where known, and the game's experiment groups; app, device and session information (app version, device model, operating-system version, screen size and a device identifier that the UXCam library reads from Android, the Android ID); and the IP address of the connection, from which UXCam derives an approximate location (city-level, with coordinates). When a recording starts, the game also sends PostHog a link to that UXCam session and user so a PostHog record can be matched to its recording. UXCam Inc. processes this information on our behalf as a service provider and processes it in the United States. Recordings are kept only as long as we need them to improve and fix the game, within UXCam's retention period for our account. Turning Usage + diagnostics OFF, or turning on DO NOT SELL OR SHARE MY DATA, stops the recording at once, deletes the session in progress and any recordings not yet uploaded, and no new recording starts while it stays off; recordings already uploaded remain with UXCam until deleted (see Your data and deletion). The iOS edition does not include UXCam.
Advertising
Version 101's packaged monetization features are disabled. In the native edition, version code 285 and later shows banner, interstitial and optional rewarded ads to every installation (see Advertising for consent in the EEA, the United Kingdom and Switzerland); there is no free option to switch ads off. A No Ads entitlement removes the banner/interstitial advertising covered by that purchase; optional rewarded offers may remain. No Ads does not itself delete analytics, attribution or purchase records. Before version code 285, PLAY LOCALLY — ADS OFF left ad requests off and an adult's CONTINUE WITH ADS choice allowed ads.
Third parties
The providers below process information for the native features described above, subject to the stated choices. Advertising partners may also process information for their own advertising, measurement and fraud-prevention purposes under their privacy policies. This policy website has its own hosting traffic, separate from the game.
| Provider | What they do |
|---|---|
| AppLovin MAX and advertising partners | Advertising and consent-related processing. The ad networks AppLovin MAX can call in this game: Google AdMob and Liftoff Monetize / Vungle (version code 279 and later); Meta Audience Network (version codes 287 through 293); Unity Ads, Pangle, InMobi and BIGO Ads (version code 287 and later); ironSource / iSX (Unity) (version code 293 and later). https://legal.applovin.com/privacy/ and https://legal.applovin.com/applovin-partners/ |
| Google / Google Play | Google UMP consent services and purchase processing. https://policies.google.com/privacy |
| Google AdMob (version code 279 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://policies.google.com/privacy and https://policies.google.com/technologies/partner-sites |
| Liftoff Monetize / Vungle (version code 279 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://liftoff.ai/privacy-policy/ |
| Meta Audience Network (version codes 287 through 293) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising); with DO NOT SELL OR SHARE MY DATA on, Meta is told to apply Limited Data Use. https://www.facebook.com/privacy/policy/ |
| Unity Ads (version code 287 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://unity.com/legal/game-player-and-app-user-privacy-policy |
| Pangle (version code 287 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://www.pangleglobal.com/privacy |
| InMobi (version code 287 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://advertising.inmobi.com/privacy-policy |
| BIGO Ads (version code 287 and later) | Advertising partner that AppLovin MAX can call once it is initialized (see Advertising). https://www.bigoads.com/privacy |
| ironSource / iSX (Unity) (version code 293 and later) | Advertising partner whose ad requests follow the AppLovin MAX consent and do-not-sell sequence described under Advertising. https://unity.com/legal/game-player-and-app-user-privacy-policy |
| PostHog | Product analytics with a pseudonymous installation identifier, controlled by Usage + diagnostics (ON by default in version code 285 and later). https://posthog.com/privacy |
| Tenjin | Install attribution and campaign/revenue measurement: opt-in inside the opt-in regions; on by default with the DO NOT SELL OR SHARE MY DATA opt-out elsewhere (version code 283 and later; for adults who chose ads in 283). https://tenjin.com/privacy/ |
| Google Analytics for Firebase (version code 285 and later) | Analytics and Google Ads campaign measurement, controlled by Usage + diagnostics and the advertising choices described above. https://policies.google.com/technologies/partner-sites |
| Sentry | Crash and error diagnostics when Usage + diagnostics is ON and a reporting service is available. https://sentry.io/privacy/ |
| UXCam (Android releases after version code 301) | Session recordings (screen video, screens visited, taps and gestures, gameplay events, installation and device identifiers, IP-derived approximate location), processed on our behalf in the United States, only when Usage + diagnostics is ON and the consent conditions above permit reporting. https://uxcam.com/privacy-policy/ |
| Render | Hosts this policy website and may process IP addresses and web-request logs. https://render.com/privacy |
Children
Crown Out is intended for adults: its target audience on Google Play is 18 and over, and it is not directed to children. Version code 285 and later does not ask for an age. Earlier native versions asked for an age range without a date of birth; where one of them stored an under-13 or 13-17 range for an installation, the game keeps advertising, install attribution and optional tracking off for it while local gameplay remains available. If you believe a child has supplied personal information through the game, contact us so we can investigate.
Your choices & data deletion
Use Settings > Privacy choices to change native-version choices, including DO NOT SELL OR SHARE MY DATA (version code 283 and later). To remove local data, clear the app's storage in Android settings or uninstall it. Device/cloud backups and Google Play restoration may retain or restore some information; uninstalling does not delete records already held by us or providers. You can also manage the advertising identifier and advertising preferences in device settings. For access, correction or deletion requests, email the contact below with the game name, edition/app version and enough information to locate the relevant records. We may need to verify the request and will explain if a record cannot be identified or must be retained for transaction, security, dispute-resolution or legal reasons. Do not send passwords or payment-card details. Provider privacy-request channels are also available. Retention depends on the data, operational needs, provider settings and applicable obligations; no fixed period or immediate deletion of all copies is promised here.
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.