1. General provisions
This Privacy Policy describes how information is accessed, used, stored, and protected in the Tasks mobile app for Android, package name com.bob.tasks.
The app is developed and published by FOP Vysotskyi V. E., Ukraine. By installing or using the app, you confirm that you have read this Privacy Policy.
The app works offline, requires no registration, creates no user accounts, and has no developer-operated servers.
2. Core data-processing principle
All data created or added by the user is processed and stored locally on the user's device. The app does not have internet access permission and does not send user data to the developer or to developer-operated servers.
The developer cannot access tasks, attachments, comments, or contacts; does not create user profiles; does not sell or disclose data; and does not use it for advertising or marketing.
3. Information processed locally
3.1. Tasks and related data
The app may locally store task titles and descriptions, due dates and times, reminders, recurrence settings, categories, comments and notes, completion status, and other information entered by the user. This data is used only for task planning and management features.
3.2. Contact details
You may voluntarily add a person's name and phone number to a task, either manually or through the device's contact picker. Selected details are stored locally with the task. The app does not copy your entire address book and does not use contacts for advertising or analytics.
Tapping the call button may open the system phone app with the selected number. The call and any charges are controlled by the operating system, mobile carrier, and user.
3.3. Photos, videos, and documents
You may voluntarily attach photos, videos, PDFs, documents, and other supported files. Selected files are copied to the app's private internal storage and are not transmitted over the internet.
3.4. Voice notes
Microphone access is used only after a direct user action to record a voice note. The app does not record secretly or in the background. The audio file is stored locally in the app's private storage. Speech recognition, voice analysis, and artificial intelligence are not used to process recordings.
3.5. Settings
The app locally stores the selected interface theme, notification settings, automatic backup settings, and other information required for its features.
4. Information the app does not collect
The app does not collect or transmit the device owner's name, personal email address, home address, age or date of birth, IP address, location, advertising ID, serial number or other device identifiers, system calendar data, browsing history, search queries, usage statistics, crash logs, diagnostic data, or payment and financial data.
Local technical identifiers for tasks and categories are used only for backup and restore. They are not linked to the user's identity and are not sent to the developer.
5. Device permissions
The app may request Android permissions for notifications, exact alarms, startup after reboot, contact selection, camera, microphone, files, and documents. These permissions support reminders, restoring scheduled events, adding contacts and attachments, recording voice notes, and choosing a backup location.
Contact, camera, and microphone permissions are requested when the relevant feature is used. You may deny or revoke permission in Android settings; the related feature may then be unavailable. The app does not request location or system calendar access.
6. Notifications and the lock screen
Reminders are created locally; the app does not use cloud messaging. A notification may show the task title and description. Depending on Android settings, this text may appear on the lock screen. You can change sensitive-content visibility in system settings.
7. Backups
7.1. Backups created by the app
You may create manual or automatic backups containing tasks, categories, comments, contact details, settings, and attachments. The folder is selected through the Android system interface and may be local or belong to a third-party cloud service.
The app does not choose a cloud provider, access your cloud account, or upload backups to the developer's servers. If you choose cloud storage, the provider's privacy policy applies to the file.
7.2. Backup encryption
You may protect a backup with a password. Protected backup files are encrypted with AES-256-GCM, and the key is derived from the password using PBKDF2-HMAC-SHA256. A password saved on the device for automatic backups is additionally protected by Android KeyStore.
A backup without a password does not receive this additional encryption. The developer never receives the password and cannot recover it if it is lost.
7.3. Android system backups
Android system backup is allowed for the app. If enabled on your device, the operating system may store some data in your Google Account or transfer it to another device. This is controlled by your settings and does not give the developer access to the data.
9. Third-party services
The app does not use Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, ad networks, behavioral analytics, tracking systems, developer-operated cloud servers, AI services, or payment services. Standard Android libraries are used only for local operation.
10. Advertising and purchases
The app displays no ads, does not use an advertising identifier, and does not share information with advertising companies. The current version has no purchases, subscriptions, or paid features. The developer does not receive or process payment data.
11. Data security
Local data is protected by Android's app-sandboxing mechanisms. The database and local attachments do not have separate application-level encryption, so users should protect the device with a PIN, password, pattern, or biometric lock.
A person with access to an unlocked or modified device may potentially access local information. No storage method can guarantee absolute security.
12. Data retention and deletion
Local data remains until you delete an individual record or attachment, clear the app's data in Android settings, or uninstall the app. Uninstalling clears the app's private internal storage.
Backups previously saved in another folder or cloud storage may remain and must be deleted separately. Android system backups are controlled through account and device settings. The developer has no access to local data and cannot delete it on your behalf.
13. Accounts
The app does not support account creation or sign-in. Therefore, a separate account-deletion process does not apply.
14. Children's use
The app was not designed specifically for children and contains no features intended exclusively for a child audience. It does not send user information, including information about children, to the developer. Parents or legal guardians should supervise device use and the data a child stores locally.
15. Changes to this Privacy Policy
This Policy may be updated when app features, data practices, laws, or Google Play requirements change. If server synchronization, analytics, advertising, purchases, accounts, or other data transfers are introduced, this Policy and the Data Safety declaration will be updated before that version is released.
16. Contact information
FOP Vysotskyi V. E.
Ukraine
Email: febdevapps@gmail.com
Phone: +380 93 817 6752
Help page: Contact and Support
Last updated: July 18, 2026