Privacy Policy

Ember: Digital Wellbeing  ·  Last updated: March 2026  ·  Effective date: March 2026

Ember is a fully offline application. We do not collect, transmit, store, or share any personal data with any server, company, or third party — ever. All data generated by your use of Ember stays on your device and only your device.

This Privacy Policy describes how Ember ("we", "our", "the app") handles information in connection with your use of the Ember: Digital Wellbeing Android application (the "App"). Please read it carefully.

By installing or using the App, you agree to the practices described in this policy. If you do not agree, please uninstall the App.

1. Who We Are

Ember is an independent Android application developed and maintained by an individual developer. We are not a company, corporation, or data-processing organisation. There is no backend server, no user account system, and no cloud infrastructure associated with this App.

Developer contact:
For any privacy-related questions, requests, or concerns, please contact:

Email: techtowndevelopers@gmail.com
App name: Ember: Digital Wellbeing
Platform: Google Play Store

2. Summary — What We Do and Do Not Do

Activity Ember's practice
Collect personal data ❌ Never
Transmit data to any server ❌ Never — app is fully offline
Sell data to third parties ❌ Never
Share data with advertisers ❌ Never — no ads, no ad networks
Use analytics SDKs (Firebase, Mixpanel, etc.) ❌ None integrated
Require account creation ❌ No accounts of any kind
Read notification content or messages ❌ Never — count only
Read what you do inside other apps ❌ Never
Access contacts, camera, microphone, location ❌ Not requested, not used
Store usage data locally on device ✅ Yes — for app functionality only
Use internet connection ❌ Never — no internet permission

3. Data Collected and How It Is Used

Ember collects only the minimum data necessary to provide its core functionality: calculating your daily mental energy (Fire Battery) and helping you understand your digital habits. All data is stored exclusively in the App's private local database on your device using SQLite (via the Drift library). It is never transmitted anywhere.

3.1 Data You Provide Manually

3.2 Data Collected Automatically (with Permission)

Screen Time / App Usage Data

Permission required: Usage Access (android.permission.PACKAGE_USAGE_STATS) — a Special App Access permission granted manually by the user in Android Settings.

What we read:

What we do NOT read:

Purpose: This data is used exclusively to calculate the Fire Battery score and display usage statistics within the App. It is processed locally on your device and never leaves it.

Storage: Aggregated daily totals are stored in the App's local SQLite database. Raw event data is not stored — only computed totals.

If permission is denied: The App functions with reduced accuracy. You can manually adjust your sleep slider, and the battery score will rely only on your manual inputs.

Notification Count

Permission required: Notification Listener Service (android.permission.BIND_NOTIFICATION_LISTENER_SERVICE) — a Special App Access permission granted manually by the user in Android Settings.

What we read:

What we do NOT read:

Our notification listener service is intentionally minimal. It increments a counter by 1 each time any notification arrives and immediately discards all other notification data. The source code for this service (CampfireNotificationListenerService) is available for inspection.

Purpose: The daily notification count is used as one input in the Fire Battery algorithm. High notification volume is a documented contributor to cognitive overload and digital burnout.

Storage: Only the daily total count is stored in the App's local SQLite database. Individual notification events are never stored.

If permission is denied: The notification count will show as 0 and will not contribute to your battery score. All other features continue to work normally.

3.3 Data Collected by Background Sync

Ember uses Android WorkManager to run a background task approximately every 6 hours. This task performs the same usage stats collection described in Section 3.2 while the app is not open. It runs entirely on-device with no network access. No data is transmitted during or after background sync.

3.4 Data We Do NOT Collect

The following categories of data are never accessed, collected, or processed by Ember under any circumstances:

4. Local Data Storage

All data generated by your use of Ember is stored in the App's private application directory on your Android device using SQLite (via the Drift database library). This storage is:

⚠️ Important: Because Ember stores all data locally and disables cloud backup, your data will be permanently and irrecoverably deleted if you uninstall the App, clear the App's data in Android Settings, or perform a factory reset without a local device backup. Ember displays this warning prominently at first launch and in the Settings screen.

What is stored locally

Data typePurposeRetention
Daily records (screen time, notif count, battery score, mood, notes) Power dashboard, insights, journal Until manually deleted or app uninstalled
User profile (name, work hours, sleep baseline) Personalisation and algorithm calibration Until manually cleared or app uninstalled
Focus session records Focus history and streak calculation Until manually deleted or app uninstalled
App preferences (reminder time, notification settings) App configuration Until app uninstalled
Daily notification count (number only) Fire Battery algorithm input Rolling — today's count only in active memory

5. Permissions — Complete List and Justification

Permission Why it is needed What happens without it
PACKAGE_USAGE_STATS (Usage Access) Read daily app usage to calculate Fire Battery score automatically Battery calculated from manual inputs only; reduced accuracy
BIND_NOTIFICATION_LISTENER_SERVICE Count daily notifications (not read content) for overload detection Notification count shows 0; feature disabled
POST_NOTIFICATIONS (Android 13+) Send local reminder notifications and fire-level alerts No reminders or alerts; all other features work
RECEIVE_BOOT_COMPLETED Reschedule local notifications after device restart Reminders may stop after reboot
WAKE_LOCK Keep focus session timer running when screen turns off Focus timer may pause when screen is off
FOREGROUND_SERVICE Required by Android for background sync and notification listener N/A — system permission
SCHEDULE_EXACT_ALARM / USE_EXACT_ALARM Schedule precise daily reminder notifications Reminders may be delayed
VIBRATE Haptic feedback on focus session completion No vibration feedback

Ember does not request the following permissions, which are commonly associated with privacy concerns: ACCESS_FINE_LOCATION, ACCESS_COARSE_LOCATION, READ_CONTACTS, CAMERA, RECORD_AUDIO, READ_CALL_LOG, READ_SMS, INTERNET, ACCESS_NETWORK_STATE, or READ_EXTERNAL_STORAGE.

6. Third-Party Services and SDKs

Ember does not integrate any third-party analytics, advertising, crash reporting, or data-sharing services. The following is a complete list of third-party libraries used in the App and their data practices:

LibraryPurposeData transmitted?
Flutter (Google) UI framework No
Drift / SQLite Local database No — local only
flutter_riverpod State management No
go_router App navigation No
flutter_local_notifications Local push notifications No — all local, no server
workmanager Background sync scheduling No — on-device only
usage_stats Read Android usage statistics No — on-device only
shared_preferences App settings storage No — local only
flutter_animate UI animations No
fl_chart Charts and graphs in Insights No
package_info_plus Read app version number No

No advertising SDKs, no analytics SDKs (Firebase Analytics, Crashlytics, Mixpanel, Amplitude, etc.), no social login SDKs, and no data brokers are integrated into Ember.

7. Children's Privacy

Ember is not directed at children under the age of 13. We do not knowingly collect any personal information from children. Since the App collects no personal information from any user and operates entirely offline, there is no risk of inadvertent collection of children's data.

If you are a parent or guardian and believe your child has provided information to the App, please note that all data is stored locally on the device and can be deleted by clearing the App's data in Android Settings or uninstalling the App.

8. Data Security

Since Ember stores all data locally on your device and never transmits it, the security of your data depends primarily on the security of your device. We recommend:

The local SQLite database used by Ember is stored in the App's private application directory, which is not accessible to other apps under normal (non-rooted) conditions.

Ember does not implement additional encryption of the local database beyond what Android's file system provides by default. If your device uses full-disk or file-based encryption (which is the default on Android 10+), the App's data is encrypted at rest.

9. Data Retention and Deletion

Retention period

All locally stored data is retained until you delete it or uninstall the App. There is no automatic expiry or deletion of historical records.

How to delete your data

You have three options to delete your data:

  1. In-app deletion: Go to Settings → Data → Clear all data. This permanently deletes all daily records and focus sessions while keeping your profile settings. This action cannot be undone.
  2. Android Settings: Go to Android Settings → Apps → Ember → Storage → Clear Data. This deletes all app data including settings and profile. Cannot be undone.
  3. Uninstall: Uninstalling the App permanently deletes all associated data from your device. Cannot be undone.

Because all data is local and we hold no copies, deletion is immediate and permanent. There is no server-side data to delete, no account to close, and no data retention period after deletion.

10. Your Rights

Since Ember does not collect, process, or store any of your data on any server or third-party system, the typical data subject rights (access, rectification, erasure, portability, objection) are automatically satisfied in the following ways:

For users in the European Union (GDPR), United Kingdom (UK GDPR), or California (CCPA), these rights are additionally guaranteed by applicable law. Since no personal data is transmitted to us, there is no data controller–processor relationship to exercise these rights against beyond your own device.

11. Google Play Data Safety Disclosure

The following reflects what is disclosed in the Google Play Data Safety section for Ember:

CategoryDisclosure
Data collected No data collected (no data sent to us or third parties)
Data shared No data shared with third parties
Security practices Data encrypted in transit — N/A (no transmission); Data encrypted at rest — depends on device encryption
Data deletion Users can request data deletion via in-app Settings or by uninstalling

12. Changes to This Privacy Policy

We may update this Privacy Policy from time to time, for example when the App adds new features that involve data, or when legal requirements change. When we update it, we will:

Continued use of the App after any changes constitutes acceptance of the updated policy.

13. Governing Law

This Privacy Policy is governed by the laws of India. For users in other jurisdictions, we comply with applicable local privacy laws to the extent required, including GDPR (EU), UK GDPR, and CCPA (California, USA).

14. Contact Us

If you have any questions, concerns, or requests regarding this Privacy Policy or the App's data practices, please contact us:

Email: techtowndevelopers@gmail.com
App: Ember: Digital Wellbeing

We aim to respond to all privacy-related enquiries within 7 business days.

15. Specific Disclosures for Sensitive Permissions

Google Play requires specific disclosure for apps that use certain sensitive permissions. We provide this disclosure here in full.

Usage Access (PACKAGE_USAGE_STATS)

Ember uses the Usage Access permission to read Android's UsageStats API. This is used solely to determine how long the device user spends in each app each day, how frequently they switch between apps, and how much total screen time they accumulate. This information is used exclusively within the App to calculate the Fire Battery score — a measure of estimated cognitive load based on digital usage patterns. The data is processed on-device in real time. Aggregated daily totals are stored in the App's private local database. No raw usage event data is stored. No data is transmitted off the device at any time.

Notification Listener Service (BIND_NOTIFICATION_LISTENER_SERVICE)

Ember uses the Notification Listener Service permission to count the number of notifications the device receives each day. This count is used as a signal in the Fire Battery algorithm because high notification volume is associated with reduced focus and increased cognitive fatigue.

Our implementation deliberately accesses only the minimum data required. Specifically, our NotificationListenerService implementation:

This permission is requested only because Android provides no other mechanism to count notifications at the system level without reading their content. The permission grants broader access than we use; our implementation intentionally uses only the minimal subset described above.

16. Health Data Disclosure

Ember is classified as a Health and Fitness application on Google Play. In connection with this classification, the following health-related data is accessed and processed by the App. All health data is stored exclusively on the user's device and is never transmitted to any server, third party, advertiser, or analytics service.

Sleep Data

What is collected: Sleep duration in hours, entered manually by the user via a slider on the dashboard each day, and a sleep baseline entered during onboarding.

How it is used: Sleep duration is used as one input in the Fire Battery algorithm. Insufficient sleep applies a penalty to the daily burnout score. This reflects the documented relationship between sleep deprivation and cognitive impairment.

Storage: Stored locally in the App's private SQLite database on the device. Never transmitted.

Health category: Sleep Management.

Mental Wellbeing and Mood Data

What is collected: A daily mood rating selected voluntarily by the user from three options: Exhausted, Okay, or Energized. An optional free-text journal note about the user's day.

How it is used: The mood rating contributes a small positive recharge to the Fire Battery score when the user reports feeling energized. The journal note is displayed only to the user in the Journal screen and is never analysed, processed, or read by anyone other than the user.

Storage: Stored locally in the App's private SQLite database on the device. Never transmitted.

Health category: Mental and Behavioural Health.

Stress and Burnout Indicators

What is collected: Screen time (minutes), notification count (integer), app switching frequency (integer), late night phone use (minutes). These are collected automatically via the Usage Access and Notification Listener permissions described in Section 3 and Section 15.

How it is used: These signals are combined to compute the Fire Battery score — a single number (0–100) representing the user's estimated cognitive load and digital burnout risk for the day. This score is displayed on the dashboard and used to generate personalised insights and recommendations within the App.

Storage: Daily aggregated totals stored locally in the App's private SQLite database. Raw event data is never stored. Never transmitted.

Health category: Stress Management, Relaxation, Mental Acuity.

Focus and Mental Acuity

What is collected: Focus session start time, planned duration, actual duration, completion status, and interruption count. This data is recorded when the user voluntarily starts a Focus Mode session within the App.

How it is used: Completed focus sessions add a recharge bonus to the Fire Battery score. Session history is shown in the Insights and Journal screens to help the user understand their deep work patterns over time.

Storage: Stored locally in the App's private SQLite database on the device. Never transmitted.

Health category: Stress Management, Relaxation, Mental Acuity.

Summary of Health Data Practices

Health data type Source Transmitted off device? Shared with third parties? Used for advertising?
Sleep duration User input (manual) Never Never Never
Mood rating User input (manual) Never Never Never
Journal notes User input (manual) Never Never Never
Burnout score (Fire Battery) Computed on device Never Never Never
Screen time Android Usage Stats API Never Never Never
Focus session data User-initiated in App Never Never Never

Ember does not connect to Google Fit, Health Connect, Apple Health, or any other health data platform. All health-related data is either self-reported by the user or derived from Android system usage statistics processed entirely on the device. No health data is processed by any external AI, machine learning system, or cloud service.

This Privacy Policy was last updated in March 2026 and applies to all versions of Ember: Digital Wellbeing distributed via Google Play Store. Earlier versions of the App may have had different policies — please refer to the policy version corresponding to the App version you are using.