Privacy policy

RainCue · version 1,

Takes effect with the first published version of the app. RainCue is not published yet and processes nobody's data today. This document exists ahead of time on purpose: it describes what the app will do, and it is checked against what the app actually does before every release.

The short version

Who is responsible

RainCue is built by an independent developer. The name and contact address appear on the app's Google Play listing, where Google displays them as a requirement. For privacy matters: magisperez73@gmail.com.

What data is processed, what for, and where it ends up

DataWhat forStored
Coordinates of the areas you choose (approximate or precise, depending on how you pick them) The core of the service: the server watches the weather at those points so it can warn you Yes, on the server, for as long as the app stays installed
Your routines: days of the week, time window, and the device's time zone Deciding whether the rain affects you, at your hour, and never messaging you outside that window Yes, on the server
Notification identifier (Firebase Cloud Messaging token) Delivering the alert to the device. It is the only identity that exists and it is not tied to any personal data about you Yes, on the server
Settings: language, sensitivity and quiet hours Making the alert behave the way you want Yes, on the server, alongside the above
The name you give each routine ("Cycling to work") Writing it inside the alert, so you know which of your plans is at risk. It is not analysed or indexed: it is only copied into the text of the notification Yes, on the server
Crash reports and anonymous usage Finding out that the app broke, and which screens get used Processed by Firebase Crashlytics and Analytics

Location, in detail

You can pick an area by searching for its name, without granting any location permission. If you prefer to use your current position, the app asks for the permission at that moment, with the app open, uses it once to fill in the area, and never reads it again on its own. RainCue does not use background location and cannot know where you are when you are not using it.

The coordinates of the area are stored on the server, because there is no other way to watch that point's sky every few minutes. They are stored on their own, with no name or email attached.

Advertising: there is none

RainCue shows no ads and bundles no advertising network. No advertising identifier is collected, your IP address is not shared with advertisers, and there is no consent form to accept, because there is nothing to consent to. The paid version is not about removing ads: it is about keeping several routines active at once.

The only third party is Google, and only for two technical things: delivering the notification (Firebase Cloud Messaging) and telling us when the app breaks (Crashlytics and Analytics). Their policy: Firebase.

How long it is kept

For as long as you use the app. If you uninstall RainCue, the notification identifier stops being valid and your areas and routines are deleted automatically once the system tells us that identifier no longer exists. On top of that, any device that goes silent for a prolonged period is removed along with its data.

How to delete your data right now

Two ways, and neither of them requires writing to anyone:

If you would rather ask in writing, write to the contact address and it will be done.

Children

RainCue is not directed at children under 13 and does not knowingly collect their data.

Your rights

If you live in the European Union, the GDPR grants you rights of access, rectification, erasure, restriction, portability and objection. Because there are no accounts, we cannot link the stored data to a specific person: that is why deletion is offered directly inside the app, which is the only party that knows its own identifier. The legal basis is the performance of the service you asked for and, for advertising, your consent.

Changes

Any change is published on this page with its date. Changes affecting what data is collected are also announced inside the app before they take effect.