Arrow Away — Privacy Policy

RayCastLab publishes Arrow Away 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 and Firebase Crashlytics, Google processes the data on our behalf under Google's data processing terms — we decide what is logged and can see the results, but not the underlying installation identifiers.

Your Google Play Games profile — your gamer name, avatar and account — is Google's, and Google handles it under its own privacy policy.

The game keeps a small amount of information in its own private storage area, which no other app can read. It is:

None of this identifies you. There is no name, no email address, no device identifier and no account in it. Apart from the progress copied to Play Games, described below, it never leaves your phone. Uninstalling the game or clearing its data deletes all of it permanently.

If you have Google Play Games, the game signs you in automatically when it starts. You do not have to: if you are not signed in, or you cancel, the game plays exactly the same, without achievements, leaderboards or the cloud save.

While you are signed in, the game sends Google the following, all tied to your Play Games player ID:

The cloud save is stored in your own Play Games account. We cannot read it, and the game never receives your name, your email address or your Google account — only what Play Games needs to show achievements, leaderboards and the save. The game also records whether signing in succeeded, as one of the analytics events below.

You can delete this game's data, or your whole Play Games profile, at any time from the Google Play Games settings.

The game uses Google Analytics for Firebase to understand how it is actually played — which levels people get stuck on, whether the difficulty curve holds up, and whether a change we ship helps or hurts. It logs a small, fixed set of events:

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 ourselves — 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 it recovers from, Firebase 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 and storage were free, whether the app was in the foreground, and the time. Crashlytics attaches its own anonymous installation identifier so that repeated crashes on one device can be counted once.

Because Analytics runs in the same app, a report also includes the most recent analytics events from the list above, which tells us which screen the crash happened on. A report contains no save data, no purchase details and nothing you typed — the game has no text input. Reports are kept by Google for 90 days.

If you stop playing for a while, the game sends a few reminders — at most after 1, 2, 3, 7, 14 and 30 days — and then stays quiet until you play again. If you have played the daily challenge before, the first one tells you that today's challenge is ready. On Android 13 and later the game asks for permission first, and you can switch reminders off in the game's settings or in Android's.

Reminders are scheduled on your phone by the game itself. No server sends them and nothing is uploaded to set them up; only the act of opening the game from one is recorded, as an analytics event.

The game is free and shows ads through Google AdMob: a banner during play, a full-screen ad after some completed levels, and rewarded ads you choose to watch for an extra life or hint.

To do that, 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.

How Google handles this is described in Google's privacy policy and in "How Google uses information from sites or apps that use our services". You can reset or delete your advertising ID at any time in Android's settings, under Privacy and then Ads.

Buying the ad removal switches off the banner and the full-screen ads permanently. Rewarded ads remain available, because those are something you choose to watch — but if you never tap one, no rewarded ad is ever requested.

Ad removal is a one-time purchase handled entirely by Google Play Billing. Google processes the payment and holds the record of it.

We never receive or store your card details, your billing address or your Google account. All the game keeps is a yes-or-no flag on your device saying that ads are off. Because the purchase is tied to your Google account, Google Play can restore it if you reinstall.

Hints refill 24 hours after they were last topped up. To make that fair, the game asks a public time server (time.google.com) what the time is instead of trusting your phone's clock, which anyone could move forward.

Only a time request is sent — no game data, no identifiers, nothing about you. As with any internet connection, the server sees the IP address the request comes from. If you are offline the request simply fails, nothing is stored, and your hints refill later when a connection is available.

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

The game itself asks Android for four permissions: internet access, for ads, purchases, Play Games and reports; vibration, for the tap feedback you can switch off in settings; notifications, for the reminders above; and permission to run at start-up, so that scheduled reminders survive a phone restart. Google's libraries add the permissions they need on their own — the advertising ID, network status and Play Billing — and none of these give access to anything on your phone beyond what is described here.

Arrow Away is a general-audience puzzle game. It is not directed at children under 13, and we do not knowingly collect personal data from them. 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 two 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.

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.