Overview
TIM is an iPhone app for tracking daily activity, reading the week more clearly, and spotting longer-term patterns over time. This policy explains how information is handled across the app, any optional Apple Health or iCloud behavior, App Store subscription verification, and the supporting backend services.
Data you create in the app
TIM stores the core tracking experience on device first. That includes activities, sessions, timestamps, mood ratings, notes, reminders, and app settings.
If iCloud sync is enabled for your build and device, a synced copy of app data may also be stored through Apple's iCloud and CloudKit services.
- Activity names, colors, targets, and schedule preferences
- Session start and stop times
- Optional mood scores and notes
- Notification preferences, theme choices, and AI preferences
Apple Health data
TIM only reads Apple Health data after you grant permission. Health access is optional.
When enabled, TIM uses the authorized metrics to improve trend analysis and pattern interpretation inside the app. Health permissions can be revoked at any time in iOS.
Purchases and Tim Pro verification
Tim Pro subscriptions are sold and billed by Apple through the App Store. TIM uses StoreKit to check whether the current device has an active entitlement.
When a Tim Pro feature needs backend access, TIM can send the verified App Store transaction data to the TIM backend so the service can issue a short-lived session token for that paid user.
Tim AI and cloud fallback
TIM prefers Apple Intelligence on supported devices. If Apple Intelligence is unavailable and cloud fallback is enabled for Tim Pro, the app can send a structured request to the TIM backend for weekly insight or Tim AI chat.
Cloud AI requests use the OpenAI Responses API with response storage disabled. TIM does not create a separate TIM web account for this flow.
Notes are excluded from cloud AI context unless you explicitly turn note sharing on inside the app settings. When note sharing is on, the app sends a short summary rather than the full note history.
Backend logs and protection
The TIM backend may store operational and security data needed to verify paid access, prevent replay attacks, enforce rate limits, and monitor service usage.
These logs can include hashed subject identifiers, hashed transaction identifiers, request IDs, timestamps, request status, provider/model metadata, token usage, estimated cost, and latency information.
Service providers
TIM relies on third-party platform providers that process data on TIM's behalf or at your direction.
- Apple for App Store billing, StoreKit verification, iCloud/CloudKit, and optional Apple Health access
- Vercel for hosting the TIM backend and this public website
- Postgres for backend request logs and rate-limit data when enabled
- OpenAI for Tim Pro cloud AI responses when Apple Intelligence is unavailable
Your choices
You can keep using TIM as a core timer without enabling Tim Pro AI, Apple Health, or note sharing.
You can revoke Apple Health permissions in iOS settings, turn AI features off in TIM settings, keep note sharing disabled, export supported records, and delete local data from your device.
Website data
This marketing site is static and does not create a customer account. It does not run a separate member portal or require sign-in for the routes on this domain.
If analytics, forms, or additional services are added later, this policy will be updated before that change goes live.
Contact
For privacy or support questions about TIM, contact the support address listed on this site.