Privacy Policy

Who we are

WakeSharp is published by KineticBit Inc., a small independent studio. For anything in this policy, write to support@wakesharp.app. For data-protection purposes, that is also the controller for the limited processing described below.

What WakeSharp does not do

• It does not require an account. Sign-in supports backup, restoration and purchase continuity.
• It does not collect your phone number or contacts. It holds your name only if you create the optional account: the name your sign-in provider shares, and the name you give the Lark to call you by, if you choose to. Your email address is held only if you create the optional account, because your sign-in provider discloses it (Apple can hide it behind a relay address).
• It does not collect a location route. On iPhone, optional weather uses a chosen city or a location fix rounded to two decimal places before transmission. Approximate location inferred from IP addresses is described below.
• Marketing measurement connects campaign interactions to app opens and subscription outcomes using AppsFlyer. Advertising identifiers are used only when available and permitted by your privacy choices. On iPhone, from version 2.10, the advertising identifier is read only after you allow tracking through Apple's prompt; before that version, and after a refusal, it is not read at all.
• We do not sell customer lists. Advertising and measurement may involve sharing with the providers and enabled advertising partners described below; regional privacy choices apply to that processing.

What stays on your device

Your morning data is written to a local database on your phone (SwiftData on iOS, Room on Android). The following data stays local unless you create the optional account and cloud backup described next:

• Your alarms, their times, repeat days and settings.
• Your smart-alarm rules and the wake times computed from them.
• A journal of alarms scheduled, fired, snoozed, missed or silenced by a completed mission.
• Your warm-up game results, personal baseline, daily Sharpness scores, streaks and freeze tokens.
• Your app preferences.

On Android the app declares android:allowBackup="false", so this data is not copied into Android's cloud backup. Deleting the app removes all of it. The only copy that can exist anywhere else is the one you create yourself with the optional account, described next.

The optional account and cloud backup

You can sign in with Apple or Google (those are the only options; there is no email-and-password login) to back up your WakeSharp data and restore it on a new phone. This is entirely optional, off by default, and alarms never depend on it: backup runs quietly after your data changes and can fail or be offline without affecting anything you rely on at 6am.

If you create an account, this is stored in your private backup:

• Your sign-in identity: a random account ID and the email your provider discloses (with Sign in with Apple you can hide your real address behind Apple's relay).
• Your alarms and settings: times, repeat days, labels, missions, snooze rules, smart-alarm rules and shift rotations, and your app preferences, including badge reminders and your answers to the onboarding questions that pick your missions.
• Your progress: daily Sharpness scores, streak and freeze tokens, badges, game results and personal baselines, a record of each morning your alarms rang and how it ended, your recent missions and wake-up times, and the journal of past alarms (only completed history; never diagnostics about your device, and never the calendar event a smart alarm woke you for).
• Your Lark: its stage, the items it has found, its outfit and decorations, and the name you asked it to call you by. That name is personal information: it is stored in your backup, linked to your account, and deleted with it.
• Your profile photo, if you add one: a small copy, 256 pixels on its longest side.
• Your mission references: the small thumbnail and on-device fingerprint of a spot or photo target you enrolled. The full photographs are never stored, on your device or in the cloud.

Deliberately not in the backup: your calendar events (smart rules are backed up, the events they read are not), camera frames, step counts, your finger-signature, and device diagnostics.

The backup is hosted for us by Supabase, Inc. on infrastructure in theUnited States, as our processor under their data processing terms, including standard contractual clauses where required for transfers from the UK or the EEA. Every row is protected by database-level rules that make it readable by your account and no other. Supabase's privacy policy is at supabase.com/privacy.

Your random account ID can also become your RevenueCat customer ID, linking purchase and measurement records across your devices. Your email is not sent by WakeSharp to PostHog or AppsFlyer as a marketing attribute. Signing out keeps your local data and stops account backups. Deleting the account (in the app at Settings → Account → Delete account, or as described at wakesharp.app/account/delete) permanently removes the backup and the login itself (for Sign in with Apple, the sign-in token is revoked with Apple), while the data on your phone is kept.

Calendar access: optional, read-only, and it never leaves your phone

WakeSharp can wake you a set number of minutes before your first meeting. To do that it needs to read your calendar. This is how that works:

• It is entirely optional. Decline it and every other feature still works. You just set your alarm times yourself.
• Access is read-only. WakeSharp never creates, edits or deletes an event.
• Events are read on your device, and used for one purpose: to compute the time your alarm should ring.
• Event titles, attendees, locations, notes and times are never transmitted to us or to anyone else. They are not written to any server, and they are not included in any diagnostic report.
• You can revoke calendar access at any time in your phone's system settings. The smart alarm stops adjusting; nothing else changes.

Optional weather on iPhone

From version 2.14, you can choose a city manually or allow location access to show local weather. Location permission is optional; declining it does not affect alarms, and you can use a chosen city instead. When using your location, WakeSharp requests an approximate fix and rounds latitude and longitude to two decimal places on your device before making the weather request. A chosen city uses that city's coordinates instead.

These rounded coordinates are sent to WakeSharp's weather service, hosted through Supabase, which requests the forecast from Apple Weather. Network providers also receive the IP address associated with the request. Weather location is not included in product analytics, advertising measurement, or your account backup. City and weather preferences are stored locally. You can turn weather off in the app and revoke location permission in iOS Settings. Apple's privacy policy is at apple.com/legal/privacy.

Permissions, and why each one exists

On iPhone, WakeSharp asks for:

• Alarms: so the alarm can ring loudly and reliably through Silent mode and Focus, using Apple's system alarm framework.
• Calendar: optional, read-only, for smart alarms only.
• Location: optional on iPhone for local weather. A manually selected city works without location permission. Coordinates are rounded before transmission, as described above.
• Camera: optional, only for an alarm you have set to Scan an Object, Fetch, Photo Proof, First Light, Face Check or Fruit Slash, when you enrol a target and while that mission runs. Face Check and Fruit Slash use the front camera. See the next section.
• Motion & Fitness: optional, only for an alarm you have set to a walking mission, to count the steps it asks for. See the next section.
• Microphone and Speech Recognition: optional on iPhone for spoken missions such as Name Five. Recognition is restricted to on-device processing. Audio buffers and transcripts are used only to check your answer, then discarded; they are not recorded to a file, logged, backed up or uploaded. If on-device recognition is unavailable or permission is declined, the mission offers a fallback.
• Notifications: for the optional pre-bed wind-down reminder, the reliability warning that rides with it, and the report shown when an alarm did not ring.
• Tracking: optional, from version 2.10, to measure which advert or link brought you to WakeSharp and whether it led to a trial or a subscription. It is never used to show you adverts inside WakeSharp, because there are none. Declining does not prevent alarm use or purchasing a plan.

On Android, the app's permissions include:

• INTERNET: for the subscription and analytics services described below. No alarm needs it.
• com.google.android.gms.permission.AD_ID: for permitted advertising and attribution. Deleting or restricting your advertising ID does not prevent purchasing a plan.
• USE_EXACT_ALARM: to schedule an alarm that fires at the exact minute you asked for.
• SCHEDULE_EXACT_ALARM: the same thing on Android 12 and 12L only, which predate the permission above. It is dropped from the build on Android 13 and later.
• USE_FULL_SCREEN_INTENT: to show the ringing screen over the lock screen.
• POST_NOTIFICATIONS: for the ring notification, the optional bedtime reminder, and the missed-alarm report.
• FOREGROUND_SERVICE and FOREGROUND_SERVICE_MEDIA_PLAYBACK: to keep the alarm tone playing while the alarm is ringing.
• RECEIVE_BOOT_COMPLETED: to restore your alarms after a restart, because Android discards scheduled alarms on reboot.
• READ_CALENDAR: optional, read-only, for smart alarms only.
• CAMERA: optional, for the Scan an Object, Fetch, Photo Proof, First Light, Face Check and Fruit Slash missions only. The last two use the front camera. See the next section.
• ACTIVITY_RECOGNITION: optional, for walking missions only. See the next section.
• WAKE_LOCK and VIBRATE: to wake the screen and vibrate while ringing.

The camera, its autofocus and the step counter are all declared not required, so WakeSharp still installs on a phone that has none of them. The missions that need them simply are not offered there.

The camera and your physical activity

Seven of the missions read a sensor. All of them are optional, all of them ask for permission when you set the alarm rather than at 6am, and sensor processing happens on your device. Live camera frames and step counts are not uploaded; enrolled reference thumbnails may be backed up with an optional account. Two of them, Face Check and Fruit Slash, use the front camera, which is a different thing to agree to, so they are described on their own below.

• The Scan an Object mission asks you to point the camera at one of a fixed list of everyday objects. Recognition runs entirely on your device: Apple's Vision framework on iPhone, a small model bundled with the app on Android. Frames are analysed in memory and discarded. Nothing is photographed, written to storage, added to your photo library, or transmitted to us or to anyone else. Only the names of the objects an alarm asks for are saved, on your phone, like any other alarm setting.
• The Photo Proof mission asks for one photograph. If you have enrolled a target for that alarm it asks you to retake it; otherwise it asks for the day's rotating prompt: the sky, your bed made, a glass of water, the view out a window, your kitchen counter or your front door, one prompt per morning and the same one for everyone. The photographs are not stored. Enrolling keeps a feature print, a few kilobytes of numbers that can be compared but never looked at, plus a small thumbnail for the picker row, and discards the frame itself. The morning's retake is judged against that print on your device: Apple's Vision framework on iPhone, a small bundled model on Android, held in memory for the comparison and then discarded. The morning retake is not written to your photo library or transmitted. The enrolled print and thumbnail are the mission referencesincluded in your private cloud backup if you create an optional account. Full camera frames are not backed up.
• The Fetch mission works the same way as Scan an Object, from a different pool: it names something to go and find (something blue, something you drink from) and checks it with the same on-device recognition. Frames are analysed in memory and discarded.
• The First Light mission uses the camera as a light meter. It reads how bright the scene is, nothing else: no frame is recognised, kept, written to storage or transmitted, and the only thing the mission learns is a number.
• The Face Check mission points the front camera at your own face and asks you to open your eyes, then to turn your head or lean in. It asks whether a face is present and awake, never whose. No face template is built, no frame is kept, and nothing is uploaded. The analysis runs entirely on your device (Apple's Vision framework on iPhone, a bundled model on Android), each frame is held in memory only long enough to be measured and is then discarded, and WakeSharp cannot recognise you or tell one person from another. Nothing about your face is written to storage or included in a backup. The mission records only that it was completed, the same as every other mission.
• The Fruit Slash mission also uses the front camera, pointed at yourhand rather than your face: it tracks a fingertip so you can slice at what is on screen. Hand tracking runs on your device, frames are discarded as they are measured, and nothing is photographed, stored or transmitted. If the room is too dark to see a hand, the mission says so and moves to slicing on the glass instead.
• The Walk It Off mission reads your device's own step counter, and only while that mission is running, to check that the steps it asked for actually happened. It is a count, not a route: this mission never requests your location.
• Decline any of these permissions and nothing breaks. The mission falls back to Math Problems at full credit, rather than leaving you with an alarm you cannot silence.

Purchases and WakeSharp Unlimited

WakeSharp is sold as a subscription, WakeSharp Unlimited. Trials and introductory offers can vary with the paywall shown to you, and your paywall displays the current price, trial terms and renewal period before purchase. Lifetime, a one-time purchase that does not renew, is no longer sold, and existing Lifetime purchases stay valid. Marketing measurement uses the same privacy controls regardless of which paywall is displayed.

If you buy it, the purchase itself is handled entirely by Apple or Google. We never see your card, your billing address, or your Apple or Google account details.

To know whether WakeSharp Unlimited is unlocked, WakeSharp uses RevenueCat, Inc., a subscription-management service. When you open the paywall or restore a purchase, the RevenueCat SDK sends:

RevenueCat processes this in the United States, as our processor and under their data processing terms, including standard contractual clauses where they are required for transfers from the UK or the EEA. Their own privacy policy is at revenuecat.com/privacy.

RevenueCat provides customer purchase histories and aggregate subscription reports. It forwards verified trial, purchase, renewal, cancellation, expiration and refund events to PostHog and, when an eligible AppsFlyer identifier is available, to AppsFlyer. Delivery can continue while the app is closed. Cancelling a subscription is different from receiving a refund. Payment card details are not included.

Usage analytics and session replay (PostHog)

WakeSharp uses PostHog, Inc., a product-analytics service, to understand how the app is used: which screens people visit, where onboarding is abandoned, whether the paywall is confusing. Records use pseudonymous identifiers and can be joined to subscription and campaign measurement:

What a session recording does and does not show. A recording is a series of screenshots of WakeSharp's own interface, so we can see the screens you moved through, the buttons and prices you were shown, and where you tapped. Before any frame leaves your device, these are blanked out:

• the camera viewfinder in the photo and scan missions;
• the photos you take to complete a mission, and the reference photos you save;
• anything you typed or named yourself: alarm labels, activity names, profile names, rotation and shift names, the names you give scanned spots and photo references, the name you enter for a wake pact, and your alarm search text;
• your email address, and the whole Account screen where it appears;
• the titles of your calendar events, everywhere they appear.

One exception: on iPhone, the profile menu in the alarm editor is drawn by iOS rather than by WakeSharp and cannot be blanked, so the profile names it lists can appear in a recording while that menu is open.

Fields the operating system marks as a password or as sensitive autofill are blanked automatically as well; in practice WakeSharp has no password field at all, because signing in uses Apple or Google and happens on their screens rather than ours. Recordings are deleted after 30 days.

If you would rather send none of this, turn it off in Settings → Product analytics in the app. Everything else works exactly the same with it off.

PostHog processes this in the United States, as our processor and under their data processing agreement, including standard contractual clauses where required for transfers from the UK or the EEA. Their privacy policy is at posthog.com/privacy.

We use PostHog to analyze product behavior, subscription outcomes and campaign performance. Session recordings are for diagnosing product problems. We do not send the recordings to advertising partners.

Marketing measurement (AppsFlyer)

AppsFlyer helps us understand which campaigns lead to a first app open, trial or payment. It receives app and SDK identifiers, permitted advertising identifiers, device and network information including IP-derived approximate location, campaign and deep-link context, and selected app events: a paywall view, the end of setup, and the first and third mornings you complete a mission. RevenueCat sends verified subscription events associated with the AppsFlyer ID. AppsFlyer counts first opens; a store download that is never opened is a separate measure.

Enabled advertising partners may receive conversion information under the applicable consent and platform restrictions. Apple's aggregate attribution can provide limited campaign results without an advertising identifier. AppsFlyer's processing is described in its services privacy policy. We do not send alarm content, calendar events, camera frames, contact lists or payment card details to AppsFlyer.

The optional source question records where you say you heard about WakeSharp: TikTok, Instagram, YouTube, the App Store, a friend or family member, Google search, or somewhere else. Your answer is stored on your device and attached to PostHog and RevenueCat measurement. It does not change your price or grant rewards, and it does not replace AppsFlyer's attributed campaign. Skipping it never prevents setup. Earlier versions of the app also offered an optional creator-code field; a code entered there was checked against a public, read-only creator catalog hosted by Supabase and stored the same way.

Turn off Settings → Product analytics to stop new PostHog and AppsFlyer collection from the app and clear the RevenueCat attribution identifiers used for future AppsFlyer delivery. This does not erase already delivered events or cancel billing; essential purchase validation continues. Updates made offline take effect on connected services after synchronization. You can also change Apple's tracking permission in iOS Settings and reopen the regional privacy form in WakeSharp Settings.

Advertising

WakeSharp shows no ads. Earlier versions could show banners supplied by Google AdMob on a free tier; that tier and the ad SDK were both removed in September 2026, and nothing in the app requests, loads or displays an advert. This section is about the other direction: we buy ads elsewhere, and we measure whether they work.

• What we measure. When an advert or a link brings someone to the App Store or Google Play and they install WakeSharp, our measurement provider AppsFlyer reports which campaign that install came from, and whether it later led to a trial or a subscription. That is the whole purpose: to spend less on adverts that do not work.
• What an advertising network receives. Where a network is enabled, it can receive the fact of an install and of those subscription events, with the identifiers your privacy choices permit. It never receives your alarms, your missions, your calendar, your camera frames, your Sharpness scores or anything you typed into the app.
• On iPhone, from version 2.10. Early in setup, WakeSharp explains what this measures and then iOS asks you to allow or refuse tracking. Refuse, and the advertising identifier is never read and advertising networks receive only aggregated campaign results. Either answer continues setup, and nothing about the app, its price or its features depends on your choice. You can change it at any time in Settings, Privacy & Security, Tracking. Versions before 2.10 do not ask, and do not read the identifier.
• On Android, the advertising ID is used for the same measurement where your regional privacy choices permit it. Deleting or restricting it does not prevent using or buying anything.
• In the EEA, the UK and Switzerland, and in the US states with their own privacy laws, a consent form appears before that measurement begins and records your choice. You can reopen it at any time from Settings, Privacy options inside the app. If you refuse there, iPhone does not additionally ask you about tracking.

Your setup answers

When you first set up WakeSharp it asks a handful of questions (how many alarms you set, whether you turn the alarm off and go back to sleep, how long it takes you to feel awake, how you feel right after waking) and records the choices you make on the way to your first alarm: wake time, bedtime, mission, difficulty, sound, wallpaper, and whether you allowed alarms. These answers reach our analytics service as part of the usage events described above. On iPhone they are also stored in a small table of our own, hosted for us by Supabase in the United States under the same terms as the backup. (The Android app does not send them yet.)

• Each row is keyed by a random ID created on your device for this purpose alone: not the analytics ID, not the subscription ID, and not anything derived from your name, email or device.
• It holds only answers from that fixed list of setup questions, sent through a write-only channel that accepts nothing else. Never the content of your alarms, your calendar, or anything you typed.
• Why we keep our own copy: so that if you later create the optional account, your first-day answers can be connected to it, and we can learn how the way people start relates to what they go on to do. Until you sign in (and most people never do) the row is anonymous, and nothing can read it back.
• Rows are deleted 180 days after the last answer. Deleting the optional account deletes them at once. Turning off Settings → Product analytics in the app stops them being sent at all.

The contact form on this website

This section is about wakesharp.app/contact only. The app itself never sends a message anywhere, and everything above still holds.

If you use that form, the name, email address, topic, optional device details and message you type are delivered to support@wakesharp.app as an ordinary email by Resend, the service that carries it. Submitting also triggers a single automatic confirmation email to the address you entered; its text is fixed and contains nothing from your submission. There is no database behind the form. Nothing is written to disk on our side, and your submission exists only as the resulting email in our inbox. It is kept while the correspondence is useful and then deleted; Resend holds a short-lived delivery log under its own retention policy. Because it is ordinary email and not a secure channel, please do not send anything sensitive through it.

How long data is kept, and how to delete it

• On-device data: kept until you delete it in the app or uninstall WakeSharp. Uninstalling removes all of it. Unless you created the optional account, we hold no copy, so there is nothing for us to delete.
• The optional account backup: kept until you delete the account, then removed immediately and permanently. Past history (the journal of past alarms, game results and the record of each morning your alarms rang) is deleted from the backup sooner, once it is 400 days old. To delete the account: Settings → Account → Delete account in the app, or the routes at wakesharp.app/account/delete if you no longer have it installed.
• Purchase records at RevenueCat: kept while the record exists, under RevenueCat's own retention policy.
• Your setup answers in our own table: deleted 180 days after the last answer, or at once when you delete the optional account. Turning off product analytics in the app stops new answers being sent.
• Analytics data at PostHog: usage events are kept for as long as we analyse them; session recordings are deleted after 30 days. To have your analytics record deleted, email us. If you can send it from the app's device or tell us roughly when you used the app and on what device model, we can locate the random ID and delete everything attached to it.
• Marketing records at AppsFlyer: retained according to the service's applicable retention settings and our measurement needs. Contact us to request access or deletion. Turning analytics off stops future collection; it does not itself delete historical records.
• Subscription and analytics records are pseudonymous and may link to your account. For help locating a purchase record, contact us with the store transaction and purchase date. Do not send payment card details. Account deletion, analytics deletion and store subscription cancellation are separate actions.

Cancelling a subscription is separate and is done in your App Store or Google Play account. Deleting the app does not cancel a subscription. A Lifetime purchase is not a subscription and has nothing to cancel.

Children's privacy

WakeSharp is a general-audience app and is not directed at children. Using it without an account can still involve the pseudonymous analytics, purchase and advertising data described above. We do not knowingly let children under 13 (or the equivalent age in your country) create the optional account, and we do not knowingly collect personal data from them; if you believe a child has created one, email us and we will delete it.

Your rights

Depending on where you live, the GDPR, the UK GDPR, the CCPA/CPRA and similar laws give you rights to access, correct, delete, port or object to the processing of your personal data.

You can manage local data and your optional backup in the app. Contact us about access, correction, portability or deletion of subscription, product-analytics or marketing records. We may need enough information to locate the relevant pseudonymous identifiers and verify the request. Deleting a backup does not automatically remove records held by every measurement or billing provider.

Where we do process data, our legal basis is the performance of our contract with you (validating a subscription you bought), and our legitimate interest in understanding how the app is used and in preventing payment fraud. Where consent is required for analytics, marketing measurement or advertising, we request it and respect withdrawal. You have the right to complain to your local data-protection authority.

Website tools and optional website analytics

The free sleep, caffeine, alarm and timer tools calculate in your browser. Their inputs and results are not sent to PostHog or AppsFlyer. Browser alarms require an open page and an awake device; they are not a background alarm service.

If you allow optional website analytics, PostHog receives tool usage and download-click events, a separate random website analytics identifier, the page, language, button placement and limited campaign tags. It also receives technical connection information such as your IP address. We do not enable website session replay or automatic form capture. Your website analytics identity is not joined to your app identity. You can decline or withdraw through Analytics preferences in the footer; the tools and downloads still work. Your choice and, if enabled, the analytics identifier are stored locally in your browser.

Download links use AppsFlyer to route you to the appropriate store or installed app. Clicking a link sends AppsFlyer the website campaign, originating page, placement, language and technical connection information. Where attribution is available and permitted, app installs and verified RevenueCat subscription events are associated with that campaign. A desktop QR code carries the same campaign context to your phone. Attribution is not available for every visit or install.

Security

Your data stays inside your phone's app sandbox and is protected by your device's own encryption and passcode. Traffic to RevenueCat, PostHog, AppsFlyer and the backup service uses HTTPS. No system is perfectly secure. Alarm execution does not depend on a marketing server. Backups are isolated by account access rules; subscription, analytics, marketing and setup records are held by the services described above.

Changes to this policy

If this policy changes we will update the date at the top of this page. Material changes will be described here rather than made quietly.

Contact

support@wakesharp.app, KineticBit Inc., publisher of WakeSharp.