Skip to content

Can I trust one sec | screen time + focus?

NOT ASSESSED 89 iOS Version 5.2.6 (Build 1654) Store version released: Last checked: riedel.wtf apps S.L. wtf.riedel.one-sec Scanned

This scan is more than 90 days old.

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

Best for
Users comfortable with GDPR-aligned usage analytics
What it means for you
The build includes the TelemetryDeck and Sentry SDKs, whose code reads app usage and crash data, both operating under GDPR-compliant terms with EU data residency and no personal identifiers. No advertising networks, behavioral trackers, or device fingerprinting tools are present. Health-related data is processed on-device only and not transmitted to external servers.
Main concern
Hardcoded webhook tokens in binary expose promo-code automation to unauthenticated abuse
The developer's description
one sec is a screen-time management and digital wellness app featuring HealthKit integration, Safari extension controls, and mindfulness tracking. Built with privacy-first analytics and strong encryption.
Third-party services
12
Findings rated low or higher
7

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 uses a privacy-focused analytics service designed from the ground up not to track individual users — it works with anonymized signals rather than advertising IDs or device fingerprints. No advertising networks, ad-tracking frameworks, or advertising identifier usage was found anywhere. The app's own official privacy declaration confirms it does not engage in cross-app tracking.

  • Manifest Mismatch

    Items recorded, result pending review

    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.

    No proprietary data formats, artificial barriers to switching, or evidence of server-side data hoarding were found. The app works primarily on your device and syncs to your own iCloud account, so removing the app removes your local data and iCloud data stays in your own account. No patterns suggesting difficult account closure or data trapping were detected.

  • Truly Local

    Strong

    Stays on the device

    Why this result

    This app presents itself as working offline or on the device alone. The check looks for any code written to send personal data to a server, including analytics, crash reporting and advertising code. None was recorded in this build.

    Apple Health mindfulness data stays on your device under Apple's controls — nothing was found sending it to outside services. Settings and history sync through your own iCloud account, not a third-party service. The two external services in use, crash reporting and usage analytics, are configured in code to include only technical diagnostic signals and are explicitly non-tracking, and the build includes no code to pass your personal habits or screen-time data to them. No data brokers or advertising networks are present.

Strengths

  • Certificate pinning implemented via SecTrustSetAnchorCertificates
  • HTTPS enforced everywhere with default ATS configuration and no per-domain exceptions
  • Strong cryptography via CryptoKit (AES-GCM, SHA-256, HMAC-SHA256) with no weak or deprecated algorithms
  • Appropriate Keychain protection classes with ThisDeviceOnly variants for device-sensitive items
  • Privacy-preserving analytics via TelemetryDeck (hashed IDs, no IDFA, GDPR-compliant)
  • Sentry crash monitoring with EU data residency (Germany, GDPR-aligned)
  • No advertising SDKs, no IDFA, no AppTrackingTransparency anywhere in the app
  • Privacy manifest fully compliant with all Required Reasons API usages correctly declared
  • HealthKit data processed on-device only with no evidence of server transmission

What the app contains

  • 12 services

    Third-party services the scan names in the build:

    • Sentry
    • TelemetryDeck
    • Alamofire
    • Kingfisher
    • Down
    • Defaults
    • CalendarKit
    • Factory
    • CustomAlert
    • FoundationModels
    • Make.com
    • Integromat

Libraries

Libraries in the build of one sec | screen time + focus
LibraryVersionAdvisory
Sentry9.10.0none confirmed
one secnot recordednone confirmed

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
17 June 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.