1. General provisions
This Privacy Policy describes how information is accessed, used, stored, and protected in the “Tasks” mobile application for Android, package name com.bob.tasks.
The developer and publisher of the application is sole proprietor Vysotskyi V. E., Ukraine. By installing or using the application, the user confirms that they have read this Privacy Policy.
The application operates primarily offline, does not require registration, does not create user accounts, and does not use the developer’s own servers. A connection to Google Play services is used only for subscriptions, verification of entitlement to Pro access, restoration of purchases, and display of the system prompt to rate the application.
2. Main principle of data processing
Tasks, categories, comments, subtasks, attachments, voice notes, contact details, settings, and other content created by the user are processed and stored locally on the user’s device. They are not transmitted to the developer or to the developer’s servers.
The application does not request the Android system permission for direct Internet access. To purchase, acknowledge, verify, renew, restore, and manage subscriptions, the application interacts with Google Play through the official Google Play Billing Library and the Google Play application installed on the device.
The developer does not have access to the contents of tasks, attachments, comments, voice notes, or selected contacts, does not create user profiles, does not sell data, and does not use it for advertising or marketing.
3. Information processed locally
3.1. Tasks and related data
The application may locally store task titles and descriptions, due dates and times, reminders, repetition and copy-creation settings, categories, priorities, subtasks, comments and notes, completion status, and other information entered by the user. This data is used solely for task planning and management features.
3.2. Contact details
The user may voluntarily add a name and telephone number to a task manually or by selecting a contact from the device’s address book. The selected data is stored locally with the task. The application does not copy the entire address book and does not use contacts for advertising or analytics.
Tapping the call button may open the system phone application with the selected number. The call and any related charges are controlled by the operating system, mobile operator, and user.
3.3. Photos, videos, and documents
The user may voluntarily attach photos, videos, PDF files, documents, and other supported files. Selected files are copied to the application’s private internal storage and are not transmitted to the developer.
3.4. Voice notes
Microphone access is used only after a direct user action to record a voice note. Recording starts only after a direct action by the user and is never started automatically or secretly. If the user minimizes the app while recording is active, recording may temporarily continue until the user stops or cancels it, or until the Android operating system terminates the app process. Android may display a system microphone usage indicator. The audio file is stored locally in the application’s private storage. Speech recognition, voice analysis, and artificial intelligence technologies are not used to process recordings.
3.5. Settings
The application locally stores the selected interface theme, notification settings, category sounds, widget settings, automatic backup settings, and other information required for application features.
3.6. Technical subscription and access data
To determine the access level, the application locally stores the technical Free, Pro, or Legacy status and the time of the most recent successful verification of an active Pro subscription. After successful verification, Pro access may be retained temporarily for up to 14 days if Google Play services are unavailable.
If a purchased subscription has not yet been successfully acknowledged by Google Play, the application may temporarily store the purchase token on the device so it can retry acknowledgment. After successful acknowledgment, the token is removed from this local list. This data is not sent to the developer’s servers.
4. Information the application does not collect
The application itself does not collect or transmit to the developer the device owner’s name, personal email address, home address, age or date of birth, IP address, geolocation, advertising identifier, serial number or other device identifiers, system calendar data, browsing history, search queries, usage statistics, crash logs, or diagnostic data.
Neither the application nor the developer receives the user’s bank card number, bank account details, CVV code, or other complete payment credentials. Payments are processed by Google Play in accordance with Google’s own privacy policy and terms of service.
Local technical identifiers for tasks and categories are needed only for application operation, backup, and restoration. The developer does not associate them with the user’s identity, and they are not transmitted to the developer.
5. Device permissions
The application may request Android permissions for notifications, exact alarms, startup after reboot, contact selection, camera use, and microphone use. Access to files and folders for attachments and backups is granted by the user through the Android system interface.
These capabilities are required respectively for reminders, restoration of scheduled events, adding contacts and attachments, recording voice notes, and selecting a backup location.
Contact, camera, and microphone permissions are requested when the related feature is used. The user may deny or revoke a permission in Android settings; the related feature may then be unavailable. The application does not request access to geolocation or the system calendar.
6. Notifications and the lock screen
The application creates reminders locally and does not use cloud messaging. A notification may display the task title and description. Depending on Android settings, this text may be visible on the lock screen. Display of sensitive notification content can be changed in the device’s system settings.
7. Backups
7.1. Backups created by the application
The user may create manual or automatic backups containing tasks, categories, subtasks, comments, contact details, settings, and attachments. The folder is selected through the Android system interface and may be local or provided by a third-party cloud storage service.
The application does not select the cloud provider, access the user’s cloud account, or send backups to the developer’s servers. If the user selects cloud storage, further processing of the file is governed by the selected provider’s policy.
7.2. Backup encryption
The user may protect a backup with a password. Protected backups are encrypted using AES-256-GCM, and the key is derived from the password using PBKDF2-HMAC-SHA256. A password stored on the device for automatic backups is additionally protected by Android KeyStore.
A backup without a password has no additional application-level encryption. The developer does not receive the password and cannot recover it if it is lost.
7.3. Android system backups
Android system backup is enabled for the application. If enabled on the device, the operating system may store some data in the user’s Google Account or transfer it to another device. This is controlled by the user’s settings and does not give the developer access to the data.
Certain local technical data related to Legacy access and Pro access verification is excluded from backup or device transfer to prevent access rights from being transferred incorrectly between devices.
9. Google Play and third-party services
9.1. Google Play Billing
The application uses the official Google Play Billing Library to purchase a monthly or yearly Pro subscription, obtain the current localized price, acknowledge a purchase, verify active status, restore a purchase, and open subscription management.
During this interaction, Google Play may process information relating to the purchase, Google Account, device, and payment method in accordance with Google’s privacy policy. The application receives from Google Play only the technical information needed to operate the subscription, including the product and plan identifier, localized price, purchase status, acknowledgment status, and purchase token.
The developer does not use an independent server to verify subscriptions and does not receive task content or complete payment credentials from the application.
9.2. Rating on Google Play
The application may invite the user to rate it through the Google Play system interface. Display of this prompt and any subsequent rating are controlled by Google Play. The application does not receive the review text or the user’s personal data through this feature.
Google Play and the Android operating system may independently generate and provide the developer with Android Vitals technical reports about crashes, ANRs, the Android version, and the device model, depending on Google’s services and the user’s settings. The app does not use Firebase Crashlytics, its own analytics or tracking system, and does not provide the developer with the contents of tasks, attachments, contacts, or voice notes through these reports.
9.3. Services not used
The application does not use Firebase Analytics, Firebase Crashlytics, Firebase Cloud Messaging, advertising networks, behavioural analytics, tracking systems, the developer’s own cloud servers, or artificial intelligence services.
10. Advertising, paid features, and subscriptions
The application does not display advertising, use the advertising identifier, or transmit information to advertising companies.
The application has a Free access level, a paid Pro access level, and a Legacy level for users who were granted full access under the conditions of earlier versions. Pro unlocks extended application features. Pro access can be purchased as a monthly or yearly subscription through Google Play.
The price, currency, billing period, and available terms displayed in the application are based on information received from Google Play and are shown again by Google Play before purchase confirmation. Terms and prices may vary depending on country, currency, taxes, and Google Play settings.
The subscription renews automatically until the user cancels it through Google Play. Uninstalling the application does not cancel an active subscription. The user can view, change, or cancel the subscription in their Google Play Account settings. Refunds are handled in accordance with Google Play rules and applicable law.
Google processes the payment and stores the payment credentials. The developer does not receive the user’s bank card number, CVV code, or complete payment account details.
11. Data security
Local data is protected by Android application sandboxing mechanisms. The database and local attachments do not have separate application-level encryption, so users are advised to protect the device with a PIN, password, pattern, or biometric lock.
Password-protected backups are encrypted separately as described in section 7.2.
A person with access to an unlocked or modified device may potentially gain access to locally stored information. No storage method can guarantee absolute security.
12. Retention and deletion
Local data is retained until the user deletes an individual record or attachment, clears the application’s data in Android settings, or uninstalls the application. Uninstalling the application normally removes its private internal storage.
Local technical access data and unacknowledged purchase data are retained only as long as needed to verify Pro access or retry purchase acknowledgment. The token is removed from the local list of unacknowledged purchases after successful acknowledgment.
Backups previously stored in another folder or cloud storage may remain and must be deleted separately. Android system backups are managed through the user’s account and device settings. The developer does not have access to local data and cannot delete it on the user’s behalf.
Uninstalling the application or deleting its local data does not cancel a subscription. The subscription must be managed separately through Google Play.
13. Accounts
The application does not support its own user accounts and does not use authentication on the developer’s servers. Therefore, a separate procedure for deleting an application account does not apply.
The user’s Google Play Account is used to purchase and manage a subscription. Management and deletion of that account are governed by Google’s rules and settings.
14. Children’s use
The application was not designed specifically for children and does not contain features intended exclusively for a child audience. The application does not transmit user information, including children’s information, to the developer. Parents or legal guardians should supervise device use, Google Play purchases, and the data a child stores locally.
15. Changes to this Privacy Policy
This Policy may be updated due to changes in application features, data processing practices, legislation, or Google Play requirements. If server synchronization, analytics, advertising, proprietary user accounts, or other new methods of data collection or transmission are introduced, this Privacy Policy and the Data Safety declaration will be updated before the relevant version is released.
The current version of this Policy is published on the developer’s official website.
16. Contact information
Sole proprietor Vysotskyi V. E.
Ukraine
Email: febdevstud@gmail.com
Phone: +380 93 817 6752
Support page: Contact and Support
Last updated: September 28, 2026