1. Scope
This Privacy Policy explains how VII Studio ("VeriWake," "we," "us" or "our") handles information when you use the VeriWake mobile application, the veriwake.app website and related support or account services (together, the "Service").
By using the Service, you acknowledge the practices described here. If you do not agree, do not use the Service.
2. Data kept on your device
VeriWake performs its core alarm and mission work locally. The following information is intended to remain on your device and is not part of normal cloud synchronization:
- Platform alarm registration identifiers, ringing state, mission routes, retry queues and system alarm runtime state.
- Camera, microphone, speech recognition, notification, alarm and device-control permission state.
- Platform-specific app or website limit selections, tokens and shields where those features are available.
- Temporary photos, video frames and downloaded file paths used while completing a mission.
- A drawn commitment signature and transient tutorial, presentation or UI flags.
Camera and photo missions use platform frameworks and on-device machine-learning models for verification. Mission photos and frames are not uploaded to the VeriWake backend as part of verification. On iPhone, spoken missions use Apple's speech recognition. VeriWake requests on-device recognition when supported; otherwise recognition may use Apple's speech service.
3. Account and cloud data
VeriWake can be used with an Apple or Google sign-in. When you authenticate, we receive provider credentials needed to verify your sign-in and create or connect a VeriWake account. We may store:
- Your name, verified email address, authentication provider and provider account identifier.
- A VeriWake user identifier, device identifier and rotating session credentials.
- Alarm definitions, including a stable UUID, name, enabled state, local time, time zone, repeat schedule, mission configuration, selected items and sound.
- Settings such as app language, time zone, mission window, pause-during-mission preference and strict mode.
- Allowed onboarding answers, your reason for waking up, routine and wake-up events or results. Your drawn commitment signature stays on the device and is not synchronized.
Access and refresh tokens are stored using secure platform credential storage, including the iOS Keychain on iPhone. Long-term synchronized account data is stored through our own VeriWake backend. The app loads local data first and attempts authentication and synchronization afterward.
4. Analytics and attribution
Installation and onboarding analytics
VeriWake records the first time an app installation is opened and may record app opens, foreground activity, onboarding progress, step completion, permitted answers stored as single values and authentication completion. This helps us understand where onboarding is unclear or fails.
This data can include an installation UUID, session UUID, device model, operating system and version, app version and build, selected app language, locale and IANA time zone. Collection starts before sign-in. After successful VeriWake account sign-in, installation and onboarding records can be linked to your account using the device identifier. These records exclude your drawn signature, permission state, photos, camera or biometric data and arbitrary device settings.
Meta App Events and advertising attribution
The app uses Meta App Events and platform attribution services for install and activation measurement. On iPhone, these can include SKAdNetwork, Aggregated Event Measurement and an advertising identifier only after the permission required by Apple's App Tracking Transparency framework. You can review advertising permissions in system settings.
Website data
This static website does not require an account and does not set a first-party advertising cookie in its current implementation. Hosting providers may still process standard request data such as IP address, user agent, timestamps and requested paths for delivery, security and operational logs.
5. How we use information
We use information only as reasonably necessary to:
- Schedule alarms, route required missions and verify completion.
- Display your wake-up history, streaks, achievements, routine and settings.
- Authenticate your account, maintain secure sessions and restore supported data on a new device.
- Synchronize user-directed changes, resolve conflicts and prevent deleted alarms from returning.
- Provide support, diagnose defects, protect the Service and prevent abuse.
- Understand aggregate installation and onboarding performance and measure advertising attribution where permitted.
- Comply with legal obligations and enforce our Terms of Use.
7. Retention and deletion
We retain account information while your account is active and as needed to operate the Service. Security, transaction or legal records may be kept for a limited period when required by law or necessary to resolve disputes and prevent fraud.
You can request account deletion inside VeriWake under Settings → Account → Delete Account. The app first requests deletion from the VeriWake backend, then removes local alarm registrations, account data and supported local records. You can also follow the steps on our Delete Account page.
Deleting a VeriWake account does not automatically cancel a store subscription. Subscription management and cancellation are handled separately through the store account used for the purchase.
8. Your choices and rights
Depending on where you live, you may have rights to request access, correction, deletion, restriction, portability or an explanation of information associated with you. You may also object to certain processing or withdraw consent where processing relies on consent.
- Change camera, microphone, speech, notification, tracking and other system permissions in your device settings.
- Sign out from VeriWake to end the current account session on the device.
- Delete individual alarms or other supported content in the app.
- Delete the full account in the app or contact us for assistance.
We may need to verify your identity before fulfilling a request.
Children
VeriWake is not directed to children who cannot legally consent to use of the Service in their jurisdiction. If you believe a child provided personal information without appropriate consent, contact us so we can review and delete it where required.
International processing
Your information may be processed in countries other than the one where you live. Where required, we use appropriate safeguards for cross-border processing.
9. Changes to this policy
We may update this policy as the Service, providers or legal requirements change. We will post the revised policy here and update the effective date. Material changes may also be communicated in the app or by other appropriate means.
10. Contact
For privacy questions or requests, email contact@veriwake.app. For technical problems, visit VeriWake Support.