Privacy Policy for Alarma

Alarma is a reminder and alarm app published under the trading name Batranelu.dev ("we", "us") by an independent developer based in the Netherlands. Batranelu.dev is not a registered company. You can reach us at batranelu.dev@gmail.com.

This policy explains what the app does with your information. It covers the Android app com.batranelu.alarma distributed through Google Play, and nothing else.

1.What stays on your device

Alarma stores the following in the app's own private storage, which other apps cannot read:

• Your reminders. For each one: a title, the type (alarm or calendar event), the date and time, whether and how it repeats, whether it is done, when you created it, how long you last snoozed it and how many times you have snoozed it.
• The alarm sound you picked, when you choose one instead of the device default. This is stored as the system reference to that sound plus the label the ringtone picker gave it, which for a sound of your own is that file's name. It is kept so the editor can show you what you chose. It is never transmitted, and it is never included in a crash report.
• Your settings. Theme, sort and grouping choices, whether finished reminders are shown, whether alarms fade in rather than starting at full volume, and your answer to the crash-reporting question. Your chosen language is kept separately, because the app has to know it before anything else loads.
• Your answer to the advertising consent form, where one applies to you. Google's consent SDK writes it to the app's own preferences in the standard format the advertising industry uses, so that the ad network can read the answer you gave. It records your choice, not you.

We have no server, no account system and no sync. We cannot see any of this, and there is nothing for us to log into.

However, Android's own Auto Backup is enabled for this app, which is the Android default. If you have device backup switched on in your Google account settings, Android may copy the app's data to your personal Google Drive backup. That is everything listed above, not a selection from it: your reminders and their titles, your settings, and the two consent answers. That backup belongs to you, is counted against your own storage, and is encrypted by Google; we have no access to it. You can turn it off in Settings → Google → Backup on your device, or per-app where your Android version offers that.

One consequence of this backup, because it may not be obvious. Restoring that backup onto a new device restores your answers along with your reminders, so the app may not ask you again on the new device. The crash-reporting question can be reopened at any time in Settings, whatever was restored. The advertising form can be reopened whenever one applies to you, which is Google's platform to decide rather than ours; section 2.3 explains what Settings tells you when none does.

2.What leaves your device

Crash reports and usage data leave only if you switch them on. When you first open Alarma, it asks whether it may send them. Until you answer, and unless you answer yes, both Google services below are switched off in the app and transmit nothing at all. You can change your answer at any time in Settings → Privacy.

Advertising is not opt-in, because the app is free and advertising is what pays for it. Where the law requires your consent first you are asked, through the form described in section 2.3, and no ad is requested until you have answered. Where no consent form applies to you, ads load without being switched on and section 2.3 sets out what Google receives. Either way, your device's own advertising controls work, and sections 2.3 and 7.2 explain them.

2.1Crash reports (Google Firebase Crashlytics)

If you consent, when the app crashes or hits a handled error we send:

• the stack trace and the type of error;
• the error message, with file paths and document names removed before sending;
• a short trail of the app's own actions leading up to it ("scheduled exact", "re-arming alarms after BOOT_COMPLETED", and similar fixed phrases). If a consent form failed to load, that trail also carries the error code and message Google's consent SDK returned, which describes what went wrong with the form and says nothing about you;
• your device model, Android version and app version;
• the exact source revision the build came from, and whether it was built from modified source (these describe our code, not you);
• which of the app's required permissions were switched on at the time: notifications, the alarm notification channel, exact alarms, full-screen alarms, unrestricted battery, app hibernation, and whether an alarm could have rung visibly at all;
• how many reminders you have, as a number;
• whether the failed alarm was scheduled exactly or inexactly;
• a random identifier Crashlytics generates for the installation, and the time of the crash.

Why: the way this app fails people is that an alarm does not ring, and almost every cause is a permission the operating system controls. Without this we cannot tell a bug from a device setting, and "my alarm didn't ring" cannot be investigated.

What is never in a crash report: the title of any reminder, its time, its repeat rule, the sound you chose or that sound's file name, and the name of any file you exported or imported. The app removes file names and document paths from error text before it is sent.

What Google receives that we do not. Sending a report means your phone contacting Google's servers, so Google sees your IP address in the process, the same way any server sees the address of a device that connects to it. It is not part of the report: it never reaches us, it is not shown to us, and nothing listed above is derived from it. Google calls this service data, meaning the technical and operational details of running the service, and handles it under its own privacy policy rather than on our instructions. For the report itself Google acts on our behalf; for this it does not. The Firebase privacy notice linked in section 4 sets out what that covers.

2.2Usage data (Google Analytics for Firebase)

If you consent, Google Analytics for Firebase collects, while you use the app:

• a randomly generated app-instance identifier;
• your IP address, which Google uses to derive an approximate location, typically country or region, and which contributes to fraud prevention;
• automatic events such as first open, app updates, session starts and session length;
• one event the app sends deliberately: whether a banner ad slot filled or came back empty, and, when it came back empty, the numeric reason code the ad network returned. It says nothing about you or about what you were doing. It exists because an unfilled slot and a broken slot look identical on screen, and without counting them we cannot tell one from the other.

Unlike crash reports, this is sent during ordinary use, not only when something goes wrong.

Three things we have deliberately switched off:

• Your Advertising ID is not collected as usage data. Analytics is configured not to collect it, in every version of the app. The app does hold the AD_ID permission, because AdMob needs it to serve the ads described in section 2.3; that is a separate system, with its own separate consent. Nothing in the usage data described in this section carries a cross-app advertising identifier.
• Install attribution is not collected. The app does not request permission to ask the Play Store how it was installed, so we do not learn which link or campaign brought you here.
• Automatic screen-view reporting is off, so Google does not receive a record of which screens you visit.

Why: to understand how many people use the app, on which devices and Android versions, and whether an update made things worse.

2.3Advertising (Google AdMob)

Alarma is free and supported by advertising served by Google AdMob.

To show ads, Google receives your Advertising ID, your IP address, general device information, and information about the ads shown to you and whether you interacted with them.

On Android versions that provide them, the ads SDK can also use Android's own Privacy Sandbox interfaces, and the app asks for the permissions they require. These are operating system features rather than something we run: Android derives coarse interest topics from the apps on your device and can pass them to advertisers, and it can measure whether seeing an ad led to an install without handing anyone a profile of you. They exist to reduce what cross-app identifiers are used for. We receive nothing from them, and you can review Android's own controls for them in your device settings under Privacy.

Where the law requires your consent before any of that, you are asked for it first, through a form provided by Google's certified consent platform. In the European Economic Area, the United Kingdom and Switzerland that form appears before any ad loads, and it asks whether Google and its advertising partners may use your data for personalised advertising. You can reopen it at any time from Settings → Manage ad consent. If you decline, you will still see ads, but they will not be personalised. Non-personalised ads still use your Advertising ID and IP address for frequency capping, aggregate reporting and fraud prevention.

Which form you see, and whether you see one at all, is decided by Google's platform from where you are, not by the app. The app asks it on every launch and shows whatever it returns; it never decides for itself that your region does not need asking. That is deliberate, so that a form becoming applicable to more people reaches you without the app having to be updated.

Your crash-reporting choice and your advertising choice are recorded separately. Neither one answers for the other.

You can reset or delete your Advertising ID at any time in Settings → Privacy → Ads on your Android device.

One thing you may notice that is not an ad.

Settings → Manage ad consent may tell you that there is no consent form to show. That is the honest answer when no consent form applies to where you are, rather than a fault or a feature that failed to load. Your device's own advertising controls, described above and in section 7.2, work regardless, and they are what section 7.2 points United States residents to for that reason.

Alarma shows one kind of ad and one only: the banner along the bottom of the screen, which everything above describes. There are no full-screen ads, none between screens, and none after you save a reminder.

3.What Alarma never collects

The app does not request or receive your name, email address, phone number, contacts, photos, precise location, calendar contents, or the contents of any other app. It has no account and no login.

When you create a calendar-type reminder and choose to add it to your calendar, Alarma hands the details to whichever calendar app you pick, using Android's standard hand-off. It does not hold calendar permission and cannot read your calendar.

When you export or import reminders, the file goes to or comes from the location you choose in your device's file picker. That file is yours; it does not pass through us.

Alarma does not need a network connection to do its job. Creating reminders, ringing alarms, snoozing, repeating, statistics, export and import all work with the device offline. The network is used for two things only: loading the ads described in section 2.3, and sending the crash and usage data in sections 2.1 and 2.2 if you have switched those on.

4.Who else is involved

For crash reports and usage data, Google acts as our processor under the Firebase Data Processing and Security Terms. For advertising, Google acts as an independent controller of the data it collects, and its own privacy policy governs what it does with it.

These services are operated by Google and data may be transferred to and stored in the United States and other countries. Google relies on the European Commission's Standard Contractual Clauses and its certification under the EU-US Data Privacy Framework for those transfers.

We do not sell your personal information, and the only parties who ever receive it are the services listed above. ("Share" has a narrower, specific meaning under California law, which section 7.2 addresses directly rather than leaning on the ordinary sense of the word.)

This policy covers the app and nothing else. When Alarma opens something outside itself, what happens there is governed by whoever runs it, not by this page. That includes the link to this policy in Settings, the Android settings screens the permission steps send you to, the calendar app you pick for an event, and the file picker you export through. We do not receive anything back from any of them.

An ad is a link out too. Tapping one hands you to Google's ad network and then to an advertiser's own page or store listing. What that advertiser collects is theirs and is covered by their policy, not this one. We do not choose which ads you see and we receive nothing about what you do after you tap.

5.Legal basis (EEA, UK and Switzerland)

We process crash reports, usage data and advertising data only with your consent, under Article 6(1)(a) UK/EU GDPR. There is no other basis, and no legitimate-interest processing of your data by us.

You can withdraw consent at any time, with no effect on the lawfulness of what was processed beforehand:

• Crash reports and usage data: Settings → Privacy → turn off "Crash reports & usage data".
• Advertising: Settings → Manage ad consent.

Withdrawing crash-reporting consent stops further collection immediately. It also deletes any report still waiting on your device to be sent, and clears the analytics identifiers held on your device.

The app works identically whether you consent or not. No feature is withheld.

6.How long it is kept

• On your device: your reminders stay until you delete them, or until you uninstall the app.
• Crash reports: Google retains Crashlytics crash data for 90 days.
• Usage data: user-level analytics data is retained for 2 months, counted from your last activity in the app rather than from when it was collected. Each time you use Alarma, the two months start again. So it is deleted two months after you stop using the app, not two months after any particular visit. Aggregated reports that cannot identify a device may be kept longer.

7.Your rights

7.1EEA, UK and Switzerland

If you are in the EEA, the UK or Switzerland, you have the right to access, correct, erase, restrict or object to the processing of your personal data, to data portability, and to withdraw consent.

We cannot action a request to delete or produce "your" data, and we do not operate a service that tries to. This is not a policy choice dressed up as a limitation. It follows from the app's design, and the law provides for it directly.

Everything we receive is pseudonymous. We receive no name, no email address, no account, no device identifier that belongs to you rather than to an app installation. The identifiers attached to a crash report or a usage event are randomly generated by Google's SDKs and mean nothing outside them. Given a person, we have no way to find their data; given a record, we have no way to find the person. We hold nothing that bridges the two, and we have deliberately not built anything that would.

Article 11(2) UK/EU GDPR covers exactly this position: where a controller can demonstrate it is not in a position to identify the data subject, the rights of access, rectification, erasure, restriction and portability (Articles 15 to 20) do not apply. Article 11(1) adds that we are not obliged to acquire or keep extra information about you purely so that we could comply. Collecting more about you in order to be able to delete you would make your privacy worse, not better, and we will not do it.

Those rights revive, under the one exception Article 11(2) itself provides: if you can supply information that identifies your data to us. In practice that would mean the Firebase app-instance identifier or the Crashlytics installation identifier for your install. The app does not display either, and we have no plans to add a screen that does, so this is a real exception rather than a practical route. If you do obtain one and send it to us, we will act on it.

What this does not mean. It does not mean the data is kept forever, and it does not leave you without control. Deletion happens by time and by your own switches rather than by asking us:

• By retention. Crash reports are deleted by Google after 90 days. Usage data is deleted two months after your last activity; see section 6.
• By withdrawing consent, which stops collection immediately, deletes any report still queued on your device, and resets the analytics identifiers held there. A reset identifier cannot be tied to the one before it, so the old records stop being about your install at all.
• By uninstalling, which removes everything held on the device, reminders included.

The effective controls are the ones in the app and on your device:

• your reminders: delete them in the app, or uninstall it;
• crash reports and usage data: withdraw consent in Settings, as above;
• advertising: reopen the consent form at Settings → Manage ad consent;
• your Advertising ID: reset or delete it in your device's Android settings;
• data held by Google: contact Google directly using the links in section 4.

You also have the right to lodge a complaint with a data protection authority. Ours is the Dutch Autoriteit Persoonsgegevens (https://autoriteitpersoonsgegevens.nl). You may also complain to the authority where you live or work, wherever that is in the EEA. You do not have to come to ours.

7.2United States

This section applies wherever you are in the United States. Several states now give residents similar rights, and rather than guess which of them we are large enough to be caught by, we give everyone the same answers and the same controls.

Categories of personal information we collect. Using the categories California's law defines:

We collect these for the purposes in sections 2.1, 2.2 and 2.3, from no source other than your own device, and we share them only with Google as described in section 4.

Selling and sharing. We do not sell your personal information for money, and never have.

However, California's law defines "sharing" specifically to include disclosing personal information for cross-context behavioural advertising, which means personalised ads. Alarma serves ads, and where you have not declined personalisation your Advertising ID and IP address go to Google for that purpose, which is "sharing" as the statute uses the word. Other states describe the same activity as "targeted advertising".

How to opt out of that. Two controls, both available now:

• On your device, at Settings → Privacy → Ads, you can turn on "Opt out of Ads Personalization" or delete your Advertising ID outright. This applies to every app, not just this one, and Google honours it.
• Declining crash reports and usage data in Settings → Privacy stops everything described in sections 2.1 and 2.2, independently of advertising.

If we later add an in-app opt-out for US residents, it will appear at Settings → Manage ad consent, which today serves only the EEA, UK and Switzerland.

Your rights. To know what we collect, to a copy of it, to have it corrected or deleted, to opt out of sale or sharing, and to limit the use of sensitive personal information. As shown above, the last of these has no basis here.

Non-discrimination. We will not charge you a different price, give you a lower level of service, or withhold any feature because you exercised any of these rights. The app behaves identically whichever way you answer.

We do not operate a data deletion or access service, the reason for that is detailed below. A request to delete or produce "your" data has to be verifiable: we have to be able to establish that the data is yours before acting on it. We cannot, for anyone. Everything we receive is pseudonymous: no name, no email address, no account, and identifiers that are randomly generated per app installation and mean nothing outside Google's SDKs.

California's law addresses this directly. Section 1798.145 provides that a business is not required to reidentify or otherwise link information that it does not, in the ordinary course of business, maintain in a form that would be considered personal information, nor to collect, retain or obtain any data or technology in order to become capable of linking a request to a person. Every state law modelled on it takes the same approach, and a request that cannot be verified must be denied rather than guessed at.

Deliberately building the ability to identify you, purely so that we could delete you on request, would mean collecting more about you than we do now. That is a worse outcome for you than the one described here, and we will not do it.

What still deletes your data, without asking us. Retention: 90 days for crash reports, and two months from your last activity for usage data, per section 6. Withdrawing consent, which stops collection, clears queued reports and resets the identifiers on your device. And uninstalling, which removes everything held locally. The device controls listed above are the ones that work, which is why they come first.

You can still write to us at batranelu.dev@gmail.com, and we will respond within 45 days, including to tell you, where that is the answer, that we could not identify any data as yours. An authorised agent may contact us on your behalf. If you can supply the Firebase app-instance identifier or Crashlytics installation identifier for your install, that changes things and we will act on it.

Do Not Track. Alarma is a mobile app, not a web browser, and receives no Do Not Track or Global Privacy Control signal from your device. We therefore do not respond to one. The device-level advertising controls above are the equivalent mechanism on Android, and those we do honour.

Children. We do not knowingly collect personal information from anyone under 18. That is well above the age of 13 set by the federal Children's Online Privacy Protection Act, and deliberately so. See section 8.

8.Children

Alarma is not directed to children and is not designed for them. It is listed on Google Play for an audience of 18 and over.

Everything we receive rests on consent, and the age at which a person can give that consent for themselves differs by country. Rather than apply a different age in each place, we apply the highest one everywhere: we do not knowingly collect personal data from anyone under 18, wherever you are.

That is higher than any of them requires. The Netherlands, where we are established, sets 16, and that is what the EEA and the UK would ask of us; the United States sets 13 under the Children's Online Privacy Protection Act, and other countries fall between. Eighteen is the age this app is listed for, so it is the age we hold ourselves to for collection as well, rather than running a store listing and a privacy policy on two different numbers. Nobody gets less protection than their own law provides, and most get more.

If you are a parent or guardian and believe a child has used Alarma, tell us at batranelu.dev@gmail.com and we will look into it. Be aware of the limit described in section 7: we receive nothing that identifies anyone, so we cannot locate one child's records among pseudonymous data any more than we can locate an adult's. The remedy that actually works is on the device and takes effect immediately. Open Settings → Privacy and turn off "Crash reports & usage data", which stops collection and clears the identifiers held on the device, then uninstall the app if you wish, which removes everything stored locally. What has already been sent then ages out on the schedule in section 6.

9.Security

Your reminders are stored in the app's private storage, which the Android operating system isolates from other apps. Everything transmitted to the services in section 4 travels over encrypted connections. We hold no database of our own, which is the strongest security property this app has: there is nothing of yours for us to lose.

No method of transmission or storage is completely secure, and we will not claim otherwise. What we can say is narrower and more useful: the part of this that is normally the risk, a server holding user records, does not exist here.

If there is ever a breach. Where a breach affects personal data and the law requires it, we will notify the Dutch Autoriteit Persoonsgegevens within 72 hours of becoming aware of it. We cannot notify you individually, and the reason is the same one that runs through section 7: we hold no email address, no account and nothing else we could reach you with. So we would also publish a notice at this address, and keep it here rather than replacing the page silently. A breach at Google affecting Crashlytics, Analytics or AdMob data is Google's to disclose, under the policies linked in section 4.

10.Legal requests, and what happens if the app changes hands

Requests from authorities. We have never received a request from a law enforcement agency or a court for user data, and we hold nothing that would answer one. There is no database, no account and no server: a request naming a person could not be matched to anything we have, for the reasons set out in section 7. If we ever do receive a lawful request we will comply with it to the extent the law requires, which for the data described in this policy means telling the requester that we hold nothing responsive. Crash, usage and advertising data sit with Google, and a request for those has to go to Google, which handles it under its own policies rather than on our instructions.

If the app is sold or transferred. Alarma is published by an independent developer, and an app can change hands. If that happens, there is no user database to transfer, because none exists. What would transfer is the app itself and the Google service accounts behind it. A new owner would take on this policy as it stands, and any change to what the app collects would go through section 11 like any other change: published here first, and asked again in the app if it is material. We will not quietly hand your consent to someone whose practices you have not seen.

11.Changes to this policy

If we change what the app collects, we will update this policy and change the date at the top. A change is published at this address before it takes effect, not after. If a change means collecting something materially new, we will ask for your consent again in the app rather than relying on this page having changed.

12.Contact

batranelu.dev@gmail.com