Privacy Policy

Developer: Dzianis Huletski

Country: Poland

Contact: d.h.emservice@gmail.com

WakeUp (“the App”) is a mobile alarm application for iPhone designed to help users wake up by combining alarms with cognitive and physical missions, followed by an optional wake-check. This Privacy Policy explains what the App stores, what permissions it uses, how alarm-related data is handled, and what remains on your device.

By using the App, you acknowledge that you have read this Privacy Policy.

1. What the App Does

WakeUp is designed to help users wake up more reliably by combining alarm ringing with short in-app tasks such as math, shake, QR or barcode scanning, and follow-up wake checks. The App may also store alarm schedules, user preferences, mission settings, and wake-up statistics for personal use inside the App.

2. Local-First Storage

The current product architecture is designed primarily around on-device storage. Alarm data and related settings are stored locally on the user’s device using app-local persistence. Depending on the version and features used, locally stored data may include:

• alarm configurations, including time, repeat pattern, sound, and mission settings;
• snooze preferences and wake-check settings;
• local alarm session history and wake-up statistics;
• streaks, success rate, dismiss timing, and similar personal progress metrics;
• subscription or premium access state as needed for app functionality;
• app onboarding status and reliability-related preference choices.

This data is generally stored only on your device unless future cloud or account-based features are introduced.

3. Notifications and Alarm Scheduling

The App uses iOS local notifications to schedule alarms, snooze reminders, and wake-check prompts. These notifications are created on your device through Apple’s notification framework and are necessary for core App functionality.

The App may recalculate and reschedule pending notifications when alarms are created, edited, deleted, or when the app returns to the foreground. This scheduling behavior is required because iOS imposes a limit on the number of pending local notifications an app can maintain.

4. Motion and Fitness Access

The App may request access to motion-related device data in order to power specific missions such as shake tasks, step-based tasks, or similar movement-triggered wake-up actions.

This access is used only to support the mission types you choose to enable.

5. Camera Access

The App may request camera access in order to support QR code, barcode, or photo-based missions. For example, the user may need to scan a code in another room or complete a location-based wake-up task.

Camera access is used only when you choose a mission type that requires it.

6. Audio Playback and Alarm Sounds

The App may use audio playback capabilities in order to play alarm sounds while the app is active in the foreground or background, subject to iOS system rules and limitations. Alarm sound files bundled inside the App may be used for this purpose.

The App does not need to upload your personal content for alarm playback. Audio settings are handled locally on the device.

7. No Account Required

The current architecture does not require users to create an account in order to use the App’s core alarm features. You can generally use the App without creating a user profile or providing a username and password.

8. Payments and Subscriptions

The App may offer free and premium functionality. If paid subscriptions or in-app purchases are introduced or enabled, billing, renewals, cancellations, and purchase restoration are handled through Apple’s App Store systems.

We do not collect or store your full payment card details.

9. Analytics and Tracking

At the time of this policy, the product description does not require advertising SDKs or third-party tracking for its core experience. The App is intended to focus on alarm functionality, wake-up tasks, and local progress tracking.

If analytics, advertising, or cross-app tracking features are added in a future version, this Privacy Policy will be updated accordingly, and any required platform disclosures or permissions will be implemented.

10. Crash Reporting

No external crash-reporting provider is required by the described MVP architecture. If a crash-reporting or diagnostics service is introduced later, this Privacy Policy will be updated before or when that change takes effect.

11. Data Retention

Alarm settings, local statistics, mission preferences, and app state are retained on your device until you delete them, reset the App, or remove the App from your device, subject to normal iOS storage behavior.

12. Deleting Your Data

You can remove alarms, change their settings, reset progress data if such a feature is provided, or uninstall the App. Removing the App may delete app-local data from your device, subject to iOS behavior and any device backups you maintain.

13. Children’s Privacy

The App is not specifically directed to children as a primary audience. We do not knowingly design the App to collect personal information from children through account creation or direct data submission as part of its core function.

14. Security

We take reasonable steps to reduce unnecessary data exposure by keeping core alarm and mission data local to the device where possible. However, no method of storage or transmission can be guaranteed to be completely secure.

15. Future Features

If future versions introduce account sync, cloud backups, cross-device functionality, remote notifications, or server-based analytics, this Privacy Policy will be updated to explain what additional data is processed, where it is stored, and how it is used.

16. International Use

The App may be used internationally. If future online features are introduced, data processing may occur in jurisdictions outside your country depending on the hosting or infrastructure used at that time.

17. Changes to This Privacy Policy

We may update this Privacy Policy from time to time. If we make material changes, we may revise the effective date above and publish the updated version on the App’s legal page.

18. Contact

If you have questions about this Privacy Policy, you can contact:

Dzianis Huletski
Poland
d.h.emservice@gmail.com