Legal

Privacy Policy

ReelBlink reminds you to blink while you watch short videos. It measures blinks with the front camera on your device only, and it keeps your statistics in a database on your phone.

App: ReelBlink (Android)
Package: com.classhai.make_blink
Developer: vikasBuildsApp (Vikas Bharat Yadav)
Contact: vikasBuilds.ofc@gmail.com
Effective date: August 6, 2026
Last updated: August 6, 2026

1. Summary

Camera frames are analysed on-device by Google ML Kit and immediately discarded. They are never recorded, stored, or transmitted.
Your blink counts, session times, streaks, settings and daily summaries are stored only on your phone. They are never uploaded.
You do not need to give us anything to use the app. Guest mode is one tap, creates an anonymous account with no name and no email address, and unlocks the whole app. Google Sign-In is optional.
ReelBlink has no application server and no custom backend. The only records that exist off-device are Firebase Authentication sign-in records.
ReelBlink shows no advertisements, contains no advertising SDK, does not use AdMob, and does not collect an advertising ID. It sells no data.
What does leave your device: sign-in, YouTube video streaming and playlist metadata, remote configuration, crash reports, and basic app-usage analytics. Each is described below.

2. Data we collect

2.1 Personal information

Data	Source	Where it goes	Why
Anonymous user ID (guest mode)	Firebase Authentication anonymous sign-in	Firebase Authentication	Lets you use the whole app without giving any personal information
Google account ID token → Firebase user ID (UID)	Google Sign-In (optional)	Firebase Authentication (Google servers)	To identify your account across reinstalls and devices
Email address, display name, profile photo URL	Google Sign-In / Firebase Authentication (optional)	Your Firebase Authentication user record on Google servers	Standard Google Sign-In account record
Display name (only)	Firebase Authentication	Copied into the local database on your phone	Shown in the Profile tab

Guest mode collects no personal information at all — the account record is an identifier and nothing else.

If you do choose Google Sign-In, the app's own code reads and displays only your display name. It does not read, store, display or transmit your email address, profile photo, contacts, phone number or Google account password. Your email address and photo URL exist in the Firebase Authentication user record because Google Sign-In creates that record; they are not used by the app and are not copied to your device's database.

2.2 Data stored only on your device

All of the following is written to a local SQLite database (makeblink, managed by the Drift library) inside the app's private storage and is never uploaded:

Users: Firebase UID, display name, guest flag, account creation timestamp.
Settings: break interval and hold time, blink-detection sensitivity, theme, language, age band, reminder on/off and reminder times, streak-protection toggle, video-cut toggle, per-screen camera toggles ("Smart Blink Detect"), a custom YouTube playlist ID if you paste one, onboarding completion, file names of custom voice cues.
Daily summaries: one row per day — total seconds, camera-on/camera-off seconds, blink counts by source (reel, reminder, exercise, game), blinks-per-minute, exercises completed, session count, reminders shown, and the age band snapshot.
Per-item statistics: internal counters that order the animated items on the blink-break screen.
Playlist cache: YouTube video ID, title, channel name, thumbnail URL and duration of videos in the playlist, plus the fetch timestamp (refreshed at most every 24 hours).
Video reports: if you tap "Report" on a video, the video ID and a timestamp are logged locally only. This log is not transmitted anywhere.
Custom voice clips: if you record or import a reminder voice cue, the audio file is written to the app's private documents directory. Only the file name is stored in settings. Clips are played back on the device and are never uploaded.

2.3 Camera data

The front camera is used only for on-device blink detection, and only on the screens where you have enabled "Smart Blink Detect" (Reel, blink reminder, eye exercises, blink game). All camera toggles are off by default; the camera is never used until you grant the Android camera permission through the in-app explanation screen.
Each frame is passed to the bundled Google ML Kit face-detection model, which runs entirely on your device (no network call, no model download at run time). The app reads only the estimated eye-open probability for each eye and the head-yaw angle.
Frames are discarded immediately after analysis. They are not written to storage, not shown to anyone, and not transmitted. There is no code path in the app that can save or send a camera frame.
Camera processing runs at a throttled rate (about 4 frames per second during playback, 15 during breaks) and stops when you change tab or the app goes to the background.
If you decline camera access, the app still works: blink reminders and exercises fall back to timers.

2.4 Microphone data

The microphone is used only if you choose to record a custom reminder voice cue in Profile → Settings. Recording is limited to 5 seconds, saved as an AAC/M4A file in the app's private documents directory, played back locally, and deleted when you replace or reset the clip.
You may instead import an existing audio file through the Android system document picker. The app receives only the file you pick; it never browses your storage.
No microphone data is transmitted. There is no background or continuous audio recording.

2.5 Data we do not collect

ReelBlink does not access or collect: location (precise or coarse), contacts, calendar, SMS, call logs, phone number, photos or the media library, health-connect or fitness data, installed-app lists, biometric identifiers, or an advertising ID. It contains no advertising SDK and no attribution or marketing SDK.

3. Authentication

ReelBlink uses Firebase Authentication with two sign-in methods:

Guest (anonymous) sign-in — one tap on the login screen. Creates a Firebase anonymous account with no personal information: no name, no email address, no photo. Every feature of the app works in guest mode.
Google Sign-In (optional) — the google_sign_in SDK obtains a Google ID token, which the app exchanges for a Firebase credential. The app requests only the default sign-in scopes (basic profile and email); it does not request access to Gmail, Drive, YouTube account data, contacts, or any other Google service. Signing in with Google adds account features such as keeping your calendar and history across reinstalls and devices.

You can upgrade a guest account to a Google account at any time; the account ID is preserved, so your on-device data survives the upgrade.

There is no custom backend server. No credential, token, blink statistic or other personal data is sent to any server operated by the developer. Firebase Authentication (Google LLC) is the only identity service involved, and the Google ID token is exchanged directly between your device and Google.

Google Sign-In use complies with the Google API Services User Data Policy, including the Limited Use requirements: data obtained through Google Sign-In is used only to authenticate you into the app, is not transferred to others, is not used for advertising, and is not read by humans.

4. Google / Firebase services used

4.1 Services present in the app

Service	Used for	Data involved
Firebase Core / Installations	Initialises the other Firebase SDKs	Firebase installation ID (a resettable app-instance identifier), app and device metadata
Firebase Authentication	Guest sign-in and optional Google sign-in; account deletion	UID, provider, sign-in timestamps, IP address at sign-in, and — for Google sign-in only — email, display name and photo URL
Firebase Analytics	App-usage measurement only	Automatically collected events (first open, session start, screen views) plus, from this app, `screen_view` events emitted by the navigation observer. No custom events are logged. Analytics collects an app-instance ID, device model, OS version, app version and coarse location derived from IP. It does not collect an advertising ID (see 4.3)
Firebase Crashlytics	Crash and fatal-error reporting	Stack traces, exception messages, device model, OS version, app version, and a Crashlytics installation UUID. No custom keys or user identifiers are set by the app
Firebase Remote Config	Reads two values: the default YouTube playlist ID and the YouTube Data API key	The device fetches configuration; standard Firebase installation and device metadata is sent with the request. No user content is sent
Google ML Kit Face Detection	On-device blink detection	Runs fully offline with a bundled model; no data leaves the device
YouTube IFrame Player API + YouTube Data API v3	Video playback and playlist metadata	See section 5

Analytics and Crashlytics collection are disabled in debug builds and enabled in release builds.

4.2 Firebase services not used

The app does not use Firebase Cloud Messaging (push notifications), Cloud Firestore, Realtime Database, Cloud Storage, Cloud Functions, Firebase Performance Monitoring, App Check, Firebase ML, AdMob, or Google Ads. All notifications in the app are local notifications scheduled by your device; no notification is ever sent from a server.

4.3 No advertising identifier

ReelBlink shows no advertisements, contains no advertising SDK, and does not monetise through advertising.

The advertising-related permissions that the Firebase Analytics SDK would otherwise contribute — com.google.android.gms.permission.AD_ID, android.permission.ACCESS_ADSERVICES_AD_ID, android.permission.ACCESS_ADSERVICES_ATTRIBUTION and com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE — are removed from the app's manifest, and Analytics is additionally configured with google_analytics_adid_collection_enabled set to false. The advertising ID is therefore not requested and not collected.

5. Third-party services and network endpoints

Endpoint	What is sent	Notes
`https://www.googleapis.com/youtube/v3/playlistItems`, `/videos`	Playlist ID, an API key from Remote Config, your device's IP address and standard HTTP headers	Read-only. No user data, no account information and no watch history is sent. The app never calls `search.list`
`https://www.youtube.com` (IFrame Player API inside a WebView, plus YouTube's own video/CDN requests)	Whatever your device sends when loading a YouTube embed: IP address, user agent, the video being played, and cookies YouTube sets in the app's WebView	Video playback is provided by YouTube. Google's Privacy Policy and the YouTube Terms of Service apply to that playback
Firebase endpoints (`firebaseinstallations.googleapis.com`, `identitytoolkit.googleapis.com`, `firebaseremoteconfig.googleapis.com`, `firebase-settings.crashlytics.com`, `app-measurement.com` and related)	Authentication requests, configuration fetches, analytics events, crash reports	Operated by Google LLC
`https://www.instagram.com/vikasbuildsapp`	Nothing — the app only hands the URL to your browser or the Instagram app when you tap the Support link	Opened externally

Because ReelBlink plays YouTube videos and uses the YouTube API Services, by using ReelBlink you are also agreeing to the YouTube Terms of Service, and Google's data handling is described in the Google Privacy Policy. Both links are also available inside the app, on the Privacy policy screen.

6. Android permissions

6.1 Declared by the app

Permission	Required?	Why
`android.permission.INTERNET`	Required	Sign-in, YouTube playback and Firebase
`android.permission.CAMERA`	Optional	On-device blink detection. Requested only from the "Smart Blink Detect" screen, which explains the use before the system dialog appears. The app is fully usable if you decline
`android.permission.POST_NOTIFICATIONS`	Optional	Android 13+ runtime permission for local eye-care reminders. Requested when you turn reminders on in Settings
`android.permission.RECORD_AUDIO`	Optional	Recording your own reminder voice cue in Settings. Requested only when you tap Record

6.2 Added by libraries (merged manifest)

These are contributed by the SDKs the app depends on, not requested by app code, and none of them show a runtime prompt:

android.permission.ACCESS_NETWORK_STATE — network availability checks.
android.permission.WAKE_LOCK, android.permission.VIBRATE — scheduled local notifications.
com.google.android.providers.gsf.permission.READ_GSERVICES — Google Play services.
android.permission.USE_BIOMETRIC, android.permission.USE_FINGERPRINT — declared by the AndroidX Credentials library used by Google Sign-In. The app itself never invokes biometric authentication.
com.classhai.make_blink.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION — an internal AndroidX broadcast-receiver guard.

6.3 Permissions deliberately removed

The following are contributed by dependencies and are stripped from the app's manifest, so they do not ship in the released app:

com.google.android.gms.permission.AD_ID, android.permission.ACCESS_ADSERVICES_AD_ID, android.permission.ACCESS_ADSERVICES_ATTRIBUTION, com.google.android.finsky.permission.BIND_GET_INSTALL_REFERRER_SERVICE — advertising and install-attribution, contributed by Firebase Analytics. The app has no ads (see 4.3).
android.permission.READ_EXTERNAL_STORAGE — contributed by the file-picker library. The app only ever opens the Android system document picker, which needs no storage permission.

No location, contacts, calendar, SMS, phone, media-library, background-location, "all files access", accessibility-service or device-admin permission is declared, at any level.

7. Local storage on your device

Store	Contents
SQLite database `makeblink` (Drift, schema version 14)	Everything listed in section 2.2, in the app's private storage
App documents directory	Custom reminder voice clips you record or import
Firebase SDK storage	Sign-in token cache, Remote Config values, queued analytics events and pending crash reports, held by the Firebase SDKs in the app's private storage
WebView storage	Cookies and site data set by YouTube during playback, in the app's private WebView profile

Everything above is inside the app sandbox and is removed when you uninstall the app or clear its data.

8. Encryption in transit

All network requests made by the app use HTTPS/TLS: YouTube Data API calls, the YouTube player WebView, Google Sign-In, and every Firebase SDK connection. No cleartext-traffic exemption or custom network-security configuration is present in the app, so Android's default block on cleartext HTTP applies.

Data stored on the device is protected by Android's app sandbox and by the device's own full-disk/file-based encryption. The app does not apply an additional layer of encryption to its local database.

9. Data retention

On-device data (statistics, settings, voice clips, playlist cache, report log): kept until you delete your account in the app, clear the app's data, or uninstall the app. The playlist cache is refreshed at most once every 24 hours and is replaced when you switch playlists.
Firebase Authentication account: kept until you delete it (in-app "Delete account", or by contacting us).
Firebase Analytics — event data: retained for 2 months.
Firebase Analytics — user data: retained for 14 months, and the retention period resets on new activity from the same user.
Firebase Crashlytics crash reports: retained in line with the Firebase Crashlytics and Google data-retention policies; this project sets no custom retention period.

10. Your rights and choices

Use the app without an account of any substance: guest mode collects no personal information. Google Sign-In is optional.
Delete your account and data in the app: Profile → Delete account. This deletes your Firebase Authentication account and erases every local row tied to it (user record, settings, daily summaries, per-item statistics). If you signed in with Google, you may be asked to sign in again first, which Google requires for recent-login verification.
Delete data by uninstalling: uninstalling ReelBlink removes all on-device data.
If you have already uninstalled the app and want your sign-in record removed, email vikasBuilds.ofc@gmail.com from the account's email address; we will delete it within 30 days. See also the account deletion page.
Revoke ReelBlink's access to your Google account at myaccount.google.com/permissions.
Turn off the camera: each camera use is a separate toggle in Profile → Settings, and Android's system settings can revoke the camera permission at any time. The app keeps working without it.
Turn off notifications: Profile → Settings, or Android's app notification settings.
Data portability / access: all of your activity data is on your device; we hold no server-side copy of it to export.
Depending on where you live, you may have additional rights under the GDPR, the UK GDPR, the CCPA/CPRA or India's DPDP Act (access, correction, erasure, objection, complaint to a supervisory authority). Email vikasBuilds.ofc@gmail.com to exercise them.

11. Children's privacy and family use

ReelBlink is designed for users of all ages. It provides blink reminders, blink games, eye exercises, and the option to use your own YouTube playlist.

Children should use ReelBlink under the supervision of a parent or legal guardian where appropriate. ReelBlink is not designed exclusively for children and is not a Designed for Families app.

What this means in practice for a younger user:

Guest mode collects no personal information — no name, no email address, no photo. It is the recommended way for a child to use the app.
No advertising, no advertising SDK and no advertising ID (section 4.3).
The camera never records anything. Frames are analysed on the device and discarded, and every camera use is off by default until a parent or user turns it on and grants the permission.
Videos come from YouTube. Playback happens inside an embedded YouTube player, and YouTube's own data handling applies to it (section 5). A parent or guardian who wants control over what is shown can set a specific playlist in Profile → Settings.

If a parent or guardian believes a child has signed in with a Google account and wants that record removed, email vikasBuilds.ofc@gmail.com and we will delete it within 30 days.

The app asks for an age band (used only to pick the healthy blink-rate reference for that age). That value is stored on the device and is never transmitted.

12. Security

Camera and microphone data are processed on the device; there is no upload path for either.
Health, blink and usage statistics never leave the device, so there is no server-side store of them to breach.
All network traffic uses HTTPS/TLS; cleartext HTTP is blocked by the platform default.
Local data lives in the app's private sandbox, protected by Android's app sandbox and device encryption.
Release builds are signed with a private release key that is not stored in the source repository.
Authentication is delegated entirely to Firebase Authentication and Google Sign-In; the app never handles or stores a password.

No system is perfectly secure, and we cannot guarantee absolute security of information transmitted over the internet.

13. Health and wellness disclaimer

ReelBlink estimates a blink rate and compares it to a published reference range for your age. This is a wellness estimate, not a medical diagnosis. ReelBlink does not detect, diagnose, treat or prevent any condition. For anything concerning your eyes, consult a qualified medical professional.

14. Changes to this policy

We may update this policy when the app changes. The updated version will be posted at this URL with a new "Last updated" date, and the in-app copy (Profile → Privacy policy) will be updated in the same release. Material changes will be highlighted in the app or the Play listing's release notes. Continued use of the app after an update means you accept the revised policy.

15. Contact

Email: vikasBuilds.ofc@gmail.com
Developer: vikasBuildsApp (Vikas Bharat Yadav)
Instagram: @vikasbuildsapp
Account deletion page: reelblink.pages.dev/site/account-deletion.html