Blinkly Privacy Policy

Last updated: November 13, 2026

This Privacy Policy describes how the Blinkly mobile application for Android and iOS (the “Application”), operated by Sergey V. (the “Service Provider”), processes and shares information. Blinkly provides eye-exercise routines, 20-20-20 break reminders, progress tracking, achievements, and a virtual garden. It is a wellness application, not a medical device, diagnostic service, treatment, or method of vision correction.

Privacy summary: Blinkly keeps exercise history, reminders, progress, and preferences on your device. A Google account is optional: signing in starts synchronization of your exercise history, achievements, reminder schedules, and app preferences with Google Cloud Firestore. Firebase Analytics is enabled by default in release versions and can be turned off in Settings. Firebase Crashlytics reports crashes and technical errors independently of that switch. Yandex Mobile Ads provides contextual inline banners on the Achievements and Garden screens. Blinkly does not send your detailed exercise history, reminder schedules, or account information to advertising or analytics services.

1. Information Stored on Your Device

Blinkly stores the following information to provide its features:

Core exercise, progress, and local reminder features do not require a Google account. Not signing in prevents account-based cloud synchronization; it does not disable the separate analytics, crash-reporting, or advertising services described below.

2. Optional Google Sign-In and Cloud Synchronization

If you choose Google Sign-In in Settings, Google Sign-In and Firebase Authentication process your authentication information. Blinkly receives your Firebase account identifier and, when available, your display name and email address. Google also processes technical connection information, including IP addresses, for authentication and abuse prevention. Blinkly does not receive your Google password. Authentication credentials and session persistence are managed by the native Google and Firebase SDKs rather than stored in Blinkly's exercise database or app preferences.

Successful sign-in immediately starts synchronization. You can subsequently use “Sync now” in Settings. The cloud copy is associated with your Firebase account identifier and contains:

Cloud Firestore stores this information on the Service Provider's behalf so you can restore and synchronize data across devices. Your email address and display name are not included in the exercise-and-settings snapshot. The usage-analytics switch is device-local and is not synchronized. Synced exercise and reminder information may reveal your wellness routines. Blinkly does not provide end-to-end encryption of the cloud copy.

3. Information Not Requested and Device Permissions

Blinkly does not ask for your date of birth, phone number, contacts, photos, payment information, medical records, diagnoses, or symptoms. It does not use the camera or microphone to track your eyes, and it does not read Apple Health or Health Connect records. Location tracking is disabled in the advertising configuration; the Application does not request device-location permission. Network providers may still infer a general region from an IP address.

If you configure reminders, Blinkly requests notification permission where required. On Android 12 and newer, it also requests the separate exact-alarm access needed for precise reminder scheduling. Reminders are scheduled locally through the operating system, and Android may restore scheduled reminders after a reboot or app update. Notification content may appear on your lock screen according to your device settings. You can manage these permissions in system settings; denying them limits reminder delivery but does not prevent use of the exercise and progress features.

4. Advertising, Analytics, and Crash Diagnostics

Yandex Mobile Ads SDK

Blinkly displays contextual adaptive inline banners on the Achievements and Garden screens on Android and iOS. The Application sends an ad-unit identifier with each ad request, without exercise, reminder, achievement, garden, account, or synchronization data. It configures the SDK with user consent set to false and location tracking disabled. The current version has no in-app advertising consent dialog or advertising opt-out switch.

The SDK may independently process IP addresses, device and application information, SDK-generated identifiers, and ad impressions, interactions, and diagnostic information to deliver and measure ads, prevent fraud, and operate its services. Android excludes the Advertising ID permission, and iOS does not request App Tracking Transparency authorization or access to IDFA. These restrictions do not mean that all SDK identifiers or network processing are disabled. AppMetrica components are included as dependencies of Yandex Mobile Ads; Blinkly does not activate AppMetrica as a separate product-analytics service or send Blinkly product events to it.

Google Analytics for Firebase

Usage analytics is enabled by default in release versions. You can turn it off or on in Settings under Privacy using the “Anonymous analytics” switch. Although this is the switch's name, SDK data is not necessarily anonymous: Google Analytics uses an app-instance identifier and processes device and application information and automatically collected events. It may derive coarse geographic information from network data.

Blinkly's own analytics events cover only these coarse actions and categories:

These events do not include individual exercise details, stored completion timestamps, reminder dates or times, account identifiers, email addresses, achievement unlocks, garden state, free text, or exception details. Blinkly does not set Analytics User-ID or custom user properties. Advertising ID collection, iOS Analytics IDFV collection, and advertising-personalization signals are disabled. Debug builds disable Analytics collection.

Turning the switch off disables further Analytics collection. It does not reset the app-instance identifier, erase previously collected server data, or disable Firebase Authentication, Cloud Firestore synchronization, Crashlytics, or Yandex Mobile Ads. The setting applies separately on each device.

Firebase Crashlytics

Blinkly uses Firebase Crashlytics for crashes and caught technical errors. Reports may include stack traces, exception types and messages, crash timestamps, device and app information, and SDK-generated installation and session identifiers. Blinkly does not attach exercise history, reminder schedules, account details, achievement or garden data, custom user identifiers, or content logs and custom content keys. Exception messages can contain runtime diagnostic details. When Analytics is enabled, its events may also be included as crash-report breadcrumbs.

Crash reporting operates independently of the Analytics switch. Reports can be held locally for later upload when a network connection becomes available.

More information about the providers' processing is available here:

5. Purposes of Processing

6. Legal Bases and Your Choices

Where applicable law requires a legal basis, the basis depends on the purpose: providing the functionality and optional synchronization you request; legitimate interests in reliability, security, and supporting the Application through contextual advertising where permitted by law; compliance with legal obligations; or consent where required and validly obtained. This Policy does not itself constitute consent. An opt-out switch does not replace prior consent where the law requires it.

You can use the core features without signing in, disable Analytics, and change notification permissions. The current version does not provide an in-app account-deletion control or a separate switch for crash reporting or advertising. To exercise additional privacy rights, contact the Service Provider using the address below.

7. Data Sharing

The Service Provider does not sell your exercise history, reminder schedules, or account information. Information is processed by Google for the Firebase and Google Sign-In services and by Yandex for advertising as described above. Cloud synchronization data is not supplied by Blinkly for ad targeting or product analytics. These providers may use subprocessors and partners under their applicable terms and policies. Information may also be disclosed when required by law or necessary to address fraud, security threats, or legal claims.

If you contact the Service Provider, your contact details and message are processed to respond to your request. Please do not include passwords, authentication tokens, or medical records.

8. Retention and Deletion

Local records remain until removed through supported app functions, device-storage controls, or uninstallation, subject to operating-system backup and restore behavior. Uninstalling the Application or clearing its local data does not delete a Firestore cloud copy or Firebase Authentication account. Synchronizing again may restore cloud records.

Cloud snapshots are retained to support future synchronization until replaced through sync or deleted following a verified request; the current version does not implement automatic expiry of inactive cloud snapshots. To request deletion of your Blinkly Firebase account and associated Firestore data, email the contact address below from the Google account email used for sign-in, where possible, and specify the request. Reasonable verification may be needed. Avoid signing in or synchronizing again while deletion is being handled to prevent data from being uploaded again. Deletion of Blinkly data does not delete your Google account.

According to Google's published policy, Crashlytics retains crash traces and associated identifiers for 90 days before starting removal from live and backup systems. Firebase Authentication retains account information until deletion is initiated, with removal from live and backup systems within 180 days after that; logged authentication IP addresses are kept for a few weeks.

Analytics retention depends on the Service Provider's Google Analytics property settings and Google's policies; standard aggregated reports may be retained separately from user-level and event-level data. Yandex retention follows its applicable policies and legal obligations. Disabling Analytics does not itself delete server data. Privacy requests can be sent to the Service Provider; requests concerning information independently controlled by Google or Yandex may also require contacting the relevant provider.

9. International Transfers

Google, Yandex, and their service providers may process information outside your country. Applicable transfer safeguards depend on the service, destination, and law, and are described in the relevant providers' privacy and data-processing terms.

10. Security

Blinkly uses local app storage and the authentication and encrypted network connections supplied by its platform and service integrations. Cloud data is associated with your authenticated account. Cloud synchronization is not end-to-end encrypted by Blinkly. No storage or transmission method can guarantee absolute security; protect access to your device and Google account.

11. General Audience and Children's Privacy

Blinkly is a general-audience wellness application and is not restricted to adults aged 18 or older. It does not ask for a date of birth, determine a user's age, or provide a verified parental-consent flow. The advertising configuration does not currently distinguish child users from other users. The data processing described in this Policy may therefore occur without Blinkly knowing a user's age.

Google account use is also subject to Google's applicable age and parental-supervision rules. Parents or guardians with concerns about a child's information can contact the Service Provider to request review or deletion, subject to appropriate verification. Where applicable law requires parental authorization for processing children's data, publication of this Policy does not replace that authorization.

12. Your Privacy Rights

Depending on where you live, you may have rights to access, correct, receive a copy of, or delete personal data; restrict or object to processing; withdraw consent where processing relies on it; and complain to a data protection authority. Contact the Service Provider to make a request. Withdrawal does not affect the lawfulness of processing before withdrawal. SDK-generated data may not be directly identifiable from your email address, so additional information or provider-specific procedures may be needed to locate it. Never send your password or authentication tokens for verification.

13. Changes to This Policy

This Policy may be updated when the Application, integrations, or data practices change. The revised version will carry an updated date, and material changes will be communicated where required by applicable law.

14. Contact Us

For questions or privacy requests related to Blinkly, contact Sergey V. at info@sedsoftware.com.