1. Developer and contact
Developer: Aleksandar Harlov
Country: Bulgaria
Privacy and support contact: stoned.gymrat@gmail.com
You can contact us with questions, support requests, or privacy requests. Aleksandar Harlov personally handles privacy requests sent to this address. Gem Rondo does not require a player account. We do not send newsletters or promotional emails to people who contact us.
This policy covers the current signed Android testing versions of Gem Rondo and the browser game. Gameplay analytics is disabled in these versions. Information about data from earlier, separate private Analytics testing is included below so those participants can understand retention and exercise their rights.
2. Game information stored on your device
Gem Rondo stores information on your device to operate the game, resume separate Endless and Daily Rondo runs, remember preferences, and show statistics. This can include boards, upcoming gems, seeds and rules, scores, levels, energy, local run identifiers and timestamps, match and cascade counters, special-gem and revive information, Daily results and streaks, completed-run history, lifetime records, tutorial progress, and audio and privacy preferences.
The Android app uses app-private native checkpoint storage and WebView storage. Detailed saves, local statistics, and diagnostic gameplay records are not automatically uploaded to a developer-operated server. The versions covered by this policy do not submit gameplay events to Google Analytics for Firebase. The app does not include Firebase Crashlytics or another developer-added remote crash-reporting SDK. Google Play may separately provide Android vitals information through platform services, depending on device and user settings.
You can export statistics to a file. Exporting does not send the file to us. If you share an export, its recipient receives its contents; local identifiers and timestamps mean an export is not necessarily anonymous.
Android backup: Android Auto Backup is enabled for eligible game data. Device, operating-system, and provider settings can allow backups or device transfers and restoration after reinstalling. We do not operate a separate cloud-save server. Analytics permission is excluded from this backup so a restored game is not treated as permission to enable analytics on a new installation.
3. Gameplay analytics in this release
Gameplay analytics is disabled and unavailable in the signed Android testing versions covered by this policy. It cannot be enabled through Privacy choices. The browser game does not include Firebase Analytics. Local statistics still work, and Google’s advertising and privacy-choice services still process information as described below.
Earlier private development testing offered optional Firebase Analytics to adults who confirmed they were at least 18, able to give their own consent, and agreed to analytics. That separate experiment is not an enabled feature in this release. Its data could include tutorial and run events, mode, levels, scores, active play time, matches, cascades, special-gem and revive use, Daily results, and automatic session and engagement events. It did not upload full boards, seeds, move histories, exports, names or email addresses.
Previously transmitted Analytics data can also include a pseudonymous app-instance identifier, app and device information, language, approximate location derived from an IP address, and available installation/referral information. Google states that Analytics does not log or store individual IP addresses. Supporting Firebase services can have separate installation identifiers and operational records. These are not the same as the Analytics app-instance identifier. Sections 9 and 11 explain retention and deletion of this earlier data; this release does not turn analytics back on.
For Google’s descriptions of these services, see Google Analytics for Firebase data disclosure, Firebase Android SDK data disclosure, and Google Privacy Policy.
4. Optional rewarded advertisements
On Android, Gem Rondo includes an optional advertising-supported revive. You can play, finish a run, and start another without watching an advertisement. Some testing versions use Google’s demonstration ads; these still use Google’s advertising and privacy-choice services. Versions configured for regular ads use the developer’s AdMob account.
The app uses Google AdMob through the Google Mobile Ads SDK. Google’s published disclosures describe processing that may include IP addresses and approximate location, app and ad interactions, technical diagnostics, and applicable device or advertising identifiers. Google and eligible advertising partners may use information for advertising operations, measurement, security, and fraud prevention under applicable settings, choices, and privacy notices.
The app checks Google’s privacy information on launch, before you decide whether to watch an ad. This service uses connection information and app, device, language, screen and existing consent information to return and display choices. It can also send operational timings, errors and technical app/device information to Google. The app’s explicit ad initialization and loading begin when you request a rewarded video. Not all consent-service processing waits for a new consent choice or an ad request.
All native ad requests use Google’s TEEN age-restricted treatment, maximum ad-content rating G, and publisher-side advertising personalization disabled, including for adults. These restrictions do not mean the advertising SDK processes no information or uses no identifiers. Non-personalized advertising can still involve device storage, measurement and fraud-prevention processing. Disabling gameplay analytics does not disable this separate consent and advertising processing.
The developer has selected Google’s automatically managed list of commonly used advertising partners in AdMob. Google manages that list, which can change. Eligible partners and applicable choices are presented through Google’s consent interface. See Google’s partner sites and apps information and Google Mobile Ads SDK (Legacy) data disclosure.
5. Privacy choices and withdrawal
On Android, open Settings → Privacy → Privacy choices to review the available Google advertising choices. The app refreshes Google’s consent information on launch. Ordinary gameplay remains available after refusal or if the privacy service is unavailable. Gameplay analytics is shown as unavailable in this release; there is no enabled analytics eligibility or fallback opt-in flow. The browser game does not use native Google ads or offer the Google privacy-choice control.
For versions using the developer’s AdMob account, the published Google privacy message targets the European Economic Area, the United Kingdom and Switzerland. It includes a Do not consent choice. English is the default language, with Bulgarian, Spanish, Simplified Chinese, German and Portuguese also configured. Google’s message can include both advertising and analytics purposes, but an analytics selection there does not enable this release’s disabled gameplay analytics. Message availability and options also depend on Google’s service, your region and whether the version uses demonstration ads.
You can revisit available choices through the same Settings entry. Changes affect subsequent processing under those choices; they cannot recall information already transmitted or guarantee that every SDK request already in progress is cancelled. Declining personalized advertising does not mean all advertising-related processing stops. Consent status, advertising configuration and regional rules can affect which ads are available. Android also provides privacy and advertising controls whose availability and effect depend on your device.
To request deletion of information from earlier private Analytics testing, see section 11. A local reset, a new installation or a remembered Google grant does not enable gameplay analytics in this release.
7. International processing and transfers
Google and Cloudflare operate internationally, including in the United States. Information can therefore be processed outside Bulgaria and the European Economic Area. We do not promise EU-only processing. A transfer safeguard addresses international processing; it does not replace the need for a lawful purpose and legal basis for using the data.
For covered advertising and Analytics transfers from the EEA to the United States, Google states that it uses the EU–US Data Privacy Framework. Its published terms also provide Standard Contractual Clauses for certain transfers where an applicable framework is not used. Google’s general transfer notice separately describes safeguards for consumer services such as Gmail. The Data Privacy Framework applies to covered transfers to participating organizations, not to every transfer to the United States.
Cloudflare’s Data Processing Addendum, incorporated into our Self-Serve arrangement, provides for covered Data Privacy Framework transfers and Standard Contractual Clauses for restricted transfers. Those clauses are European Commission-approved contractual protections. These safeguards apply within the respective services’ terms; they do not mean every service uses the same agreement or every international transfer uses the same mechanism.
You can use the links above to read the published safeguards or contact stoned.gymrat@gmail.com for the safeguards applicable to our services and a copy of the relevant clauses, subject to necessary redactions protecting others. A service you choose for backups or exports has its own arrangements.
8. Purposes and legal bases
Where EU data-protection law applies, the bases below apply to personal-data processing for the purposes we determine. They do not replace the separate responsibilities or notices of Google, advertising partners or other providers acting for their own purposes.
Game functions and local records: We rely on Article 6(1)(f) GDPR, our legitimate interests in reliable gameplay, preserving your requested progress and preferences, displaying your records, and protecting game integrity. This includes local saves and the statistics described in section 2. It does not authorize uploading them as optional analytics.
Local troubleshooting: We also rely on Article 6(1)(f) for the limited purpose of investigating game faults and checking reliability using local diagnostic run history and tutorial timing/counters. These records are collected by default, kept in bounded histories and not automatically sent to us. We receive them only if you choose to share an export. Section 9 explains the limits and deletion controls. This is a separate purpose from remembering a tutorial choice or providing the current save, and is not a claim that every diagnostic record is essential to play.
Privacy-message operation: We rely on Article 6(1)(f) for delivering usable privacy choices, applying decisions and diagnosing failures of that mechanism. This uses the message-selection, rendering and operational information described in section 4, including processing before a new choice is made. Our interest is a reliable choice mechanism that honors users’ decisions, not optional gameplay measurement or unrelated profiling. Google’s independent service processing is governed by its own responsibilities and notice.
Advertising: For advertising measurement or other advertising purposes requiring consent, our basis is Article 6(1)(a), consent for the relevant purpose. Separately, we rely on Article 6(1)(f) for the limited technical purposes of delivering a rewarded video you request, handling delivery errors and protecting the integrity of the ad request and reward. This technical interest is not a substitute for refused consent to measurement, profiling or device storage. Requesting a video is not, by itself, privacy consent. Google and eligible partners also process advertising information under their own applicable bases and the choices available through Google’s interface.
Privacy requests and necessary consent records: Article 6(1)(c), compliance with legal obligations, applies to proportionate contact and identification information and request/outcome records needed to handle GDPR rights under Articles 12–22, and necessary records demonstrating and honoring consent or withdrawal under Article 7. This does not classify all consent-service traffic or diagnostics as legally required.
Support and policy delivery: Under Article 6(1)(f), we use your voluntarily supplied contact details and messages to answer inquiries and resolve problems, and connection/request information to make this policy accessible and protect its delivery. These interests do not cover marketing or unrelated profiling. Section 9 gives our email-retention limit; Gmail and Cloudflare also have their own processing responsibilities.
Earlier private Analytics testing: The basis for optional gameplay measurement in that separate test was consent under Article 6(1)(a). Withdrawal does not affect processing that was lawful before withdrawal. It does stop authorizing future consent-based processing; earlier records and deletion requests are handled as described in sections 9 and 11. This is not a basis for new gameplay analytics in the release covered here.
Your interests and choices: Where we rely on legitimate interests, they must not override your rights and interests, including the protections due to younger players. You can object by contacting us; we will assess the objection under applicable law. Ordinary play does not require watching ads, and consent can be revisited as described in section 5.
Device storage and access: Consent requirements for storing or accessing information on your device are separate from GDPR legal bases. A legitimate-interest basis does not replace device consent where it is required. Exceptions are narrow, such as storage strictly necessary for a service you expressly request or for communication transmission. Local-only records, non-personalized ads and SDK bundling do not by themselves establish an exception. The technical interests stated above do not make every SDK operation essential or mean that all processing waits for consent.
9. Retention and deletion
Local game data: Saves, preferences and lifetime records normally remain until you reset them, clear app data or uninstall, subject to backup or restoration. Recent player history and detailed diagnostics use bounded storage rather than a universal time limit: the default limits are 20 player-history entries and 100 diagnostic sessions. A previously customized history limit can retain up to 200 entries. Local tutorial diagnostics can remain until local data is cleared.
Delete Player Statistics clears player-facing statistics and records while preserving the current game, Daily progress, preferences and separate diagnostic history. The current Endless run is not counted again in the reset statistics. Delete All Local Data clears app-owned game records, including those diagnostics and ordinary preferences. On Android, it also records a local instruction to keep analytics off while retaining Google’s shared consent choices so you can revisit them; a remembered Google grant cannot undo the local off instruction automatically. An interrupted local reset is completed before game data is restored. New play can create new local records.
Earlier private Analytics data: Local reset, withdrawal, uninstalling or deleting statistics is not a server-side deletion request. Both configured Analytics properties retain user data and event data for two months, with reset-on-new-activity disabled. Standard aggregated reports are not governed by the same user/event retention setting. Remote deletion requests and applicable rights are explained below. Google may retain information required under its terms and applicable law; no instant or universal erasure is promised.
Separate Firebase records from private testing: Analytics reset does not delete a separate Firebase installation identity, its server records or all supporting SDK operational records. The two-month Analytics setting does not define those records’ lifetime. Google describes its separate Firebase Installations deletion lifecycle. Deleting that identity does not delete Analytics records, and an enabled Firebase service may create another identity. These are separate processes from withdrawing Analytics consent.
Other data: Support and privacy emails are retained for up to one year from receipt, unless longer retention is required by law or to handle an unresolved legal claim. Advertising and consent-service information is retained according to Google’s and applicable partners’ policies. Files you exported, sent to others or backed up are not removed from those destinations by an in-app reset; use the relevant provider’s controls.
10. Data security
We use app-private storage, restricted account access, HTTPS/TLS for supported provider communications, and data minimization to reduce risk. The policy website does not load external scripts or fonts. No storage, network, or service can be guaranteed completely secure. Keep your device and app updated and avoid sharing exports or identifiers publicly.
11. Your privacy rights
Depending on applicable law, you may have rights to access, rectify, erase, restrict processing, obtain portable data, object to certain processing, and withdraw consent. You can contact stoned.gymrat@gmail.com. EU requests are normally answered within one month, with extensions or exceptions explained where the law permits them. You can complain to the Bulgarian Commission for Personal Data Protection or your competent supervisory authority.
Earlier private Analytics data: We do not maintain player accounts or a name-to-Analytics-identifier directory. If you retained your Analytics app-instance identifier during private testing, you can voluntarily include it in a private deletion request. Do not post it publicly. The signed testing release does not enable Analytics or provide retrieval of an active Analytics identifier. We use an identifier you supply only to locate the applicable records and submit a deletion request through Google’s administrative process. No identity document is normally required for this technical request; further proportionate verification may be needed to protect another person’s data.
We distinguish Google’s acceptance of a deletion request from completed erasure. We will explain the request’s scope and any known limitations; an acknowledgement does not mean every copy has already been removed. See Google’s Analytics user-deletion process.
After a reset, reinstall or identifier change, the old identifier may no longer be available. A later identifier cannot necessarily identify earlier installations. If you cannot provide the relevant identifier, tell us what is available: we will explain what we can locate and the applicable retention limits. We will not re-enable analytics to try to reconstruct an old identifier. Local reset alone does not delete previously transmitted records, and a remote request does not remove exports or copies held by other recipients.
Other Firebase installation data from private testing: The Analytics ID is not the separate Firebase installation ID. The app does not provide a control to display or delete that separate ID, and an Analytics-only deletion request does not erase its records. Contact us if your request concerns this data too. We will explain the identification limitation and investigate the available provider process; we will not report deletion as completed when it has not been established.
12. Age and intended audience
Gem Rondo is intended for ages 13 and above. Gameplay analytics is unavailable in the versions covered here. Earlier private Analytics testing separately required participants to confirm that they were at least 18 and able to give their own privacy consent; that condition did not change the game’s audience. No date of birth or parental account is collected for that check.
The private test’s 18+ condition was a conservative product restriction, not a statement that one age determines consent capacity in every country. We do not offer a parental-consent analytics flow. Advertising uses the restrictive treatment described above for every player. If you believe information about a child was processed inappropriately, contact us.
13. Privacy Policy website
This standalone policy website is hosted on Cloudflare Pages and is publicly accessible without an account. It does not load game code, third-party fonts, analytics scripts, advertising, or tracking pixels. Cloudflare may process connection information, such as IP addresses and request details, to deliver and secure the page. This project does not enable Cloudflare Web Analytics, Zaraz, Logpush, a database, or user accounts. See Cloudflare’s Privacy Policy.
14. Policy changes and future features
We will update this policy when practices materially change and show the applicable effective date. Where a new purpose requires consent, a policy update alone will not enable it. Daily Rondo currently runs locally; the app does not provide a server leaderboard. This policy does not authorize future accounts, remote leaderboards, exported-statistics uploads, or crash reporting that have not been implemented and disclosed.