Nap & Stay Awake
Privacy Policy
Last updated: October 31, 2026
TakeKApp ("we") provides Nap & Stay Awake, an app that signals scheduled times through vibration. This policy explains information used by the app and its advertising, purchase and usage analytics services.
1. Alarms and settings stay on your device
No Nap & Stay Awake account is required. Alarm names, display messages, weekdays and times, vibration patterns, dismiss and snooze steps, and other settings are stored locally. Information needed to schedule an alarm is also passed to the device operating system. We do not send alarm-related input such as alarm names, messages, selected times, custom vibration waveform data or challenge answers. On Android, if you enter a provided access code, the code is sent to RevenueCat to verify premium access. It is not recorded in usage logs. Fixed feature categories, such as vibration modes, dismiss methods and relaxation sound types, and their usage counts may be sent as usage data described below.
Alarm names and messages may appear on the lock screen, depending on device settings. Operating system backups and restores may be subject to the settings and policies of Apple, Google or another OS provider.
2. External services and information sent
| Service and use | Information and purpose |
|---|---|
| Google AdMob / Google Mobile Ads SDK When ads are shown | May process IP addresses (including approximate location inferred from them), device and app identifiers, ad impressions and interactions, and diagnostics and performance information for ad delivery, fraud prevention and measurement. Ad personalization follows applicable regional consent and, on iOS, App Tracking Transparency (ATT) permission. If tracking is not authorized on iOS, the app requests non-personalized ads. Non-personalized ads may still process identifiers and network information. |
| Google User Messaging Platform (UMP) Region and ad consent | Uses information such as region and device details, together with consent choices, to determine which consent messages to show and whether ads may be requested. Region information also helps determine whether to ask for analytics consent. Analytics consent is handled separately from advertising consent. Consent messages and privacy choices may differ by region. |
| RevenueCat Purchase status, purchase and restore | Uses an anonymous or provided app user ID, product and transaction information, purchase history, premium entitlement status, and basic device and app information for purchase verification, restoration, entitlement management and purchase analytics. We do not register your email address as an app user ID. |
| App Store / Google Play Payment | Apple or Google processes purchases and payment details under its own policies. We do not receive your payment card number. |
| Google Analytics for Firebase Usage measurement and improvement (normally automatic) | Uses an app instance identifier, device, OS and app information, approximate location inferred from IP addresses, automatic session and purchase events, fixed screen names and categories for onboarding, permissions, alarm operations, vibration and dismiss methods, Night screen and relaxation sounds, premium views, purchases, restores and operation failures. This helps us understand usage and improve the app. Where consent is required, we ask before collection starts. Collection does not start while the region cannot be determined. Alarm names, display messages, selected times and task answers are not sent. Advertising ID analytics, ad personalization and sharing with advertising products are not enabled. |
| Cloud Firestore / Firebase Authentication Usage counters | We use an identifier generated by anonymous authentication to store daily and monthly counts of app opens, onboarding, permission setup, alarm operations, vibration and dismiss methods, Night screen and relaxation sound use, premium views, purchases and restores. The Firestore counter database is located in the eastern United States (us-east1). Counters include OS family, app version, app language, new/returning use and free/premium status. The identifier is pseudonymous rather than fully anonymized; it does not use your name or email. Counts do not represent exact people across devices or reinstalls. No sign-in screen, name or email registration is required. We do not store alarm names, messages, selected times, challenge answers or purchase receipts in these counters. |
| Firebase Crashlytics Investigating problems | Uses crash, unhandled exception and operation failure information, stack traces, device, OS and app information, and Crashlytics installation identifiers to diagnose problems and improve stability. Our added diagnostics use fixed error categories; we do not attach input content, complete exception messages or a custom user ID. SDK-generated crash reports may contain technical information required for diagnosis. |
Ads may appear on the Vibration and Settings tabs (and the recurring alarm tab on Android) and, after the device is unlocked, below dismiss, snooze and trial challenges. On the in-app ringing screen, a small banner may be requested after 20 seconds of eligible foreground display with the device unlocked and applicable consent in place. Loading may take longer. Stopping or snoozing the alarm does not require viewing an ad. Ads do not appear on the Alarm setup tab, Night screen, or full-screen editors, help, purchase or permission guides. They are not displayed while the device is locked or the app is in the background. Ads are not shown when a premium purchase has been verified. RevenueCat communication needed to verify purchases is separate from ad display.
3. Your choices
- You can allow or stop usage counters and diagnostic uploads under Settings → About the app → Usage data. An explicit opt-out from a previous version is also preserved. Stopping collection does not automatically erase previously sent information.
- When additional advertising privacy choices are required, you can review them through the advertising privacy setting. Availability and choices depend on your region and consent status.
- You can review or change tracking permission under iOS Settings → Privacy & Security → Tracking. You can use the app without allowing tracking.
- You can change alarm and notification permissions in device settings. Related features may not work without permission.
Analytics, Firestore counters and Crashlytics uploads follow the same usage data choice. Where consent is required, at most 64 action events are held only in memory before a decision and sent if you allow collection. Unsent events are discarded on refusal or app exit. Stopping collection prevents new counter uploads, discards queued action events and requests deletion of unsent Crashlytics reports. Requests already in flight may not be cancellable. Advertising and purchase processing follow their separate choices and purposes.
4. Device permissions
The app uses OS features and permissions for scheduled notifications, alarm display including lock screen presentation, vibration, background alarm operation, restoring schedules after restart, and preventing automatic lock while the Night screen is open. It does not request camera, microphone, contacts or precise location access.
5. Support information
If you email us, we use your email address, message and any device, OS or purchase information you choose to include to respond and investigate the issue. Do not send passwords, card numbers or unnecessary personal information.
6. Retention, deletion and international processing
You can manage local schedules and settings by editing or deleting them or removing the app. Also check any OS schedules and backups. Firestore counters retain counts per date and anonymous installation so that we can produce daily and monthly usage reports through administrator tools. Contact us below about deletion requests for submitted counters and diagnostics. Information already sent to external services is retained according to their retention settings and policies, the needs of purchase restoration and fraud prevention, and applicable law. Services such as Google, RevenueCat and Apple may process information outside your country.
The app does not offer a user-facing account with a name, email address or sign-in screen. It uses the anonymous authentication identifier described above to protect access to usage counters. Contact us below about access or deletion requests. Identity verification and identification of the relevant data may be necessary. Some information, including store transaction records, cannot be deleted by us.
7. Children
Nap & Stay Awake is a general audience utility and is not designed primarily for children. If we learn that personal information has been collected from a child, we will investigate and take appropriate action, including deletion where required.
8. Service policies
9. Updates and contact
We may update this policy as features or requirements change. The date above identifies the latest update. Material changes will also be communicated in the app or by other appropriate means when needed.