Legal

Privacy Policy

Effective date: October 8, 2026. WakeSnap collects and uses personal data to provide account access, subscriptions, alarm scheduling, wake-mission verification, progress tracking, customer support, product analytics, and error diagnostics.
01

Information we collect

We collect the information you provide or authorize when you use WakeSnap, including your email address, display name, and the authentication provider you use to sign in, such as Apple or Google.

We collect subscription and billing-linked account data needed to unlock paid features, including your RevenueCat app user or customer identifier, entitlement status, product identifier, renewal status, store, and subscription expiration details.

We collect the alarm and app settings you create, including alarm times, selected days, mission preferences, sound selection, and timezone.

We collect wake-session and progress data generated by your use of the app, including whether a wake session was completed, retried, missed, or expired, along with streak and badge progress.

If you use a photo-based wake mission, we collect the proof photo you capture, the mission payload sent with it, and verification result data so we can determine whether the mission was completed.

02

How we use information

We use personal data to create and manage your account, authenticate you, schedule alarms, run wake missions, verify mission completion, sync subscription access, prevent fraud or misuse, maintain streaks and badges, and provide customer support.

Camera access is used for photo proof and for on-device push-up and squat tracking. Exercise camera frames and body landmarks are processed on your device, not uploaded for AI verification or kept as recordings. Mission results such as repetition counts and completion times may be synced. Notification and alarm permissions deliver the wake events you enable.

Your proof photo is sent to our backend so the active wake mission can be verified.

Photo-mission verification uses Google Gemini AI. Your proof photo and mission details are shared with Google through our backend to check whether the mission is complete. This is separate from the on-device processing used for push-ups and squats.

03

Product analytics and error diagnostics

We use PostHog to understand how WakeSnap is used and improve its features. We send app interaction events, such as app launches, onboarding steps, paywall views, purchase and trial events, and mission outcomes, together with relevant event details, timestamps, platform, app version, build number, and timezone. Analytics also includes technical device and operating-system information provided by the SDK.

After sign-in, PostHog events are linked to your account using your WakeSnap user ID or RevenueCat customer ID. We also send your display name, onboarding completion status, and subscription details such as status, product, store, and renewal status. These analytics records are not anonymous.

We use Sentry to diagnose app and backend errors and crashes. Reports may include error messages, stack traces, diagnostic breadcrumbs, app version, and device and operating-system information. In the app, reports are linked to your account through your WakeSnap user ID or RevenueCat customer ID. Default personal-information collection and performance tracing are disabled in our Sentry configuration; this does not make account-linked error reports anonymous.

We use these services for product analytics, reliability, and support. We do not use this information to track you across other companies’ apps or websites for targeted advertising or advertising measurement, or share it with data brokers.

04

Storage and retention

Account, subscription, alarm, settings, wake-session, streak, and badge records are kept for as long as your account remains active and as long as needed to operate the service, maintain security, and resolve support issues.

WakeSnap does not keep a lasting archive of the raw proof photo in its application database after verification completes. The photo is used for verification transit and processing, and the uploaded verification file is scheduled for deletion from the verification provider after the request finishes. This cleanup may be delayed or fail; we do not promise immediate deletion or zero retention by the provider.

WakeSnap may keep proof-related metadata and verification results, such as timestamps, mission payload details, and accept or retry outcomes, until you clear proof history or delete your account.

Analytics and diagnostic records are stored by PostHog and Sentry under the retention settings configured for those services. Deleting your WakeSnap account does not automatically remove records already held by these providers. Contact us to request deletion of account-linked analytics or diagnostic records; limited records may be retained where needed for security or legal obligations.

05

Sharing, deletion, and your choices

We share data with service providers that help us operate the app, including authentication and cloud hosting providers, RevenueCat for subscription management, Google Gemini for photo-mission verification, PostHog for product analytics, and Sentry for error and crash reporting.

If you delete your account, WakeSnap deletes your account record, alarms, wake sessions, badge awards, and proof-history data stored in the app service. Limited billing, security, or legal records may be retained only where reasonably necessary.

You can contact us about privacy questions or account deletion at wakesnap@proton.me or through https://wakesnap.app/support.

Privacy questions and account deletion requests: wakesnap@proton.me