Privacy Policy
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 usage analytics. The app contains no advertising, no usage-analytics SDK, no ad identifiers, and no third-party trackers. If the app crashes, it can send a crash report about the app itself, which never contains your Sentry data and is not linked to you. This is on by default, and you can turn it off (§5).
- One small server, for one feature. Push notifications require a relay we operate. It stores the minimum needed to deliver them (§3): never your Sentry token, and never the event data that Sentry's webhooks carry.
- 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. Only the app itself uses it, to call the Sentry API directly from your device. The widgets make no network requests: they show a small summary (unresolved count and the newest issue titles) that the app saves in a container shared with them on the device. The notification extension does not read the token or contact Sentry; it shows the notification as delivered.
- 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 appearance and app icon, favorite projects, which event types notify you, your project and minimum-level notification filters, the issue list filters you last used in each list, and the filters you save by name (a saved filter keeps its search text).
- Issues you follow on the Lock Screen: their IDs, kept so a Live Activity can start again (entries older than 30 days are dropped). A Live Activity shows the issue's title, status, and counters on your Lock Screen and in the Dynamic Island; iOS keeps it on the device, and the app updates it from Sentry while it is open.
- Crash report files (§5), only while "Share crash reports" is on: a report waiting to be sent after a crash, the crash reporter's working files and its random installation ID (removed from every report before it is sent), and whether the app was installed from TestFlight or the App Store. Turning crash reports off deletes them.
- 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, the cached data (including what the widgets use), your notification registration and filters, your remembered and saved issue list filters, and the issues you follow. Other preferences, such as favorite projects and appearance, stay on the device until you delete the app, which removes everything.
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 set up notifications, the app never registers with it. On the free plan, registered devices get a daily digest of new issues; Tracebell Advanced replaces it with real-time delivery of every event, with event-type, project, and minimum-level filters, and adds Live Activity updates and starts. Every registered device gets a weekly summary (in weeks with new issues). The relay stores your notification settings either way (it uses the filters only with Advanced); it accepts Live Activity data only with Advanced.
3.1 What the relay stores
- Your device's APNs push token (and whether it is a development or production token), so Apple can deliver notifications to the right device.
- Your Sentry organization slug, shown in the daily and weekly summaries and in the Live Activities the relay starts.
- Your notification settings — which kinds of events (new issues, regressions, resolved, assigned, archived, alerts) should produce a real-time notification, and your optional filters: the projects to watch (their numeric IDs and slugs, up to 50) and a minimum level (Info, Warning, Error, or Fatal).
- Live Activity data (Advanced only). While Live Activities are enabled for Tracebell in iOS Settings, the app syncs the start token iOS gives it, so the relay can start a Live Activity, and whether "Start Automatically" is on. When you follow an issue, the relay saves its numeric Sentry ID (up to 20 issues). Only while a Live Activity is running, the relay also keeps its update token, the issue's numeric ID, whether the app or the relay started it, and the last status and counters it showed (phase, event, user, and alert counts, last seen time, and when they changed), so every update can carry the full state. It stores no issue titles.
- Your integration's client secret, which you paste when connecting a Sentry internal integration. It is encrypted at rest and used only to verify that incoming webhooks really come from your Sentry organization; it cannot be used to read your Sentry data.
- Two random secrets, stored only as hashes: the secret part of your personal webhook URL, and the credential the app uses to update or delete its registration.
- An anonymous RevenueCat user ID and the last entitlement check, used only to decide between the free tier and the Advanced features (real-time delivery, filters, and Live Activity). It is a random identifier, not your name or email.
- Two counters — how many new issues arrived today and this week — for the digest and summary. Only the numbers are kept, and they reset after each summary.
- Timestamps of when the registration was created and last updated.
- Short-lived issue references (Advanced only, for real-time notifications). So that one issue produces one notification when Sentry reports it twice, the relay records the issue's numeric ID for 60 seconds after each real-time notification. If you receive alert notifications, it also keeps each issue's numeric ID, short ID (such as CHECKOUT-42), and project slug from Sentry's issue webhooks for 7 days, so an alert notification can show the same project and short ID as the issue notification. Both are deleted with the registration, and expired ones by a daily cleanup, so they can remain up to about a day longer. No titles or event data.
To slow down abuse, the relay counts requests in fixed time windows: registrations per client IP address (10 per 10 minutes), and per device: incoming webhooks (300 per 5 minutes), real-time pushes (60 per 5 minutes), test notifications and test Live Activities together (5 per hour), Live Activity sync requests from the app (30 per 10 minutes), Live Activity update pushes (30 per 5 minutes), and Live Activity starts (4 per hour). Each counter holds only its key, the start of its window, and a count. For registrations the key is a SHA-256 hash of the IP address, never the address itself; for everything else it is the registration's random ID. A device's counters are deleted with its registration, and a daily cleanup deletes every counter whose window started more than an hour earlier, so none is kept much longer than a day.
3.2 What the relay reads from webhooks
When Sentry calls your webhook, the relay receives the whole webhook body, which for alerts can include event data such as a stack trace. It verifies the signature and reads only the few fields a notification needs, and never stores or forwards the rest: the event type, the issue ID and short ID, the project slug, the issue's web link, and the issue title (or, for alerts, the alert rule name and event title), shortened to fit a notification. These are sent to Apple's push service (APNs) as the notification itself, so Apple processes them in transit to deliver the push. When the relay starts a Live Activity, the same fields (plus the issue's level) travel to APNs as the activity's contents. Updates to a running Live Activity carry only its status and counters. Of these fields, the relay keeps only the issue ID, short ID, and project slug, for a limited time (§3.1). It does not write webhook bodies, issue titles, alert rule names, or notification content to its database or to logs.
3.3 What the relay never has or keeps
- Your Sentry auth token. The relay has no copy of it and could not browse your Sentry data if it wanted to.
- Your stack traces, events, and source code. The app fetches those directly from Sentry (section 2). The relay receives Sentry's webhook body, reads only the fields in §3.2, and never stores or forwards the rest.
Disconnecting notifications, or signing out of the app, removes the registration from your device and asks the relay to delete it. Deleting on the relay is best effort: if it cannot be reached at that moment, the app still forgets the registration, and the relay removes the leftover record the next time it tries to send that device a push and Apple reports the token as invalid (for example after the app is deleted), or when the same device registers again. Until a push is attempted the record stays; email us and we will delete it. Deleting a registration also deletes its Live Activity data. If an Advanced purchase lapses, the registration falls back to the free notification tier, and when you next open the app it asks the relay to clear its Live Activity start token, setting, and followed issues.
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. Crash reports
To find and fix bugs in Tracebell itself, the app can send a report to the developer when it crashes. Only crashes are reported: no usage statistics, no performance data, no screenshots, and nothing about what you do in the app. The report is sent the next time the app starts (including a start in the background), to our own Sentry organization, which is separate from your Sentry account.
5.1 What a crash report contains
- When and where in Tracebell's code the crash happened: the date and time of the crash (and when the report was sent), the type of crash, a fixed description of it (such as "Index out of range"), the signal and Mach exception codes (for a system error, its domain and code), and the stack traces of all threads at the time of the crash, as memory addresses and function names.
- The list of loaded binary images (the app and the system libraries): their names, file paths that contain no device-specific folder, build UUIDs, load addresses, and sizes, which turn the addresses into function names.
- The app's bundle ID, version, and build (as the release name), whether it is a TestFlight or App Store build, and whether the app was in the foreground.
- The device family and model (for example "iPhone17,1"), its processor architecture, whether it is a simulator, and the iOS version and build.
- The app's language, only as English, Japanese, or other.
- How the app was connected at the time, only as demo, sentry.io, self-hosted, or not connected. The address of a self-hosted server is never sent.
- The crash reporter's name and version (sentry-cocoa), a random event ID for each report, and a random trace ID for each app launch. They identify the report, not you or your device.
5.2 What a crash report never contains
Your issues, events, stack traces, releases, or anything else from your Sentry account; your token; organization or project names; issue titles; the text of the crash message; your name or email address; and any identifier for you or your device. The crash reporter's random installation ID, thread names, file paths that contain a device-specific folder, and the device's memory, storage, battery, time zone, and language and region settings are removed on the device before anything is sent.
Your IP address is not included in a report and is not stored. As with any internet connection, Sentry's servers see the address a report comes from, and our Sentry organization has "Prevent Storing of IP Addresses" turned on for the whole organization. Reports are therefore not linked to you.
5.3 Your choice
Crash reports are on by default, from the first time you open the app. The app does not ask about them or show a notice at first launch or after an update. You can turn them off at any time with the "Share crash reports" switch in Profile → Diagnostics, where "What is sent" lists what a report contains. Turning it off takes effect immediately and deletes any report waiting on the device. The app works the same with it off.
5.4 Where and how long
Crash reports are processed and stored by Sentry (Functional Software, Inc.) in the United States, as our processor, and are deleted after 30 days. If that retention period changes, this page changes with it.
5.5 The push relay's own failures
The relay reports its own failures (for example, when Apple's push service rejects its key) to the same Sentry organization. Such a report names the part of the relay that failed, the kind of error, where in the relay's code it happened, and fixed details such as the route pattern or Apple's status code. It contains nothing from a device, an account, a webhook, or a notification: no tokens, secrets, organization slugs, issue titles, or IP addresses. To cap these reports at 50 a day, the relay keeps one counter per day, holding only the date and a number, and deletes earlier days' counters daily.
6. Third parties, complete list
| Service | Purpose | What it receives |
|---|---|---|
| Sentry (your own account) | The service the app is a client for | API requests made with your token, directly from your device |
| Apple (APNs, App Store) | Push delivery and purchases | Push tokens, notification payloads, and Live Activity contents; purchase processing |
| RevenueCat | Subscription management | Anonymous user ID, purchase status |
| Cloudflare | Hosts the push relay and this website | The relay data listed in §3.1; standard web server logs for this site |
| Sentry (our own organization, United States) | Crash reports from the app and failure reports from the relay | The crash and failure reports described in §5. The connecting IP address reaches Sentry's servers but is not included in reports or stored |
That's the whole list. There is no usage-analytics provider, no advertising network, and no data broker. Our Sentry organization receives only the app's crash reports and the relay's failure reports described in §5.
The third parties we share user data with (Sentry, RevenueCat, and Cloudflare) process it only for the purposes listed above and provide the same or equal protection of user data as stated in this policy and required by Apple's App Store Review Guidelines.
7. In App Store terms
For Apple's privacy "nutrition label", the data collected is: Identifiers (the APNs push token, the Live Activity push tokens, and the anonymous RevenueCat user ID), Purchases (purchase and subscription status), Other Data (the organization slug, notification settings, webhook secrets, Live Activity settings, followed-issue IDs, the status and counters of running Live Activities, the short-lived issue references (issue IDs, short IDs, and project slugs), and the rate-limit counters described in §3.1), and Diagnostics → Crash Data (the crash reports in §5), all used only for app functionality. 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, all five types (Device ID and User ID under Identifiers, Purchase History, Other Data, and Crash Data) are declared as not linked to you, and nothing is shared with data brokers.
8. 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 verified against your integration's signing secret.
- We never ask for, and cannot access, your Sentry password.
9. 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 asks the relay to delete them (best effort; see §3.3). Your notification settings and Live Activity settings are replaced each time the app updates the registration.
- A running Live Activity's record is deleted when the activity ends, and in any case it expires 8 hours after the activity started (when iOS ends Live Activities); expired records are removed by a daily cleanup, so a record can remain for up to about 32 hours.
- Rate-limit counters are deleted with the registration, or by the daily cleanup once their window has passed (§3.1).
- Issue references expire 60 seconds (duplicate check) or 7 days (alert labels) after they are written, and are deleted with the registration or by the daily cleanup after they expire (§3.1).
- The relay keeps no log of notification contents.
- Crash reports and the relay's failure reports are deleted by Sentry after 30 days. A report still waiting on your device is deleted when you turn crash reports off. The relay's daily report counter is deleted the next day.
- Purchase records are retained by Apple and RevenueCat under their own policies.
10. Your choices
- Notifications: disconnect them any time in the app (or sign out); this asks the relay to delete your registration (best effort; see §3.3).
- Token: revoke it any time in your Sentry account settings; the app immediately loses access.
- Local data: sign out to clear the token and cached data, or delete the app to remove everything.
- Crash reports: on by default; turn "Share crash reports" off in Profile → Diagnostics at any time; it applies immediately (§5).
11. 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.
12. 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.
13. Contact
Questions about this policy? Email [email protected].