Privacy Policy

Last updated: November 14, 2026

Tracebell ("the app", "we") is an unofficial iPhone client for Sentry, built by an individual developer. This policy describes exactly what the app does with your data. The short version:

• Your Sentry auth token never leaves your device. It is stored only in the iOS Keychain, on that device, and is never synced to iCloud or sent to any server we operate.
• The app talks directly to Sentry. Your issues, stack traces, and project data travel between your device and the Sentry API over HTTPS. They do not pass through our servers.
• No ads, no tracking, no analytics. The app contains no advertising, no analytics SDK, no ad identifiers, and no third-party trackers.
• One small server, for one feature. Push notifications require a relay we operate. It stores the minimum needed to deliver them (§3) and never your Sentry token or event payloads.
• Purchases are handled by Apple and RevenueCat. We never see your payment details.
• We don't sell, rent, or trade your data. Ever.

1. Information stored on your device

Almost everything the app knows lives only on your iPhone:

• Your Sentry auth token (a User Auth Token you create in Sentry and paste into the app), stored in the iOS Keychain with device-only protection — it is not included in iCloud Keychain sync. The app, its widgets, and its notification extension read it through a shared Keychain access group so each of them can call the Sentry API directly from your device.
• Connection details: the server address (sentry.io or your self-hosted URL) and the organizations you selected.
• Cached Sentry data (issue lists, project summaries) kept locally so the app and widgets open fast.
• App preferences such as display options and notification filters.
• Demo data: the demo workspace is fictional sample data bundled with the app; it involves no network access and no real accounts.

Signing out removes the token and the cached data, including what the widgets and extensions use.

2. The app talks directly to Sentry

When you browse issues, read a stack trace, or resolve an issue, the app calls the Sentry API (sentry.io, its regional domains, or your self-hosted server) directly from your device over HTTPS, using your token. We operate no proxy in that path, so we never see your issues, events, stack traces, or source context. Your use of Sentry itself is governed by Sentry's own terms and privacy policy.

3. The push relay (notifications)

Push notifications cannot work purely on-device: Sentry needs a webhook destination that is always reachable, and only Apple can deliver a push to your iPhone. For this one feature we operate a small relay (a Cloudflare Worker). If you never turn on notifications, the app never registers with it. The free tier includes a heads-up notification for new issues and a weekly summary; Tracebell Advanced adds real-time delivery of every event and event-type selection. The relay stores the same data either way.

3.1 What the relay stores

• Your device's APNs push token, so Apple can deliver notifications to the right device.
• Your Sentry organization slug, so notifications can be labelled and routed to the right account in the app.
• Your event-type preferences — which kinds of events (for example new issues, regressions, alerts) and which project/level filters should produce a notification.
• A webhook secret — a random secret that is part of your personal webhook URL (stored hashed) and, if you choose to provide it, your integration's signing secret, used to verify that incoming webhooks really come from your Sentry organization.
• An anonymous RevenueCat user ID, used only to check whether Tracebell Advanced is active, which determines the notification tier (free heads-up and weekly summary, or real-time delivery of every event). It is a random identifier, not your name or email.

3.2 What the relay never stores

• Your Sentry auth token. The relay has no copy of it and could not browse your Sentry data if it wanted to.
• Webhook payloads. When Sentry calls the relay, the relay extracts the minimum needed to form a notification (issue ID, short ID, project, level, event type, and — only if you allow it — a truncated title) and discards the body. Payloads are not written to a database or to logs.
• Notification content, in the private mode. You can choose "don't send titles through the relay". The push then carries only an issue reference, and the notification extension on your device fetches the title and details directly from the Sentry API with your local token before showing it.

Turning notifications off, or signing out, deletes your relay registration. If an Advanced purchase lapses, the registration falls back to the free notification tier.

4. Purchases (RevenueCat and Apple)

Tracebell Advanced and the optional tips are sold through Apple's in-app purchase system. We use RevenueCat to manage purchase status. RevenueCat receives an anonymous app-generated user ID, your purchase and subscription status, and standard receipt information from Apple — never your name, email, or payment details, which stay with Apple. See RevenueCat's privacy policy for details on their processing.

5. Third parties, complete list

That's the whole list. There is no analytics provider, no crash-reporting provider, no advertising network, and no data broker.

6. In App Store terms

For Apple's privacy "nutrition label", the data collected is: Identifiers (the APNs push token and the anonymous RevenueCat user ID) and Purchases (subscription status), both used only for app functionality, and the organization slug and notification preferences described in §3.1. None of it is used for advertising or tracking as Apple defines it, none of it is linked to your real-world identity by us, and nothing is shared with data brokers.

7. Security

• The token is stored in the iOS Keychain with device-only accessibility (no iCloud sync).
• All network traffic uses HTTPS.
• Webhook deliveries to the relay are authenticated with a per-user secret URL, and optionally verified against your integration's signing secret.
• We never ask for, and cannot access, your Sentry password.

8. Data retention

• On-device data stays until you sign out or delete the app.
• Relay registrations stay until you turn notifications off or sign out, which deletes them.
• The relay keeps no log of notification contents.
• Purchase records are retained by Apple and RevenueCat under their own policies.

9. Your choices

• Notifications: turn them off any time in the app; this deletes your relay registration.
• Private notification mode: keep issue titles out of the relay entirely (§3.2).
• Token: revoke it any time in your Sentry account settings; the app immediately loses access.
• Local data: sign out to clear it.

10. Children

The app is a developer tool, is not directed at children under 13, and we do not knowingly collect information from children under 13.

11. Changes

If this policy changes, we will update the date at the top of this page. Material changes will be noted in the app's release notes.

12. Contact

Questions about this policy? Email oikon48@gmail.com.