What you should knowNullWave uses Accessibility to detect and limit short videos. Statistics and settings are stored on your device; Android may back them up according to your settings. The app includes Google AdMob, so some advertising data is processed off your device. You do not need to create a NullWave account.
01. Scope and purpose
This policy applies to the NullWave Android app developed by tlongz5 and this policy page. NullWave helps you set short-video limits, track view counts and estimated watch time, view statistics, maintain daily goal streaks, and stop watching when you reach your chosen limit.
This policy explains data access, use, retention, and sharing. Reading this page does not grant Android permissions or replace any separate consent required when the app requests permissions or processes data that requires consent.
02. Permissions, APIs, and device settings
REQUIRED FOR AUTOMATIC COUNTING AND BLOCKING
Accessibility service · AccessibilityService
After you enable the service in Android Settings, NullWave receives window-change, content-change, and scroll events. It identifies the foreground app's package name and reads the interface structure, element IDs, text, content descriptions, and element states provided by Android in supported apps.
This information helps distinguish short-video areas from other screens, identify new videos, avoid duplicate counts, and estimate watch time. The service may run while the NullWave interface is closed and you are using another app. Supported platforms include YouTube, TikTok, Instagram, Facebook, and certain other social platforms.
When you reach your limit, NullWave may display a counter or pause screen over the app you are using and perform the Back or Home action. These overlays use the accessibility service's capabilities.
Text provided by Android may contain personal information displayed on screen. NullWave processes detection data on your device and has no mechanism to automatically send interface content, viewing history, or setup answers to the developer's servers or include them in ad requests. Local diagnostic logs are explained in section 03.
NullWave does not capture screenshots or screen recordings to detect videos. You may decline or disable the service at any time; automatic detection and blocking will not work while it is disabled.
OPTIONAL
Notifications · POST_NOTIFICATIONS
This permission allows the app to send NullWave's own notifications on Android 13 and later. The app includes a permission request and checks whether notifications are allowed. Counting and blocking currently use the accessibility interface and overlays; granting notification permission does not automatically enable a reminder schedule.
This permission does not allow access to other apps' notifications. You may decline or disable notifications and still use counting and blocking if Accessibility is enabled.
OPTIONAL
Battery settings and background operation
NullWave checks battery-saver status and whether it is exempt from battery optimization to display setup guidance. It may open Android Settings so you can choose “Unrestricted” or “Don't optimize” yourself, to reduce interruptions to the counting and blocking service.
NullWave does not change this setting automatically. This is a background-operation setting, not permission to access other apps' battery-usage history. You may leave battery optimization enabled; background reliability depends on your device and operating system.
Internet, network status, and advertising services
INTERNET and ACCESS_NETWORK_STATE support network connections and connectivity checks, including loading ads. The advertising SDK also declares AD_ID, ACCESS_ADSERVICES_AD_ID, ACCESS_ADSERVICES_ATTRIBUTION, and ACCESS_ADSERVICES_TOPICS to support identifiers, measurement, or advertising APIs on compatible devices. Actual access depends on the Android version, SDK, and privacy settings.
Included libraries also declare WAKE_LOCK and FOREGROUND_SERVICE to support background tasks when used. These technical permissions do not themselves grant access to messages, contacts, the microphone, or the camera.
NullWave does not request permissions to read SMS, call logs, contacts, the camera, the microphone, GPS location, all files, the full installed-app inventory, or Android Usage Access. However, displayed information may be accessed through Accessibility as described above, and advertising services may infer approximate location from your IP address.
03. Data processed and stored on your device
- Preferences: language, video limits, goal and platform settings, initial setup status, and whether notification permission has been requested.
- Setup answers: if you complete the questionnaire, the app stores your selections about when you tend to scroll, your most-used app, your self-estimated usage time, and your focus goal.
- Statistics: dates, counted videos, corresponding limits, views and estimated watch time per platform, current and longest streaks, and lost or restored streak status.
- Rewards: used and available wheel spins, the most recent ad-reward timestamp, bonus views, and limit-related timestamps.
- Temporary detection data: interface structure and text, and video-identification signals held in memory for counting and avoiding duplicate counts.
Settings and statistics are stored in the app's private data area managed by Android. Statistics are aggregated by day and platform; they are not a collection of downloaded video files.
Local diagnostic logs
The app writes operational logs to diagnose detection, counting, overlays, and advertising errors. Logs may contain app package names, view counts, and portions of text or identification signals obtained from the interface. They remain in the device's logging system; NullWave does not include a feature that automatically uploads these logs to the developer's servers. If you choose to send an error report or logs, that information is handled as part of your support request.
04. Advertising and Google AdMob
NullWave integrates Google Mobile Ads (AdMob), including rewarded ads for features such as earning wheel spins or restoring a streak. The SDK is initialized and may preload ads when the app opens, before you choose to watch a rewarded ad.
According to Google's documentation, data processed by the SDK may include:
- IP address, which may be used to infer approximate location.
- Interactions such as app launches, taps, and ad or video views.
- Diagnostic information and app and SDK performance information.
- Android advertising ID, App Set ID, and other device or account identifiers where applicable.
Google processes data to provide and measure advertising, perform analytics, and prevent fraud. Specific uses also depend on service configuration and applicable privacy choices. This is a separate data flow from locally stored Reels statistics.
You may choose not to watch rewarded ads. This does not mean the SDK has not connected to the network. Depending on your Android version, you can reset or delete your advertising ID and manage advertising options in your device settings.
See Google's Privacy Policy and how Google uses information from partner apps.
05. Parties that process or receive data
- Google/AdMob: processes the advertising data described in section 04. Google services may process information in multiple countries under their policies.
- Android or device-manufacturer backup services: may back up or transfer app data according to your device settings.
- Email support: when you email the developer, we receive your email address, message, and any files you choose to send. A support email template may prefill your device manufacturer, model, and Android version; you can edit it before sending. Emails are processed through your email provider and the developer's Gmail service to respond to questions, investigate issues, and handle feedback.
- Cloudflare Pages: when this page is served through Cloudflare, the provider may process IP addresses and request or connection data to deliver and protect the page. See Cloudflare's Privacy Policy.
This policy page does not embed ads, visitor analytics, data-collection forms, or externally hosted fonts. When you follow external links, the destination service's policies apply. The developer does not sell your interface content or Reels statistics.
06. Retention and backups
- Settings, setup profile, and streaks: remain in app storage until changed, reset, or deleted.
- Statistics history: keeps up to the 365 most recent daily records. When saving data exceeds this limit, older records are removed. This is a record-count limit, not automatic deletion as soon as a record becomes 365 days old.
- Daily counters and wheel spins: reset when the app processes a new day; aggregated information may remain in history or streak records.
- Detection data in memory: exists during processing; buffers may be replaced or released when the process stops. Device logs have a separate lifecycle managed by the operating system.
- Support emails: are kept for as long as needed to handle your request and follow up on related issues. Information that is no longer needed is deleted, except where retention is necessary to resolve disputes or meet legal obligations. You may request a review for deletion by email.
- Provider-held data: retention depends on the data type and the policies of Google, Cloudflare, or your backup service. See how Google retains data.
NullWave allows Android to back up app data. Depending on your device, account, and settings, preferences and statistics may be included in cloud backups or transferred to a new device. The developer does not operate a separate backup server or access backups in your account.
Uninstalling the app or clearing its storage removes the corresponding local data, but does not guarantee immediate deletion of backups, emails, or data already processed by providers. Data may be restored after reinstallation if you choose to restore a backup.
07. Data security
Local data is stored in the app's private area, subject to Android's isolation and access controls. Protection depends on device security, screen locking, the operating system, and access granted to diagnostic tools. Private app storage does not mean the app separately encrypts each data field.
Google states that data transmitted by the Mobile Ads SDK is encrypted in transit using TLS. When deployed on Cloudflare Pages, this page uses HTTPS. These measures protect transmission; no storage or transmission method can guarantee absolute security.
Please do not include passwords, verification codes, payment information, or unnecessary private content in support emails. If you send screenshots or logs, redact unrelated personal information first.
08. Your controls and data deletion
- Stop detection: Android Settings → Accessibility → NullWave → Off. Disabling the service does not automatically delete saved statistics.
- Turn off notifications: Android Settings → Apps → NullWave → Notifications.
- Change battery preferences: Android Settings → Apps → NullWave → Battery, or your device's Battery optimization settings.
- Delete local settings and statistics: Android Settings → Apps → NullWave → Storage → Clear data/Clear storage; or uninstall the app. Clearing the cache alone does not delete all statistics.
- Manage backups: use the backup or account settings on your device or in your backup service.
- Advertising data: use Android's advertising options and Google's privacy tools. Deleting an advertising ID does not mean all data previously processed by the SDK has been deleted.
- Support data: request access to, correction of, or deletion of information you have sent by emailing btlong2610@gmail.com. We may need to verify that you are the person making the request.
Menu names vary by manufacturer and Android version. NullWave does not provide an online account that needs separate deletion; the developer cannot remotely read or delete information stored only on your device. Requests to exercise other rights under applicable law may be sent to the contact address below.
09. Children's data
NullWave does not require a date of birth to use video counting. If you are a parent or guardian and believe a child has sent personal information to the developer, please contact us to request a review and appropriate handling of that information. Do not send a child's identity documents or identifying information unless requested for an appropriate verification purpose.
10. Changes to this policy
This policy is updated when features or data practices change. The update date appears at the top of the page. Changes requiring notice or separate consent must be handled through an appropriate in-app flow; updating this page does not replace permission or consent requests.