Tracebell is an unofficial client. It is not affiliated with Sentry (Functional Software, Inc.).

Privacy Policy

Last updated: November 16, 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:

1. Information stored on your device

Almost everything the app knows lives only on your iPhone:

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

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

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

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

ServicePurposeWhat 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

9. Data retention

10. Your choices

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].

Tracebell is an independent, unofficial client. It is not affiliated with, sponsored by, or endorsed by Functional Software, Inc. Sentry is a registered trademark of Functional Software, Inc.