Privacy Policy

Aura Alarm Clock · com.aurora.alarm · As of 4 October 2026
Applies to the Google Play version and to the direct install.

English · Deutsch ·

1. The principle

Aura is an alarm clock. By far the largest part of what you enter — your alarms, their times, days, sounds, wake-up tasks, your statistics and your settings — stays on your device and is not transmitted anywhere.

Aura contains no advertising, no third-party tracking, no analytics tools and no advertising identifiers. There are no password-protected accounts and no sign-in. There is one lean count of our own — on how many days a device fetches its replies and gifted days — and section 2b describes it openly.

Data leaves your device only in the six cases described individually below. You initiate five of them yourself; the sixth (weather) is a setting that is off by default.

2. Feedback (“Feedback & Ideas”)

When: Only when you fill in the feedback screen and send it. Nothing is transmitted before that.

What is transmitted:

About the screenshots, and please read this before sending: A screenshot shows everything that was on screen at that moment — possibly including your alarm names or other personal details. Aura neither selects nor inspects the images; what goes along is entirely your decision. They expire with the rest of the entry after 180 days.

What does NOT go along: your alarms, your alarm history, your location, your profile picture.

The same route, two more occasions: an icon proposal (Settings → App icon → propose your own icon) sends the image you choose and crop yourself, together with the app version, Aura ID and claim secret — nothing else. And when you write back to a reply from us (section 2a), your text goes to the same mailbox with the same identifiers.

Where it is stored: On a Cloudflare Worker with KV storage. Entries expire automatically after 180 days. The mailbox stores no IP address. To prevent abuse, Cloudflare counts per IP address how many messages arrived within the last minute; this counter lives for at most one minute and is neither stored nor viewed by us.

Two exceptions to the 180 days — both arise only when we act ourselves:

• Gifted Premium days: when we gift you days, we store a grant — the number of days, the reason, the time, the identifier it goes to (claim secret or Aura ID) and, once your device has picked it up, the time of pickup. Grants have no automatic expiry: they are the proof that the days are yours, and they bring them back after a reinstall.
• Our name list: so we can keep several messages from the same person together, we may give an identifier in the mailbox a name (for example the one you sign with). This list also has no automatic expiry.

We delete both immediately on request (contact in section 10; please state your Aura ID).

Legal basis: Art. 6(1)(a) GDPR (consent) — before sending you confirm a checkbox above which all the fields listed here are shown.

2a. Replies from us to you (inbox)

When: If we reply to feedback you sent. The reply shows up in the app’s inbox — the envelope at the top left of the home screen.

What is stored: free text from us, your claim secret (the secret random identifier of your device — not your public Aura ID), the time it was sent and, once your device has picked it up, the time of delivery.

Why the secret and not the Aura ID: the Aura ID is meant to be shared — anyone who knows it could otherwise fetch a reply addressed to you. Replies are therefore tied to the secret alone; older feedback without one cannot receive a reply.

How it reaches you: your app uses the same request that also fetches gifted Premium days — no additional network path. Fetched replies then live on your device and can be removed there with “Clear inbox”.

How long: like every mailbox entry, replies expire after 180 days. As long as they have not been delivered, we can withdraw them.

Update notes in the same inbox are created on your device and never go online.

Legal basis: Art. 6(1)(b) and (f) GDPR — replying to feedback you sent is the very purpose for which you sent it.

2b. Fetching replies and gifted days — and the count that comes with it

When your app asks: replies (2a) and gifted Premium days (section 6) are picked up with one single request. It runs

• when you open “Account & Profile”;
• when the app starts — only if you have sent feedback before, and at most once a day;
• during the seven days after your most recent feedback, additionally on its own, so a reply reaches you without you having to look: in the background roughly every 15 minutes, with the app open every 30 seconds to 3 minutes. After that it switches itself off.

If you never send feedback and never open “Account & Profile”, this request never happens.

What is transmitted: your Aura ID and your claim secret — nothing else. No device or app details, no location.

What the mailbox records — the count: at most once every 20 hours it notes, for your Aura ID, the day of the first and of the last request and on how many days in total a request was made. This produces a list of how many devices actually use Aura, and it helps us match feedback to a device. The claim secret is not in this list. An entry expires 180 days after the last request. In addition, the mailbox keeps, for at most 24 hours, a technical cache of what is currently waiting for your identifiers — a copy, no new data.

Legal basis: Art. 6(1)(f) GDPR — our legitimate interest in delivering replies and gifts and in knowing how many devices use the app. You can object at any time (section 8); we then delete your entry.

3. Profile sync (transferring alarms to another device)

When: Only when you create a profile in the settings or connect using a code. Without a profile code nothing happens here.

What is transmitted: Your alarms and your app settings — end-to-end encrypted.

How the encryption works: The content is encrypted on your device using AES-GCM; the key is derived from your profile code via PBKDF2. The code itself never leaves your device — the server only sees an address value derived from it and an encrypted block it cannot read.

Which also means: whoever knows your code can reach your alarms. Do not pass it on. If you have passed it on, renew it (Settings → Profile & Sync → renew code) and reconnect your other devices — as long as one of them still holds the old code, it no longer protects anything.

Where it is stored: Cloudflare Worker with KV storage. Envelopes expire 400 days after the last upload. To prevent abuse the IP address is used briefly as a counter — Cloudflare counts the requests of the last minute per address, and the service additionally counts in memory — and is not stored permanently.

Deletion: Settings → Profile & Sync offers two separate routes. “Disconnect profile” detaches this device only; the envelope stays so other devices can keep using it. “Delete profile” removes the envelope on the server and invalidates the code. Your alarms on the device remain unchanged in both cases.

Legal basis: Art. 6(1)(b) GDPR (performance of the function you requested).

4. Crash reports

When: Only if you explicitly agree at the next start after a crash. Without your consent the report does not leave the device — until then it is stored locally only.

What it contains: Error type and stack trace, app and Android version, device model, plus an excerpt of the technical alarm trace (which alarm sound was selected, whether the backup sound took over, timestamps).

What it does NOT contain: alarm names, your texts, your location, your account data. Of the alarm sounds only the type of source is logged (e.g. “content”, “http”), never a title — a music title would be personal data.

Route and retention: As with feedback (section 2), so 180 days.

Legal basis: Art. 6(1)(a) GDPR (consent).

5. Temperature display (optional, off by default)

When: Only if you switch on the temperature display and allow location access.

What happens: Aura requests the approximate location (ACCESS_COARSE_LOCATION — area-level, not metre-level) and uses it to fetch the current temperature and the forecast for the coming hours from the weather service. From version 1.0.8 that is the Norwegian Meteorological Institute (MET Norway) (api.met.no); up to version 1.0.7 it was Open-Meteo (api.open-meteo.com). Latitude and longitude are transmitted, rounded to about one kilometre, together with — because MET Norway requires it from every app — an identification of the app (name, version, our contact address), nothing about you. As with any request on the internet, the weather service sees your IP address. Aura itself stores the last coordinates locally only, so it does not have to locate you again on every glance. The weather data is licensed under CC BY 4.0, source: MET Norway.

There is no Aura-side location storage, and the location is not transmitted to any of the Aura services.

Legal basis: Art. 6(1)(a) GDPR (consent — the system prompt).

5a. Watch and sleep data (optional, off by default)

Everything in this section is off until you switch it on yourself. Without a watch on your wrist, nothing here changes for you.

Aura on your watch. Aura ships a small watch app of its own. It shows the next alarm as a tile, and while an alarm rings, a screen for dismissing or snoozing. For that, your phone sends the time and name of the next alarm to your paired watch — over Google’s Wear OS data layer, that is from your device to your device. That message never reaches a server of ours; we do not see it.

Pairing a watch. The pairing dialog comes from the operating system and shows you devices nearby. All Aura learns from it is that a watch belongs to your phone — no location, no health data, no connection data. In return, Android is slower to shut Aura down in the background, and that is exactly what the pairing is for.

The Sleep Coach — sleep data from Health Connect. If you switch the Sleep Coach on and grant permission, Aura reads your sleep times from Health Connect — Android’s local health store, which your watch or fitness app writes to. Aura measures nothing itself: no microphone, no motion sensor, nothing running through the night.

• What is read: sleep records only, start, end and duration only, from the last 14 nights only.
• What for — and this is a feature, not a display: Aura works out from your sleep goal and your next alarm when you would need to be in bed, and brings that recommendation forward by however much you actually fell short of your goal in the nights it measured. It reminds you quietly in the evening, shows your average across those 14 nights and how many of them met your goal — and compares short nights with how often you hit snooze the morning after.
• Where it goes: nowhere. The sleep times themselves are read when displayed and discarded afterwards — not stored, not transmitted, not included in feedback, and not placed into profile sync. Aura writes nothing back to Health Connect and does not read in the background.
• The one exception, and it is here because it is one. So that the evening reminder names the same bedtime as the card, Aura stores a single derived number on your device: by how many minutes, in the median, you fell short of your goal — capped at 60. No night, no date, no duration; only that number. It stays on the device, is not placed into profile sync, expires after a week and disappears the moment you switch the Sleep Coach off. That is exactly why it exists: without it, Aura would have to look into Health Connect in the background each evening — and it will not.
• Never for advertising. Aura does not use health data for advertising, does not sell it and does not pass it on to anyone.
• Withdrawing: two ways, both stopping every read immediately — the “Sleep coach” switch inside Aura (Settings → Look back → History → Sleep) or Health Connect → Permissions → Aura. The sleep times were never stored in the first place. The switch inside Aura deletes the one derived number at that same moment, together with the record of which evenings you responded to the reminder. If you revoke only the permission in Health Connect, Aura cannot learn of it — the number then expires by itself after a week at the latest, and reads zero the next time you open the sleep card.

Legal basis: Art. 6(1)(a) GDPR (consent) and, because this is health data, Art. 9(2)(a) GDPR — your explicit consent, which you give in the Health Connect dialog and withdraw in the same place.

6. Premium purchase (Play version only)

When: Only if you buy “Aura Premium” or restore an earlier purchase.

Who handles the payment: Google, via Google Play Billing. Aura sees no payment data — no card number, no billing address, not your name. You provide those to Google, and Google's privacy policy applies to them.

What Aura learns: Only whether the product aura_premium_lifetime was purchased, together with the purchase token Google requires for acknowledgement. This state stays on the device and is not transmitted to any Aura service.

Restoring: On start-up the app asks Google about existing purchases, so that Premium reappears by itself after a reinstall or on a new device. No Aura account is needed — the purchase belongs to your Google account.

Gifted Premium days (as a thank-you for feedback) do not go through Google; they use the secret redemption token from section 2.

Legal basis: Art. 6(1)(b) GDPR (performance of the purchase contract).

7. Permissions and what they are for

8. Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20) and objection (Art. 21). You may withdraw consent at any time with effect for the future.

In practice: most of your data is on your device anyway — you delete it there by uninstalling the app or clearing its data. For the server-side parts (feedback, profile envelope) an informal message to the contact address is enough; please state your Aura ID (Settings → Account & Profile), otherwise your entries cannot be identified.

The individual steps are set out on the data deletion page — including which type of data sits where and how long it stays if you do nothing.

You also have the right to lodge a complaint with a supervisory authority (Art. 77 GDPR).

9. Processors

• Cloudflare, Inc. — operation of the workers and the KV storage for feedback and profile sync, and delivery of the update files.
• Norwegian Meteorological Institute (MET Norway) — weather retrieval from version 1.0.8, only with the temperature display switched on. An independent recipient, not a processor: it receives the rounded coordinates from section 5.
• Open-Meteo — weather retrieval up to version 1.0.7, likewise only with the temperature display switched on.
• Google LLC — Play version only: delivery, in-app updates, payment processing via Google Play Billing (see section 6) and (if enabled) Google Play services for QR recognition.

10. Controller and contact

Controller within the meaning of Art. 4(7) GDPR

Contact for access and erasure requests
support.aura.wecker@gmail.com

The same details appear in the legal notice.

11. Changes

Changes to this policy are announced via the store listing and in the app. The version in force carries the date shown above.