WAKERULE

PRIVACY POLICY

Last updated: 22 October 2026

WakeRule is an alarm app whose alarm stops only when your phone confirms you completed a task you set. Most tasks are checked entirely on your phone. A task you type in your own words is checked with the camera, by sending a few still frames about once a second to an AI service. This policy explains, in plain terms, what data that involves, who it is shared with, how long it is kept, and your choices. It is provided by NEXARLABS LTD, a company registered in England and Wales ("we").

The short version

When you save an alarm with a task typed in your own words, the text is sent to Google Vertex AI to turn it into checkpoints. When that alarm rings and you start the task, your phone sends a few still photos from the camera about once a second, through our server, to OpenAI's API, which answers whether you are doing the task. We do not keep those photos. OpenAI does not use them to train its models, but by default it may keep what we send it for up to 30 days to check for abuse, as described below. When a task you typed has to be heard — counting out loud, a phrase, humming — short clips of what the microphone hears are sent through our server to Google's Gemini to be checked, as described below. Every other mission — including the exercise presets and Shout — is checked entirely on your phone, and nothing from its camera or microphone is sent anywhere. WakeRule is for adults only. We do not show ads, sell your data, or use third-party advertising or cross-app tracking SDKs. A few technical identifiers we use to run the service, and Google's on-device libraries, are described below.

What we collect

  • Mission text — the task you type when you create an alarm. Sent to our backend and, once, when you save the alarm, to Google Vertex AI to compile it into checkpoints.
  • Camera frames — during a camera task, from the moment you tap START until the task is confirmed or the attempt ends, the app sends about once a second a small set of still JPEG images (up to five, each at most 768 pixels on its longest side, with no sound) to our backend, which passes them to OpenAI's API, together with a short description of your task's checkpoints, to verify the task. The frames are held in memory and are not saved to your phone's storage.
  • Account information — if you sign in with Google, we receive your email address, name, and a Google account identifier, and store them on our backend to sync your alarms and credit balance across devices. Sign-in is required to use AI-verified missions.
  • Purchase and credit records — if you buy a credit pack in the app, the purchase token and product identifier from Google Play, and an obfuscated account identifier (a token issued by us, not your name or email, which we also give to Google Play so a purchase can be matched to your account); if you buy one on our website, your Stripe customer identifier, the payment identifier, and which pack you bought. We also keep a ledger of the credits added to and spent from your balance. We use these to add each pack's credits exactly once, to charge for verification, and to handle refunds. We do not receive or store your card details; the payment is handled by Google Play or by Stripe.
  • Wake and attempt history — for each alarm: when it fired, when you started and finished, whether the task was verified, how long it took, and your task text. Used for your streak, statistics, daily attempt limits, and our own cost accounting. Stored on our backend.
  • Device and session metadata — a random per-install identifier (not a hardware or advertising ID), your platform and app version, your timezone (to know when your morning is), the browser or app user-agent string, and sign-in session records. Used to run your account, bind your alarms to it, and secure sign-in.

What we do NOT collect

  • Microphone audio from the on-device missions. The Shout mission is checked entirely on your device: the sound is reduced to loudness readings on the phone and is never recorded to a file, uploaded, or sent to any AI service. The camera frames sent for a camera task are still images with no sound. Typed tasks that have to be heard are the one exception, described under “Who we share it with”.
  • Anything from the on-device missions. Math, Typing, Shake, Colour Tiles, Scan a code, Item hunt, Photo, Steps, Shout, and the six exercise presets (out of bed, jumping jacks, squats, push-ups, touch your toes, stand on one leg) are verified on your phone by our own code and Google's on-device ML Kit. Their camera images, sensor readings, and sound never leave the phone.
  • No location, contacts, calendar, messages, or files.
  • No advertising, no advertising identifiers, no marketing or cross-app tracking, and no selling of your data. Some technical identifiers we do use, and telemetry from Google's on-device libraries, are described under "Device identifiers and analytics" below.

Device identifiers and analytics

We do not run advertising or product analytics SDKs, we do not use an advertising ID, and we do not profile you or track you across apps. Three technical details are worth naming plainly:

  • A per-install identifier. When you sign in, the app generates a random identifier for your installation — a random value kept in the app's private storage and deleted when you uninstall. It is not your hardware ID and not an advertising ID. It is sent to our backend on sign-in, token refresh, and alarm sync to label your device's session and bind your alarms to your account; it is never used to track you across apps.
  • What our app sends about your device. Besides that per-install identifier, our own requests include only a fixed platform value, our app's version number, your timezone, the user-agent string, and sign-in session records. We do not send your device model, manufacturer, operating-system version, phone number, hardware serial, MAC address, or any advertising identifier.
  • Google's on-device libraries (ML Kit). To start the countdown and to tell when the camera is covered, the app uses Google's ML Kit face detection, pose detection, and image labeling, which run entirely on your device — your images are not sent to Google by these libraries. ML Kit does, however, send Google diagnostic and usage data governed by Google's terms rather than ours. Google documents this as including your device manufacturer, model, operating-system version and build, a per-installation identifier Google states is not intended to identify you or your device, and API performance metrics.

Who we share it with

Google Vertex AI (Gemini) — microphone clips for a typed task that has to be heard. When a task you typed has to be heard (for example counting out loud, saying a phrase, or humming), the app records what the microphone hears while you do it, cuts it into short clips at each pause, and sends each clip through our server to Google's Vertex AI. Gemini writes down the words or names the sound it hears, and checks them against your task. The words it wrote down are sent back to your phone with the answer and sent again with the next clip of the same attempt, so a count said slowly can still be followed; they are discarded when the attempt ends. We do not store the clips or the words on our server. The same Google Cloud terms, training statement, abuse-monitoring retention and global-endpoint processing described for your typed task below apply to these clips.

MiniMax — only when Google is unavailable. If Google's service refuses a request, the text of your typed task, or the words Gemini wrote down from a clip (never the audio itself), may be sent to MiniMax's API instead, to compile the task or to check those words against it. MiniMax receives no camera images and no audio.

Google Vertex AI (Gemini) — your typed task. When you save an alarm with a task typed in your own words, the text is sent to Google's Vertex AI to compile it into checkpoints. No camera images are sent to Google. This is a third-party AI service; your data is processed under Google Cloud's terms. Google states it does not use this data to train or fine-tune its models. By default, Google's abuse-monitoring stores what customers send to Vertex AI for up to 90 days, where authorized Google staff may review flagged content; this applies to what we send it, including the microphone clips described above. We use Google's global Vertex AI endpoint, which Google states provides no data-residency or in-region-processing guarantee, so this processing may take place in any region in which Google operates. Google also applies automatic context caching to speed up similar requests, which may hold the mission text we send it for up to 24 hours before the cache expires.

OpenAI — camera frames. During a camera task, the frames described above, with a short description of your task's checkpoints, are sent to OpenAI's API (its Decisions API) about once a second to check whether you are doing the task. OpenAI processes this data for us as a service provider, under its Services Agreement and Data Processing Addendum. OpenAI states that data sent to its API is not used to train its models unless the customer explicitly opts in; we do not opt in. By default, OpenAI keeps abuse-monitoring logs, which may contain what we send it, including the images, for up to 30 days, unless longer retention is required by law or reasonably necessary to protect its services or others from harm. OpenAI limits access to that data to authorized employees and specialized contractors bound by confidentiality, to investigate abuse and misuse. OpenAI also scans images for child sexual abuse material and keeps any image its classifier flags for manual review. To speed up similar requests, OpenAI may keep encrypted data derived from a request in a cache for up to 24 hours. We use OpenAI's standard API without a data-residency setting, so this processing may take place in any region in which OpenAI operates.

Google Play, the Google Play Developer API, and Google Cloud Pub/Sub. If you buy a pack in the app, Google Play processes your payment as merchant of record and gives us a purchase token; we ask the Google Play Developer API to confirm and acknowledge the purchase, and Google Play sends us purchase and refund notifications through Google Cloud Pub/Sub. These messages carry your purchase identifiers, never your payment details.

Stripe — payments on our website. If you buy a pack on our website, the payment is processed by Stripe. You enter your card details into Stripe's payment form, not into WakeRule, and we never receive, see, or store your card number. We give Stripe your email address so it can identify you as its customer and send you receipts, and Stripe gives us back a customer identifier and a payment identifier, which we store with the pack you bought. Stripe handles your payment data under its own privacy policy, at stripe.com/privacy.

Google Sign-In. When you sign in, Google confirms your identity and gives us your Google account identifier, email, and name. We verify Google's signature but do not send your personal information back to Google to do so.

Amazon Web Services. Our backend runs on Amazon Web Services in the United States, which hosts our servers and database as our infrastructure provider.

We do not sell your data, and we do not share it with advertisers, data brokers, or analytics providers.

How long we keep it

  • Camera frames: we do not write them to disk on our backend, and the app does not save them on your phone; they exist only in memory for the moment of verification. Our server logs record that a check happened — when, how many frames, the size of the request, how long it took, and the answer (for example, whether the action matched) — never the images themselves. OpenAI's retention is described above.
  • Alarms, mission text, and compiled tasks: stored on your device, and on our backend while your account exists so they sync across your devices. Uninstalling the app removes the copies on your device.
  • Account and sync data (email, alarms synced to the backend, credit balance, sessions): kept while your account exists; when you delete your account it is anonymized and scrubbed as described below, with limited records retained. Sign-in sessions expire automatically.
  • Server logs: our server logs, which include the task text you enter, an internal account identifier, and the outcome of each camera check, are kept searchable for 30 days and in an access-restricted archive for up to 12 months, then deleted automatically.
  • Database backups: automated backups are kept for 7 days, so data you delete may persist in a backup for up to 7 days before it ages out.

How we protect your data

  • Data in transit is encrypted with HTTPS/TLS (TLS 1.2 or higher); release builds of the app refuse plain-HTTP connections.
  • Our database is a managed PostgreSQL instance whose storage is encrypted at rest, is not reachable from the public internet, and accepts only encrypted connections from our own servers.
  • Camera frames are never written to disk on our backend or saved on your phone — they exist only in memory for the moment of verification, then are discarded.
  • Sign-in tokens are stored on our backend only as one-way hashes, never in the clear; refresh tokens rotate on every use and a reused token revokes the whole chain. On your device they are kept in encrypted storage.
  • Purchases are verified with Google Play or Stripe on our servers, and credits are counted there too; the app is never trusted to grant itself credits.

Your choices and deletion

You can delete your account from within the app, or by using our account-deletion page, or by emailing [email protected]. Data stored only on your device is removed by uninstalling the app.

Deleting your account immediately anonymizes and scrubs your record: we sign you out of every session, remove your name and email, null the task text on your wake history, and delete your alarms. A few things are kept, and we want to be plain about them:

  • An identifier tied to your Google account is retained (marked deleted) so that if you ever sign in again you are recognized and not locked out.
  • Your purchase and credit records — including the Google Play purchase token or the Stripe customer and payment identifiers, and the credit ledger — are kept as financial and accounting records.
  • The timing and outcome of your past wake attempts are kept (with your task text removed), because they settle against our cost records.

Deleting your account is not a refund. Credits are bought outright, so there is nothing to cancel first, and any credits left on the account are lost when it is deleted.

We keep records of your purchases and credits — including Google Play purchase tokens, Stripe customer and payment identifiers, and our related accounting entries — for 6 years after the end of the financial year in which the transaction took place, to meet our tax and company-law obligations, even after you delete your account. The anonymized wake-attempt timing records, which we use only to reconcile our AI processing costs, contain no information that identifies you; we keep them until the relevant billing period is reconciled and in any case no longer than 24 months. We keep the purchase records because the law requires it, and where it does not strictly require them, to prevent fraud and resolve disputes; we keep the Google-account identifier to recognize a returning user. This overrides a deletion request only to the extent the law allows.

Legal basis (EU/EEA/UK users)

We process your camera frames and mission text to provide the camera-verified alarm you paid for, on the basis of performing our contract with you (GDPR Article 6(1)(b)). Verification is the service you chose and paid for, so the camera is a necessary part of it. Because verification only checks the action in front of the camera and never tries to identify who you are, we treat these images as ordinary personal data, not biometric data. We keep your purchase and accounting records to comply with our legal obligations (Article 6(1)(c)), and rely on our legitimate interests (Article 6(1)(f)) to prevent fraud, resolve disputes, and reconcile our costs.

You have the right to access, correct, delete, or export your data, to object to or restrict processing, and to complain to your data protection authority — in the UK, the Information Commissioner's Office (ico.org.uk). To exercise any of these, email [email protected].

Children

WakeRule is for adults. It is intended for people aged 18 and over, and it is declared as an adults-only app on Google Play (an "18 and over" target audience with minor access restricted), so users Google identifies as under 18 cannot download it or buy credits in it. We do not knowingly collect data from anyone under 18. If you believe a minor has used WakeRule, email [email protected] and we will delete the account and its data.

International transfers

WakeRule is operated internationally and your data is processed outside your own country. Our backend — which handles your account and sync data, purchase and credit records, mission text, and your camera frames (held in memory only, for the moment of verification) — runs on Amazon Web Services in the United States. A typed task is compiled by Google's Vertex AI using Google's global endpoint, and camera tasks are verified by OpenAI's API without a data-residency setting; neither guarantees where processing takes place. For EU/EEA/UK users, transfers to Google are governed by Google's Cloud Data Processing Addendum, transfers to OpenAI by OpenAI's Data Processing Addendum, and transfers to Amazon Web Services by the AWS Data Processing Addendum. Under each, the provider acts as our processor, and each incorporates the Standard Contractual Clauses and, for UK data, the UK International Data Transfer Addendum.

Changes to this policy

We will update this page when our practices change and revise the "Last updated" date above.

Contact

Questions or requests: [email protected] (NEXARLABS LTD, a company registered in England and Wales).