This policy explains how DDBlue Studio handles information in MergeCompass, which services are currently used, and how to contact us about privacy.
1. Scope and responsibility
DDBlue Studio is responsible for the MergeCompass processing described in this policy. This policy covers the game, including its current test builds, and communications you send us about it. The studio website has a separate website Privacy Policy. Services you choose outside the game, such as a recipient app in the Share Sheet, have their own privacy practices.
2. Current implementation and release status
MergeCompass currently uses Firebase Analytics, Firebase Crashlytics, device-local saves, and Apple’s native Share Sheet. Cloud Save has been implemented, but live CloudKit production acceptance is pending. AdMob and StoreKit production validation has not started, and Game Center production configuration is not final. There is no App Store listing yet. These pending features are described conditionally below; they are not represented as validated live services. This policy and the App Store privacy disclosures will be reviewed against the actual shipping build before submission and before new processing is enabled.
3. Categories of information processed
Depending on the feature you use, processing includes the following categories:
- Usage and gameplay information: app launches, sessions, interactions and gameplay events reported through analytics.
- Technical information and identifiers: app version/build, device model, operating-system version, language/locale, and app-instance or installation identifiers used by the SDKs. Approximate country or region may be derived by the analytics service from network information; this is not precise GPS location.
- Diagnostics: crash traces, error details, device/app context and diagnostic identifiers.
- Saved game information: progress, scores, game inventory and settings stored locally, and potentially synchronized through Cloud Save if that feature becomes available.
- Communications: your email address and the contents or attachments you voluntarily send for support or privacy requests.
MergeCompass does not provide a studio player-account system or social login. Ordinary gameplay does not ask for your real name, phone number, contacts, precise location, social profile, payment-card details or Apple ID password. SDK installation identifiers should not be understood as anonymous simply because they do not contain your name.
4. Purposes of processing
We use information to run the game and preserve progress; understand use and improve features and game balance; detect and resolve crashes; respond to questions and privacy requests; and maintain reliability and security. If purchases or other pending features become available, their information will be used to provide the requested functionality as described in the updated policy. We do not intentionally include names, email addresses, passwords or unnecessary sensitive information in analytics events or diagnostic reports.
5. Analytics
Firebase Analytics, a Google service, helps us understand sessions, feature use, engagement and gameplay patterns. It may process usage events, app-instance identifiers and device/app information described above. Network information can be processed by the provider to deliver the service and derive approximate geography. We use analytics to improve MergeCompass; the presence of analytics does not mean personalized advertising or cross-app advertising tracking has been implemented. Collection and retention depend on the app’s SDK configuration and the Analytics property settings. We do not promise an in-app analytics switch that has not been verified in the current build.
6. Crash diagnostics
Firebase Crashlytics, a Google service, processes crash and non-fatal error reports so we can identify technical failures and assess their impact. Reports may include stack traces, app version, device model, operating-system information and Crashlytics installation identifiers. We do not intentionally attach player names or email addresses. Google describes the service’s processing and retention in its Firebase privacy documentation.
7. Local saves
MergeCompass stores progress and settings on your device between sessions. Local data may include scores, coins, power-up and Special Tile inventory, progression/tutorial flags, rewards state, settings and the active game state. Local storage is distinct from sending gameplay events to analytics. Deleting the app generally removes its app-local data, but device backups and platform restore behavior may preserve or restore copies. Deleting local data does not automatically delete reports already sent to Firebase.
8. Cloud Save
Cloud Save implementation exists, but live Apple iCloud/CloudKit production acceptance is pending. If enabled and available in a future released build, it is intended to synchronize long-term progress through Apple’s services. This may include Best Score, Highest Tile, Coins, power-up and Special Tile inventory, tutorial/progression flags, Daily Reward or Lucky Box state, and selected settings. Active in-progress runs may remain local.
Cloud Save is intended to be optional and depends on the available feature and your Apple/iCloud settings. MergeCompass does not receive your Apple ID password or create a separate studio account for this purpose. Apple manages its own service processing under its privacy terms. Removing the app should not be assumed to remove cloud records. Contact us for guidance about available deletion options if Cloud Save is enabled; no unverified cloud-deletion control is promised here.
9. Purchases
StoreKit production validation has not started. If in-app purchases are made available, Apple will process payment through the App Store. MergeCompass may process product, transaction and entitlement information to deliver items, verify purchases or restore eligible entitlements. DDBlue Studio does not receive your credit-card number or Apple payment credentials through StoreKit. The final purchase data flow and any additional validation service will be reflected in this policy before release; this section does not claim purchases are currently production-ready.
10. Advertising
AdMob production validation has not started. Advertising providers, ad formats, data flows and consent requirements are not finalized for a public release. This policy does not represent personalized ads, advertising identifiers (including IDFA), or an App Tracking Transparency permission flow as implemented. Before advertising is enabled in a released build, we will update this policy to identify the provider, information processed, purposes and applicable choices or permissions. No advertising-specific consent or opt-out control is promised in the current implementation.
11. Game Center
Game Center production setup is not final. If enabled in a released build, Apple may process Game Center player identifiers, display information, scores or achievement information required by the enabled features. The final scope, including any public leaderboard visibility, will be described before those features are released. This section does not claim a validated Game Center integration or a studio player-account system.
12. Sharing results
Sharing uses Apple’s native Share Sheet and starts when you choose to share. The content you select is passed to the destination you choose in iOS. The recipient app or service handles that content under its own terms, and shared content may become public depending on your choice. Ordinary sharing does not require MergeCompass to obtain a social-media login or access your social profile. Check the content and destination before sending.
13. Support communications
If you email us, we receive your email address, message and any attachments or device/app details you choose to include. We use these to investigate your issue, reply and maintain a record of the request. Please send only information needed for the issue and avoid passwords, authentication codes and full payment details. Player support is available at [email protected]; privacy requests should go to [email protected].
14. Service providers and disclosures
Current app providers include Google for Firebase Analytics and Crashlytics, and Apple for device functionality and the native Share Sheet. Email providers process support communications. Apple CloudKit, StoreKit and Game Center, and advertising services, are subject to the pending-feature descriptions above. Providers process information needed for their services under applicable terms; their roles and practices can differ by service. See Firebase privacy information, Google’s Privacy Policy and Apple’s Privacy Policy.
Information may also be disclosed where required by applicable law or reasonably necessary to respond to a lawful request, protect rights or security, or address abuse. The current described implementation has no data-sale arrangement or sharing for cross-context behavioral advertising. Sending technical information to analytics or diagnostics providers remains a disclosure of data; it is not a claim that the game collects no information.
15. Retention and deletion
Local saves remain subject to app deletion, device storage and backup behavior. If Cloud Save becomes available, cloud records will depend on the enabled functionality and Apple’s storage/deletion processes. Analytics event-level retention follows the configured Analytics settings and provider rules; aggregated reports can have different retention. We do not state an unverified fixed Analytics retention period. Google currently documents a 90-day Crashlytics retention period before its removal process starts.
Support messages are retained while needed to handle the request and reasonable follow-up, or for applicable legal or security needs. We review deletion requests in light of data we can identify and control. Backup cycles, provider procedures and legal requirements may affect deletion timing. Removing the app does not itself remove provider-held analytics, crash reports or correspondence.
16. Security
We use the platform and provider security features available for the described services and seek to limit unnecessary information in events, reports and support exchanges. No transmission or storage system can be guaranteed completely secure. Please contact the privacy address below if you believe information has been exposed or handled incorrectly.
17. International processing
Google, Apple and communication providers may process information in countries other than where you live. The applicable locations and protections depend on the service and its terms. Where data-protection law requires safeguards for an international transfer, the relevant provider arrangements and legally available mechanisms must apply. We do not claim that all information stays in your country or that DDBlue Studio holds a transfer certification. Contact us for information about the arrangements relevant to your request.
18. Your choices and requests
You can choose whether to send support information or share results, remove the app and its local data, and use available device or platform privacy settings. Cloud Save, purchase, advertising and Game Center choices depend on whether those features become available. Device settings do not necessarily stop all Analytics or Crashlytics processing.
Depending on applicable law, you may request access, correction, deletion, a copy of your information, or restrictions on or objections to processing. Email [email protected] with enough context to understand your request. We may need proportionate verification, but please do not send identity documents or sensitive credentials unless a secure and necessary process has been agreed. Because there is no studio player-account system, we may not be able to locate a particular SDK record from your email address alone. We will explain applicable limits and respond as required by law. This policy does not promise deletion of data outside our control.
19. Children
MergeCompass is not designed to collect children’s personal information through a registration or messaging system, and we do not knowingly solicit personal information from children under 13, or below a higher age threshold where applicable law requires it. Analytics and diagnostics can still process device and usage information; absence of registration does not mean absence of processing. If you believe a child has provided information that should not have been collected, contact us so we can investigate and take appropriate steps. This policy does not establish a verified age gate, a final App Store age rating, or participation in Apple’s Kids Category.
20. California and other U.S. state privacy rights
If a U.S. state privacy law applies to DDBlue Studio and your information, you may have rights to know or access categories and specific information, correct inaccuracies, request deletion or portability, and opt out of certain sales, targeted advertising or legally defined sharing. Certain laws also provide an appeal process, authorized-agent requests or limits on specified sensitive-information uses. Applicability depends on the law’s coverage and exceptions; this policy does not assert that every state law applies.
The categories, purposes, sources and recipients in the sections above describe the current processing. No data-sale or cross-context behavioral advertising arrangement is part of the described implementation. We therefore do not present a sale or targeted-advertising opt-out as an implemented feature. Send applicable rights requests, agent requests or appeals to the privacy address. We will handle them under the applicable law and will not unlawfully discriminate for exercising privacy rights.
21. EEA and UK privacy rights
Where EEA or UK data-protection law applies, DDBlue Studio is responsible for the processing it determines, while providers may have separate responsibilities for their services. Depending on the circumstances, the relevant basis for processing may be providing a service you request, legitimate interests in operating and improving the game or responding to support, compliance with legal obligations, or consent where required. This policy does not itself obtain consent or establish that an unverified consent mechanism exists.
Subject to applicable conditions, you may have rights of access, rectification, erasure, restriction, portability and objection, including objection to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. Contact us to exercise these rights or ask about the basis for a particular use. You may also complain to your local data-protection authority, including the UK Information Commissioner where relevant. These rights can have exceptions and do not guarantee access to records we cannot identify.
22. Changes to this policy
We will post updates on this page and revise the date above when practices change. Material changes will receive additional notice or consent where required by applicable law. Pending services will be reviewed before activation in a released build so this policy reflects actual processing.
23. Contact
For privacy questions and data requests: [email protected].
For gameplay and technical support: [email protected]. Please identify MergeCompass and the app version, if available, so we can route your request.