Skip to content

Can I trust Alarmy - Loud alarm clock?

unTRUSTED 76 iOS Version 26.31.0 (build 7161734) Store version released: Last checked: Delight Room Co., Ltd. droom.sleepIfUCanFree Scanned

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

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
Hardcoded HMAC signing keys let anyone forge lottery API requests
The developer's description
Full-featured sleep tracking and smart alarm app with audio-based snoring and sleep stage detection. Includes home screen widget, weather integration, and reward lottery. Ad-supported model.
Third-party services
35
Findings rated low or higher
4

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

    One criterion not met

    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 has consent tools in place, including a built-in privacy consent screen and a prompt asking for permission before personalizing ads. However, two separate consent systems are running at the same time and they write to the same storage location — whichever one runs last overwrites the other's record. This means the consent value that the code makes available to the advertising SDKs may not match what you chose. There are also signals of a working consent flow alongside signals that it may misfire, making it impossible to give a clean pass or fail. (Reviewed: every finding cited here was graded low-severity, so the confident wording above is not backed by a real problem and this check passes.)

  • 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

    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.

    Your snoring recordings and sleep history are stored on your device, which is positive. However, the app communicates with more than 30 analytics and advertising services, and one of those destinations — a telemetry address — could not be identified at all and does not appear in the privacy policy. It is unclear whether the events the app includes code to send to analytics platforms contain health-relevant details such as when you fell asleep, how long you slept, or your sleep quality scores. (Reviewed: every finding cited here was graded low-severity, so the confident wording above is not backed by a real problem and this check passes.)

Strengths

  • Keychain items use device-only protection, preventing sleep schedule data from migrating to iCloud or other devices
  • Facebook automatic event logging is disabled, limiting unsanctioned behavioral data collection
  • The build names EU-based Amplitude endpoints as the destination of European users' analytics data
  • Event analytics self-hosted via Snowplow under the developer's own infrastructure rather than a third party
  • TikTok tracking is currently fully disabled despite the SDK being bundled
  • Payment processing uses Stripe with local AES encryption of payment data

What the app contains

  • 35 services

    Third-party services the scan names in the build:

    • Firebase Analytics
    • Firebase Crashlytics
    • Firebase Remote Config
    • Firebase Messaging
    • Amplitude
    • Snowplow
    • Airbridge
    • Braze
    • Datadog
    • Didomi
    • Google UMP
    • Google AdMob
    • Meta Audience Network
    • AppLovin MAX
    • Unity Ads
    • Vungle/Liftoff
    • Mintegral
    • Chartboost
    • TikTok Pangle
    • InMobi
    • Fyber/IASDKCore
    • Moloco
    • PubMatic OpenWrap
    • Amazon TAM
    • HyBid/PubNative
    • BidMachine
    • FiveAd
    • Daro Ads
    • Stripe
    • RevenueCat
    • Zendesk
    • TikTok Business SDK
    • Open Measurement SDK
    • Papertrail
    • hCaptcha

Libraries

Libraries in the build of Alarmy - Loud alarm clock
LibraryVersionAdvisory
Alarmynot recordednone confirmed

Changes since the previous scan

  • Version 26.31.0 (build 7161734), score 76.
  • Score 59 before, 76 after.
  • Score change since version 26.31.0 (build 7161734): +17 points.
  • Since the previous scan: 13 findings added, 10 removed.
  • Version 26.31.0 (build 7161734), score 59.
  • 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
23 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.