Konquera — Privacy Policy

RayCastLab publishes Konquera and is the controller for the data described here. Contact: info@raycastlab.com.

For the advertising data that Google collects through the ads in the game, Google acts on its own behalf as an independent controller — we cannot access it, and requests about it are handled by Google.

For Firebase Analytics, Crashlytics and Remote Config, Google processes the data on our behalf under Google's data processing terms — we decide what is logged and can see the results, but we cannot look up an individual player.

The game keeps its save data in its own private storage area, which no other app can read. It never leaves your phone. It is:

None of this identifies you. There is no name, no email address, no device identifier and no account in it. Uninstalling the game or clearing its data deletes all of it permanently.

In the European Economic Area, the United Kingdom and Switzerland, the game shows Google's consent form the first time it starts and before any ad is requested. The form is Google's User Messaging Platform; what you choose there is stored by Google's SDK on your device and applied to the ads.

If the form is required and you do not consent, the game does two things: it does not request any ads at all, and it switches analytics collection off. The game itself stays fully playable.

You can change your answer at any time in the game's settings — the row is called Privacy options and appears only where the form applies. Whether the form was answered, and whether ads may be requested afterwards, is recorded as one analytics event (consent_response) so we can see how many players are asked.

The game uses Google Analytics for Firebase to understand how it is actually played — where the difficulty curve breaks, which offers get ignored, whether a change we ship helps or hurts. It logs a fixed set of events:

Alongside the events, the game sets four properties on the installation so results can be grouped: your current level, your current region, whether you have ever bought anything (yes or no), and a rough bracket of how many coins you hold.

To attach these events to a device, Firebase assigns an anonymous installation identifier — it is not your name, email or Google account, and it is a different identifier from the advertising one used for ads. Firebase also records ordinary technical details alongside every event: device model, OS version, app version, and an approximate location derived from your IP address, no more precise than city level.

The Google Mobile Ads SDK also reports a couple of events to Firebase on its own, independently of the events we log — a screen view when a full-screen ad opens, and a record when a rewarded ad pays out.

How Google processes this data is described in Google's privacy policy and in the Google Analytics for Firebase documentation. Uninstalling the game or clearing its data ends that installation's history; a fresh install gets a new, unconnected identifier.

If the game crashes or hits an internal error, Crashlytics sends Google a report so we can fix it: the stack trace, the device model, the OS version, the app version, how much memory was free, and the time. To make a report reproducible, the game attaches four keys — the level and region you were on, the graphics tier in use and the device tier the game detected.

A crash report contains no save data, no purchase information and nothing you typed — the game has no text input. Reports are grouped by Google and kept for 90 days.

Some of the game's numbers — ad frequency, offer timing, economy and difficulty dials, feature switches — can be adjusted without an update. The game asks Google's Remote Config for them at most once every four hours, waits at most eight seconds, and falls back to its built-in values if the request fails or you are offline.

The request carries what the service needs to pick a value for your device: the same anonymous installation identifier as analytics, the app version, your device's language and country, its OS version and time zone. No save data and no personal information is sent.

The game is free and shows ads through Google AdMob: a banner during play, a full-screen ad on the way out of the victory screen, and rewarded ads you choose to watch — for triple coins after a win, reinforcements after a loss, an extra chest, the daily free coins, a discount on an upgrade, hero tokens, or to rescue a broken daily-reward streak.

Full-screen ads are gated: never before level 3, never in the first two minutes after launch, at most one every two levels, at least 90 seconds apart, never after a loss and never at the start of a level. Rewarded ads only ever play when you tap the offer.

To show ads, Google's advertising SDK collects information from your device — typically your advertising ID, IP address, and details about your device, operating system and the app. Google uses it to select ads, limit how often you see the same one, measure performance and detect fraud.

AdMob is the only ad network in the game; no other advertising SDK is included. How Google handles the data is described in Google's privacy policy and in "How Google uses information from sites or apps that use our services". On Android you can reset or delete your advertising ID at any time in the system settings, under Privacy and then Ads.

Buying No Ads or the Starter Pack switches off the banner and the full-screen ads permanently. Rewarded ads remain available, because those are something you choose — and the rewards they pay are then paid to you automatically, without the ad.

On iOS, Apple's App Tracking Transparency applies. After your second level the game asks, in its own words, whether it may ask for tracking permission; only if you say yes does the system dialog appear, and it appears once. Saying no to either keeps Google from using your device's advertising identifier — you still see ads, but not ones personalised to you.

This section does not apply on Android, which has no such dialog. Where the consent form of the section above applies, it applies on both platforms.

In-app purchases — No Ads, the Starter Pack, gem packs and the time-limited packs — are handled entirely by the store you bought them from. Google (or Apple) processes the payment and holds the record of it.

We never receive or store your card details, your billing address or your store account. On your device the game keeps only what it needs to deliver: which permanent products you own, the identifiers of purchases already delivered (so nothing is delivered twice), and the time of your last purchase, which some offers use. Analytics learns the product and the price tier of a purchase, and whether you have ever bought anything, as described above.

Because a permanent purchase is tied to your store account, the store can restore it on a new device — the Restore purchases button in settings asks it to.

The daily reward, the Daily Operations, the offer windows and the countdown on time-limited packs all run on your device's own clock. The game does not ask a time server what the time is and makes no network request for it.

To be explicit about the things apps commonly do that this one does not:

The game declares no permissions of its own. The Google SDKs it includes add internet access, network-state access and, on Android 13 and later, the advertising-ID permission. Vibration uses the system's haptic feedback, which needs no permission, and can be switched off in settings.

Konquera is a general-audience strategy game. It is not directed at children under 13, and we do not knowingly collect personal data from them. The game is not part of Google Play's Designed for Families programme. If you believe a child has provided personal data through the game, write to us and we will look into it.

You have the right to ask for access to your personal data, its correction or deletion, and to object to or restrict its use. In practice these requests fall into three groups:

You are welcome to write to info@raycastlab.com regardless, and we will help where we can. If you are in the European Economic Area or the United Kingdom you may complain to your data protection authority; if you are in Türkiye, Article 11 of the KVKK gives you equivalent rights and you may apply to the KVKK.

On your device: until you uninstall the game or clear its data. Analytics: for the retention period set in Firebase, at most 14 months for data tied to an installation, after which Google deletes it and only aggregated reports remain. Crash reports: 90 days. Remote Config requests: not stored beyond the request. Advertising data: under Google's own retention rules. Purchase records: by the store, under its terms.

If this policy changes, the date at the top of the page changes with it. Material changes will also be noted in the app's store listing.

Questions about this policy: info@raycastlab.com.