Privacy Policy

1. Who this applies to

This policy explains how the Mornio iPhone app (“Mornio”, “we”, “us”) and the website at mornioapp.com handle information. By using Mornio you agree to this policy.

2. No account required

Mornio has no sign-up. You don’t create an account, and you don’t give us an email address or password to use the app. Because there’s no account, there’s no profile for us to hold on a server and nothing for you to “log out” of.

3. What information Mornio stores, and where

Everything below is stored locally on your iPhone, inside Mornio’s private app storage. It is not uploaded to a Mornio server (we don’t run one):

• Alarms: the time, repeat days, label, the reason you pick (for example “Work shift” or “Flight”), and your wake-check delay.
• Saved verification methods: for each QR code or barcode you register, a one-way secure check of the code plus a label you choose (for example “Bathroom mirror”). See section 4.
• Alarm history: how past mornings went (for example whether you woke on the first alarm, needed the backup, or used the emergency exit).
• Preferences: your settings and onboarding state.

4. QR and barcode (Wake Check) data

When you register a code, Mornio does not keep the camera image and does not keep the code’s readable value. Instead it saves a one-way cryptographic hash (a “fingerprint”) of the code, together with the label you typed. In the morning, Mornio hashes whatever you scan and compares fingerprints, so it can confirm you scanned the same code without ever storing the original. A hash cannot be turned back into the original code.

This data stays on your device and is removed when you delete the saved item, erase all Mornio data, or delete the app (see section 14).

5. Camera

Mornio uses the camera for one purpose only: to scan the QR code or barcode you chose, during setup and when you turn off an alarm. The camera preview is live. Mornio does not save photos or video, and does not send any images anywhere. Only the resulting one-way code check (section 4) is stored. iOS will ask for camera permission the first time; you can change it any time in the iOS Settings app.

6. Alarm and notification permissions

Mornio asks iOS for permission to schedule reliable alarms (so an alarm can sound through silent mode, Focus and a locked screen). It may also ask for notification permission to send a small number of supplementary reminders, for example a “charge your phone before your protected alarm” warning, or a heads-up that setup is incomplete. These permissions are used only to run your alarms and reminders. They don’t send any personal information to us.

7. App Group and the Live Activity widget

Mornio’s ringing-alarm widget (a Live Activity) needs to show the same alarm you set. To do that, the app and the widget share Mornio’s private on-device storage (an “App Group” container) so they read the same alarms and steps. This sharing happens entirely on your iPhone; nothing is sent off the device.

8. iCloud

Mornio does not sync your data to any Mornio account or upload it to iCloud itself. If you have iCloud Backup turned on for your iPhone, your device’s encrypted backup, which Apple manages, may include Mornio’s local data along with your other apps. That is controlled by your iOS settings and Apple’s terms, not by Mornio.

9. Purchases (handled by Apple)

Mornio Pro is sold through Apple’s in-app purchase system. When you buy or restore Pro, Apple processes the payment using your Apple Account. Mornio receives from Apple only what it needs to know whether you currently have an active Pro entitlement; we do not receive your full payment details. Apple’s handling of purchases is covered by Apple’s Privacy Policy.

10. Crash, diagnostic and usage information

Mornio includes no crash-reporting SDK. Crash information reaches us only through Apple:

• During the TestFlight beta, Apple may collect crash logs, basic performance and usage diagnostics, and any feedback you choose to submit, and may share crash/diagnostic data with us, under Apple’s TestFlight terms.
• On the App Store, if you have turned on “Share With App Developers” (or the equivalent analytics sharing) in iOS settings, Apple may give us aggregated, non-identifying crash and diagnostic reports.

This information comes from Apple, not from tracking code inside Mornio, and helps us fix bugs and crashes.

Separately, since version 1.0.1 Mornio sends pseudonymous usage events to TelemetryDeck (TelemetryDeck GmbH, Germany, an EU-hosted privacy-first analytics service) so we can see how many people reach each step of the app: for example “onboarding completed”, “alarm scheduled”, “scan succeeded”, “stay-awake check completed” or “paywall viewed”. Some of these events also include your App Store country (the country of your Apple Account, for example “USA”, as reported by Apple, not your device’s location), which screen a purchase was started from and how a purchase attempt ended (for example, cancelled or pending), and, when a purchase completes, which plan was bought and its price and currency, whether camera access was allowed when the scanner was needed, how an alarm setup screen was left (saved, cancelled, or the app was closed) and roughly how long it was open, and, only if you choose to answer the optional “Where did you hear about Mornio?” question during setup, the option you picked.

Since version 1.0.11, some events also record:

• which plan you selected on the paywall, and whether its prices loaded;
• how a Restore Purchases ended (for example, restored or nothing to restore);
• for a completed purchase, the App Store country it was made in, and whether it was a real App Store purchase or a test purchase (TestFlight, App Review or developer testing), so test purchases can be left out of our figures;
• whether you skipped the setup questions, and from which screen. If you skip them, Mornio also records which of two versions of the next step you were randomly shown (straight to the permissions screen, or the optional Pro screen first) so we can compare them; which version you got is stored only on your iPhone;
• when an alarm is switched on or off or deleted, and why, as a fixed category (for example, by you, or automatically after a one-time alarm’s morning);
• an alarm’s repeat pattern (for example “weekdays”) and how far ahead it rings in broad ranges (for example “6–12 hours”), never the time itself;
• how a morning ended (for example, woke up, emergency stop, or missed), with the number of restarts and the minutes until the first scan in broad ranges;
• roughly how many times an alarm was stopped from the lock screen without opening the app (counted on your iPhone and reported the next time you open Mornio);
• that the scanner refused a code because it was the wrong item or a duplicate, never the code itself.

The pseudonymous device identifier. Each event carries a code for your device so we can count how many different devices reach each step and see the steps one device went through (for example, whether a device that saw the Pro screen later bought Pro). Before anything leaves your iPhone, the TelemetryDeck code inside the app turns Apple’s “identifier for vendor” (an ID Apple gives Mornio for your iPhone, different from the one other developers’ apps see) into a one-way SHA-256 hash, and only that hash is sent. It is not your name, Apple Account, phone number or advertising identifier, and it is not combined with data from other companies. Apple resets it when you delete Mornio (and any other apps from the same developer) and install it again.

Standard technical details. TelemetryDeck also adds the same technical details to every event: Mornio’s version and build; your iPhone model, iOS version, screen size and orientation; your language, region and time-zone settings and the local hour and day of the event; whether the app came from the App Store or TestFlight; display and accessibility settings (such as dark mode, text size or Reduce Motion); and simple usage counters (the date you first opened Mornio, how many sessions and days you have used it, and average session length).

We use this only to understand how the app is used, improve it, and see which channels bring people to Mornio. It is never used for advertising or shared with advertisers. These events are not linked to your identity and are not used to track you across apps or websites. They contain no name, no email, no account, no advertising identifier and no GPS or other location data, and never the contents or hashes of your QR codes or barcodes, your alarm times, labels, wake messages or history, or any purchase transaction number. Its privacy policy is at telemetrydeck.com/privacy.

11. Support emails

If you email us at support@mornioapp.com, we receive your email address and whatever you include in the message, and use it only to respond to you. Please do not include the actual contents of your private QR codes or barcodes in a support message.

12. Third-party services we actually use

For the Mornio iPhone app, the third parties involved are Apple (its alarm system AlarmKit, its in-app purchase system StoreKit, and, if applicable, the TestFlight/App Store crash and diagnostics described above) and TelemetryDeck, which receives only the pseudonymous usage events described in section 10. The app contains no advertising networks, no social-login providers, and no third-party trackers.

The Mornio website (mornioapp.com) is hosted on Vercel, which serves the pages and, like any web host, processes standard technical request information (such as IP address and browser type) needed to deliver the site. The website also uses Vercel Web Analytics to understand aggregate traffic, for example which pages are popular and roughly how many people visit. This analytics is privacy-friendly: it does not set cookies, does not store your IP address, does not build an advertising profile, and does not track you across other websites. It runs only on the website, never inside the app. On the free tools at mornioapp.com/tools it also records an anonymous count of interactions — that a calculation was run, that a QR code was generated or downloaded, that the checklist was completed, or that an App Store button was tapped and which page it was tapped from. These events record the action only, never the content: your shift times, your chosen label and the code you generate stay in your browser and are never transmitted. For details on how Vercel processes this data, see Vercel’s Privacy Policy.

On the homepage, we also count App Store button taps by button position and page version, and whether the walkthrough was played. Events include only these fixed labels and a broad “iPhone” or “other” browser category, not the full browser identifier. To count a first button tap within a visit, the page uses browser-tab session storage containing a page-version label, a last-activity time, and a yes/no value. No unique visitor identifier is created, and the local time is not transmitted. This count starts again after 30 minutes without a homepage visit or button interaction. If session storage is unavailable, these paired visit counts are omitted. Homepage custom events respect Global Privacy Control and Do Not Track signals. A website button tap does not tell us whether you installed the app; Apple supplies separate, aggregate campaign reporting.

On the guides, free tools, blog and Wake School pages, each App Store button tap is also counted with TelemetryDeck, the same EU-hosted service the app uses, in a separate website project. The count records the page the button was on, which button it was, the first page of your visit, a broad category for where the visit came from (such as “google”, “social” or “direct”, never the full address you came from), and the campaign label already in the App Store link. It sets no cookies and uses one fixed label in place of a visitor identifier, so visitors cannot be told apart. The first page and its source category are kept in browser-tab session storage for the visit. These taps, like the other website button counts, are not recorded when Global Privacy Control or Do Not Track is on.

13. No tracking, no ads, no selling data

Mornio does not track you across other apps or websites, does not show advertising, and does not sell or share your personal information for advertising. Mornio does not use your location. The app’s pseudonymous usage events (section 10) and the website’s privacy-friendly analytics (section 12) are used only to measure how the app and site are used; neither identifies who you are, builds an advertising profile, nor follows you across other apps or sites.

14. Data retention and how to delete your data

Your on-device data stays until you remove it. You can:

• Delete an individual alarm or a saved verification method inside the app; or
• Open Mornio’s Settings → Erase all Mornio data to permanently delete your alarms, saved verification methods, alarm history and preferences on that iPhone; or
• Delete the Mornio app, which removes its local data from your device.

Because Mornio has no account, there is no separate account to delete. Note that erasing your local data does not cancel an Apple subscription. Manage that in the iOS Settings app under your Apple Account. Purchase records and any Apple-side diagnostics follow Apple’s own retention policies.

15. Children’s privacy

Mornio is a general-audience productivity app and is not directed to children, and we do not knowingly collect personal information from children. If you believe a child has sent us personal information through a support email, contact us and we will delete it.

16. Security

Mornio’s data is held in the app’s private, sandboxed storage on your device and benefits from iOS device encryption when your iPhone has a passcode. Registered codes are stored only as one-way hashes (section 4), not as readable values. Because there is no Mornio server holding your alarms, there is no central database for an attacker to breach. No method of storage is ever 100% secure, but Mornio is designed to keep your information on your own device.

17. International users

Mornio stores your information on your own device, wherever you are located; we do not move your alarm data across borders because we don’t operate servers that hold it. Apple processes purchases and any diagnostics under its own global terms. Depending on where you live, you may have rights under local data-protection laws such as the EU/UK GDPR or California’s CCPA/CPRA. Because Mornio keeps your data on your device and holds no personal data on its own servers, you can exercise the heart of those rights yourself: viewing, correcting and deleting your information directly in the app (see section 14). For data Apple processes, please refer to Apple.

18. Changes to this policy

We may update this policy as Mornio evolves. When we do, we’ll change the “Last updated” date above, and for significant changes we’ll make the update reasonably noticeable in the app or on this page.

19. Contact

Questions about this policy, or a request about your data? Email support@mornioapp.com and we’ll help.