Privacy Policy

The short version

Your WiseWake routine stays on your device.

WiseWake works without a WiseWake account or cloud service. Alarm schedules, reminders, wake-mission progress, Morning Launchpad entries, and streak history are processed and kept on your device. The app does not transmit this information to WebziteAi or SafeNet Creations.

What the app processes

Information used on your device

WiseWake processes the following only to provide features you select:

• Alarm names, times, repeat schedules, enabled state, and selected wake mission.
• Reminder titles, optional notes, schedules, completion state, and snooze state.
• Wake-mission progress and local alarm-occurrence history.
• Morning Launchpad entries, including water confirmation, stretch or breathing progress, your main task, intention, and local wake streak.
• Device time, time zone, notification status, and alarm-permission status needed to calculate and diagnose local schedules.
• New step changes during an active Walk 12 mission, when you grant Physical Activity access on Android or Motion & Fitness access on iOS.

WiseWake does not use step information for advertising, profiling, medical diagnosis, fitness scoring, or sale. It is used to show progress toward the Walk 12 wake mission you selected.

Access you control

Device permissions

Alarms and reminders

To schedule time-sensitive alarms you create. Android may provide special exact-alarm and full-screen alarm access. On supported iOS versions, WiseWake uses Apple’s system alarm authorization.

Notifications

To present reminders, their Done or Snooze actions, and alarm notifications on supported fallback paths.

Physical Activity / Motion & Fitness

Requested only when Walk 12 is selected, so the app can count new steps while that mission is active.

Android foreground alarm resources

Foreground service, wake lock, sound, and vibration help keep an active alarm visible and audible until it is stopped or reaches its safety timeout.

You can change permissions in system settings. Removing a permission may stop the related feature from working. WiseWake provides recovery guidance and does not bypass your operating-system choices.

Local by design

Storage and operating-system backups

WiseWake stores current app data in its private local storage. It normally remains until you delete the relevant item, clear WiseWake’s storage through device settings, or uninstall the app.

The current Android release disables operating-system backup and device transfer for WiseWake app data. On iOS, WiseWake data may participate in Apple device backup depending on your iCloud or computer-backup settings. WiseWake does not operate or access Apple’s backup service; Apple handles those backups under its own terms and privacy policy.

Current mobile release

Data collection, sharing, and tracking

The current WiseWake app:

• Does not send personal data or app activity to the publisher or support team.
• Does not contain advertising or cross-app tracking technology.
• Does not sell or share user data with data brokers or advertisers.
• Does not create an online account or maintain a remote user profile.
• Does not use a third-party app analytics or crash-reporting service.

Apple and Google may process store downloads, purchases, device backups, or platform diagnostics under their own policies. That platform activity is not collected through a WiseWake-operated app service.

Only when you contact us

Email support

WiseWake has no in-app support form or support account. If you choose to email info@safenetcreations.com, SafeNet Creations will receive the email address, message, attachments, and ordinary email metadata you provide. This information is used to investigate and respond to your request and to protect the support service.

Email is handled by the sender’s and recipient’s email providers. Do not send passwords, payment-card details, health records, or sensitive text from your alarms, reminders, tasks, or intentions. You may request deletion of a support conversation, subject to security, legal, and record-keeping obligations.

Static public information

This website

These WiseWake information pages are static and do not contain analytics, advertising, account registration, or a contact form. They do not set a WiseWake analytics or advertising cookie.

The pages are hosted using Google Firebase Hosting. Google may process technical request information, such as an IP address, browser information, and security or delivery logs, to provide and protect the hosting service under Google’s applicable terms and privacy policy.

You remain in control

Deleting WiseWake data

Delete individual alarms and reminders using their controls in the app. To remove all locally stored WiseWake data, clear the app’s storage in Android system settings or uninstall WiseWake. On iOS, uninstalling removes the app’s local container; platform backups may remain according to Apple’s backup settings and retention rules.

WiseWake currently has no online account or publisher-held app database, so there is no remote WiseWake account record to delete. See the separate email-support section for support correspondence.

Practical safeguards

Security

WiseWake uses the operating system’s private app container and permission model. No local storage method is guaranteed to be completely secure, particularly on a compromised or shared device. Avoid putting highly sensitive information in alarm names, reminders, main tasks, or intentions if someone with device or notification access could see it.

General utility

Children

WiseWake is a general alarm and morning-routine utility. It is not designed as a service directed specifically to children and does not knowingly collect children’s information through an app server.

Policy administration

Changes and contact

This policy may be updated when WiseWake’s features or legal obligations change. The public page will show a revised effective date. Features such as accounts, cloud sync, analytics, subscriptions, advertising, or online AI would require this policy and the relevant store disclosures to be updated before release.