Summary
Hi Eye is local-first and does not require an account.
Version scope: the released Android/iOS version 0.2.0 (36) does not include Firebase Analytics or Crashlytics. The Analytics and crash-reporting sections below apply to the 0.2.1 Android/iOS update when that version is installed; publishing this policy does not itself update your app. Hi Eye's web and desktop builds do not initialize these app reporting services.
In the 0.2.1 mobile update, usage analytics is optional and off until you allow it. Crash reports are collected automatically and independently of that choice.
Reminder settings, theme preferences, selected sound, local alert state, and daily stats remain stored locally. The mobile update may send the limited usage events and diagnostics described below to Google Firebase; it does not upload full settings or progress history.
Hi Eye does not include advertising or payment features in these versions, sell personal data, or use this information for advertising or cross-app tracking.
Information We Do Not Collect
The Hi Eye app does not automatically collect names, email addresses, phone numbers, contacts, precise location, photos, audio recordings, camera images, health records, or payment information. Information you choose to send by email is handled as described under Support and Feedback.
Hi Eye does not upload complete settings, exact timer schedules, break history, or daily stats to a BaTip app backend. In the 0.2.1 mobile update, optional usage analytics can record limited app actions using fixed feature identifiers and coarse duration categories, as described below.
Information Stored on Your Device
Hi Eye may store the following information locally on your device:
- Reminder interval
- Break duration
- Theme preference
- Reminder delivery choices, selected sound, and local alert state
- Daily stats such as breaks completed, focus time, and streak
This local data provides the app features. Full local records are not sent to BaTip servers. Limited setting-change events, such as the chosen sound's fixed identifier, may be sent to Firebase only while optional usage analytics is enabled in the 0.2.1 mobile update.
Backups and Device Transfer
For local timer, settings, and progress records, Hi Eye has no app backend and does not provide app-managed cloud sync. There is no BaTip-operated app backend for syncing those records. Firebase reporting in the 0.2.1 mobile update is a separate Google-operated service described below.
The Android app disables cloud backup and device-to-device transfer for its app-owned local data.
On iOS, local preferences stored by the app may be included in an operating-system-managed iCloud or device backup according to your Apple device and backup settings. This is managed by Apple and your device, not by Hi Eye or BaTip, and BaTip cannot access that backup.
Support and Feedback
Hi Eye does not send support data automatically. If you choose Send feedback or contact support by email, your email app or email provider sends the message only after you choose to send it.
BaTip receives the sender email address, message, attachments, the app version and build number prefilled by Hi Eye, and any device or operating-system details you choose to include. This information is used only to respond, troubleshoot the reported issue, improve support, and maintain an appropriate support history; it is not used for advertising or tracking.
Support correspondence is retained only as long as reasonably necessary for those purposes or to meet legal obligations. You may request access, correction, or deletion by emailing nguyenanhtiep12@gmail.com. BaTip will honor the request unless applicable law permits or requires the information to be retained.
Notifications
Hi Eye may ask for notification permission so it can remind you to take an eye break.
Notifications are optional. If you turn reminders off or deny notification permission, the app can still be used as a timer and break guide.
On Android, Hi Eye may restore local reminders after your device restarts and may use vibration for eye break reminders when your device supports vibration. These features run locally on your device and do not send settings or stats to BaTip.
Use Alarm is off by default. Only when you explicitly enable Use Alarm for audible session-ending alerts does Hi Eye try native Alarm delivery where the system supports and authorizes it. If Use Alarm is off, Alarm access is unavailable, or native Alarm scheduling fails, Hi Eye attempts a local notification instead when notification permission and system delivery settings allow it. Hi Eye does not request Alarm access from app launch, timer Play, or the Work reminder bell.
On iOS 26 or later, enabling Use Alarm may request separate AlarmKit authorization. On Android, enabling Use Alarm may request exact-alarm access; while delivering an exact alarm, Hi Eye may use the alarm audio stream and vibration, run a bounded foreground service, and briefly hold a wake lock while the alert is sounding. Exact deadlines and reminder payloads stay on your device. The 0.2.1 mobile update may record bounded setting changes and permission-flow outcomes only while optional analytics is enabled; these are not used for advertising, cross-app tracking, or remote messaging.
Hi Eye does not use notification permission for advertising or tracking.
Device Permissions
Hi Eye uses notification permission for local reminders. It requests the platform's separate Alarm authorization only after you explicitly enable Use Alarm, and uses native Alarm delivery only while that setting remains on and access is available. On iOS 26 or later, this uses AlarmKit. On Android, local session-ending Alarm delivery may use an exact alarm, a bounded foreground service, vibration, and a brief wake lock; restart recovery may restore eligible local reminders. If Use Alarm is off or unavailable, Hi Eye attempts local notification delivery when notification permission and system delivery settings allow it.
Hi Eye does not request access to your camera, contacts, precise location, photos or videos, microphone, or health records.
Optional Usage Analytics — Mobile Version 0.2.1
Firebase Analytics (Google Analytics 4) helps BaTip understand which features are used and where app flows can be improved. It is off by default, including after an upgrade, until you explicitly allow it. You can change your choice at More → Privacy → Help improve Hi Eye. Declining the once-only invitation does not limit the timer or reminders.
While enabled, Analytics may receive logical screen views, accepted Work/Rest timer starts and actions, observed timer completion, rest-entry and completion-screen acknowledgements, selected setting changes such as sound choice, permission-flow outcomes, and reminder-related entries observed by the app. Custom parameters use fixed feature identifiers, bounded values, and coarse duration categories. A timer finishing or an acknowledgement does not prove a person rested, heard a sound, or received a reminder.
The SDK also processes automatic app/session and engagement events, an SDK-generated app-instance identifier tied to this app installation, and technical information such as app version, platform, operating system, and language. Google may derive an approximate country or region from network information such as the IP address. Hi Eye does not request GPS or device-location permission for Analytics. This data is not represented as anonymous or identifier-free.
Hi Eye does not send support email or message contents, free text, complete settings snapshots, full progress/history, exact reminder deadlines, notification bodies, health feedback, or an app-assigned user ID. Advertising-ID collection and advertising consent are disabled. Hi Eye does not enable Google Signals, advertising personalization, or advertising-account linkage for this measurement.
Turning this choice off stops future app-event forwarding, disables Analytics collection, and resets supported local Analytics state. Events from before permission are not saved for later replay. A local reset cannot retract data already transmitted and does not turn off Crashlytics. Analytics may buffer permitted data locally while offline and send it later.
Automatic Crash Reports — Mobile Version 0.2.1
Android and iOS release builds of the 0.2.1 update use Firebase Crashlytics automatically to help diagnose crashes and selected unexpected operational failures. There is no separate in-app crash-reporting switch. The Help improve Hi Eye switch controls usage analytics only. Web and desktop builds do not initialize these app reporting services.
Reports may include stack traces, app version/build, device model and operating system, app/device state, timestamps, and Firebase-generated installation and session identifiers. Hi Eye adds fixed diagnostic categories, such as an operation code or build mode. App-recorded Dart exception messages are replaced with the error type; native crash reports can still contain information generated by the operating system or native libraries.
Hi Eye does not intentionally attach email, support text, reminder payloads, exact schedules, full settings snapshots, progress/history, health feedback, or an app-assigned user ID. Analytics breadcrumbs may accompany a crash only when usage analytics is enabled. Reports are for reliability, not advertising, and are not described as anonymous.
Diagnostics can be buffered locally while offline and sent later, including after relaunching following a crash. Timer and reminder operation does not depend on a successful upload.
Third-Party Services
The released 0.2.0 (36) mobile app does not include Firebase Analytics or Crashlytics. The 0.2.1 mobile update includes Firebase Core, optional Firebase Analytics, automatic Firebase Crashlytics, and their supporting installation/session services. These reports are processed by Google and made available to BaTip for the purposes above. Hi Eye does not provide account login or app-managed cloud sync.
Google may process data on servers outside your country under its applicable terms and safeguards. Provider details are available at https://firebase.google.com/support/privacy and https://policies.google.com/privacy.
Platform services such as Google Play, Apple App Store, and operating-system notification services may process information under their own privacy policies.
Children
Hi Eye is a general-audience wellness utility and is not directed specifically to children under 13. The app does not knowingly collect personal information from children.
Data Retention
Local app data remains on your device until you delete it, clear app data, or uninstall the app.
For the 0.2.1 mobile update, the dedicated Hi Eye Analytics property's event/user retention is set to two months, with reset on new activity off. This setting applies to relevant event/user-level data; it does not mean every aggregate standard report is deleted after two months.
Firebase states that Crashlytics retains crash stack traces and associated identifiers for 90 days before starting removal from live and backup systems. Uninstalling Hi Eye or turning Analytics off does not delete reports already sent.
For access, correction, or deletion requests, email nguyenanhtiep12@gmail.com. BaTip will assess available provider controls and applicable obligations. Because Hi Eye has no account and does not attach an email to telemetry, we cannot promise to identify an individual report from an email address alone. Support correspondence follows the separate retention described above.
Because Hi Eye does not provide accounts, there is no account deletion flow.
Security
Hi Eye keeps its local settings and stats using standard platform storage. The reporting services described for the 0.2.1 mobile update use encrypted connections. No storage or transmission method can be guaranteed completely secure.
Translations
If this Privacy Policy is translated into other languages, the English version controls in case of any inconsistency.
Changes to This Policy
This policy distinguishes the released 0.2.0 (36) app from the 0.2.1 mobile Analytics/diagnostics update. If data practices change again, BaTip will update this policy and the applicable store declarations before distributing that change.
Contact
If you have questions about this Privacy Policy, contact:
nguyenanhtiep12@gmail.com