About This Policy

This Privacy Policy explains how Wake AI processes information when you use the Wake AI application. For privacy questions or account help, contact Wake AI support at support@wakeai.app.

Account and Authentication

Wake AI uses Supabase Auth for account creation, sign-in, session management, email/password authentication, and Google Sign-In. Supabase Auth processes your internal user ID, email address, authentication provider details, session tokens, and related authentication records. Google Sign-In may provide Google account information such as your email address and profile metadata to Supabase Auth. Wake AI uses your user ID and email to identify your account, display account information, scope local data, and link subscription entitlement status through RevenueCat. Wake AI also writes onboarding completion status and completion time to Supabase Auth user metadata.

Wake AI and Supabase Data

The app does not store alarm records, wake history, camera frames, or pose landmarks in custom Supabase database tables. Server-side Wake AI data is limited to Supabase Auth account data and onboarding metadata. Account deletion uses a Supabase Edge Function to delete the authenticated Supabase Auth user.

Alarms and Wake Challenges

Alarm data can include title, time, repeat days, enabled state, movement type, target repetitions, difficulty, sound, vibration, snooze settings, creation time, and update time. Wake challenge history can include alarm title, scheduled time, completed time, movement type, target repetitions, completed repetitions, difficulty, and completion status. These records are stored locally on your device under your authenticated user ID.

Camera and Pose Processing

Wake AI uses the camera during supported movement challenges such as Squats and Push-ups. Camera frames are analyzed on device through VisionCamera frame processors and the Wake AI pose detection module using Google ML Kit pose detection. The app receives pose landmarks and frame metadata in memory to verify movement and count repetitions. Wake AI does not intentionally save challenge photos or videos, does not upload camera frames to Wake AI servers, and does not persist or transmit pose landmark results. Camera access is used for movement verification, not identity recognition.

Alarms, Notifications, and Device Permissions

Wake AI uses device capabilities needed for alarms, including notifications, exact alarms, foreground service behavior, full-screen alarm display, alarm sound, vibration, and wake lock. Camera permission is requested when a movement challenge needs camera verification. Optional wake reminders are scheduled locally. Device permission status is read from the device so Wake AI can explain or request access where needed.

Local Storage

Wake AI stores most app data locally. MMKV stores alarms, alarm defaults, notification preferences, wake completion history, and acknowledged achievement reveals. AsyncStorage stores Supabase session persistence and onboarding progress. Android private preferences store scheduled and active alarm payloads used by the native alarm scheduler. The in-app account deletion flow cancels scheduled Wake AI alarms and reminders, clears local alarms, defaults, notification preferences, wake completion history, achievement reveal state, onboarding state, and the local Supabase auth cache on this device after server-side account deletion is confirmed.

Third-Party Services

Wake AI uses Supabase for authentication and account deletion, Google Sign-In for optional Google authentication, Google ML Kit for on-device pose detection, RevenueCat for subscription entitlement and purchase status management, and Google Play for app distribution, Android billing, payment processing, and subscription management links. Wake AI does not currently use active analytics, advertising, or tracking SDKs. Wake AI does not sell personal information.

Subscriptions and Purchases

Wake AI uses RevenueCat to fetch available subscription offerings, start Google Play subscription purchases, restore purchases, and determine premium access from the active RevenueCat entitlement. Google Play handles payment processing and displays localized price, billing period, renewal, cancellation, and any eligible trial or promotional terms before purchase. Wake AI does not directly receive full payment-card details. Uninstalling Wake AI or deleting a Wake AI account does not automatically cancel a Google Play subscription.

Account Deletion and Retention

You can delete your Wake AI account from within the Wake AI app. You may also contact support@wakeai.app for account or privacy assistance. The app uses a Supabase Edge Function to delete your authenticated Supabase Auth user, then cancels local scheduled alarms and reminders and clears the local Wake AI data described above on this device. Some records may remain with service providers where required for security, fraud prevention, billing, dispute handling, legal obligations, or provider logs. Account deletion and subscription cancellation are separate; manage any Google Play subscription in Google Play.

Your Choices and Rights

You may request access, correction, or deletion of applicable personal information, subject to applicable law and technical limitations. Contact support@wakeai.app for privacy requests. Wake AI is intended for users who can safely manage an account and perform the supported movements; the app does not currently contain an in-app age gate. Wake AI does not knowingly seek personal information from children.

Security and Changes

Wake AI uses service-provider authentication, private local storage, and platform permission controls to help protect app data. No app, device, or network can be guaranteed to be completely secure. Wake AI may update this Privacy Policy as the app changes; the Last updated date shows when this policy was revised.

Contact

For privacy questions or account help, contact Wake AI support at support@wakeai.app.