The short version: Oom has no accounts, no ads and no tracking. Your alarms, settings and mornings are stored on your phone, and we never see them. A few features have to talk to a server, and this policy names each one: linked phones and wake buddies (end-to-end encrypted, so we can’t read the messages), the streak time check, invite codes, subscriptions, app updates and, only if you turn them on, usage stats and crash reports. We don’t sell personal information, and we don’t use it for advertising.
Applies to: the Oom app for iPhone and Android, and the website oomalarm.com.
1. Who we are
Oom is published by Mohammed Al-Ayouti, an individual developer based in Cairo, Egypt, who uses the brand name Acurus. Acurus is a brand name, not a company. In this policy, “we”, “us” and “our” mean Mohammed Al-Ayouti. He is the controller of the personal information described in this policy.
Contact for any privacy question or request: support@oomalarm.com
2. What stays on your phone
These are saved on your phone only. They aren’t sent to us or to anyone else:
- your alarms: times, repeat days, labels, sounds, looks and how each one is ended (steps, NFC tag or printed QR code);
- your settings and the look of your Oom avatar;
- the random codes that pair your NFC tag or printed QR code with an alarm;
- the rings Oom has scheduled;
- your mornings, your streak, the restores you have used and saved (including extra restores from codes), pauses, and what you have earned;
- the keys and PIN for linked phones and buddies (the PIN is stored scrambled).
If your phone’s own backup is on (iCloud on iPhone, Google backup on Android), the backup may include Oom’s data. That backup is held by Apple or Google under your account with them and under their terms.
The first-open date. Oom gives you 7 free days counted from the first time you open it. To keep a reinstall from restarting those days, Oom keeps that date on your phone, and on iPhone also in the iOS Keychain, which can keep it after Oom is deleted. Oom may also read the date the store first recorded your download. None of this is sent to us.
3. Phone permissions
Oom asks for each permission only when you pick the feature that needs it. You can turn any of them off in your phone’s settings.
| Permission | Why Oom asks |
|---|---|
| Alarms (AlarmKit on iOS 26 and later) and notifications | To ring at the time you set, including when the phone is locked or silenced. Exact alarms on Android, for the same reason. |
| Motion & Fitness (iPhone) / Physical activity (Android) | To count your steps while an alarm rings, if the alarm ends with steps. The live count is used only to end the alarm. Step data isn’t saved or sent. |
| Camera | To scan your printed wake-up code while an alarm rings, if the alarm ends with a code. The image is read on the phone, then discarded. Nothing is recorded, saved or sent. |
| NFC | To write your wake-up tag and read it to end the alarm, if the alarm ends with a tag. |
Oom doesn’t use the microphone, your location, your contacts or your photos.
Wake-up tags. A tag set up by Oom holds a link like oomalarm.com/wake/<random code>. The code says nothing about you. If a phone without Oom reads the tag, it opens the link in a browser, and our website logs it like any page visit (see section 8).
4. Linked phones, wake buddies and group alarms
These features let phones exchange messages through a relay on oomalarm.com. Examples are alarms set from a Parent phone, “I’m up”, the name and avatar you choose to show, and the streak days you share. Every message is end-to-end encrypted on the sending phone, and only the receiving phone can read it. We can’t. No account is created. The phones recognize each other by keys made on the phones, and you confirm a link by comparing a 6-digit code.
The relay keeps only what it needs to deliver messages:
- encrypted messages, until the other phone collects them (at most 30 days);
- each phone’s public key;
- a scrambled fingerprint of the code each phone uses to collect its messages;
- message counters, so nothing is delivered twice;
- if notifications are allowed, the phone’s push token, so the relay can nudge it. The nudge says only that there is something new.
How long the relay keeps things: a link is deleted 400 days after it was last used, or 30 days after it was closed. A pairing code nobody used is deleted after 15 minutes. Your IP address is used in scrambled form only to limit request rates, and it is forgotten within the hour.
Reports. You can report a buddy in the app. A report holds only the connection it concerns, which side reported it, the reason and the time. It never holds a message. We review it and may close the connection. Reports are kept up to 30 days.
4a. Shared alarms and invite links
When you share an alarm or invite a friend, everything travels inside the link, after its # sign. Browsers never send that part to a server, so our website reads it in your friend’s browser and keeps nothing. A link can also carry your invite code (?r=CODE), which our server sees like any page address but doesn’t store.
Android exception: if your friend doesn’t have Oom yet and taps “Get Oom” on that page, the shared alarm (its time, days, how it ends and its label, if it has one), the invite and your code go to Google Play in the store link, so Oom can open them once installed. Google receives them as the app’s install referrer. Until Oom is in the stores the page has no store link, so nothing is passed on.
5. Your streak (time check)
So that a phone’s clock can’t decide whether a morning counts, Oom asks oomalarm.com for a signed time when you set an alarm and when you get up. This check is part of how streaks work, and it has no on/off switch. It sends:
- a fingerprint, made on your phone from that moment and a random number, which reveals nothing about the alarm;
- your time zone’s name;
- a random streak key and a scrambled number for this installation.
Nothing about your mornings is stored. We keep only which installation currently holds each streak (both scrambled), for up to 400 days after last use. Moving a streak to a new phone sends it end-to-end encrypted through the relay, which deletes it once the new phone has it.
6. Usage stats and crash reports (optional, off by default)
Both are off until you turn them on. Setup offers one “Help make Oom better” switch for both. Under Settings → Privacy they are two separate switches. With both off, Oom starts no analytics client and sends nothing.
- Usage stats are a closed list of five events: Oom was opened, setup finished, an alarm was saved (how it ends, whether it eases in, whether it is a buddy alarm), an alarm was ended (how, and how many snoozes first), and an alarm rang out without being ended. They never include a label, an alarm time or days, a name, a code or a tag.
- Crash reports include the error, phone model, system version and app version.
Both are sent with a random identifier made on your phone. It isn’t linked to a name, an email or an account. Oom never records your screen or captures your taps. Turning a switch off stops sending and clears the identifier. We ask our analytics provider to discard IP addresses.
7. Subscriptions, invite codes and updates
Subscriptions. Oom sells an optional subscription in the app (currently $29.99 a year or $7.99 a month in the US; local prices may differ). Payment is handled entirely by Apple or Google, and we never see your card details. We only learn whether you are subscribed or on the free version, and the subscription numbers.
Invite codes. You can get a personal code to share. Entering a friend’s code gives you 2 extra streak restores, and each friend who uses your code gives you 2. A code never adds free days or subscription access. Where offered, a free month can also be redeemed through Apple’s offer-code sheet. Nothing about codes is sent until you use them: the first time you open Invite or enter a code, and from then on when Oom opens, Oom sends our referral service, through oomalarm.com, your anonymous app ID, the day you first opened Oom, whether you are subscribed, the code you entered, and the rewards earned. If you never invite anyone or enter a code, none of this is sent. It isn’t linked to your name or email. Your alarms, labels and buddies are never sent. A link you share carries only your code.
Updates and ratings. Oom checks for small app updates and reads a small settings file from oomalarm.com (for example, how to apply an update). Like any connection, these requests carry your IP address. After a few alarms, Oom may show Apple’s or Google’s standard “rate this app” prompt, which the store handles; we don’t learn whether or how you rated.
8. The website (oomalarm.com)
oomalarm.com sets no cookies and runs no analytics. It counts one thing: on the NFC stickers page, each time a store link or the country search is used, it adds one to that day’s total for that link and for the visitor’s country, which our hosting provider works out from the connection. Only the totals are kept, for about a year, with nothing that could tell one visitor from another. Its hosting provider keeps standard server logs (IP address, browser, page, time) to run and secure the site. The site serves its own fonts and images, so your browser connects to no one else.
9. Service providers
These providers process data for us. Each only gets what is listed here, and their own privacy policies describe how they handle it.
| Provider | What it gets, and why |
|---|---|
| Vercel (hosting, Frankfurt) | Runs oomalarm.com and the relay, the time check, invite-code requests and the settings file. Standard server logs: IP address, browser, page, time. |
| Upstash (database) | Holds the relay data in section 4 (encrypted messages, public keys, scrambled fingerprints and push tokens) and the scrambled streak record in section 5, for the periods stated there. |
| Expo (updates and push) | App updates: the app version, platform, update channel, an installation ID that Expo creates, and your IP address. Push nudges (if notifications are allowed): your push token and a message saying only that there is something new. |
| Apple and Google (stores) | Downloads, payments, subscriptions, the rating prompt, push delivery and, on Android, the install referrer (section 4a). They hold your card details; we never do. |
| RevenueCat (subscriptions) | An anonymous app user ID it generates (not your name or email), your purchase and renewal records from Apple or Google (product, dates, store transaction IDs, country and currency), and basic device and app information. Used only to tell whether you are subscribed, and to understand subscription numbers. |
| WinWinKit (invite codes) | What section 7 lists for invite codes, sent through oomalarm.com. Never your alarms, labels or buddies. |
| PostHog (EU data center) | Only if you turn usage stats or crash reports on (section 6): the events and crash details listed there, with a random identifier. IP addresses are discarded. |
10. Email
If you write to us, we keep your message and email address to answer you, and we delete them when they are no longer needed. We don’t add you to a mailing list.
11. Legal bases (EEA/UK)
- Contract: to provide the features you use (relay, streak check, subscriptions, codes).
- Consent: usage stats and crash reports. You can withdraw consent at any time.
- Legitimate interests: keeping our services secure and working (rate limiting, server logs, reviewing reports, app updates).
- Legal obligation: where we must keep or disclose information by law.
12. Sharing, selling and transfers
We don’t sell personal information or “share” it for cross-context behavioral advertising (as those terms are used in California law). We disclose information only to the providers in section 9, which act on our behalf, or where the law requires it. They may process data outside your country, including in the EU and the United States. Where required, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses.
13. Retention
The relay, the streak record and reports are kept for the periods in sections 4 and 5. The rest:
| Data | Kept |
|---|---|
| On-device data | Until you delete it or delete the app (except the iOS Keychain first-open date, which can remain on the phone) |
| Analytics/crash data (if on) | Up to 7 years, under PostHog’s retention on our plan |
| Support email | Until no longer needed to help you |
14. Your rights
Wherever you live, you can ask us to access, correct or delete information we hold about you, or object to how we use it. Under the GDPR (EEA/UK) you also have rights to restrict processing, to data portability, and to complain to your local data protection authority. Under California law (CCPA/CPRA) you have the rights to know, delete and correct, to opt out of sale or sharing (we do neither), and not to be discriminated against for using these rights.
Most of your Oom data never reaches us, so the simplest way to control it is in the app, or by deleting the app. For anything we hold (a support email, a streak holder record, relay data), write to support@oomalarm.com. We may need a detail from the app (such as your invite code) to find the record, because we don’t know who you are.
15. Children
Oom isn’t directed to children under 13, and we don’t knowingly collect personal information from them. If you think a child has given us personal information (for example, in a support email), contact us and we will delete it.
16. Security
Messages between phones are end-to-end encrypted, and connections to our servers use TLS. No system is perfectly secure, but we keep what we store to a minimum.
17. Changes
When Oom changes what it does with information, we will update this page and the date at the top before the change reaches the app. If a change matters, we will also say so in the app.
18. Contact
Mohammed Al-Ayouti (Acurus), Cairo, Egypt
Email: support@oomalarm.com (support, privacy and legal)