Skip to privacy policy
Dubón IA
← Back to the game

Privacy policy — Match3 Collection Premium

Effective date: 9 November 2026.

Developer and scope

The developer responsible for the game is ERIC MAURICIO DUBON GUZMAN, an individual developer using the Dubón IA brand, based in Honduras. Privacy and support contact: ericdubon24@gmail.com.

This policy covers Match3 Collection Premium, Android package com.dubonia.match3collection, closed-test version 0.10.1. The game is intended for teenagers aged 13 and above and adults. It does not request a date of birth or create a player account. The intended age range does not mean that everyone over 13 is an adult or replace regional rules for minors.

Progress and settings on your device

The game stores levels, stars, virtual gems, boosters, hero teams, powers, outfits, rewards and settings such as language, audio, accessibility and seasonal presentation locally. These support saved progress and game rules. Manually choosing a hemisphere, neutral presentation or cultural themes does not require GPS.

We do not operate player accounts, a game-save server or our own cloud synchronization. Android, your device manufacturer or device services may include app data in system backup and restore according to your settings. These are not game-save accounts or cloud services operated by us, and do not guarantee that we can recover your progress.

Local data remains while the installation and its files are retained. Android settings let you manage or clear app data; clearing it may erase your progress. Uninstalling or changing devices may also affect progress, subject to system backup behavior.

Optional local diagnostics

Our own diagnostics are off by default. If you enable them, the game records a limited set of usage events on your device, such as levels, moves, duration, powers, rewards and ad status. It does not automatically upload those files to our server or include a persistent player identifier, email address, GPS data or free text.

You may choose a country manually for diagnostics. It is not inferred from GPS and does not determine your nationality, age or Play availability. Diagnostic controls let you disable recording, export files or delete them. Exporting creates a file that you choose to keep or share; it is not an automatic upload. Files you export or send are not erased by clearing the internal log.

The internal log applies retention of up to 30 days and file size/count limits when the diagnostic module processes its records. We do not promise deletion by a background service while the app is not running. You can delete the logs without waiting for that cleanup.

Demonstration ads and Google

This closed test uses Google Mobile Ads Next-Gen 1.4.0 and Google User Messaging Platform (UMP) 4.0.0, with official demonstration identifiers. It does not activate commercial ads or generate real revenue. Advertising assistance is optional: a rewarded offer is not shown during the first 20 distinct completed levels and, when available afterward, offers one hammer. You can keep playing without watching ads.

The app does not automatically start an advertising request when opened. When you choose to prepare ads in Privacy, consent information is updated through UMP and applicable forms are resolved. The adapter only enables ads after a successful update and a NOT_REQUIRED or OBTAINED UMP status. An error or unresolved status keeps availability closed.

When UMP indicates that it is required, the game provides access to privacy options to review your choices. The test configuration sets under-age-of-consent treatment (TFUA=true), maximum ad content rating G and not child-directed treatment (TFCD=false). These are conservative test settings, not an age check or a promise of automatic compliance in every region.

Even with demo ads, Google and its SDKs may process your IP address, from which approximate location may be inferred, app or advertising interactions, technical and diagnostic information, and device or app identifiers including App Set ID, to provide, measure and secure the service and prevent fraud. We do not use GPS for this feature. The audited Android configuration of this test does not declare the advertising identifier permission AD_ID; this does not mean there are no other identifiers or data.

Rejecting an option, not watching an ad or using demo identifiers does not justify promising that Google receives no data: consent requests and other technical functions may involve communications. The game's local diagnostic setting and advertising privacy choices are separate controls.

See Google's Privacy Policy, its explanation of data retention, and the advertising SDK's data disclosure. Google's own retention periods and controls apply to data it processes; they are not the game's 30-day local log limit.

Purchases and virtual resources

This version does not include billing or real-money purchases. The premium pass is a preview and cannot be purchased. Gems, boosters and rewards are virtual resources with no cash value, cash withdrawal or earnings from playing. You do not need to provide bank details or identity documents to play.

Support and privacy requests

If you email support, we receive your address and the message or files you choose to send. We use them to respond, investigate the issue and handle your request. Do not send passwords, identity documents, bank information or unnecessary personal information. You may redact personal information in screenshots or logs.

Our support retention criterion is to keep what is needed while a case remains open and for any additional period justified by security, legal duties or handling claims. We cannot promise a universal deadline or a fixed-day automatic deletion process. You may request information, correction or deletion of material you sent; we will review the request and applicable obligations. We cannot use our inbox to erase a copy held by Google or a local file we never received.

Changes and contact

Relevant changes will be published on the game's policy page with the corresponding date. If actual data handling changes, the description and store declarations must be updated before that variant is distributed. Please use the contact listed above for questions.