Wakebound privacy

Clear information about your data.

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

Last updated: 20 November 2026

Who runs Wakebound

Publisher and contact

Publisher
OPTIMUMTECH FUSION SRL
Privacy contact
contact@wakebound.app

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.

In iOS App Store and TestFlight builds and in Android release builds, Firebase Cloud Messaging routes remote notifications. Remote push stays off until you turn on Rival notifications or Offers and news in the app, and it also needs notification permission. When you turn one on, the app creates a Firebase installation identifier and a push registration token (on iOS, through APNs); Offers and news alone does this only if you already have an account. Wakebound stores the token on its server, linked to its account identifier and notification preferences, including alert categories, muted rivals, preview privacy, sounds, quiet hours, and local time-zone offset. Firebase, and on iOS 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. Turning off both Rival notifications and Offers and news deletes the token from Wakebound’s server and from Firebase; account erasure deletes it too, along with Wakebound’s stored preferences. The Firebase installation identifier itself stays on the device after you opt out. You can also turn off notification permission in system settings. Local alarms and local notification history work independently of remote delivery. TestFlight uses separate Wakebound sandbox account data.

Optional services

Account, cloud save, and Premium

Wakebound creates an account identifier the first time the app sends a finished wake-up to its server, or when you use Backup & sync or make or restore a Premium purchase or subscription. It is a persistent identifier and is personal data; it is not an email sign-in account.

Backup & sync keeps one cloud save for your account so you can restore your progress. Once the account exists, the app updates that save automatically after a finished wake-up or an Ember purchase. You can turn this off with "Back up automatically" in Backup & sync, and still back up by hand. The save holds your game progress, Embers, characters, streak and wake-up history, your app and notification settings, and your Premium, social, family and privacy settings and status in the app. It can also hold identifiers the app uses, such as the account identifier and a notification token. Alarms are not backed up. On iPhone, the account identifier and the device sign-in key are also kept in the iPhone Keychain, which iOS can keep after you delete the app. If you install Wakebound again on the same iPhone, the app uses them to offer to restore your save. If you choose "Start new", Wakebound deletes that copy. Wakebound keeps the save until you erase your account.

When your account records a finished wake-up, Wakebound's server keeps that morning's alarm settings, such as the challenge, difficulty and character you chose, and whether you snoozed, so it can work out the Ember reward. Account erasure deletes them.

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

For your account, Wakebound stores your Premium status: the plan and store, whether a subscription is active, cancelled, paused, in a billing grace period, has a billing issue, has expired or moved to another account, whether it is in a free trial, and its renewal and end dates. To decide whether to show a one-time Lifetime offer, it uses whether your trial ended without payment, whether you ever paid for a subscription, how often you close Premium screens, and when an offer was prepared, shown and expires. Account erasure deletes all of this. Erasing your account does not cancel a subscription: cancel it in your App Store or Google Play settings.

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.

The Android release also disables Crashlytics collection, clears unsent crash reports during startup, and does not include Firebase Analytics. It registers for remote push only after you turn on Rival notifications or Offers and news. Local alarm notifications do not require these services. It does not use the advertising ID.

App Store and Google Play releases that show the Share anonymous usage data setting send product analytics and crash reports to PostHog in the EU. Events describe how features are used, such as finishing a wake-up challenge or opening a screen, and when the app is opened, sent to the background or updated. Each event carries its time and a random installation identifier, plus device maker and model, operating system, app version, language and region, time zone, screen size, network type and, on Android, the mobile carrier. A crash report adds the error type, the code location and the names of the last few events before it, never the error text. Alarm events include the exact time an alarm is set to ring. For an alarm that is missed or stopped outside the app, they also include how long after that time this happened. The same connection fetches feature switches and may show a short in-app question; answering is always optional. Events never include your account identifier, name, email, alarm labels or other players' identifiers, and no person profile is created. IP addresses are discarded. Turn this off at any time in Settings, Privacy. Apple TestFlight builds send no analytics. When Share anonymous usage data is on, the same PostHog connection also records a session replay: a sequence of screenshots of how you move through Wakebound, plus the screens you open. Text, what you type, photos and images are masked, and the recording does not include where you tap, so a keyboard cannot be read back from the taps. Account, name, alarm labels, referral codes, friend and leaderboard names, and purchase screens are masked as a block as well. The recording respects the same Settings, Privacy switch: turning Share anonymous usage data off stops new events and stops the recording. PostHog Inc. processes this in the EU (Frankfurt). Recordings are kept for the retention period configured on the Wakebound PostHog project. Apple TestFlight builds and debug builds send no replay.

wakebound.app and support.wakebound.app use PostHog web analytics in the EU. What it records depends on your choice in the Cookie and privacy choices panel, described in Website analytics and your choices below.

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

Website choices

Website analytics and your choices

wakebound.app and support.wakebound.app show a Cookie and privacy choices panel on your first visit. Accept and Reject are equally easy, nothing is chosen in advance, and scrolling or continuing to use the site is not consent. Until you choose, the site behaves as if you had rejected.

If you reject, or have not chosen yet, PostHog web analytics in the EU runs in cookieless mode. It sets no cookies and keeps nothing on your device that identifies you. A visit is counted with an identifier that PostHog derives from your IP address, your browser and a secret that changes every day; the IP address itself is never stored. It records the pages you open, what you click and where on the page, how far you scroll, the site that referred you, page speed measurements and script errors, together with your browser, operating system, device type, screen size, language and time zone. No session replay is recorded.

If you accept, PostHog keeps a random identifier in a cookie and in your browser's local storage, so your later visits from this browser are linked, and it records a session replay of the pages you open: the page layout, scrolling, mouse movement and clicks. Every input and all text on the page are masked in your browser before anything is sent. On wakebound.app, Accept also turns on Google Analytics, described in the next section. PostHog Inc. processes this in the EU (Frankfurt). Recordings are kept for the retention period configured on the Wakebound PostHog project.

If your browser sends Do Not Track or Global Privacy Control, we treat it as Reject and do not load the analytics script at all, so nothing is recorded, not even a cookieless visit count. The panel does not open by itself; when you open it, it shows this state. A choice you save there applies only once the signal is off.

Your choice is kept in your browser's local storage, separately for wakebound.app and support.wakebound.app, for up to 180 days; after that the panel asks again. You can change it at any time with Cookie and privacy choices at the bottom of every page, and the change applies at once. Reject stops the replay, deletes what PostHog stored in your browser and returns to cookieless counting. It does not erase data already sent; to ask for that, contact us at the address at the top of this page.

Optional website Google Analytics

Updated October 31, 2026. On wakebound.app, Google Analytics 4 is optional and off until you choose “Accept” in the Cookie and privacy choices panel. Rejecting is equally available. No Google analytics script or request is sent before acceptance. This applies to the marketing website only; it does not enable Firebase Analytics in the mobile apps or add Google Analytics to this support site.

If you accept, Google receives page views, App Store / Google Play click intent, browser and device information, and your IP address as part of the connection. We send page paths without query strings or fragments, and only the referring site's origin. First-party Google Analytics cookies identify a browser for up to 90 days; we do not send account IDs, email addresses, purchase details, or link these records to PostHog or RevenueCat users. Advertising storage, Google Signals and advertising personalization are disabled. Automatic form, download, scroll and outbound-link measurement is off. A store click does not prove an install or purchase.

You can refuse or withdraw at any time through “Cookie and privacy choices” in the wakebound.app footer. Withdrawal stops subsequent GA4 measurement and removes its first-party cookies; it does not erase data already processed by Google. The same choice also decides whether PostHog keeps an identifier and records session replay, as described above. We remember only your choice and its date in local storage for up to 180 days. Do Not Track or Global Privacy Control keeps Google Analytics off even if a prior choice was accepted.

Google may process data outside your country. Read Google's privacy policy and how Google uses information from partner sites. Contact contact@wakebound.app about privacy rights and requests.

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.

You can choose a display name. Any player can see it, and can find you by typing its first letters (at least three) in search. It appears on the global ranking if you joined it, on Wake Attacks, rivalries, friend requests and family invites, and on your friends' and family members' screens. Without a name you appear as player- followed by six characters, and search cannot find you. Offensive names and names that copy Wakebound or its staff are refused, and a moderator can remove a name. After your first change, you can change it once every 7 days. When you change your name or delete your account, a keyed fingerprint of the old name is kept for 30 days so no one else can take it at once. The fingerprint cannot be turned back into the name, and after account deletion it is not linked to you. A report about you keeps the name you had when it was filed. Deleting your account deletes your name and every report you filed or that is about you. When a moderator removes a name, it is held for good as a keyed fingerprint, so no one can pick it again. We also keep a record of the decision: the name, the date, the reason and who decided. The app shows you that decision and how to challenge it. The name is deleted from the record after 6 months. The rest stays while your account exists, so a person can see repeated breaks of the name rules. Deleting your account deletes the record.

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.

When a friend joins with your invite link, Wakebound records the link between the two accounts, and the inviter sees the friend's display name and whether they have completed the qualifying wake-ups. Invite rewards are Embers and Premium time. Account erasure deletes your invite code and those links.

Wake Attack messages use preset messages.

Children

Children under 13

Wakebound is for people aged 13 and over. We do not knowingly collect personal data from children under 13.

Before Rivals opens, the app may ask for your birth month and year. If the answer is under 13, Rivals, player names and invite links stay closed. Your answer stays on your device and is never sent to us.

If you believe a child under 13 has given us personal data, email contact@wakebound.app and we will delete it.

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@wakebound.app 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. For 30 days it also keeps a keyed fingerprint of a deleted display name, not linked to you, so no one else can take that name at once.

Your choices

Export, delete, or ask a question

  • Export your save from the app’s Data & storage screen.
  • Use the in-app Data & storage controls to delete local data or erase an account and cloud data. Use Backup & sync to turn automatic backup off.
  • For a privacy question, use contact@wakebound.app.

Provider information

Read the providers’ current notices