Boo Alarm Privacy Policy
Android last updated: October 13, 2026; iOS app / website last updated: June 12, 2026
This Privacy Policy explains how Tengen Labs LLC handles information in Boo Alarm. The Android and iOS sections below describe each platform. Boo Android does not require an ordinary in-app account or an email address to use the app. Local app records and information processed by service providers are described separately.
Android: information on your phone
Boo stores your name or nickname, onboarding selections, alarm configuration, preferences, wake-up history, streaks and mission progress on your phone. Some information derived from these features is also used in app-usage events and provider records described below. Local storage does not mean that all information about using those features stays on the phone.
For example, the Android app records the length of a supplied nickname in a usage event, rather than including the nickname itself in that event. It also records selected mission types, repeat-day selections and counts, alarm actions, and mission completion and duration. Certain onboarding events record that a question was answered without including the answer.
Android: camera and optional system access
Camera-based missions use camera frames for on-device ML Kit processing. The explicit mission-completion event records mission type, queue count and duration; it does not include camera frames, images, pose coordinates or repetition counts. ML Kit can separately process device, app, installation and feature-diagnostic information. On-device camera analysis should not be understood as a promise of no SDK diagnostics.
Notifications and full-screen alarm access support alarm presentation. Distraction Block uses separately authorized accessibility, usage access and overlay access to identify and cover selected apps during a block. Selected package identifiers and the most recently observed foreground package are stored locally by that feature. Its explicit analytics events report selection counts and block-usage information. Commitment Lock is not enabled for normal release builds.
Android: analytics, attribution, subscriptions and notifications
Boo's configured Android providers include PostHog for product analytics, AppsFlyer for attribution and marketing measurement, RevenueCat for subscriptions and access, and OneSignal for notification messaging. Their processing can include installation or advertising identifiers, IP addresses, device and app metadata, app interactions, subscription and entitlement information, and notification tokens and properties. IP information can be used to derive approximate location.
The app links provider-generated identifiers across subscription, attribution and notification integrations. These are pseudonymous identifiers; they should not be described as completely anonymous or impossible to associate with an installation. Some app usage concerns exercise missions and their completion or duration.
Configured RevenueCat integrations can forward subscription events and attributes to AppsFlyer, OneSignal, PostHog and Superwall, subject to the integration's applicable identity and platform conditions. AppsFlyer's configured Android TikTok integration can forward install and selected app/subscription events, including values and revenue for applicable subscription events. The Android app does not display third-party advertising; attribution and marketing measurement remain separate data uses.
These client SDKs can initialize when the app runs. Disabling notification permission controls notification delivery; it does not turn off analytics, attribution or subscription processing. The app currently has no general SDK analytics/attribution opt-out control.
Android: purchases and reviewer access
Google Play processes Android purchases. RevenueCat validates and manages subscription and entitlement access. Boo does not receive full payment-card details. Manage or cancel a subscription through Google Play using the purchasing account. Uninstalling Boo does not cancel a subscription.
The reviewer-access flow sends the installation's current RevenueCat app-user identifier and an access credential over HTTPS to Boo's reviewer service. That service verifies access and reads or grants the named entitlement through RevenueCat. It stores minimal operation receipts, including the installation identifier, requested entitlement, campaign, expiry and operation status, to handle retries and confirm access. The service's provider API key is not included in the Android app. Reviewer access does not require a personal purchase or ordinary Boo account.
Android: retention and data requests
Local app data remains on the phone until removed, including by uninstalling the app. Provider records are separate from local data and are retained under the relevant service arrangements and policies. Removing local data does not automatically delete provider records or subscription history.
Reviewer operation receipts are retained through the review campaign plus 90 days. This is separate from the fixed entitlement-access expiry and other provider retention rules.
For privacy inquiries or a data request, contact info@tengenlabs.com. Say that you use Android, your app version, whether the installation is still available, and whether your request concerns local records, provider records or subscription cancellation. Do not send camera images, full device logs, payment details, passwords or reviewer credentials. Locating pseudonymous provider records can require additional information and verification. We will explain which records we can identify and any applicable retention. Uninstalling alone does not establish deletion of provider records.
Android: security, rights and audience
Boo's reviewer endpoint uses HTTPS, protected server configuration and minimized request logging. Provider connections have their own security arrangements.
Boo is intended for teens and adults aged 13 and over. Some teens may be treated as children under rules applicable in their country. Privacy rights and required consent depend on applicable law; contact info@tengenlabs.com with an inquiry.
Provider information
iOS app / website
This Privacy Policy explains how Tengen Labs LLC (“Tengen Labs,” “we,” “us,” or “our”) handles information in the Boo Alarm mobile application (the “App”). Boo Alarm is designed to keep your data on your device: we do not operate user accounts, we do not ask you to sign in, and we do not collect your name or email address. Almost everything stays on your iPhone.
1. Who we are
- Entity: Tengen Labs LLC
- Product: Boo Alarm
- Postal address: c/o Republic Registered Agent LLC, 5830 E 2nd St Ste 7000, Casper, WY 82609, USA
- Privacy contact: info@tengenlabs.com
2. Information stored on your device (we do not receive it)
The following is created and stored only on your device. It is not sent to us or to any server, and we cannot see it:
- The display name and onboarding answers you enter (such as your wake-up goals and habits).
- Your alarms, the missions you choose, your wake-up history, streaks, and badges.
- Your in-app preferences, including theme.
You can remove all of this at any time by deleting the App from your device.
3. Camera and photos — processed on your device only
Some wake-up missions (for example, push-ups, squats, or photographing an object, pet, the sky, grass, or your made bed) use your device camera. This camera and image processing happens entirely on your device using Apple's on-device Vision framework. Camera frames and images are never uploaded to us or to any third party, are not stored, and never leave your device.
4. Information collected automatically
Analytics (anonymous). We use PostHog (hosted in the United States) to understand how the App is used so we can fix bugs and improve features. PostHog collects product-interaction events (such as which missions are used), app-lifecycle events, and basic diagnostic data (app version, device model, operating system version), tied only to a randomly generated analytics identifier.
These analytics are anonymous. We do not attach your name, email, or any account identifier to them — the App has no account and collects no email. We do not use this data for advertising, and the App does notrequest permission to track you across other companies' apps or websites.
Purchases. Purchases are processed by Apple through the App Store and validated using RevenueCat (our subscription infrastructure provider). We receive your subscription and entitlement status (whether Boo Alarm Pro is active) so the App can unlock and restore your subscription, tied to an anonymous RevenueCat identifier. We do not receive or store your full payment card details.
Notifications. We use OneSignal (hosted in the United States) to send push notifications, such as wake-up check reminders and occasional subscription-related messages. If you allow notifications, OneSignal receives a push token from Apple along with basic device data (such as device model, operating system version, language, time zone, and IP address), tied to the same randomly generated identifier used for your subscription (see Purchases above) — not your name or email. The App still has no account and collects no email. Push notifications are optional: you can turn them off at any time in iOS Settings.
5. How we use information
- Operate the App on your device and unlock Boo Alarm Pro features.
- Validate and restore your subscription.
- Send push notifications you have allowed, such as wake-up reminders and subscription-related messages.
- Understand anonymous, aggregate usage so we can fix bugs and improve the App.
- Detect, prevent, and address fraud, abuse, and security issues.
- Comply with legal obligations.
We do not sell your information, and we do not use it for advertising.
6. How we share information
We do not sell your personal information. The only parties that receive any data are:
- Apple — App Store and In-App Purchases.
- RevenueCat — purchase validation and subscription management.
- PostHog — anonymous product analytics (see Section 4).
- OneSignal — push notifications and subscription-related messaging (see Section 4).
- Legal and safety — where required by law, or to protect the rights, safety, and security of users, the public, or Tengen Labs.
- Business transfers — in connection with a merger, acquisition, or sale of assets, subject to this policy.
These providers act as our service providers, are permitted to use the data only to provide services to us, and are contractually required to provide the same or equal level of protection of your information as set out in this Privacy Policy and as required by applicable law and the App Store Review Guidelines.
7. International data transfers
Our analytics and notification providers (PostHog and OneSignal) process data in the United States. Where required for the limited data described above, we rely on appropriate safeguards such as the EU Standard Contractual Clauses for transfers out of the EEA/UK.
8. Data retention and deletion
Data stored on your device remains until you delete it or delete the App. Deleting the App removes the App's on-device data from your device. Anonymous analytics events are retained by PostHog for a limited period for product analysis; because they are not linked to your identity, they cannot be traced back to you individually. We operate no account and store no personal profile on our servers, so there is no server-side account to delete.
9. Your privacy rights
Because the App has no account and we do not collect information that identifies you, we generally cannot link the limited, anonymous data we receive to a specific person, and we may be unable to locate “your” data on request. The personal data the App holds lives on your device and is under your control — you can delete it by deleting the App.
Depending on where you live, you may have rights to access, correct, delete, or port personal data, to object to or restrict processing, and to withdraw consent. To ask a question or exercise a right, contact info@tengenlabs.com. EEA/UK users also have the right to lodge a complaint with their local data protection authority.
We do not sell or “share” personal information as defined by the CCPA/CPRA, and we will not discriminate against you for exercising any right.
10. Legal bases for processing (EEA/UK users)
Where the GDPR or UK GDPR applies, we rely on:
- Performance of a contract — to provide the App and process and restore your purchases.
- Legitimate interests — to secure, maintain, and improve the App through anonymous analytics, where not overridden by your rights.
- Consent — where required; you may withdraw consent at any time.
- Legal obligation — to comply with applicable law.
11. Security
We use technical and organizational measures designed to protect information, including on-device storage and encryption in transit (HTTPS) for analytics and purchase validation. No method of transmission or storage is completely secure, so we cannot guarantee absolute security.
12. Children's privacy
Boo Alarm is not directed to children under the age of 13 (or the higher minimum age required in your country, such as 16 in parts of the EEA). We do not knowingly collect personal information from children under that age. If you believe a child has provided us information, contact us and we will address it.
13. Third-party services and links
The App relies on the third-party services listed in Section 6, which have their own privacy practices:
- Apple: apple.com/legal/privacy
- RevenueCat: revenuecat.com/privacy
- PostHog: posthog.com/privacy
- OneSignal: onesignal.com/privacy_policy
We are not responsible for the privacy practices of these third parties.
14. Website and Android waitlist (booalarm.app)
This section covers the booalarm.app website, which is separate from the App described above. Browsing the website does not require an account.
If you choose to join the Android waitlist, we collect the email address you submit. We use it only to email you if and when Boo Alarm becomes available on Android, and for related launch updates. We do not sell it or use it for advertising.
- Processor: Resend stores the waitlist email on our behalf — resend.com/legal/privacy-policy
- Unsubscribe: use the link in any email we send, or write to info@tengenlabs.com and we will remove you.
- Legal basis (EEA/UK): consent, which you may withdraw at any time.
15. Changes to this Privacy Policy
We may update this Privacy Policy from time to time. We will revise the “Last updated” date above and, for material changes, provide additional notice in the App or by other means. Your continued use of the App after changes take effect constitutes acceptance.
16. Contact us
Tengen Labs LLC
Privacy questions: info@tengenlabs.com
Postal address: c/o Republic Registered Agent LLC, 5830 E 2nd St Ste 7000, Casper, WY 82609, USA