Health information is sensitive. BF table requests only read access and does not write to or modify Health Connect records. Depending on the automatic metrics you select, the Application may request:
- **Steps (`android.permission.health.READ_STEPS`)** — to read the total number of steps during the relevant day or time period and evaluate a step-based habit;
- **Exercise sessions (`android.permission.health.READ_EXERCISE`)** — to calculate exercise duration during the relevant day or time period and evaluate an exercise-based habit; and
- **Active calories burned (`android.permission.health.READ_ACTIVE_CALORIES_BURNED`)** — to calculate active calories burned during the relevant day or time period and evaluate a calorie-based habit.
Access is optional and is requested only for the Health Connect features you choose. If you do not grant access, or later revoke it, the relevant automatic habit cannot be evaluated from Health Connect, but you can continue using other parts of the Application.
BF table reads aggregated values for the time period needed to evaluate your configured habit. It uses those values to calculate progress and completion. The Application may store the resulting measured value, unit, evaluation status, and evaluation time locally as part of your habit history. It does not store copies of individual underlying Health Connect records.
Health Connect data and health-derived values are not used for advertising, marketing, profiling, creditworthiness, lending, or sale. They are not shared with third parties by the Application. They are processed only to provide the user-facing habit tracking and automatic evaluation features you select.
You can review or revoke BF table's Health Connect access at any time in your device's Health Connect settings. Revoking access stops future reads but does not automatically delete habit results already calculated and stored by BF table. You can delete those results by deleting the related Application data as described below.
### Device activity and installed-app information
If you choose a screen-time or app-activity automatic habit, the Application may handle:
- the names and package identifiers of launchable apps installed on your device, so you can select an app and so total screen time can be calculated across launchable apps;
- app foreground-use events and duration;
- app launch events and counts;
- total screen time; and
- device unlock events and counts.
The Application uses this information only to calculate the automatic habit metrics you configure. It may store locally the selected app's package identifier and the resulting measured value, unit, evaluation status, and evaluation time. It does not send your installed-app list or device activity to the Service Provider or third parties.
Android treats usage access as special access rather than a normal runtime permission:
- **Usage access (`android.permission.PACKAGE_USAGE_STATS`)** — allows the Application to read device and app usage events needed for app-use duration, total screen time, app launch count, and device unlock count.
You must enable this access in Android settings. You can revoke it at any time. Without it, device-activity automatic habits cannot be evaluated, but other features remain available.
## Other permissions and system access
The Application declares or uses the following additional access:
- **Notifications (`android.permission.POST_NOTIFICATIONS`)** — on supported Android versions, allows BF table to show the optional daily review reminder you enable. Denying this permission prevents reminder notifications but does not affect habit tracking.
- **Run after device startup (`android.permission.RECEIVE_BOOT_COMPLETED`)** — allows BF table to reschedule an enabled daily review reminder after the device restarts. This does not cause the Application to collect or transmit data.
- **Keep the device awake (`android.permission.WAKE_LOCK`)** — added by an AndroidX background-work library so short background operations, such as widget-related work, can finish reliably. It does not give the Application access to personal information.
- **View network connections (`android.permission.ACCESS_NETWORK_STATE`)** — added by the AndroidX background-work library to determine whether a network connection is available when scheduling work. BF table does not declare the Internet permission, and this permission alone cannot send data over the Internet.
- **Foreground service (`android.permission.FOREGROUND_SERVICE`)** — added by the AndroidX background-work library to support eligible long-running background work when Android requires it. It does not itself provide access to personal information. BF table does not use it to upload your data.
- **Internal non-exported receiver permission (`com.productivity.bftable.DYNAMIC_RECEIVER_NOT_EXPORTED_PERMISSION`)** — a signature-level permission added by AndroidX to protect internal broadcast receivers from other apps. It is granted automatically, is not requested from you, and does not expose personal information.
- **App discovery through Android package visibility** — allows BF table to display launchable apps for app-specific habits and calculate total screen time. This is declared through an Android package-visibility query and is not a runtime permission.
- **User-selected document access** — when you import or export a backup, Android's system document picker gives BF table access only to the file you select or create. The Application does not request broad access to your photos, media, or files.
The weekly home-screen widget reads locally stored habit information to display your weekly habit table. Widget content may be visible on your home screen to anyone who can view your device. Reminder content may similarly be visible on your lock screen depending on your Android notification settings.
## How information is used
The Application processes information only as needed to:
- create, organize, display, and track habits, notes, progress, and reviews;
- evaluate automatic habits from the permissions and data sources you select;
- show the weekly widget and optional daily reminder;
- remember Application settings;
- import, export, and restore backups at your direction; and
- support direct transfer of Application data when you move to another Android device.
Where applicable law requires a legal basis, this processing is performed to provide the Application features you request and, for optional permission-based features, with your consent. You may withdraw permission through Android or Health Connect settings. Withdrawal does not affect processing that occurred before access was withdrawn.
## Storage, backups, and transfers
Application data is stored locally in BF table's private storage. The Application excludes its data from Android cloud backup. Android may include the local database and preferences in a direct device-to-device transfer when you set up or move to another device.
You may also create a JSON backup using the Application's export feature. A backup can contain your habits, schedules, history, notes, automatic habit settings, selected app package identifiers, and stored health- or usage-derived evaluation values. It does not contain copies of the individual underlying Health Connect or usage-event records. You choose where the backup is saved and are responsible for protecting, sharing, and deleting it. If you save it to a cloud storage provider or another third-party location, that provider's privacy terms apply.
The Application does not itself perform international transfers of your information to the Service Provider. A storage provider you choose for an exported backup, the Android operating system, Health Connect, or an app store may process information under its own terms and in locations determined by that provider.
## Sharing, sale, advertising, and tracking
The Application does not sell, rent, or share personal information or Health Connect data with the Service Provider, advertisers, data brokers, or other third parties. It does not use cookies, pixels, advertising identifiers, or tracking technologies. It does not use your information for cross-context behavioral advertising.
The Application relies on Android system components, including Health Connect, notifications, the document picker, widgets, and device transfer. Those components are provided and controlled by the operating system. If you obtain the Application through Google Play or another app store, the store may independently process download, device, diagnostic, payment, or account information under its own privacy policy. That store information is not received through BF table's in-app functionality.
## Data retention and deletion
Locally stored information remains on your device until you delete it, clear the Application's storage, or uninstall the Application. You can use **Settings > Data > Delete all data** in BF table to delete the habits, notes, history, stored automatic evaluation results, and related database information maintained by the Application. Some preferences, such as language or reminder settings, may remain until you clear the Application's storage or uninstall it.
Deleting BF table data does not delete the original records held by Health Connect, Android usage history controlled by the operating system, or backup files you exported. You must manage those separately in the relevant system settings or storage location. Uninstalling BF table also does not delete exported backup files or information independently held by an app store or storage provider.
Because the current Application does not upload your data to the Service Provider and does not provide accounts, the Service Provider generally cannot view, retrieve, correct, or remotely delete information stored only on your device.
## Your choices and rights
You can:
- choose whether to enable optional Health Connect, usage access, and notification features;
- revoke Health Connect permissions in Health Connect settings;
- revoke usage access or notification permission in Android settings;
- edit or delete individual content where the Application provides that control;
- export a copy of your locally stored Application data;
- delete Application data through BF table's data settings; and
- clear Application storage or uninstall BF table.
Depending on where you live, privacy law may provide additional rights regarding personal information controlled by the Service Provider. You may contact the Service Provider using the address below. Please note that the Service Provider cannot fulfill a request for data that the Service Provider does not possess and cannot remotely access data stored only on your device.
### California privacy notice
The current Application does not sell or share personal information as those terms are defined by the California Consumer Privacy Act, and it does not use or disclose sensitive personal information for purposes other than providing the features you request. California residents may contact the Service Provider to ask about access, correction, deletion, or other applicable rights concerning any information the Service Provider possesses. Exercising a privacy right will not result in discriminatory treatment.
## Children's privacy
The Application is not directed to children under 16, or a higher minimum age where required by applicable law. The Service Provider does not knowingly collect personal information from children through the Application. Because Application data remains locally on the device, a parent or guardian should use the device and Application controls described above to review or delete that data. If you believe a child has sent personal information directly to the Service Provider, contact the Service Provider so it can be deleted where appropriate.
## Security
BF table uses Android's app-private storage for its local data and limits sensitive access through Android and Health Connect permissions. No method of storage is completely secure. Protect your device with an appropriate screen lock and store exported backups securely. Exported backups are readable JSON files and are not encrypted by BF table.
## Required disclosures
The Service Provider may disclose information that you send directly to the Service Provider if required by law, legal process, or a valid government request, or when reasonably necessary to protect rights, safety, or security. This does not give the Service Provider access to information that remains only on your device.
## Changes to this Privacy Policy
This Privacy Policy may be updated to reflect changes to the Application, legal requirements, or privacy practices. The updated policy will include a new effective date and will be made available through the Application's distribution or publication channel. Where required by law, additional notice or consent will be provided.
## Contact us
If you have questions about this Privacy Policy or the Application's privacy practices, contact:
**Email:** soliev.ilhom.2005@gmail.com