LimitWatch Lite Privacy Policy

1. Data we process

• A privacy-filtered quota snapshot produced by the Mac or Agent you select, such as provider name, remaining percentage, reset time, aggregate cost, and alert state.
• APNs or FCM device tokens and bounded platform, locale, app-version, registration, and delivery metadata when notifications are enabled.
• Crash, performance, and other diagnostic data when anonymous diagnostics are enabled.
• Messages you choose to send to support.

2. QR pairing and local network

The iOS and Android pairing QR contains only a version, private-LAN snapshot endpoint, local access token, and token fingerprint. It contains no upstream LimitWatch credential, quota snapshot, push registration, account profile, or full session. Apple devices can use it to connect to a Mac on a different Apple Account.

Scanning occurs on the device. LimitWatch Lite does not save or upload camera photos or video. Connection data is stored using platform secure storage. The current v1 LAN path permits bearer-protected HTTP, so the HTTP content itself is not encrypted and should be used only on a network you trust.

3. Apple iCloud

Apple-native clients may use iCloud KVS to sync a privacy-filtered quota snapshot, minimal connection discovery, and required preferences across devices on the same Apple Account. Cross-account Apple pairing uses the Mac QR and local-network path described above. Android does not use iCloud. Apple processes iCloud data under its terms.

4. Push notifications

iOS uses Apple Push Notification service. Android uses Firebase Cloud Messaging and Firebase Installations. The push service stores only device identifiers and bounded runtime metadata needed for routing and delivery, and does not return full tokens through health responses or the UI.

5. Anonymous diagnostics

LimitWatch Lite uses Sentry for crash, performance, and other diagnostic data, not advertising or cross-product tracking. Anonymous diagnostics are on by default and can be disabled in Settings for future reports. Reports already sent are not deleted, and an already authorized queued report may still finish sending. User-interaction tracing and navigation recording are disabled.

6. Purchases

The iOS app uses Apple StoreKit and the Android app uses Google Play Billing. Both load the yearly and lifetime products, process transactions, restore purchases, and determine entitlement. Purchasing is not yet publicly available. Once enabled, Apple or Google Play processes payment and subscription management; LimitWatch Lite does not access full payment-card details. Android currently queries and acknowledges owned Google Play purchases on-device without exposing a purchase token to JavaScript. If future server verification transmits purchase records or tokens, we will re-audit the Play Purchase history declaration before Data Safety submission. Auto-renewing plans can be managed in the corresponding store-account settings.

7. Data we do not collect

• Advertising identifiers or cross-app/site tracking data
• Contacts, precise location, photos, videos, or audio files
• Raw AI-provider credentials
• Full terminal output, full sessions, raw transcripts, or project paths

8. Purpose and sharing

Data is used only to provide sync, quota displays, widgets, alerts, purchase restoration, reliability, and support. We do not sell personal data. Apple, Google Firebase, and Sentry act only as service providers for their respective functions.

9. Retention, security, and controls

Connection credentials use platform secure storage. Local cache and preferences stay on the device or in the app group. Server-side records are retained only as long as needed for push delivery, troubleshooting, and security. You can disable diagnostics, disable notifications, clear a connection, or uninstall the app.

10. Children, transfers, and changes

The product is not directed to children under 13. Service providers may process data outside your region under their published safeguards. We update the date on this page when material terms change.