Good context.
Clear boundaries.

When Crumb collects anything

Adding Crumb to an app doesn’t start any collection. Starting the SDK doesn’t take a screenshot, read logs, write a report, or make a network request.

Crumb collects information only when a person explicitly opens the reporter, either through a control the app provides or by shaking the device while the app is open. It then captures that single moment. Nothing is collected continuously.

Optional features, off by default

• Crash capture for React Native. If a developer turns it on, Crumb keeps a small, cleaned-up record of a fatal JavaScript error so it can be reported after the app restarts.
• Rendering diagnostics. If a developer turns it on, Crumb keeps the last five seconds of frame-timing numbers in memory while the app is open. The data is cleared when the app goes to the background. No images are kept.
• Screen context. A developer can attach a fixed screen name to reports. Crumb doesn’t record navigation history or read navigation parameters.

What a report can contain

When someone sends a report, it can include:

• the category they selected and the description they wrote;
• a contact value, if the app shows that field and they fill it in;
• a screenshot taken just before the reporter opened, with sensitive areas masked, unless they removed it;
• technical context such as the app version, device model, operating system, language, display, memory, CPU, temperature state, and network type;
• a short, limited excerpt of recent logs from the app; and
• the result of one optional check on whether the Crumb service is reachable.

If React Native crash capture is on, a report can also include the error type, message, a limited stack trace, and recent Crumb breadcrumbs.

What Crumb never collects

• Screen recordings or a replay of what someone did in the app.
• Anything from other apps on the device.
• System-wide Android logs.
• The contents of the app’s network requests or responses.
• The app’s internal state or memory.
• The developer’s project key. It’s used to send reports and is never included in one.

Protection on the device

Before anything is saved or sent, Crumb removes or hides sensitive information on the device itself.

• Screenshots. Text fields and any areas the app marks as sensitive are covered before the image is created. The unmasked image is never saved or uploaded.
• Logs and descriptions. Crumb strips out recognizable passwords and access tokens, email addresses, payment card numbers, and sensitive parts of web addresses.
• Limits. Logs are limited by age and size, and reports that are too large are rejected rather than sent.
• Review. The person reporting sees what’s attached and can remove the screenshot before sending.

Storage and sending

Draft and submitted reports are stored in the app’s private storage on the device, which other apps can’t access. A submitted report is saved to a local queue before the reporter confirms it was sent, so it isn’t lost if the connection drops or the app restarts.

If the app is set up to upload reports, Crumb sends them over an encrypted HTTPS connection and retries until they’re delivered. If it isn’t, reports stay on the device.

On iOS, Crumb’s requests are fully separated from the app’s own cookies and saved credentials. On Android, a cookie handler the app sets up for all its connections may also apply to Crumb’s requests. Our developer documentation explains how to keep them separate.

Who controls the data

Crumb is a tool that developers add to their own apps. The app’s developer decides whether to use Crumb, which information to collect, and where reports are sent.

Once reports reach a developer’s Crumb workspace, that developer controls who can see them, how long they’re kept, and when they’re deleted. If you’ve sent a report from an app and want to see or delete it, contact that app’s developer. They can act on your request from their workspace.

If you build with Crumb

As the developer of an app that uses Crumb, you’re responsible for:

• describing Crumb’s collection accurately in your app’s privacy notice;
• choosing collection settings that fit your users and where they live;
• keeping sensitive values out of the logs you share with Crumb;
• getting any consent your users must give for screenshots, diagnostics, or contact details; and
• responding to your users’ requests to see or delete their reports.

Crumb’s iOS packages include Apple privacy manifests covering the system features the SDK uses. You still need to fill in your app’s own data-collection details for the App Store, based on how you’ve set Crumb up.

This website

crumbsdk.com doesn’t use cookies, analytics, advertising, or tracking scripts. Its fonts and images are served from this site, not from third parties.

Questions and changes

If you’re a Crumb customer, send privacy or security questions to the support contact shown in your Crumb workspace. If you sent a report from an app, contact that app’s developer.

When this page changes, we’ll update the date at the top.