Privacy Policy

Where your data lives

Session and haptic logic run locally on the watch, and AtLeast keeps working with no network at all. Nothing is uploaded as an AtLeast account or personal profile—there is no account to make, and we run no server of our own.

Your custom timers and session history sync between your own devices through your private iCloud database whenever you are signed in to iCloud. There is no sync switch inside AtLeast: sync follows your iCloud account, and you can turn it off for AtLeast in iOS Settings under your Apple Account's iCloud app list, or by signing out of iCloud. That is your iCloud account, not ours: BrightDigit cannot read it. Starting a session also sends limited configuration via analytics (see below)—never for advertising.

Apple Health

Each timer has an optional session type. If you set one, a finished session is saved to the Health app on your own device—as Mindful Minutes, or as a workout (Yoga, Mind & Body, Flexibility, Cooldown, Core Training, or Traditional Strength), depending on the type. A timer with no session type writes nothing to Health. Saving to Health is free; AtLeast Pro widens the range of session types you can choose from.

AtLeast only writes to Health. It never reads your Health data—the app requests no read permission at all—and nothing you save to Health is sent to BrightDigit or to any third party. The record is written by the device that ran the session, and Health itself syncs it between your devices under Apple's terms. Whether it appears in Health, and what you do with it afterwards, is controlled by you in the Health app.

The first time you pick a session type, iOS shows the Health permission sheet. It asks for both mindful-session and workout sharing at once, so that switching a timer from meditation to yoga later does not need a second prompt—that is why a meditation timer asks about workouts. You can change either permission at any time in the Health app under Sharing.

Analytics

We use Plausible, a privacy-friendly analytics service that does not use cookies or persistent identifiers and is not used for advertising or cross-app or cross-site tracking.

• Website: page analytics for atleast.app; outbound-link clicks; custom events Nav: UseCases click (variant) and TestFlight: Click (variant, location)
• iPhone and Apple Watch apps: cookieless events via AviaryInsights (a Plausible client) on both platforms— a launch event (ios_open) with a watch_paired property on iPhone; pageview screen views across app screens; and session_start on each watch session with duration_seconds, tap_interval_seconds, haptic_config, and preloaded_from_phone. All app events also carry a device model identifier (a system-model property such as iPhone16,1 or Watch7,4), which is likewise part of the User-Agent Plausible uses for its device breakdown. It names a hardware model shared by millions of devices—it is not a personal or persistent identifier.

Turning it off. App analytics are on by default, and you can switch them off at any time: open AtLeast on your iPhone, go to Settings, and turn off Analytics & crash reports. The setting applies to both the iPhone app and the Apple Watch app—the watch has no Settings screen of its own, and the choice is carried to it through your iCloud account—and it covers crash reports (below) as well as analytics. With it off, the apps send no events and no crash reports. The toggle is an app setting; the website's page analytics, described above, are separate and set no cookies.

Crash reports

When the app crashes or hits an error, a report goes to Sentry so we can find and fix it. A report describes what the app was doing when it failed—the error, where in the code it happened, and the device and app version. It carries no personal profile and is never used for advertising.

Crash reporting shares the analytics opt-out. The in-app Analytics & crash reports toggle in Settings on your iPhone controls both, on the Watch as well as the phone: it is on by default, and turning it off stops AtLeast sending either one.

Purchases

If you buy anything in AtLeast, your purchase history is processed by RevenueCat, which manages purchases and entitlements on our behalf. There are still no accounts: RevenueCat identifies a purchase with an anonymous app user ID.

That purchase history is used for app functionality—unlocking the Pro features you paid for and validating receipts—and for analytics, such as purchase charts and customer history. It is not linked to your identity, and it is not used for advertising or cross-app tracking.

What we do not collect

• No accounts or sign-in
• No personal identifiers or advertising IDs
• No location data
• No reading of your Health data—AtLeast only writes the sessions you choose to save
• No advertising SDKs, and no cross-app or cross-site tracking

Third parties

Plausible provides analytics for the website and for the iPhone and Apple Watch apps (via AviaryInsights). Sentry receives crash and error reports from the apps. RevenueCat processes in-app purchases and entitlements. Those are the only third parties AtLeast shares data with, and none of it is advertising: AtLeast has no advertising SDKs. Your synced timers and history sit in your own iCloud account, and any sessions you save to Health sit in your own Health app—both held by Apple under Apple's terms, not in any system of ours, and not readable by us.

Contact

Questions about this policy? Email us at support@atleast.app .