Alarmly Privacy Policy

Introduction

Alarmly is published by Artifocial ("we," "our," or "us"). We are committed to protecting your privacy and ensuring transparency about how we handle your data.

This Privacy Policy explains what information Alarmly collects, how we use it, how we store it, and your rights regarding your data. Alarmly is designed with privacy-first principles: everything you create in the app — your alarms, your Assistant conversations, your voice — is stored and processed locally on your device. Separately, the app measures usage so we can tell which features actually help people wake up; that is described in full under "Usage Analytics" below, and you can switch it off.

Information We Collect

Data You Provide

Alarmly stores the following information that you directly provide, entirely on your device:

• Alarm Data: Alarm times, labels, sounds, volume, and repeat schedules
• User Preferences: Personality mode (Nice, Mean, Adaptive), voice settings, and consent preferences
• Chat History: Messages you send to the Assistant, transcribed and answered locally

Data We Do NOT Collect

Alarmly does NOT collect:

• Personal identification information (name, email, phone number)
• Location data
• The content of your alarms (labels and times), your Assistant messages, or your voice
• Advertising identifiers (IDFA) or cross-app tracking identifiers
• Contacts, photos, or financial information

How We Use Your Information

The data you create is used solelyto provide the app's core functionality — scheduling and triggering alarms, sending notifications, generating briefings, and powering the Assistant. That processing happens locally on your device. Voice input is transcribed and speech is synthesized using your device's built-in capabilities; audio is never uploaded. The only data that leaves your device is the usage analytics described below and the feedback you choose to send (see "Voluntary Feedback"). Reading this page, or using the Alarmly Web app, also records a page view — see "This website" below.

Usage Analytics

Starting with version 1.1, Alarmly measures how the app is used — not what you put in it. We do this to see which features genuinely help people get up, and whether people keep using the app after the first week. Analytics are processed by PostHog, on servers in the United States.

What is recorded: product events and a few coarse properties attached to them.

• Events: app opened, first run, notification permission prompted and its result, alarm created, alarm fired, alarm dismissed, alarm snoozed, wake-check started / passed / re-prompted, and briefing played.
• Properties: your total number of alarms, snooze counts, how many re-prompts a wake-check took and how many seconds it took you to wake, the personality mode in use (Nice / Mean / Adaptive), whether an alarm was a snooze, and the permission result.
• Attached to every event:your install week as a cohort label (for example "2026-W32"), the app version, the platform (iOS or Android), and a coarse bucket for how you found Alarmly (content, organic search, referral, paid, direct, or unknown).

A per-install identifier: to measure whether people keep using the app — which is the whole reason the analytics exist — events carry a random identifier that is created on first launch and stored on your device. It is not your name, your Apple ID, or an advertising identifier; it is not shared with other apps or with anyone other than our product-analytics processor; and deleting the app discards it. It is also why, further down, we say we generallycannot single out one person's events: events from a single install hang together, even though nothing in them says who you are.

What is never recorded: your alarm labels or alarm times, the text of your Assistant conversations, any voice audio or transcript, your name, email, phone number, location, contacts, photos, or financial information. Nothing in an event says who you are — there is no account system, so we cannot look up an event by your name, email or Apple ID. What an event does carry is the per-install identifier described above, which is why we say we generally cannot connect events back to a person rather than claiming we never can.

How to turn it off: open Settings → Privacyin the app and switch off analytics. The change takes effect immediately, is remembered, and nothing further is sent. The app works exactly the same with analytics off. That switch covers the app's product events described above. It does not cover the website measurement described next, which is a separate thing with a separate processor.

This website

Everything above is about the Alarmly app. Separately, the artifocial.com website uses Vercel Web Analytics for aggregate page-view measurement. It runs on every page of the site — including the Alarmly Web app, the Alarmly marketing page, and this privacy page — so simply reading this sentence has already recorded one page view. It is cookieless — nothing is stored on your device and nothing follows you to other sites. Vercel does distinguish one visitor from another for up to 24 hours, using a hash it derives from the incoming request; we never see that hash, and Vercel discards it after 24 hours. Each page view also includes the page URL, referrer, filtered query parameters, timestamp, coarse location (country, region and city), browser, operating system and device type.

There is no off switch for this one.The Settings → Privacy toggle lives in the iPhone app and stops the PostHog product events only; it has no effect on the website, and the website has no toggle of its own. If you would rather not be counted at all, a content or script blocker will stop it, as will not visiting the site.

The app also contains dormant events for a future paid tier (paywall viewed, trial started, subscription started, subscription cancelled). Alarmly has no paid tier today, so these never fire.

Voluntary Feedback

The Alarmly Web app (artifocial.com/apps/alarmly/web) includes an optional feedback form. The iPhone app does not — it has no feedback form and no contact form of any kind. If — and only if — you use the web form, what is transmitted to Formspree, a third-party form processor, is the message you typed, the personality mode you have selected, a label saying the message came from the Alarmly Web app, and the time you sent it — solely so we can read and answer it. Your alarms and your Assistant conversation are not attached.

To be exact about what leaves your device on iPhone, because an earlier version of this policy was not: usage analytics are sent unless you switch them off in Settings → Privacy, and that is the only thing the iPhone app transmits. There is no feedback form there to avoid using.

How We Store Your Information

Local Storage Only

All data is stored locally on your device using platform-specific storage:

• iOS: UserDefaults and local file system
• Android: SharedPreferences and local file system
• Web: Browser LocalStorage and IndexedDB

What this means:

• ✅ Your alarms, Assistant conversations and voice never leave your device
• ✅ We cannot read your alarms or your conversations
• ✅ Your content is not backed up to our servers
• ✅ From the app, the only things that leave your device are usage analytics (switchable off) and feedback you voluntarily submit. From the website, a cookieless page view is also recorded

Permissions We Request

• Notifications (required): to trigger alarms and wake you up. We do not read your other notifications.
• Microphone (optional): to enable voice input when you press the microphone button. Voice is transcribed locally; audio is not recorded in the background or stored.

Revoking Permissions

You can revoke any permission at any time through your device settings:

• iOS:Settings → scroll to "Alarmly" → toggle off any permission.
• Android:Settings → Apps → Alarmly → Permissions → toggle off any permission.

Revoking a permission may limit what the app can do — with notifications turned off, for example, alarms cannot fire.

Data Sharing and Third Parties

Alarmly does NOT sell your data or provide it to advertising networks or data brokers. Three service providers process data on our behalf, and only for the purposes described above:

• PostHog— product analytics (United States). Receives the usage events listed under "Usage Analytics", and nothing else. Switch it off in Settings → Privacy.
• Formspree — voluntary feedback from the Web app only. Receives your message, your selected personality mode, a label identifying the Alarmly Web app, and the time you sent it, and only when you choose to submit the form. The iPhone app never contacts Formspree.
• Vercel— hosting for artifocial.com, and cookieless page-view analytics for the website (see "This website" above). Receives the page-view details listed there whenever you load a page on the site, including the Alarmly Web app and this page. It receives nothing from the iPhone app, which never contacts it.

On iPhone, if you switch analytics off and never send feedback, nothing is transmitted off your device at all. On the website that is not true: page views are measured with no per-visitor off switch, as described above.

Your Data Rights

Everything you create is stored locally on your device and can be viewed and edited within the app. To delete it all, simply uninstall the app — this permanently removes all Alarmly data from your device.

Usage analytics carry no name, email or account, so we generally cannot look up or export "your" analytics records. You can stop collection at any time in Settings → Privacy, or email us at info@artifocial.com with any analytics question.

Data Retention

• Data on your device is kept indefinitely, until you delete it. You control retention yourself by managing alarms, clearing chat history, or uninstalling the app.
• We have no access to your on-device data, so we cannot delete it remotely on your behalf.
• Usage analytics are held by our analytics processor, PostHog. Because those events carry no name, email or account, we generally cannot single out and delete one person's events; switching analytics off in Settings → Privacy stops any further events from being sent.
• How long analytics events are kept:these events leave your device, so you are owed a storage period for them and not just a way to stop future collection. They are kept for as long as our analytics plan with PostHog retains event data. We have not configured a shorter period, and we hold no separate copy — we do not export, archive, or back up analytics events anywhere outside PostHog — so an event's life ends when PostHog's retention window for our project ends. When we can state that window as a specific period, we will publish the number here in place of this sentence.
• Website page views are held by Vercel. Its request-derived visitor hash expires after 24 hours and is never shown to us. We see page-view metrics and the coarse dimensions listed above, but have no account, name, email address or persistent identifier with which to look up, export or delete one visitor's records.
• The bullets above cover everything Alarmly collects today, including the analytics that already leave your device. If a future version adds a new category of data — cloud sync, or an account, for example — we will state its retention period here before we begin collecting it, and you will be able to request deletion.

Privacy Choices

Depending on where you live and which law applies, you may have additional rights. We will review privacy requests, verify them when necessary, and respond within the period required by applicable law. Our current commercial launch scope is the United States; making this policy available elsewhere is not a representation that Alarmly is actively marketed in every jurisdiction.

• Access: view the content stored locally in the app.
• Correction: edit locally stored alarms and preferences in the app.
• Deletion: delete individual content or uninstall the app to remove its local data.
• Analytics choice: switch off analytics in Settings → Privacy; the app continues to work.

We do not sell your personal information. Usage analytics are collected on the basis of our legitimate interest in improving the app, and you can withdraw from that collection at any time using the toggle above.

Children's Privacy

Alarmly is not directed to children under the age of 13. We do not knowingly collect personal information from children under 13.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by updating the "Last Updated" date at the top of this policy.

Contact Us

If you have questions about this Privacy Policy, please contact us at: info@artifocial.com(subject: "Alarmly Privacy Inquiry"). Alarmly is published by Artifocial; a registered mailing address is available on request.