<!-- Markdown mirror of https://wakeify.app/privacy. Generated from the HTML; the page is the source of truth. -->

# Wakeify Privacy Policy

Wakeify is a free music alarm clock app for iPhone and iPad that wakes you up to any song, album, artist or playlist from Spotify or Apple Music.

Last updated 2 August 2026 · Applies to the Wakeify app for iPhone and iPad, and to the website wakeify.app.

The short version: Wakeify has no accounts and no server of its own. Your alarms, your chosen songs and your streaming logins stay on your device. The only thing that ever leaves it is anonymous usage and crash statistics, and there is a switch in the app's Settings that turns those off.

Wakeify is made by **Yuval Fatal**, an independent developer. In this policy, "Wakeify", "the app", "we" and "I" all refer to that one person. If anything here is unclear, write to [support@wakeify.app](mailto:support@wakeify.app) and it will get answered.

## 1. No account, and no data of yours on our servers

Wakeify does not ask you to register. There is no username, no password, no email address and no profile. We do not operate a backend that stores your content, and we never receive your name, email address, phone number, contacts, photos, location, health data or calendar.

## 2. What stays on your device

All of the following is stored locally in the app's own container and is never uploaded to us:

- **Your alarms**: times, repeat days, labels, snooze settings and which song is attached to each one.
- **The sound each alarm uses**, so it can ring with no connection. It is private to this app.
- **Your Spotify login token**. See the next section.
- **App preferences**, such as the 24-hour clock switch, whether you have finished onboarding, and your analytics choice.
- **A random install identifier**, a randomly generated value created the first time the app runs. It is not derived from your device or from you, it is not linked to any account, and it is never transmitted anywhere: it exists so the app can recognise its own storage. (Firebase keeps a separate identifier of its own, described in section 4.)

Deleting the app removes all of it. Nothing is backed up to a Wakeify server, because there isn't one.

## 3. Connecting Spotify and Apple Music

### Spotify

Connecting Spotify opens Spotify's own login page in a secure system browser sheet. Wakeify never sees your Spotify password. Spotify returns an access token and a refresh token, which Wakeify stores in the **iOS Keychain** (the encrypted, hardware-protected store iOS provides for secrets) as a private item readable only by this app, and only after the device has been unlocked at least once since it was powered on. On the rare build where iOS refuses the Keychain, they fall back to a file in the app's own container written with full file protection, so it is encrypted at rest and unreadable while the device is locked.

Those tokens are sent only to Spotify's own servers, and never to us or to anyone else. Tapping **Disconnect** in Wakeify's Settings deletes them from the Keychain immediately.

### Apple Music

Apple Music access is handled by Apple, through iOS's own permission prompt. Wakeify does not store an Apple Music credential of any kind; iOS holds the authorisation and Wakeify only asks whether it has been granted. You can revoke it at any time in **iOS Settings → Privacy & Security → Media & Apple Music**.

### Searching

What you type into the search field goes to whichever service's tab you are on, Apple Music to Apple and Spotify to Spotify, because that is the only way to get results back. It is not sent to us, and it is not recorded in analytics.

### Setting an alarm

Saving an alarm sends the title and artist of the item you picked to Apple, and nothing else: no identifier, no account, no device information beyond what any ordinary web request carries. When the picker has nothing to show yet it also asks Apple for its public "most played" charts, which takes only your **storefront country** from the device region, and nothing about you.

## 4. Analytics in the app

Wakeify uses **Google Analytics for Firebase** (Firebase Analytics) to understand which features get used and whether the app is crashing. This is the only third-party analytics tool in the app, and none of it is linked to an identity, because there is no identity to link it to. Apple's App Store privacy label for Wakeify declares **Usage Data** under **Data Not Linked to You**; the app also sends the crash and performance diagnostics listed below, which Apple classes as *Diagnostics*.

### What is sent

An event name plus a handful of non-identifying parameters. The complete list:

| Event | Sent when | Parameters |
|---|---|---|
| app_opened | The app is launched or returns to the foreground | none |
| onboarding_completed | You finish the first-run setup | none |
| service_connected; service_disconnected | You connect or disconnect a music service | which service (Apple Music or Spotify) |
| alarm_created; alarm_edited; alarm_deleted; alarm_enabled_changed; alarm_fired | You add, change, delete or toggle an alarm, or one goes off | which service the sound came from; whether Full Song, repeat and snooze are on; whether the alarm is enabled |
| sound_previewed | You tap play to hear a result | the kind of item (song, album, artist or playlist) |
| full_song_armed | A Full Song alarm is armed | which service |
| language_changed | You pick a display language in Settings | the language code you chose (for example `fr-FR`) |
| wake_succeeded | You tap Stop on a ringing alarm, the signal that a wake-up actually worked | how many times that has now happened on this install (a running count, no dates) |
| review_prompt_shown | The "rate Wakeify" prompt is shown | none |
| paywall_shown; paywall_dismissed; purchase_started; purchase_completed; purchase_failed; purchases_restored | Purchase screens. Currently dormant: the app is free and shows no paywall | which screen it opened from; the App Store product identifier; an error reason |
| metrics_report | iOS delivers its daily performance summary | peak memory in megabytes; number of foreground launches |
| diagnostic_crash; diagnostic_hang; diagnostic_cpu_exception; diagnostic_disk_write_exception | iOS reports a crash, freeze or resource problem | exception type, signal and termination reason; duration in seconds; CPU seconds; megabytes written |

### What Firebase adds by itself

Firebase attaches a small amount of standard context to every event, and records a few events of its own (a first open, a session start, an app update). We do not choose this and cannot switch individual pieces off, only the whole thing, with the switch described below. It is:

- the **device model**, the **iOS version** and the **Wakeify version**;
- the device **language and region**;
- an **approximate location**, usually no finer than a city, that Google derives from the IP address the request arrived on. Wakeify never asks iOS for your location and has no location permission;
- a randomly generated **app instance identifier**, plus Apple's per-vendor device identifier (IDFV), so separate events can be recognised as coming from the same copy of the app.

### What is never sent

Song titles, artist names, album or playlist names, your music library, your search terms, your alarm times, your alarm labels, your Spotify or Apple ID, your name, your email address, your contacts, your precise location, your photos, and the contents of anything you type.

### Identifiers, and what is not one

The app instance identifier is not your Apple ID, is not tied to a name or an email address, and is reset if you delete and reinstall the app. Wakeify shows **no ads** and contains **no ad network**; it never requests the advertising identifier (IDFA), never shows an App Tracking Transparency prompt, and does not track you across other companies' apps or websites. Because it never asks for tracking permission, iOS keeps the IDFA unreadable to it regardless.

### Turning it off

Open Wakeify → **Settings** → **Privacy** and switch **Share Usage Analytics** off. That stops the app from recording events and also disables Firebase's own collection. It takes effect immediately and the setting persists. Nothing in the app stops working when you turn it off.

## 5. Analytics on this website

wakeify.app uses **Google Analytics 4** (the web side of the same Firebase project) to count visits and to see which download link people use. It is deliberately configured to be as minimal as a hosted analytics tool can be:

- IP addresses are not stored. Google Analytics 4 uses the IP only to work out a coarse location and then discards it, and the tag additionally sets `anonymize_ip`.
- Google Signals and advertising personalisation are switched off, so this site feeds no ad audiences.
- If your browser sends **Do Not Track** or **Global Privacy Control**, the analytics script is never loaded and nothing at all is recorded.
- Beyond the automatic page view, the only events recorded are: which App Store button was clicked (with the part of the page it sits in), which FAQ question was opened, and which outbound link was followed, that last one carrying the link's address, its host, and the first 80 characters of its visible text.
- Google Analytics also records the usual page-view context of any web analytics: the page address and title, the referring page, your browser and operating system, your screen size and language, and a coarse location from the IP.

Being honest about cookies: when it does run, Google Analytics sets first-party cookies (names beginning `_ga`) in your browser so that repeat visits are not counted twice. There are no advertising cookies, no third-party tracking pixels, no social widgets and no embedded fonts or scripts from anyone other than Google Analytics. You can block or clear these cookies in your browser at any time without affecting the site.

## 6. Purchases

Wakeify is currently free and presents no purchase screen. If in-app purchases return, they are processed entirely by Apple through the App Store. Apple does not give us your payment details, billing address or Apple ID. The app only ever learns whether a purchase is active, and it stores that answer on your device.

## 7. Other companies whose services the app touches

When you use those parts of Wakeify, your data is handled by these companies under their own privacy policies, which we do not control:

- **Apple**: App Store distribution, Apple Music, the Apple services described in section 3, and crash and performance diagnostics. [Apple Privacy Policy](https://www.apple.com/legal/privacy/)
- **Spotify**: only if you choose to connect it. [Spotify Privacy Policy](https://www.spotify.com/legal/privacy-policy/)
- **Google**: Firebase Analytics in the app and Google Analytics on this site. [Google Privacy Policy](https://policies.google.com/privacy)
- **Firebase Hosting** serves this website; its server logs may briefly record request data such as IP address, as any web server does.

These providers operate globally, so the anonymous statistics described above may be processed on servers outside your country, including in the United States.

## 8. How long anything is kept

Data on your device stays until you delete it or delete the app. Anonymous analytics events are retained by Google under the retention period configured for the Firebase project, after which they are deleted automatically. There is no separate archive anywhere else.

## 9. Your choices and your rights

- **Stop analytics**: the Settings switch in the app; Do Not Track or Global Privacy Control in your browser for the website.
- **Delete a music connection**: Settings → Music Services → Disconnect. You can also revoke Wakeify from your [Spotify apps page](https://www.spotify.com/account/apps/) and in iOS Settings for Apple Music.
- **Delete everything**: delete the app. Alarms, their sounds, tokens and preferences go with it.
- **Access, correction, erasure, portability, objection**: if you are in the EU, the UK, California or another region with data rights, you can exercise them by writing to [support@wakeify.app](mailto:support@wakeify.app). In practice there is usually nothing to hand over: the analytics data is not linked to you, so it cannot be searched for "your" records. Where that is the case we will say so plainly rather than pretend otherwise.

Where the GDPR applies, the lawful basis for the anonymous usage statistics is legitimate interest (keeping a small app working and knowing which features are worth maintaining) and you can object to it at any time with the switch in Settings. We do not sell or share personal information as those terms are defined by the California Consumer Privacy Act, and we have never done so.

## 10. Children

Wakeify is a general-audience alarm clock. It is not directed at children under 13 and we do not knowingly collect personal information from them. If you believe a child has provided personal information, contact [support@wakeify.app](mailto:support@wakeify.app) and it will be removed.

## 11. Security

Streaming tokens are held in the iOS Keychain. Network requests use HTTPS. Because there is no Wakeify account and no Wakeify server, there is no central database of users to breach. The realistic risk to your data is physical access to an unlocked device, so use a passcode.

## 12. Changes to this policy

If this policy changes in a way that affects what is collected, the date at the top will change and the app's release notes will mention it. Material changes will not be applied retroactively to data already collected.

## 13. Contact

Yuval Fatal, [support@wakeify.app](mailto:support@wakeify.app)
Questions about the app itself are answered on the [support page](https://wakeify.app/support).
