Privacy Policy

1. Introduction

Welcome to PushClock. PushClock is operated by PushClock LLC ("we," "our," or "us"), a United States company, which is the data controller responsible for the personal information described in this policy. The PushClock app is currently published on the App Store and Google Play through the developer account of an affiliated company, Kaizen Technologies LLC, which is why that name may appear as the seller or developer on the app's store listing. PushClock is a fitness-alarm application that combines push-up detection with alarm clock functionality, offers optional sleep insights based on Apple Health data, and includes optional community features: Wake Squads, small invite-only groups whose members can see whether each other got up in the morning. We are committed to protecting your personal information and your right to privacy.

This Privacy Policy explains what information we collect, how we use it, what we share with third parties (including advertising, attribution, and backend service partners), and what rights you have in relation to it. Please read it carefully. If you disagree with its terms, please discontinue use of the app.

2. Information We Collect

2.1 Information You Provide Directly

• Account Information: Creating a PushClock account is optional: the alarm and mission features work without one. An account exists so that your alarms and progress can be backed up and restored on a new device, so that you can join a Wake Squad, and so that you can save Mission Memories if you choose to (see Section 4.3). We authenticate you using Sign in with Apple or Sign in with Google on iOS, and Sign in with Google on Android; an account created with Apple cannot currently be used to sign in on Android. The provider gives us an opaque user identifier and an email address (with Apple, this may be a privacy relay address that hides your real email). We store this authentication record through our backend provider, and we also send your email address to our analytics provider as a property of your analytics profile (see Section 11). PushClock does not create or store passwords. On iOS, Apple's sign-in prompt also offers to share your name with us; we neither read nor retain it.
• Profile: A display name (up to 30 characters) and an optional avatar photo that you select from your device's photo library. You are asked to choose a display name at the point you create or join a Wake Squad, not when you sign in. Your display name and avatar are visible to the other members of any squad you join (see Section 5.2), and avatar image files are stored at publicly accessible URLs; see Section 5.2 for what that means in practice.
• Alarm Preferences: Alarm times, snooze settings, push-up goals, and other configuration data you set within the app. If you are signed in to an account, this configuration is included in the account backup described in Section 2.2. Separately, on iOS, some of your alarm settings are included in the alarm diagnostics described in Section 2.2, whether or not you are signed in.
• Fitness Goals: Push-up targets or custom workout goals you configure per alarm.
• Onboarding Questionnaire Responses: During onboarding, the app asks you a series of demographic and behavioral questions, including your age range (the options include a 13–17 bracket), your gender, and self-reported habits such as your typical sleep, mood, and wake-up patterns. Your answers are sent to our analytics provider, both as events and as user properties tied to a pseudonymous analytics identifier, to help us understand our audience and improve the app. These answers are not published on the leaderboard. See Section 6 and Section 11 for how our analytics provider processes this data.
• Referral Information: PushClock includes a referral program. If you enter or share a referral code, we record that code and link it to a referral record in our backend, associated with a pseudonymous analytics identifier, so we can attribute referrals and credit any rewards.
• Wake Squad Information: If you create or join a Wake Squad, we store the squad's name and emoji, who created it, the list of its members and the date each member joined, and the invite codes generated for it. Invite codes are short alphanumeric strings that expire after seven days and can be redeemed a limited number of times. A squad is limited to eight members, and you can belong to at most three squads.
• Moderation Reports: If you report another user, we collect the reason category you select (such as inappropriate name, inappropriate photo, impersonation, or spam/abuse) and an optional free-text note you choose to include.

2.2 Information Collected Automatically

• Camera Data (pose detection, on-device): For push-up counting and exercise form, PushClock uses your device camera for real-time pose detection that runs entirely on your device. Pose detection itself does not save, transmit, or share any video or images, and no frame is sent off your device for it. Recording a video of your mission is a separate feature, described in the next two items and in Section 4.3.
• Mission Recordings (Record My Missions, on-device): While you complete a wake-up mission, PushClock records a video of it. This setting, Record My Missions, is on by default, and you can turn it off in Settings. Camera missions (such as push-ups and squats) record the front camera. Photo missions record the back camera with a small picture-in-picture view from the front camera, which shows your face. Missions that do not use the camera record the mission screen, with a small front-camera selfie view added. Voice missions (such as reading aloud or tongue twisters) are not recorded. Recordings are silent: no microphone audio is recorded. A single recording is limited to 4 minutes. The video stays on your device. After the mission the app plays it back and offers to share it, and it leaves your device only if you choose to share or save it. Unless you share it, save it, or keep it as a Mission Memory, the recording is deleted automatically. See Section 4.3.
• Mission Memories (optional, off by default, uploaded): If you turn on Save to Memories (in Settings, next to Record My Missions, or when the app offers it once on the screen shown after a mission), PushClock keeps one "memory" for each day: the first alarm you complete on each calendar day in your local time. A memory is that mission's recording, sped up if needed to fit 60 seconds and re-encoded at a reduced resolution (540 pixels wide) with no audio, plus one still image taken from it. Both files are uploaded to our backend provider, into private storage tied to your account. With each memory we store the date and your time zone, when you completed the alarm, the alarm's set time and name, which missions you completed and how long they took, your streak day count, and the clip's duration, pixel size and file sizes, and your device's platform (iOS or Android). Save to Memories requires a PushClock account; turning it on while signed out asks you to sign in. See Section 4.3.
• Photos (verification missions, processed off-device): Certain optional alarm-dismissal missions ask you to take a photo, for example a made bed, the sky, grass/outdoors, a sketch, a specific object, a selfie recreating a reference image, or a custom "Snap This" photo. To check whether the photo satisfies the mission, the single image is transmitted through our backend to an automated AI vision service (Anthropic's Claude API) for analysis. Depending on the mission, the photo may include your face, body, or images of your home, bed, or surroundings. The image is used only to return a pass/fail result and a short reason; it is not stored or retained on PushClock's own systems (including our backend) and is not added to any profile. Once transmitted to Anthropic's API, the photo is subject to Anthropic's own handling of API inputs. See Section 4 for details.
• Account Backup & Sync: If you sign in, PushClock backs your app data up to our servers so it can be restored on a new device. The backup includes your alarms and their settings, your goal wake-up time, and your day-by-day activity history (for each day you used the app: when you completed your alarm, how long it took, how many push-ups, squats, jumping jacks, or high knees you completed, which dismissal method you used, and your progress on math missions). Your streak is derived from this history. This data is private to your account; it is not shown to other users except as described in Section 5.2.
• Wake Activity Shared With Your Squads: If you join a Wake Squad, PushClock records one entry per day describing that morning: the time your first alarm was set for, the time you finished your mission (if you did), whether you woke on time, woke late, or slept through your alarms, how many backup alarms fired, which mission you completed and its target (for example a rep count), your device's time zone, and whether you are using iOS or Android. The other members of your squad can see these entries; Section 5.2 sets out the exact limits.
• Approximate Location: From the features above we derive coarse location only: your device's time zone (needed to decide which calendar day a wake-up belongs to) and, if the leaderboard is ever enabled, your country. Alarm diagnostics (described below) also include your time zone and your device's language and region setting. We do not collect precise or GPS location.
• Leaderboard Activity (not currently available): The global leaderboard described in Section 5.3 is not currently offered in the app. Were it enabled, it would rank users by their fastest alarm-dismissal response times and would sync your best dismissal times and the mission behind each.
• Usage Data: App open/close events, feature interactions, alarm completion rates, leaderboard views, and session duration, collected to improve app performance.
• Device Information: Device model, operating system version, unique device identifiers, and crash and diagnostic reports. Crash reports are provided through Apple's native App Store Connect crash reporting; we do not integrate a third-party crash-reporting SDK. Separately, the app sends its own alarm diagnostics to our backend provider, as described in the next item.
• Alarm Diagnostics (iOS, uploaded automatically): The iOS app keeps a log on your device of what its alarm system does. It uploads this log to our backend provider automatically, whether or not you are signed in, so that we can find out why an alarm did not ring and answer your support requests about it. An upload happens when you open the app (at most once every 12 hours), about 30 seconds after an alarm error or a completed wake-up mission, and immediately when you tap Contact Support. Nothing is uploaded while a wake-up mission is on screen. Each upload contains:
  • Identifiers: a random identifier the app creates for your installation (the same identifier our analytics provider uses, and the "Support ID" described in Section 10), the identifier our subscription-management provider assigns to you, and your PushClock account identifier if you are signed in.
  • Device and app details: device model, iOS version, app version and build number, your language and region setting, your time zone, and whether Low Power Mode is on.
  • Your alarms: each alarm's name (the text you typed), its time, its repeat days, whether it is on or off, and which wake-up missions it uses.
  • Alarm activity: when alarms were scheduled, rang, rang again, and were dismissed, when missions were completed, and error messages from the alarm system.
  • Your wake-up results for the last 14 days: for each day, whether you completed your mission, which mission it was, how long you took to respond, and how quickly you woke up.
  • Permissions: whether you have granted the app alarm and notification permissions.
  • Subscription status: whether you have an active subscription, and the product identifiers and expiry dates of your subscriptions.
  Alarm diagnostics do not include your email address, your name, photos or camera images, video or audio recordings, anything you say into the microphone, the text of your missions (such as photo prompts or flashcards), the names of custom sounds, file paths on your device, your precise location, or your contacts. They are linked to your installation's identifier and, if you are signed in, to your account, so they are not anonymous. We use them only to diagnose alarm problems and to handle support requests. We do not use them for advertising, and we do not sell them or share them for marketing. Because alarm names are text you type, please do not put anything in an alarm's name that you would not want us to see. See Section 7 for how long they are kept and Section 10 for how to have them deleted. The Android app does not upload alarm diagnostics.
• Motion & Fitness Data: Accelerometer and motion-sensor data used to support activity detection and motion-based alarm-dismissal missions (such as shake or step challenges), where applicable.
• Microphone & Voice (on-device): Some optional missions and features use your microphone: speaking a tongue-twister to dismiss an alarm, or recording a custom alarm sound. Speech recognition for tongue-twisters runs on your device, and recorded custom sounds are stored only on your device. We do not transmit your voice recordings or audio to our servers or any third party.
• App-Blocking Selections (Screen Time / Family Controls): If you use the optional app-blocking feature, PushClock uses Apple's Family Controls / Screen Time framework to block apps you choose until you complete your alarm. The apps you select are represented by opaque system tokens that are stored on your device; we do not receive the list of apps you use or block, and this information is not uploaded to our servers.
• Subscription & Purchase Data: When you start a trial or purchase a subscription or lifetime access, we and our partners process related data such as product identifier, price, currency, transaction and subscription status, and trial start, to operate billing, paywalls, and advertising measurement. Payment card details are handled by the app store, not by us.
• Advertising Identifiers (IDFA/GAID): We may collect your device's advertising identifier (Apple IDFA or Google Advertising ID) for attribution and advertising measurement purposes. You can reset or limit use of this identifier through your device's settings (iOS: Settings > Privacy & Security > Tracking; Android: Settings > Google > Ads).
• Screen Recording of One Onboarding Screen (iOS): To understand where people get stuck during setup, the iOS app records what is shown on one onboarding screen (the alarm-sound picker) for a randomly selected sample of app sessions (currently about one in ten). The recording is a series of screenshots of that screen and your interactions with it; it starts when the screen appears and stops the moment you leave it. That screen has no text entry, camera view, photos, or questionnaire answers on it. Recordings are sent to our analytics provider, associated with your pseudonymous analytics identifier, and deleted after 30 days. No other screen is recorded for analytics or sent to our analytics provider, and the Android app does not record any screen for analytics. Mission recordings, described above, are a separate feature: they stay on your device unless you choose to share or save them or keep them as a Mission Memory.
• Website Download Links (pushclock.com/download): Links to PushClock in our social media profiles, advertisements, and creator partnerships may point to a short redirect page on our website that sends you on to the App Store or Google Play. When you open that page, it records an event with our analytics provider so we can measure which links and campaigns lead people to the app. The event includes the address of the page you opened (including any campaign tags in the link, such as utm_source), the page that referred you, whether you are on iOS or Android, whether you opened the link inside an in-app browser (Instagram, Facebook, or TikTok), which store you were sent to, and the time. If the page has to show you an "open" or "copy link" button, taps on those buttons are recorded as well. As with any web request, our analytics provider also receives your IP address. To count unique visitors, the page stores a randomly generated identifier in your browser's local storage (not a cookie). It does not contain your name, email address, or any account information, the page does not pass it to the app or to the app stores, and you can remove it at any time by clearing your browser's site data for pushclock.com.

2.3 Health & Sleep Data (Apple Health / Apple Watch, and Health Connect on Android)

• Sleep Data: With your permission, PushClock reads sleep data (such as sleep duration and the sleep stages recorded by your Apple Watch) from Apple Health (HealthKit). We use this data solely to show you in-app sleep insights, for example summaries and trends about your recent sleep displayed within the app.
• On-device only: Your sleep and health data is read and processed entirely on your device. We do not upload, transmit, or store it on our servers, it is not part of your account backup, and it is never associated with your profile or shared with your Wake Squad.
• No advertising or sharing: Consistent with Apple's requirements, we never use Apple Health data for advertising, marketing, or data-mining purposes, and we never sell it or share it with any third party.
• Permission and control: PushClock requests Health access before reading any data, and you choose which categories to grant. You can revoke access at any time in the Apple Health app (Sharing → Apps) or in iOS Settings > Privacy & Security > Health. Revoking access disables sleep insights but does not affect alarm or push-up features.
• Android (Health Connect): On Android, PushClock offers the same sleep insights by reading sleep sessions from Health Connect, with your permission. It is handled the same way: read and processed entirely on your device, never uploaded to our servers, not part of your account backup, never shared with your Wake Squad, and never used for advertising or sold. You can review or revoke access at any time in the Health Connect settings on your device.

2.4 Information We Do Not Collect

• We do not collect biometric identifiers beyond what is necessary for on-device pose detection. Mission recordings and Mission Memories are video of you, and may show your face, but they are not used for face recognition or any other biometric identification (see Section 4.3).
• We do not upload your Apple Health or sleep data to our servers. Sleep data read from Apple Health is processed only on your device (see Section 2.3).
• Mission recordings stay on your device and are deleted automatically unless you share them, save them, or keep them as a Mission Memory. We store video on our servers only if you turn on Save to Memories, and then only one clip per day (see Section 4.3). We do not retain the photos you submit for mission verification on our own systems; they are processed transiently to return a result and then discarded. Our AI provider may keep its own short-lived logs, as described in Section 4.2.
• We do not collect precise location data.
• We do not collect financial or payment information directly (payments are processed by the relevant app store platform).
• Your full alarm and activity history is uploaded only if you create an account. If you use PushClock without signing in, your goal wake-up time, your full wake-up history, and your exercise counts stay on your device. Once you sign in, they are backed up as described in Section 2.2. Alarm diagnostics on iOS are the exception. Whether or not you are signed in, the iOS app uploads your alarm settings and your wake-up results for the last 14 days, as described in Section 2.2.

2.5 Sensitive Information

Some of what PushClock handles may be considered sensitive under privacy laws. We use it only to run the feature you chose, never for advertising, and we never sell it:

• Health and sleep data from Apple Health or Health Connect, processed only on your device (Section 2.3).
• Camera images and video, which for some photo missions, and in mission recordings and Mission Memories, may show your face, body, or home, handled as described in Section 4.
• Your voice, for tongue-twister missions and custom alarm sounds, processed and stored only on your device.
• Age range, gender, and self-reported sleep and mood habits from the onboarding questionnaire, sent to our analytics provider as described in Section 2.1.
• Religious content: the app includes an optional Bible-verse mission. Which mission you choose is recorded with your usage data and in alarm diagnostics, and, if you are in a Wake Squad, shown to your squadmates as part of your daily entry, so choosing this mission may indicate your religious beliefs. It is never used for advertising. If you would rather not share that, choose a different mission.

Where the law requires your consent to process this kind of information, we rely on the choices you make in the app (granting a permission, selecting a mission, or answering an optional question), and you can withdraw that consent by revoking the permission, changing the mission, or contacting us.

3. How We Use Your Information

We use the information we collect to:

• Operate the app: deliver alarm functionality, track push-up completion, and apply your preferences.
• Keep alarms reliable and answer support requests: use alarm diagnostics (Section 2.2) to find out why an alarm did not ring and to answer your support requests about it.
• Show sleep insights: display in-app summaries and trends based on sleep data you allow us to read from Apple Health, processed entirely on your device.
• Power optional features you enable, such as photo-, motion-, or voice-based alarm-dismissal missions and app-blocking, including verifying mission photos and applying the app blocks you configure.
• Record your missions and show you your Mission Memories: record your wake-up missions on your device so you can watch and share them, and, if you turn on Save to Memories, show you your own memories in a calendar of past mornings inside the app.
• Process subscriptions: manage trials, paywalls, purchases, and subscription status.
• Operate your account and its backup: authenticate you, and back up your alarms and activity history so they can be restored on a new device.
• Operate Wake Squads: let you create and join squads, generate and redeem invite codes, and show the members of a squad each other's daily wake-up results.
• Moderate the community: review user reports and take action against accounts that violate our Terms of Service.
• Improve the product: analyze usage patterns to fix bugs, optimize performance, and develop new features.
• Communicate with you: send service-related notifications, updates, and support responses.
• Ensure security: detect, investigate, and prevent fraudulent or unauthorized activity.
• Advertising measurement & attribution: attribute app installs and in-app events to advertising campaigns, and measure the effectiveness of our advertising on platforms such as Meta (Facebook and Instagram), using a mobile measurement partner.
• Comply with legal obligations: fulfill applicable legal, regulatory, or contractual requirements.

We do not sell your personal information to third parties for their own marketing purposes.

4. Camera, Pose Detection, Photo Verification & Mission Recording

PushClock uses your camera in three distinct ways, which are handled differently:

4.1 Push-up pose detection (on-device)

• On-device processing only: All pose detection and push-up counting is performed locally on your device using on-device machine-learning models.
• No transmission: For pose detection, the camera feed is never transmitted to our servers or any third party.
• No storage by pose detection: Pose detection itself does not save any video, image, or frame to your device or our systems. Recording a video of your mission is a separate feature, described in Section 4.3.
• Not biometric identification: Pose detection analyzes body position in real time to count repetitions. It is not used to identify or recognize you, and we do not create, store, or share any facial or biometric template or "faceprint."

4.2 Photo-verification missions (processed off-device)

Some optional alarm-dismissal missions ask you to take a photo (for example: a made bed, the sky, grass/outdoors, a sketch, a specific object, or a custom "Snap This" photo). When you complete one of these missions:

• The image is sent off-device for analysis: The single photo is transmitted securely (over TLS) through our backend to an automated AI vision service, Anthropic's Claude API, which returns only a pass/fail result and a short reason. Depending on the mission you choose, the photo may include your face, body, or images of your home, bed, or surroundings. Once the photo has been transmitted to Anthropic's API for analysis, it is subject to Anthropic's own handling of API inputs under Anthropic's terms and privacy practices.
• Not stored on our systems: The photo is used solely to evaluate that mission. It is not stored or retained on PushClock's own systems, including our backend; it is not linked to your profile, and we keep no copy; it is discarded after the check. We do not have a zero-retention arrangement with Anthropic, so Anthropic may keep the image and result in its own systems for a limited period (under its current commercial terms, generally up to 30 days) for purposes such as detecting abuse, after which they are deleted. Under those terms Anthropic does not use content sent through its API to train its models. For details, see Anthropic's Privacy Policy (linked in Section 11).
• Automated analysis may be imperfect: Because verification is automated, it may occasionally accept or reject a photo incorrectly. The photo is not reviewed by a human unless required to investigate abuse or a technical problem. The only consequence of this automated check is whether your alarm mission is marked complete; we do not use automated processing to make decisions that have legal or similarly significant effects on you.
• Separate from mission recording: The verification photo is separate from the video of the mission. If you have turned on Save to Memories, that mission's recording (which may show the same scene) can be kept as a Mission Memory, as described in Section 4.3. Mission recordings and Mission Memories are not sent to Anthropic.

4.3 Mission recording and Mission Memories

Record My Missions (on your device). This setting is on by default, and you can turn it off at any time in Settings. While it is on:

• What is recorded: Camera missions (such as push-ups and squats) record the front camera. Photo missions record the back camera with a small picture-in-picture view from the front camera, which shows your face. Missions that do not use the camera record the mission screen, with a small front-camera selfie view added. Voice missions (such as reading aloud or tongue twisters) are not recorded.
• No sound: Recordings are silent. No microphone audio is recorded. A single recording is limited to 4 minutes.
• Stays on your device: The video stays on your device. After the mission, the app plays it back and offers to share it.
• Sharing only when you choose: A recording leaves the app only if you share it yourself through your device's standard share sheet, which also offers "Save Video" to your Photos library. A shared copy has your alarm's sound mixed in (not your voice) and a PushClock overlay.
• Deleted automatically: Unless you share it, save it, or keep it as a Mission Memory, the recording is deleted automatically.

Mission Memories (optional, stored in the cloud). Mission Memories are off by default. You turn them on with the Save to Memories switch, which is in Settings next to Record My Missions and is also offered once on the screen shown after a mission. Mission Memories require a PushClock account; if you turn the switch on while signed out, the app asks you to sign in. While it is on:

• What is kept: The first alarm you complete on each calendar day (in your local time) becomes a memory: that day's mission recording, sped up if needed to fit 60 seconds, re-encoded at a reduced resolution (540 pixels wide) with no audio, plus one still image taken from it. With each memory we store the date and your time zone, when you completed the alarm, the alarm's set time and name, which missions you completed and how long they took, your streak day count, the clip's duration, pixel size and file sizes, and your device's platform (iOS or Android).
• Where it is stored: Both files are uploaded to our backend provider, into private storage tied to your account. Access rules allow only you, signed in to your account, to read or change them. The app downloads them through short-lived signed links.
• Who sees it: Your memories are shown only to you, in a calendar of past mornings inside the app. They are not shown to your Wake Squad members or anyone else, not sent to any analytics provider, not sent to Anthropic, and not used for advertising or to train any model.
• Not used for identification: A memory is stored video that may show your face. It is not used for face recognition or any other biometric identification, and we do not create a facial or biometric template from it.
• How long it is kept: A memory is kept until you delete it. There is no automatic expiry on our servers.
• Deleting a memory: You can delete any single memory in the app. This removes it from our servers and then from your device. Deleting your account deletes every memory and its files (see Section 5.4).
• Turning it off: Turning off Save to Memories stops new memories from being created. A memory that was already captured but has not finished uploading will still upload after you turn the switch off; you can then delete it in the app.
• Signing out: Signing out removes your device's copies of memories that are already on our servers. Memories that have not been uploaded yet stay on your device, and are removed if a different account signs in.
• On your device: The app keeps a local cache of your recent memory videos (up to 30 days or 250 MB) so they play without downloading.
• Saving and sharing: You can save a memory to your Photos library or share it through your device's standard share sheet. Both happen only when you choose.

Permission and control. The app requests camera permission before these features activate. You may revoke camera access at any time through your device settings, though doing so will disable push-up detection and photo-verification missions.

5. Accounts, Wake Squads & Community Features

5.1 Your account

An account is optional and is never required to use the alarm, mission, or app-blocking features. It exists so that your alarms and progress can be restored on a new device, so that you can join a Wake Squad, and so that you can save Mission Memories if you choose to.

Sign in with Apple or Google. We authenticate accounts using Sign in with Apple or Sign in with Google on iOS, and Sign in with Google on Android. The provider issues us an opaque user identifier and an email address (with Apple, this may be Apple's privacy relay address). We handle authentication through our backend provider, and we neither create nor store passwords. Your email address is also sent to our analytics provider as a property of your analytics profile (see Section 11).

What signing in uploads. Signing in enables the account backup described in Section 2.2: your alarms, your goal wake-up time, and your day-by-day activity history. That backup is private to your account and is not shown to other users. Signing in does not by itself upload any video: Mission Memories are uploaded only if you also turn on Save to Memories (Section 4.3).

On Android. Android offers only Sign in with Google, so an account created with Apple on an iPhone cannot currently be used to sign in on Android. Note also that Android's system backup may preserve your signed-in session, so a phone restored from an Android backup can return you to the app already signed in.

5.2 Wake Squads

A Wake Squad is a small, invite-only group (up to eight members) whose members can see whether each other actually got up in the morning. You can belong to up to three squads. Squads are optional, and you need to be signed in and to choose a display name in order to create or join one.

What the other members of your squad can see. For each day, they can see your display name, your avatar, and:

• the time your first alarm was set for;
• the time you finished your mission, if you did;
• whether you woke on time, woke late, or slept through your alarms;
• how many backup alarms fired;
• which mission you completed and its target (for example, "30 pushups");
• your device's time zone, and whether you use iOS or Android;
• any emoji reactions left on an entry, and who left them.

Limits that apply by design. These are enforced by our database, not only by the app:

• A squad member can see your entries only from the date they joined that squad onwards. Joining a squad does not reveal your earlier history.
• Someone who holds a valid invite code but has not joined can see only the squad's name, its emoji, and how many members it has, not who those members are.
• Squad information is not public and is not visible to anyone who is not signed in.
• Your mission photos, mission recordings, and Mission Memories are never shared with your squad, only the mission's name and target. Photo verification is described in Section 4.2.
• We do not share your precise location, your Apple Health or sleep data, your recorded alarm sounds, or your app-blocking selections with a squad.

Invites. Squad invites are short codes that you share, using your device's standard share sheet (in a message or a chat app, for example). PushClock does not send invitations on your behalf: we operate no email or SMS service, and we never receive the contact details of the person you invite. Invite codes expire after seven days and can be redeemed a limited number of times.

Live updates. While you have the app's social screen open, your squad's entries update in real time over a secure connection. The visibility limits above apply to those updates in exactly the same way.

Avatar upload and storage. When you choose an avatar, the image is resized on your device to a 512×512 JPEG and uploaded to cloud file storage operated by our backend provider. Avatar files are served from publicly accessible URLs; while these URLs are not published or indexed outside the app, they are not access-controlled, and anyone who possesses or can guess a URL can view the image. Please choose an avatar with that in mind.

Photo library access. The avatar chooser uses your operating system's standard photo picker. This lets you share a single selected photo with PushClock without granting access to your entire photo library.

5.3 Global leaderboard (not currently available)

The global leaderboard described in this subsection is not currently offered in the PushClock app. It has no entry point in the shipping app, and no leaderboard data is being published. We describe it here because the underlying capability remains in place and may be re-enabled in future. If we do re-enable it, participation would be optional and would require signing in and claiming a display name.

Were it enabled, the leaderboard would rank players by how quickly they dismiss an alarm by completing its mission, and the following would be visible to other users: your display name (limited to 20 characters in that feature), your avatar photo, your country, your best (fastest) alarm-dismissal response times on an all-time, weekly, and monthly basis, and which mission produced each of your best times. You should assume that anything published to a leaderboard is readable by anyone who uses the app, whether or not they are signed in.

Your alarms, your day-by-day activity history, and your Wake Squad entries would not be published to the leaderboard.

5.4 Reporting, blocking & deleting your account

Reporting and blocking. Where the app offers a reporting control, you can report another user's display name or avatar. Reports are stored on our servers and are associated with your account so that we can review them and prevent abuse of the reporting system itself. Where a blocking control is offered, blocks are stored locally on your device and hide that user from your own view only; they do not remove the user for anyone else.

Deleting your account. You can permanently delete your account from within the app, in Settings. Deleting your account removes your authentication record, and the data we hold that is linked to it is deleted along with it: your profile (display name and avatar), your squad memberships and any squads you created, your invite codes, your wake entries and the reactions on them, your account backup, your Mission Memories, the alarm diagnostics linked to your account, and any leaderboard entry. Your stored avatar image files and the video and image files of your Mission Memories are deleted too. Your local app data (alarms, preferences, and on-device history) is not affected by account deletion; you can remove that by deleting the app.

Three things are worth knowing about deletion. Moderation reports you have submitted about other users may be retained separately, as described in Section 7. Alarm diagnostics are linked to an installation of the app, and that installation is linked to your account once you sign in on it, so deleting your account deletes that installation's diagnostics, including any sent before you signed in. Diagnostics from an installation where you never signed in (another phone, or an earlier installation of the app) are not removed by account deletion; to have those deleted, contact us with that installation's Support ID (see Section 10). If you keep using the app after deleting your account, it continues to send alarm diagnostics, linked only to your installation. And records relating to our referral programme and to cancellation surveys are keyed to a pseudonymous analytics identifier rather than to your account, which means in-app account deletion does not remove them; if you would like those deleted as well, contact us using the details in Section 16 and we will remove them.

6. Sharing Your Information

We do not sell your personal information. We may share your information only in the following limited circumstances:

• Service Providers: Trusted third-party vendors who process data on our behalf to operate the app and website, in these categories: cloud hosting and backend infrastructure (authentication, database, and file storage, including avatar images, the videos and still images of Mission Memories, and alarm diagnostics); product analytics (including your onboarding questionnaire responses about age range, gender, and self-reported sleep, mood, and wake-up habits, and, if you create an account, your email address); subscription and paywall management; mobile attribution and advertising measurement; sign-in (Apple and Google); website hosting and analytics; and automated AI analysis of photo-verification mission images (Anthropic, as described in Section 4.2). These vendors are bound by confidentiality obligations and may not use your data for their own purposes, except that our AI provider may keep verification photos for a limited period under its own terms, as described in Section 4.2. Section 11 describes each category, and the specific vendors we use are available on request.
• Other Members of Your Wake Squads: If you join a Wake Squad, the information described in Section 5.2 (your display name, your avatar, and your daily wake-up entries from the date each member joined onwards) is shown to the other members of that squad as an inherent part of the feature. It is not shown to anyone outside your squads.
• Sharing You Choose: Mission recordings and Mission Memories leave the app only when you share them yourself through your device's standard share sheet or save them to your Photos library. We do not share them on your behalf; whoever or wherever you send them to receives them.
• Other Leaderboard Users: The global leaderboard is not currently available (see Section 5.3). Were it re-enabled, anything described there as visible would be shown to other users of PushClock as an inherent part of that feature.
• Advertising & Attribution Partners: We share certain pseudonymous data (such as device advertising identifiers, in-app events, and conversion signals) with our mobile measurement partner and with advertising platforms including Meta (Facebook and Instagram). This data is used to attribute app installs to advertising campaigns and to measure and optimize advertising performance. California residents may opt out of this sharing (see Section 13). Meta processes data in accordance with its own privacy policy (see Section 11).
• Linked Pseudonymous Identifiers: To attribute installs and in-app events and to operate our referral program, we may link the pseudonymous identifiers our providers assign, for example, your analytics identifier and your attribution identifier, to one another and to a referral record. Alarm diagnostics (Section 2.2) also store your analytics identifier, your subscription-management identifier, and, if you are signed in, your account identifier together in one record. These identifiers are not your name, but they can be used to recognize the same device or app installation across these services.
• Legal Requirements: When required by law, subpoena, court order, or to protect the rights, property, or safety of PushClock, our users, or the public.
• Business Transfers: In connection with a merger, acquisition, or sale of assets, your information may be transferred. We will notify you before your information becomes subject to a different privacy policy.
• With Your Consent: In any other circumstances with your explicit prior consent.

7. Data Retention

We retain your personal information for as long as your account is active or as needed to provide you services. You may request deletion of your account and associated data at any time (see Section 10). We may retain certain information as required by law or for legitimate business purposes such as fraud prevention, even after account deletion.

Account, backup, and squad data. Your profile, your account backup, your Wake Squad memberships, and your daily wake entries are retained for as long as your account exists, and are removed when you delete your account from within the app (see Section 5.4). We do not currently apply an automatic time limit to this data; it persists until you delete your account. A squad is deleted automatically once its last member has left it. Invite codes stop working after seven days, though the record of a code is kept until its squad is deleted. Moderation reports you submit about other users may be retained separately for a reasonable period to support abuse prevention and repeat-offender detection, even after your own account is deleted.

Mission recordings and Mission Memories. Mission recordings stay on your device and are deleted automatically unless you share them, save them, or keep them as a Mission Memory. Mission Memories are kept on our servers until you delete them in the app or delete your account; we do not apply an automatic time limit to them. Your device also keeps a local cache of recent memory videos (up to 30 days or 250 MB). See Section 4.3.

Alarm diagnostics. We delete alarm diagnostics automatically on a rolling basis. For each installation of the app we keep only the 12 most recent uploads of the alarm activity log, and we delete each of them 90 days after we receive it. The rest of an installation's diagnostics (its identifiers, device details, alarm settings, recent wake-up results, and subscription status) is replaced when a newer upload includes it, and is deleted once 90 days pass with no new upload from that installation. Alarm diagnostics linked to your account are deleted when you delete your account (Section 5.4), and you can ask us to delete any others sooner (Section 10).

Automatically collected usage data (other than alarm diagnostics, described above) is retained for a maximum of 24 months before being deleted or anonymized. Screen recordings of the onboarding sound-picker screen (Section 2.2) are deleted after 30 days. Photos sent for mission verification are not retained by us; our AI provider may keep them for up to 30 days (Section 4.2). Crash and diagnostic reports delivered through Apple's App Store Connect are subject to Apple's own retention policies. Attribution data processed by our mobile measurement partner is subject to that partner's own retention policies.

8. Data Security

We implement industry-standard technical and organizational security measures to protect your information, including:

• Encryption of data in transit (TLS/HTTPS)
• Encryption of data at rest
• Access controls limiting employee access to personal data
• Regular security reviews and vulnerability assessments

No method of electronic transmission or storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security.

9. Children's Privacy

PushClock is not directed to children under the age of 13 (or under the applicable age of digital consent in your country, which is 16 in parts of the European Economic Area). We do not knowingly collect personal information from children under these ages, and our community features (including Wake Squads, where members can see each other's display names, avatars, and daily wake-up results) are not intended for them. If you believe we have inadvertently collected such information, please contact us immediately at support@pushclock.com and we will take prompt steps to delete it.

10. Your Rights and Choices

Depending on your location, you may have the following rights regarding your personal information:

To exercise any of these rights, contact us at support@pushclock.com. We will respond within 30 days. We may need to verify your identity before fulfilling your request.

Deleting your account in-app. You can delete your account and its associated server-side data directly from within the app, in Settings, without needing to contact us. Section 5.4 sets out exactly what deletion covers, and the two categories it does not.

Mission Recording & Mission Memories

• Stop recording missions: Turn off Record My Missions in Settings.
• Stop saving memories: Turn off Save to Memories in Settings. This stops new memories; a memory already captured but not yet uploaded will still upload, and you can then delete it.
• Delete a memory: Delete any single memory in the app. This removes it from our servers and then from your device.
• Delete all memories: Deleting your account deletes every memory and its files (see Section 5.4).

Alarm Diagnostics

• No setting to turn it off: The app sends alarm diagnostics automatically and does not currently offer a setting to turn them off.
• Your Support ID: When you tap Contact Support in the app, the email it prepares includes a line labeled "Support ID". This is your installation's identifier, and it is how we find your diagnostics. Reinstalling the app creates a new Support ID.
• Deleting your diagnostics: If you are signed in, deleting your account deletes the alarm diagnostics linked to it (Section 5.4). Otherwise, email support@pushclock.com and include your Support ID, and we will delete the diagnostics for that installation.

Camera, Microphone & Notification Permissions

You can manage camera, microphone, motion, speech-recognition, and notification permissions at any time through your device's operating system settings. Revoking camera access disables push-up detection and photo missions; revoking microphone or speech access disables voice missions and custom-sound recording; revoking notifications disables alarm alerts. You can also turn off app-blocking and revoke Screen Time / Family Controls access in your device settings.

Apple Health Permissions

PushClock reads sleep data from Apple Health only with your permission, and processes it on your device. You can review or revoke this access at any time in the Apple Health app under Sharing → Apps, or in Settings > Privacy & Security > Health. Revoking access disables sleep insights.

Health Connect Permissions (Android)

PushClock reads sleep sessions from Health Connect only with your permission, and processes them on your device. You can review or revoke this access at any time in your device's Health Connect settings. Revoking access disables sleep insights.

Advertising Identifier & Tracking (iOS)

On iOS, PushClock requests permission to track your device's advertising identifier (IDFA) via Apple's App Tracking Transparency (ATT) framework. If you decline, we will not use your IDFA for attribution or advertising measurement purposes. You can change this permission at any time in Settings > Privacy & Security > Tracking.

Do Not Track and Global Privacy Control

Some browsers can send a "Do Not Track" or "Global Privacy Control" signal. Our website does not currently change its behavior in response to these signals. The website does not use advertising cookies or cross-site tracking; the limited analytics it does use are described in Section 2.2 (Website Download Links) and Section 11 (Website Hosting & Analytics). In the app, you control tracking through your device's settings, as described above.

11. Third-Party Services

PushClock integrates with or depends on the following third-party services. We name a provider where you interact with it directly, where it receives especially sensitive data, or where we are required to; the rest are described by category. The specific vendors we use in each category, and their roles, are available on request at support@pushclock.com.

• App Store Platforms: Apple App Store and/or Google Play Store handle payments and distribution under their own privacy policies.
• Apple (Sign in with Apple): We use Sign in with Apple to authenticate PushClock accounts on iOS. Apple provides us with an opaque user identifier and an email address (which may be a privacy relay address). Apple's prompt also offers to share your name; we neither read nor retain it. See Apple's Privacy Policy.
• Apple Health (HealthKit): With your permission, we read sleep data (including Apple Watch sleep recordings) from Apple Health to provide in-app sleep insights. This data is processed on your device and is not transmitted to us or any third party. See Apple's Privacy Policy.
• Google (Sign in with Google): If you choose to sign in with Google, Google provides us an opaque user identifier and your email address to authenticate your PushClock account. Sign in with Google is the only option on Android. See Google's Privacy Policy.
• Backend Infrastructure: We use a cloud backend provider for authentication, database, and file storage, and to host the backend functions that process photo-verification missions. It stores your authentication record; your profile (display name and avatar URL); your account backup (alarms, goal wake-up time, and day-by-day activity history); your Wake Squads, their memberships and invite codes, your daily wake entries and the reactions on them; avatar image files; your Mission Memories, if you turn them on (video clips, still images, and the details stored with each, as described in Section 4.3); referral records (see Section 2.1); cancellation-survey responses; alarm diagnostics uploaded by the app (see Section 2.2); any leaderboard entry; and any moderation reports you submit.
• On-Device Pose Detection: Push-up and exercise pose detection uses a third-party machine-learning library that runs entirely on your device. No camera frames or images are transmitted to the library's developer, or to us, for this feature.
• Anthropic (Photo Verification): When you complete a photo-verification mission, the image (which, depending on the mission, may include your face, body, home, bed, or surroundings) is sent to Anthropic's Claude API to return a pass/fail result. We do not retain the image on our own systems (including our backend); once transmitted, it is handled by Anthropic as an API input under Anthropic's own terms and privacy practices. See Anthropic's Privacy Policy.
• Product Analytics: We use an analytics provider to understand how the app is used (for example, screen views, feature usage, mission and alarm activity, and subscription events) so we can fix bugs and improve the product. We also send it your onboarding questionnaire responses, including age range (which may indicate you are a 13–17-year-old), gender, and self-reported sleep, mood, and wake-up habits, as events and as user properties tied to a pseudonymous analytics identifier. If you create an account, we also send it your email address as a property of that profile, which means the profile is no longer pseudonymous to us. We also use this provider on the download-link page of our website, as described under "Website Download Links" in Section 2.2.
• Website Hosting & Analytics: Our website (pushclock.com) is hosted by a cloud hosting provider whose built-in analytics count page views and show which pages are visited. It does not use cookies, does not store a persistent identifier on your device, and does not track you across other websites. The provider processes limited technical data (such as the page URL, referrer, browser, device type, and approximate country) to produce aggregate statistics.
• Subscriptions & Paywalls: We use a subscription-management provider to present paywalls and manage subscription and trial flows. It processes paywall interactions and transaction/subscription status.
• Mobile Attribution: We use a mobile measurement partner (MMP) to attribute app installs and in-app events to advertising campaigns. It may collect device identifiers (including the advertising identifier where you permit it), IP address, install and session timestamps, and in-app event data. The in-app events we send it are a small set of activation milestones (completing onboarding, your first successful wake-up, and reaching a three-day streak) with no revenue attached; subscription and revenue data reaches it from our subscription-management provider server-to-server rather than from the app. It is contractually bound to use this data only for attribution and analytics.
• Meta (Facebook/Instagram): We run paid advertising campaigns on Meta (Facebook and Instagram). Third parties, including Meta, may collect or receive information from the PushClock app, such as pseudonymous attribution and conversion data through Meta's SDK or server-to-server integrations, and use it to provide measurement services and targeted ads. This may include device identifiers, in-app event signals, and hashed identifiers. You can opt out as described under "Advertising Identifier & Tracking" in Section 10 and in Section 13. See Meta's Privacy Policy.
• Apple (Crash & Diagnostic Reporting): Crash reports are provided through Apple's built-in App Store Connect crash reporting. We do not integrate any third-party crash-reporting or diagnostics SDK. The app's own alarm diagnostics (Section 2.2) are stored by our backend provider, described above.

We are not responsible for the privacy practices of third-party services. We encourage you to review their privacy policies. The same applies to other websites and services that our app or website links to, such as the App Store, Google Play, and our social media profiles.

12. International Data Transfers

If you are located outside the United States, please be aware that your information may be transferred to and processed in the United States or other countries. We ensure that any such transfers comply with applicable data protection laws through appropriate safeguards such as standard contractual clauses.

13. California Privacy Rights (CCPA/CPRA)

If you are a California resident, you have additional rights under the California Consumer Privacy Act (CCPA) and California Privacy Rights Act (CPRA), including the right to:

• Know what personal information is collected, used, shared, or sold.
• Delete personal information we have collected from you.
• Opt out of the sale or sharing of personal information. Note: we do not sell personal information. However, we do share certain pseudonymous data with advertising platforms (including Meta) and our mobile measurement partner for cross-context behavioral advertising measurement purposes. You have the right to opt out of this sharing.
• Non-discrimination for exercising your privacy rights.

To opt out of the sharing of your personal information for cross-context behavioral advertising, or to submit any other CCPA/CPRA request, contact us at support@pushclock.com or through the in-app settings menu. We will process your request within 45 days.

Other U.S. State Privacy Rights & Consumer Health Data

Residents of other U.S. states with comprehensive privacy laws (such as Virginia, Colorado, Connecticut, and others) may have similar rights to access, correct, delete, and obtain a copy of their personal information, and to opt out of targeted advertising. You can exercise these rights using the same contact details above.

Certain states regulate "consumer health data" (for example, Washington's My Health My Data Act and Nevada's health-privacy law). The sleep data you optionally allow PushClock to read from Apple Health is processed on your device for in-app insights and is not sold or shared with third parties. Separately, if you create an account we store your day-by-day wake-up and exercise history on our servers, and if you join a Wake Squad you choose to share that day's wake-up result with the other members of that squad. On iOS, whether or not you have an account, alarm diagnostics include your wake-up results for the last 14 days (Section 2.2). If you turn on Save to Memories, we also store one video of your mission each day, with details such as how long it took and your streak (Section 4.3); it is shown only to you. We do not sell this data or share it with advertising partners. Where these laws apply, we will obtain any required consent before collecting consumer health data and will not share it without the separate authorization those laws require.

14. European Privacy Rights (GDPR)

If you are located in the European Economic Area (EEA), United Kingdom, or Switzerland, we process your personal information under the following legal bases:

• Performance of a contract: to provide you with the app's functionality, including your account, its backup, and Wake Squads when you choose to sign in.
• Legitimate interests: for analytics, security, product improvement, community moderation, advertising measurement, and alarm diagnostics (finding out why an alarm did not ring and answering support requests about it), where these don't override your rights.
• Legal obligation: where processing is required by law.
• Consent: where you have given explicit consent (e.g., optional features, IDFA tracking on iOS).

You have the right to lodge a complaint with your local data protection authority if you believe we have not handled your data in accordance with applicable law.

15. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last Updated" date at the top of this page. For material changes, we will provide a more prominent notice (such as an in-app notification or email). Your continued use of PushClock after changes take effect constitutes your acceptance of the revised policy.

Summary of changes in the October 8, 2026 update. In this update we: (1) added alarm diagnostics: the iOS app uploads a log of what its alarm system does, including your alarm settings and your wake-up results for the last 14 days, to our backend provider, whether or not you are signed in, so we can diagnose alarm problems and answer support requests, and we described what is and is not included, how it is used, how long it is kept, and how to have it deleted (Sections 2.2, 3, 7, and 10); (2) updated our statement that your alarm and activity data is uploaded only if you create an account (Section 2.4); and (3) updated the sections on sensitive information, account deletion, sharing, our backend provider, crash reporting, consumer health data, and legal bases to match (Sections 2.5, 5.4, 6, 11, 13, and 14).

Summary of changes in the September 23, 2026 update. In this update we: (1) corrected earlier statements that PushClock never records or stores video from your camera: the app records a video of your wake-up missions on your device (Record My Missions, on by default), which earlier versions of this policy did not describe (Sections 2.2, 2.4, and 4.3); (2) added Mission Memories, an optional, off-by-default feature that uploads one short, silent clip and one still image per day to private storage tied to your account, and described what is stored with each memory, who can see it, how long it is kept, and how to delete it (Sections 2.2, 3, 4.3, and 7); (3) clarified that push-up pose detection still runs entirely on your device, separately from mission recording (Sections 2.2 and 4.1); (4) stated that mission recordings and memories are not used for face recognition or biometric identification (Sections 2.4 and 4.3); (5) updated the sections on sharing, account deletion, Wake Squads, your choices, and our backend provider to cover these features (Sections 5, 6, 10, 11, and 13); and (6) described most of our service providers by category rather than by name, naming only Apple, Google, Anthropic, and Meta, and stated that the specific vendors are available on request (Sections 2 through 7, 10, 11, and 13). How the app handles your data did not change as a result of item (6).

Summary of changes in the September 21, 2026 update. In this update we: (1) disclosed that our website uses a cookieless page-view analytics service (see Section 11); (2) described the analytics our website's download-link page sends to our analytics provider, including the random identifier it stores in your browser (Section 2.2); (3) identified PushClock LLC as the data controller, explained why Kaizen Technologies LLC appears on our store listings, and changed our contact address to support@pushclock.com; (4) disclosed that the iOS app records one onboarding screen for a sample of sessions, and that those recordings are deleted after 30 days (Sections 2.2 and 7); (5) added Health Connect, which the Android app uses for sleep insights (Sections 2.3 and 10); (6) added a summary of the sensitive information we handle (Section 2.5); (7) clarified that our AI provider, Anthropic, may retain verification photos for up to 30 days and does not use them to train its models (Section 4.2); and (8) added statements on automated decisions, Do Not Track and Global Privacy Control signals, and third-party links. These changes describe existing practices more completely; how the app handles your data did not change.

Summary of changes in the August 24, 2026 update. In this update we: (1) disclosed that creating an account backs up your alarms, goal wake-up time, and day-by-day activity history to our servers, and removed earlier statements that said this data never left your device; (2) added a full description of Wake Squads: what a squad is, what its members can see about you, the limits enforced on that visibility, and how invites work; (3) disclosed that we derive coarse location (your device's time zone, and country if the leaderboard is enabled); (4) noted that the global leaderboard is not currently offered in the app, and scoped its description accordingly; (5) disclosed that your email address is sent to our analytics provider when you create an account; (6) changed our mobile measurement partner and described what we send it; (7) added the selfie-based photo mission to the list of photo-verification missions; (8) clarified account deletion: what it covers, and the referral and cancellation-survey records it does not; (9) described our actual retention practice for account and squad data; and (10) described the on-device pose-detection technology we use.

Summary of changes in the July 6, 2026 update. In this update we: (1) corrected the description of leaderboard data: the leaderboard ranks users by their fastest alarm-dismissal response times and syncs only your display name, avatar, best dismissal times, and the mission behind each best time (not push-up totals, streaks, badges, or alarms); (2) disclosed that onboarding questionnaire responses, including age range, gender, and self-reported sleep, mood, and wake-up habits, are sent to our analytics provider; (3) added a disclosure of our referral program and the identifiers it links; (4) clarified how photo-verification images are handled, including that they may show your face, body, or surroundings, are transmitted to Anthropic's API for analysis, and are not stored on our own systems; (5) clarified that we link pseudonymous identifiers across providers for attribution and referrals; and (6) updated our advertising-partner and crash-diagnostics disclosures.

16. Contact Us

If you have questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us:

PushClock LLC
Email: support@pushclock.com

We are committed to resolving any complaints about your privacy and our collection or use of your personal information promptly and transparently.

This Privacy Policy was last updated on October 8, 2026.