Skip to content

Can I trust Tiimo: To Do List & AI Planner?

NOT ASSESSED 84 iOS Version 3.61.0 (Build 1434) Store version released: Last checked: tiimo com.tiimo.app Scanned

This app has an open trust check or a verdict held for review.

Best for
General use with standard privacy expectations
What it means for you
The app may include code to pass standard usage and device data to the app developer and integrated services. The breakdown below lists the data types and third parties involved.
Main concern
ATS exception permits insecure HTTP/TLS 1.1 for all tiimoapp.com subdomains
The developer's description
Tiimo is a productivity and planning app for neurodivergent users featuring task management, scheduling, and on-device mood tracking via HealthKit to monitor emotional well-being.
Third-party services
20
Findings rated low or higher
8

How the score and the label work

Open on the App StoreOpens the app's listing on the App Store in a new tab.

Full findings

Open this scan in your dashboard

The account that ran this scan sees every finding and the Rescan button there.

Trust checks

  • Secure by Design

    Items recorded, result pending review

    Security gaps detected

    Why this result

    This check looks for security issues at high severity or above in the code of this build, and at least one was recorded. Issues of this kind include a credential or token another app on the device can reach, sensitive data stored without protection, and network paths that expose information in transit.

  • Data Minimization

    Strong

    Tracking done right

    Why this result

    The check looks at analytics and attribution code for companies other than the developer: the data it reads, the companies named in code as recipients, and whether a consent step runs before that code. In this build, either no such code was recorded, or a consent step runs before it and the app's own disclosures describe the collection.

    The app correctly implements Apple's tracking permission prompt before activating marketing attribution. All 16 marketing tracking endpoints are confirmed to be gated behind the consent prompt — the marketing SDK will not fire until the user responds. No evidence of analytics or tracking starting before the user sees a consent prompt was found. The consent prompt text contains a spelling error but the mechanism itself is properly implemented.

  • Manifest Mismatch

    One criterion not met

    Disclosure incomplete or contradicted

    Why this result

    The check compares the app's privacy disclosures against what the code does, and at least one claim did not match in this build. Mismatches of this kind include a data category collected but not disclosed, a recipient the disclosure omits, and an identifier attached to data the disclosure describes as anonymous.

  • User Control

    Strong

    No lock-in

    Why this result

    The check looks for a way to export the data an account has accumulated and a way to delete the account itself. In this build, either both were found, or the app has no account of its own and keeps its data on the device. For an app without an account, the developer has no server-side copy to export or delete, and deleting the app removes the data in its own storage.

  • Truly Local

    Items recorded, result pending review

    Contains code to send personal data off the device

    Why this result

    This app presents itself as working offline or on the device alone, and this build contains code written to send personal data to servers. The check covers analytics, crash reporting, advertising code and any first-party endpoint the code addresses personal data to. Code of this kind is common; what this check reports is the distance between that code and how the app describes itself.

Strengths

  • Credentials stored using biometric-bound hardware keychain with App Attest device integrity verification
  • Marketing attribution properly gated behind ATT consent prompt — IDFA only accessed after user approval
  • External web content opens in sandboxed Safari view the app cannot intercept or inject into
  • Firebase Analytics disabled — only crash data collected via Crashlytics
  • Braze and Mixpanel route to EU servers, supporting data residency for European users
  • HealthKit mood data is stored on-device, and the build contains no code to transmit it to third parties

What the app contains

  • 20 services

    Third-party services the scan names in the build:

    • AppsFlyerLib
    • BrazeKit
    • PurchaseConnector
    • RevenueCat
    • RevenueCatUI
    • Mixpanel
    • Sentry
    • Firebase Crashlytics
    • Firebase Installations
    • Google Sign-In
    • Auth0
    • Alamofire
    • Kingfisher
    • Lottie
    • SnapKit
    • EmojiKit
    • ZIPFoundation
    • Factory
    • CoreStore
    • KeychainAccess

Changes since the previous scan

  • Version 3.61.0 (Build 1434), score 84.
  • Score 83 before, 84 after.
  • Version 3.57.0 (build 977) before, 3.61.0 (Build 1434) after.
  • Score change since version 3.57.0 (build 977): +1 point.
  • Since the previous scan: 13 findings added, 13 removed.
  • Version 3.57.0 (build 977), score 83.
  • First public scan of this app.

Method and limits

Static analysis: the decompiled code, manifest and resources of this build, read file by file. Network traffic at run time is established by a capture of the running app.

Scan date
11 July 2026

Corrections

No correction is published for this app.

Developer response

No response is published for this app.

Report an error Opens an email to [email protected] that names this app and this scan.