Get the app

Timme training guide

Privacy Policy - Timme

A fully customizable fitness timer app for iPhone, iPad, Apple Watch, and Apple Silicon Mac.

Privacy Policy

Last updated: July 2026

Timme (“we”, “our”, or “the app”) is committed to protecting your privacy. This Privacy Policy explains how we handle information when you use our fitness timer application.

Information We Collect

Data Stored Locally by Default

Timme stores the following data on your device:

  • Workout configurations - Custom workouts you create and save
  • App preferences - Theme settings, sound preferences
  • Workout history - Records of completed workouts (if enabled)

Saved workouts can also be stored in your private iCloud database if you choose to enable iCloud Sync. Live Activity and anonymous-counter data are handled as described below.

Optional iCloud Sync

If you enable iCloud Sync, saved workout configurations and deletion records are sent to Apple’s CloudKit service and stored in your private iCloud database so your Apple devices can stay in sync. Timme’s Cloudflare backend does not receive this data. You can disable sync in Timme Settings and manage your iCloud data through your Apple account and devices.

Data We Do NOT Collect

Timme does not collect, store, or transmit:

  • Personal identification information (name, email, address)
  • Location data
  • Health records, location, or motion-sensor data
  • Per-user behavioral tracking
  • Advertising identifiers (IDFA) or any device-level identifier

Anonymous Counters

Timme shares anonymous, aggregate counters with us so we can see how the app is being used overall. This is on by default since version 1.5.0, and you can turn it off at any time in Settings → Anonymous usage counters. Because the counters contain no identifier of any kind (see below), they cannot be used to track you — but the off switch is always yours.

When enabled, the app sends three event types to our own server (Cloudflare Workers, hosted by us — not a third-party analytics service):

  • workout_started — sent when a workout timer begins
  • workout_completed — sent when a workout finishes
  • paywall_shown — sent when the upgrade screen is displayed

Each request contains the event name, the app version (for example 1.5.0), and a random one-time delivery key used to prevent duplicate counting. The key is not reused across events, workouts, app launches, or devices. It does not contain a user ID, device ID, advertising ID, workout name, or other stable identifier.

Cloudflare necessarily processes network information, including the source IP address, to deliver the request and enforce short-lived abuse limits. Timme does not write source IP addresses to its database or application logs. A delivery record containing the one-time key and its event bucket is deleted within 24 hours. Daily totals by event and app version are retained for up to 24 months. Individual usage cannot be reconstructed from those totals.

The purpose is to know things like “how many workouts were started this week” — not who started them.

Live Activity (iOS)

If you enable the Lock Screen / Dynamic Island Live Activity (iOS only), Timme sends data to a Timme-operated Cloudflare Worker so Apple can deliver reliable updates while the app is backgrounded. This includes a random session ID, workout ID/name/type, round and set counts, phase timeline and current timer state, and the temporary Apple Live Activity push token. It does not include an account, advertising ID, or stable device identifier.

Session creation returns a random credential used only for that Live Activity. The server stores only a cryptographic hash of the credential. Session records, event snapshots, push-delivery logs, and abandoned sessions are automatically deleted within 24 hours of their last update. Cloudflare processes the source IP transiently for delivery and abuse prevention, but Timme does not store it. Turning both Live Activity surfaces off stops server updates; the timer itself always works without a network connection.

Apple Watch Sync

If you use Timme with an Apple Watch:

  • Workout data is synced directly between your iPhone and Apple Watch using Apple’s WatchConnectivity framework
  • This sync happens locally over Bluetooth/WiFi
  • No data is sent to external servers

Third-Party Services

Timme does not integrate with advertising or third-party analytics SDKs such as Google Analytics, Firebase Analytics, Mixpanel, Amplitude, Adjust, AppsFlyer, or Branch. Cloudflare provides the infrastructure for Timme’s anonymous counters and Live Activity service and processes requests on Timme’s behalf.

If you subscribe to Timme Pro, payments are processed by Apple (App Store) and managed via RevenueCat for receipt validation. Apple receives information necessary to process the payment per its own privacy policy.

Data Security

Locally stored data is protected by your device’s security features. Optional iCloud data is stored by Apple in your private CloudKit database. Timme’s backend can process the limited Live Activity data listed above during its retention period; it cannot use that data to identify an account because Timme has no accounts.

Children’s Privacy

Timme does not knowingly collect information from children under 13. The app is designed for general audiences interested in fitness timing.

Changes to This Policy

We may update this Privacy Policy from time to time. Any changes will be posted on this page with an updated “Last updated” date.

Contact Us

If you have questions about this Privacy Policy, please contact us:

Email: support@timme.app

Back to Home