TaskKind

To-do lists & reminders · by Code Terra

TaskKind privacy policy

Updated 16 October 2026. TaskKind is published by Code Terra. For support and privacy questions, contact rohanprajapati7860@gmail.com.

Your reminders stay on your device

TaskKind stores tasks, descriptions, subtasks, lists, completion history, settings, and selected places in app storage on your device. Selected attachments are copied into app storage where possible; if a copy cannot be made, a reference to the selected local file may remain. Source files, exports, and shared copies can exist outside the app. We do not run a task-sync server, require an account, or automatically upload your reminders to the developer. This does not mean the app never uses the internet.

Optional usage analytics

Usage analytics is off by default and needs your separate opt-in in Settings → Privacy. When Firebase is configured and you opt in, Google Analytics for Firebase receives feature events such as task creation/completion, use of repeat reminders or subtasks, goal image sharing, backup/restore outcomes, and permission results. Event properties are limited to feature flags and outcomes. The app does not send task titles, descriptions, list names, attachment contents, chosen audio filenames, website links, precise coordinates, or your installed-app list as analytics event properties.

Google Analytics for Firebase can also collect usage/session information, device and app details, approximate location, and an app-instance identifier. Google processes IP addresses for purposes including approximate location and service security, and states that Analytics does not log or store individual IP addresses. This is pseudonymous telemetry, not a guarantee of anonymity. We do not set an account/user ID, enable advertising ID collection, or enable personalized advertising. Analytics collection requires a connected Firebase project and your opt-in.

Optional crash reporting

Crash reporting has a separate opt-in and is off by default. If configured and enabled, Firebase Crashlytics receives crash/error diagnostics, app and operating-system versions, device information, timestamps, stack traces, and installation identifiers. For Flutter errors forwarded by our app code, the app sends generic error codes and filtered app-code stack frames instead of the original error message. Native crashes and automatic SDK reports can contain additional diagnostic context, including error messages; do not assume every report is fully anonymous. We do not intentionally attach your reminder content or attachments to automated crash reports. Firebase documents Crashlytics diagnostic/identifier retention as 90 days before removal begins. Google Analytics retains data according to the project retention controls and Google retention and deletion practices. These controls apply to user-level and event-level exploration data; standard aggregated reports may be retained separately. See Google data retention information at https://support.google.com/analytics/answer/7667196.

Your choices

You can use reminders without opting in to either telemetry option. Changing a telemetry preference does not change your tasks or backups. Turning usage analytics off stops new app events and requests a local analytics reset. Turning crash reporting off stops new collection and requests deletion of unsent reports. Previously received reports are subject to the provider's retention and deletion processes; switching off does not recall data already sent. Privacy choices are local to this installation and are not transferred through task backup files.

Maps, place search, and location

Map browsing requests map tiles from OpenStreetMap (or a configured tile provider). The provider receives your IP address and the map tile area requested. Place suggestions and reverse lookup contact the configured search provider, currently Photon operated by komoot. Search text, map coordinates, and location coordinates used to rank nearby results can be sent to that provider when you use place search. These requests are necessary for the feature and are separate from optional analytics. Provider privacy policies and service terms apply.

With permission, Android location services and Google Play services support nearby places and arrival/leaving reminders. Background location is requested for place alerts while the app is closed; it is not required for ordinary reminders. Stored reminder coordinates are used on the device for these alerts, not sent as analytics. You can revoke location permissions in Android settings. Your device's location provider may process location data under its own settings and privacy policy.

For reminders before the first phone unlock after a reboot, a limited schedule is kept in Android device-protected storage: internal reminder identifiers, timing, recurrence and sound/vibration flags. Task titles, descriptions, attachments, website links, custom sound file locations and saved-place coordinates are not copied there. Notifications shown before the first unlock use generic text and, when sound is enabled, the system default sound.

Website icons and opening links

To show a website icon, the app may request /favicon.ico from the origin of a website linked to a task after connectivity becomes available. The request uses the site origin, without the task link's path, query, or fragment. The website, and any host it redirects the request to, receives your IP address and normal request information. Icons are cached locally. Opening an external website or app is your action and is governed by that service's own privacy practices.

Permissions and device integrations

Notification, precise-alarm, lock-screen popup, and overlay access support reminder delivery. Microphone access is used when you choose to record audio. Calendar access is used when you enable device calendars. Selected documents, photos, videos, and audio use Android pickers and their grants. On Android 7–9, saving a goal image to the gallery can require legacy storage write access. App/browser listings are used on the device to choose what a reminder opens, not uploaded as analytics.

Backups, deletion, and sharing

Local recovery copies, manually saved local backups, and an upgrade safety copy of an existing database are stored in app storage. Android can delete this storage on uninstall, clearing app data, or a device reset; do not rely on it surviving uninstall. Export a portable backup to a place you control before deleting app data. Exported backup files and shared goal images contain the data you choose and are not described as end-to-end encrypted. Protect them accordingly. Deleting local backups in the app also removes the upgrade safety copy, keeps your live tasks, and pauses automatic backup until you save again. Exported copies and copies already shared to other apps must be deleted separately.

Completed and deleted tasks may remain in local history/recently deleted or retained backup copies until those copies are removed. Removing the app with its data removes private task storage; external exports, shared copies, and data already received by telemetry providers are separate.

Problem reports

Report a problem prepares text for you to review and copy or share using Android. Diagnostics are excluded unless you select them. Local diagnostic reports can contain technical errors and file paths. Review the preview before sharing. The app does not automatically send a support message or upload your attachments.

Processing locations and privacy requests

Third-party services, including Google/Firebase and our website host, may process data in countries other than yours under their applicable terms and safeguards. TaskKind currently does not display advertisements or sell your task data. If advertising or data handling changes, this notice and the relevant choices must be updated before those changes are introduced.

For privacy questions or requests to access, correct, or delete information we hold about you, use the current support contact below. We do not have a server copy of your task database and cannot retrieve or delete tasks stored only on your device. Requests concerning optional telemetry or information you sent to support depend on the information available to identify the relevant records and applicable law.

When you contact support, we receive your email address and the information you choose to send. We use this to respond to and investigate your request and retain correspondence as needed for that purpose or applicable obligations. You can request deletion using the support contact below.

Third-party information

Google/Firebase privacy: https://firebase.google.com/support/privacy Google Analytics privacy: https://support.google.com/analytics/answer/6004245 OpenStreetMap privacy: https://osmfoundation.org/wiki/Privacy_Policy komoot privacy: https://www.komoot.com/privacy

Reading the current policy

When you open the privacy policy or use maps/place search in TaskKind, the app can request the current policy or map-service configuration from rohanprajapati.dev, hosted on Vercel. Map-service configuration can change the HTTPS tile/search endpoints or temporarily disable their network requests. The policy must be reviewed when providers change. The host receives your IP address and standard request information. This request does not include your tasks or attachments. A copy is saved on your device for offline reading. Website hosting information: https://vercel.com/legal/privacy-policy.

Contact and policy updates

Publisher: Code Terra.

Support and privacy contact: rohanprajapati7860@gmail.com.

This notice will be reviewed when data handling or third-party services change. The updated date above identifies the current notice.