Scan results

    Reflect Notes

    iOS

    Reflect is a cloud-synced journaling and note-taking app that prioritizes privacy and encryption. Notes are encrypted at the application layer before cloud storage, and the app contains no advertising or tracking networks.

    unTRUSTED

    This app did not meet two or more trust checks, has a critical issue in one, or carries a red flag.

    The five trust checks

    CITT SCORE
    87
    out of 100
    unTRUSTED

    Quick Verdict

    Best for: Daily journaling with encrypted cloud sync

    What It Means For You

    Journal and note content is encrypted before syncing to the developer's own Firebase storage. No advertising, attribution, or broad analytics SDKs are present. Error reporting via Sentry is configured to limit behavioral data capture, and authentication flows through Google Sign-In and Firebase.

    Method and Limitations

    Static analysis only. CITT reviewed the code of this build without running the app, so runtime behavior was not observed. The findings below describe the analyzed build and may not reflect server-side controls or later versions. CITT makes no determination about compliance with any law or platform policy; it reports what the artifacts contain and cites the published guidance so a reader can compare.

    How CITT scores an app

    Findings (3)

    Network Security

    1 total
    1 Low

    Code Security

    1 total
    1 Low

    Privacy

    1 total
    1 Low

    Third-Party Services

    Firebase Auth, Firebase Realtime Database, Firebase Storage, Firebase Dynamic Links, Google Sign-In, Sentry, AppAuth, GTMAppAuth, GTMSessionFetcher, SQLCipher, Logflare, Capacitor, RecaptchaInterop

    Security Strengths

    • No advertising networks, attribution SDKs, or broad-reach analytics SDKs are present
    • Journal and note content is encrypted at the application layer before syncing to Firebase
    • All API traffic uses HTTPS with no observed cleartext connections
    • Sentry breadcrumb capture is disabled, limiting behavioral interaction data sent to third parties
    • Share extension data stays within the developer's own first-party app group (Team ID-gated)
    What changed since the last scan

    Version diff is on the Developer plan. See developer plans.

    Context Tags

    notes
    journal
    sensitive data
    cloud sync
    health

    Package

    app.reflect.ReflectMobile

    Version

    1.0.43 (Build 202605221946)

    Analysis Date

    Aug 6, 2026

    Classes Analyzed

    395

    Was this analysis helpful?

    Feedback helps us improve our analysis

    View on App Store

    Recommendation: Trustworthy

    Reflect provides strong privacy protection with application-layer note encryption, cloud sync, and no advertising or attribution networks. Network communications are secured throughout, and Sentry receives the account email address for crash diagnostics as the primary contact with a third-party service.

    Key Findings

    Data Security: 0 findings

    Network Security: 1 finding (1 low)

    Code Safety: 1 finding (1 low)

    Privacy: 1 finding (1 low)

    Privacy Concerns

    What Leaves the Device

    • Account email address: sent to Sentry for crash diagnostics and error monitoring
    • Journal notes and content: synced to Firebase cloud storage; content is encrypted at the application layer before leaving the device

    What Stays on the Device

    No sensitive data was identified as processed only on the device.

    Third-Party Data Sharing

    Third parties that may receive data from the app:

    • Sentry - crash reporting and error monitoring (receives account email address)
    • Firebase (Google) - cloud storage and authentication infrastructure for notes and account management
    • Google Sign-In - user authentication
    • Logflare - application logging

    Understanding the Scores

    Security: 84/100
    Privacy: 93/100

    Security Breakdown

    • Data Security: 86/100. Note content is encrypted at the application layer before reaching cloud storage, and the app's overall data handling is careful and limited in scope.
    • Network Security: 91/100. All network communication uses HTTPS with no cleartext connections observed throughout the app.
    • Code Safety: 83/100. The app's codebase follows sound practices, with one low-severity input-handling concern in the navigation layer identified.

    Privacy Breakdown

    • Data Collection: 93/100. The app's external data footprint is minimal, with no advertising, attribution, or broad-reach analytics SDKs present and external data sharing limited to cloud sync and crash diagnostics.
    • Data Sharing: 95/100. Data is shared only with the developer's own cloud infrastructure and a small set of essential services, with no advertising, attribution, or behavioral profiling data flows identified.
    • User Control: 93/100. Users manage their account through Firebase authentication, and note content is encrypted at the application layer before cloud upload.

    Positive Security Features

    • No advertising networks, attribution SDKs, or broad-reach analytics SDKs are present in the app
    • Journal and note content is encrypted at the application layer before syncing to cloud storage
    • All API traffic uses HTTPS with no cleartext connections observed
    • Crash-reporting behavioral capture is disabled, limiting what interaction data is sent to third parties
    • Share extension data stays within the developer's own first-party infrastructure

    Areas for Improvement

    GDPR / CCPA Compliance

    The app's privacy practices could be strengthened by:

    1. Crash Reporting Identity Linkage
      Sentry is configured to attach the account email address to crash reports and performance traces. Using a pseudonymous identifier for crash-reporting sessions would reduce the personal data sent to this service.

    2. App Privacy Manifest
      Adding an app privacy manifest could make the App Store privacy label more complete and accurate.

    3. Sign-In SDK Location Permissions
      The Google Sign-In library declares approximate location as a data type linked to user identity. Confirming whether this permission is actively used and limiting it where not needed would reduce the app's declared data footprint.

    Security Enhancements

    1. Local Data Encryption
      The database library linked to the app includes a built-in encryption capability. Enabling it for locally stored data would strengthen on-device data protection.

    2. Network Request Filtering
      The embedded web layer is configured to allow network requests to any origin. Restricting this to known first-party and approved domains would add a layer of network defense.

    3. Authentication Configuration
      Authentication configuration values embedded in the app bundle could be moved to server-side retrieval to reduce their exposure.

    Technical Context

    App Type: Personal journaling and note-taking, sensitive data
    Classes Analyzed: 395
    Third-Party Services: 13
    Context Tags: notes, journal, sensitive_data, cloud_sync, health


    About This Analysis

    This security analysis was conducted by CITT (Can I Trust That), an independent security analysis service. The analysis is static code review of iOS applications, intended to help people make informed decisions about app security and privacy.

    App Details

    Developer: Reflect
    Version: 1.0.43 (Build 202605221946)
    Analysis Date: 2026-08-06
    Package: app.reflect.ReflectMobile

    Analysis Limitations

    • Static analysis only (code review without running the app)
    • Based on iOS app version 1.0.43 analyzed on 2026-08-06
    • May not reflect server-side security controls
    • Cannot detect all runtime behaviors

    Right of Reply

    Developer not yet contacted