Telemetry & Crash Reporting
This notice is published in English. English is the authoritative version; any translation is provided for convenience only.
This document exists because "we collect anonymous usage data to improve the app" is the kind of sentence that tells you nothing. Below is what qUnleashed actually transmits, what it refuses to transmit, why the default is what it is, and how to stop it. It is written against the project's own design record for this subsystem, so it describes the shipped behaviour rather than an intention.
Crash reporting is ON by default and sends automatically. There is no consent gate. A notice is shown once at first launch explaining this and offering an immediate Turn it off button, and reporting is already running while that notice is on screen. We are telling you, not asking you — and we are telling you here too, rather than on page 14 of a policy.
1. Why it is on by default
qUnleashed talks to physical hardware over two transports across five operating systems. The failures that matter most are the ones nobody on the project can reproduce: a Bluetooth stack misbehaving on a specific handset, a USB serial driver on a Windows build we do not have, a firmware write interrupted by a vendor's battery optimiser.
An opt-in crash reporter on a tool with this audience collects from a single-digit percentage of installs. That is not a sample; it is noise. The decision was made explicitly — on by default, sent automatically, with the privacy work done up front in the scrubbing and masking rather than in a consent dialog nobody reads — and the consequence of that decision is that this page has to be unusually specific.
2. What is sent
| What | Detail |
|---|---|
| Crashes | Native and Dart crashes: exception type, message, stack trace, thread state |
| Handled errors | Failures the app caught and recovered from, with the frames that produced them |
| Log lines | What the app logs at its kept levels, after scrubbing. The app has no on-screen log of its own any more; this channel replaced it. |
| Build identity | App version, build number, release channel (stable or dev), commit identity |
| Environment | Platform, OS version, device model, locale, available memory and storage state |
| Flipper identity | Device name, serial number, Bluetooth LE address and the device info
dump — when the report concerns a connected device |
| Performance | Traces and metrics for operations such as archive sync, file transfer and firmware install |
| Session replay | Android and iOS only, masked, uploaded only when something fails — see §4 |
2.1 Why the Flipper's identifiers are not hidden
Device name, serial, BLE address and the device info dump are sent intact,
and that is a decision rather than an oversight. These identify a Flipper Zero, not a
person. A Flipper's name is generated, not chosen from your identity, and a serial or a
BLE address is frequently the single fact that explains why a bug happens on one unit and
not another.
An earlier design blanket-redacted every long hexadecimal run, which took these out along
with everything else. The result was the worst of both worlds: reports that named no
device beside logs that said <redacted> where the answer should have
been. That rule was removed on purpose.
3. What is never sent
A scrubber runs on every event, breadcrumb, log line and trace immediately before transmission. Nothing reaches the network without passing through it.
| Never leaves | How it is prevented |
|---|---|
| Recovered MIFARE keys and card UIDs | No log call in the MIFARE tooling writes a key or card UID into a message; the replay masks those surfaces outright |
| GPS coordinates | Latitude/longitude pairs are stripped by the scrubber; the map widget is masked in replay |
| Archive file names | Names under /ext and /int are replaced. The extension
survives, because the format matters to a diagnosis and the name does not |
| Your account name and home path | C:\Users\yourname\… becomes ~\…, in both the native and
the file:/// URI spelling, so a stack trace does not carry it |
| URL query strings | Stripped by the scrubber |
| Your IP address | IP storage is disabled server-side at Sentry, so it is not retained with the event |
| Screenshots and view hierarchy | Both disabled explicitly in the SDK configuration, not merely left at a default |
| Advertising identifiers | Never read. The app contains no advertising SDK on any platform. |
| Account data | There is no account. sendDefaultPii is set to false. |
| Your archive contents | File bodies are never attached to any event |
A second layer of scrubbing rules runs server-side at Sentry, covering the same patterns. That layer exists because native crashes do not pass through the application's own scrubber at all — they are captured by the platform before Dart code can touch them.
4. Session replay, in detail
"Errors only" describes the upload, not the recording. The recorder runs continuously into a rolling in-memory buffer; that buffer is thrown away unless a crash arrives, and only then does the preceding segment get uploaded. We state it this way because "errors only" could be read as "recorded only then", which would be false.
What makes this acceptable as a default is that masking is applied at capture time. The buffer never contains card bytes, a recovered key, a pulse capture or your location in the first place — not even for the seconds it exists before being discarded.
4.1 What is masked
All text is masked by default. Beyond that, the following are named individually in the configuration, because each paints its own pixels or glyphs and no automatic rule reaches them:
- The hex editor, which paints card bytes directly
- The remote-desktop screen, which is your Flipper's live display
- The code and text editor — this is the view you land on by default, so opening an NFC file would otherwise show the UID, ATQA, SAK and key blocks
- The CLI terminal, where
storage read,nfcandsubghzoutput lands as raw text - The pulse plotter, with its bit view and histogram
- The map, which would otherwise record your own position with your GPS-tagged pins on it
- Every raw image, as a catch-all — in this app a raw image is device or user content by construction
Masking is applied by enclosing type rather than per-screen, and the filter stops descending once it decides to mask, so a new widget added inside any of those is covered the day it is written rather than the day somebody remembers to add it. Automated tests assert that each rule is present and that it masks rather than unmasks.
4.2 What is deliberately left legible
A replay where every label is a grey rectangle is five minutes of silent video nobody can read, which helps no one. Buttons, navigation labels and the device info line are unmasked on purpose, so a replay shows what you were doing without showing what you were doing it to.
4.3 What it costs you
Roughly +13% CPU and +5% memory on Android, and +6% CPU on iOS — paid by every session, not only the ones that fail, because the recorder is always running. That is precisely why replay has a switch of its own rather than riding on the crash-reporting switch. Replay does not exist on macOS, Windows or Linux; the SDK does not support it there, and the settings row is hidden rather than shown as a control that does nothing.
5. The two switches
Settings → Diagnostics
- Share logs with developers — the master switch. Off means
Sentry.close(): the SDK and its native crash handlers are shut down. Nothing is captured, nothing is queued, nothing is transmitted later when you reconnect. Switching it back on starts it again. - Session replay — subordinate to the first. Off means crash reports still go, without the recording and without its CPU cost. Hidden on desktop, where replay does not run; hidden when the master switch is off, because there would be nothing to attach a replay to.
The first-launch notice also carries a Turn it off button, so the choice costs one tap at the moment you are being told, rather than a hunt through settings afterwards.
6. What turning it off costs you
Stated plainly, because it is real: with diagnostics off, nothing records a failure beyond what the screen in front of you already says.
qUnleashed has no local log screen. There used to be one, and it was removed when Sentry became the single diagnostic channel — keeping both meant two mechanisms, two scrubbing levels and two notions of what a repeated line is, to preserve a manual copy-and-paste route for the small minority who had opted out.
So if you turn it off and then hit a bug, the way to report it is to describe it in words in a GitHub issue: what you did, what you expected, what happened, which platform and which app version. That works; it is just slower than a report that arrives with a stack trace.
7. Who receives it, and for how long
Reports go to Sentry (Functional Software, Inc., trading as Sentry), acting as a processor for the project under its Data Processing Addendum. Processing may take place in the United States; transfers out of the EEA and the UK rely on the EU–US Data Privacy Framework and/or Standard Contractual Clauses as set out in that addendum.
Events are visible to project maintainers, are retained for the retention window of the project's Sentry plan and are then deleted automatically. The project does not export events into any other system, does not build profiles from them, does not sell them and does not share them for advertising. They are read for one purpose: finding out why something broke.
8. Builds with no reporting at all
The reporting endpoint is supplied at compile time. A build compiled without it — which
includes any build you compile yourself from source — initialises no SDK
and transmits nothing, regardless of how the switches are set. The source is GPL-3.0 and
the whole telemetry subsystem lives in one folder, so you can read exactly what it does
instead of taking this page's word for it:
lib/services/telemetry/,
with the design record in
docs/adr/0013-observability-with-sentry.md.
Google Play's pre-launch report, which runs on Firebase Test Lab, never starts reporting either — a robot's session does not become real events.
See also: Privacy Policy · Terms of Service · Legal Notice & Licenses