Wakebound
English

Wakebound privacy

Clear information about your data.

This page describes the current Wakebound product and the services configured for its release.

Who runs Wakebound

Publisher and contact

Publisher
OPTIMUMTECH FUSION SRL
Privacy contact
contact@optimumtechfusion.com

For privacy questions, contact the publisher at this email address.

Data on your device

Local alarms and progress

Wakebound stores alarm settings, alarm labels you enter, game progress, and app settings on your device so local alarms and wake-up challenges can work. Its local notification history records alarm event times, snoozes, completion status, and the character associated with an event. Notification preferences control optional reminders, preview privacy, and character autoplay. You can export your save or remove local data from Data & storage in the app.

Local wake-up alarms do not require Firebase remote push notifications.

On iOS App Store and TestFlight builds, Firebase Cloud Messaging processes an app installation identifier and APNs/device registration tokens to route remote notifications. Wakebound can associate a registration token with its account identifier and notification preferences, including alert categories, muted rivals, preview privacy, sounds, quiet hours, and local time-zone offset. Remote rival alerts require an additional in-app opt-in and notification permission. Firebase and Apple process the notification payload for delivery; private previews omit personal details from supported payloads. Firebase may also process technical device and app metadata needed to provide its service. You can turn off Rival notifications in the app or notification permission in system settings. Account erasure deletes Wakebound’s stored tokens and preferences. Local alarms and local notification history work independently of remote delivery. TestFlight uses separate Wakebound sandbox account data. The Android launch configuration does not register for remote push.

Optional services

Account, cloud save, and Premium

If you choose an account-backed feature, such as Backup & sync or Premium purchase or restore, Wakebound uses an account identifier for that service. It is a persistent identifier and is personal data; it is not an email sign-in account.

Backup & sync is optional. When you use it, Wakebound stores one cloud save for that account so you can back up or restore your progress.

For permanent Premium purchases, Apple handles payment on iOS and Google Play handles payment on Android. Wakebound uses RevenueCat to verify the purchase and permanent Premium entitlement. RevenueCat receives the account identifier and purchase information needed for that service. Your app store shows the current local price before purchase.

Purchases and diagnostics

Information from these services

Automatic Firebase Crashlytics uploads are disabled in the current iOS release, and retained crash reports are cleared during startup. Product analytics and session replay are not enabled in this release.

The Android launch release also disables Crashlytics collection, product analytics, and remote push registration. Local alarm notifications do not require those services. It does not use the advertising ID.

RevenueCat processes purchase and entitlement information for Premium. It can also provide purchase and sales reporting for the publisher.

Social features

Wake Attacks and social controls

When you use Wake Attacks, Wakebound stores the sender and recipient, the challenge details, the difficulty and related results, and an optional preset message. Wakebound also stores social relationships, block choices, and reports so those features can work.

Reports use one of five preset reasons. The report reason does not include free text, and the person reported is not told who sent the report.

Wake Attack messages use preset messages.

Deletion and retention

What happens when you erase an account

Start account erasure from Data & storage in the app. Wakebound deletes the local account data it controls and queues the related RevenueCat erasure request. The account-erasure deployment is verified for the current release, while provider deletion can remain pending while the request is processed.

You can also request deletion of your Wakebound account and associated cloud data by emailing contact@optimumtechfusion.com with the subject “Wakebound account deletion”. Include your Wakebound account ID from Settings > Account if you still have access to the app. If you cannot open the app, explain that in your request. We may need to verify ownership before deleting an account; do not send passwords, recovery codes, or payment-card details.

Normal encrypted service backups have a 31-day retention window. A deleted account can remain in a backup for that window. Wakebound keeps limited records needed to complete an erasure request and prevent deleted data from returning after recovery.

Your choices

Export, delete, or ask a question

Provider information

Read the providers’ current notices