Privacy Policy
This policy is published in English. English is the authoritative version; any translation is provided for convenience only.
The short version. qUnleashed has no accounts and no advertising, and it does not sell or share your data with anyone for marketing. Your Flipper files, saved keys and settings stay on your device. The one thing that leaves automatically is a diagnostic stream of crash reports, errors and logs, sent to Sentry. There is a switch for it in Settings. Keys, card UIDs, GPS coordinates and archive file names are removed before anything is sent.
1. Who is responsible, and how to reach us
qUnleashed is developed and published by the DarkFlippers project, an unincorporated open-source project. For the purposes of the EU and UK General Data Protection Regulation, the project acts as the controller for the limited processing described in this policy.
The project does not operate a support mailbox. The contact channel for anything in this policy, privacy requests included, is:
- GitHub Issues — github.com/DarkFlippers/qUnleashed/issues (a privacy request can be opened as a normal issue, and you do not have to disclose anything beyond the request itself)
Issues are public. Do not post anything you would not want published; if a request needs private detail, say so in the issue and we will arrange a private channel.
2. What stays on your device
qUnleashed is a local-first application. The following is created, read and stored only on the device you installed it on, and is never uploaded to any server operated by the project — because the project operates no such server:
- Your archive: Sub-GHz, Wardriving, RFID 125, NFC, Infrared, iButton, Bad USB and JavaScript files synced from your Flipper Zero, including saved keys and card data
- Recovered MIFARE keys and card UIDs computed by the Extract MIFARE Keys tool
- Files you browse, edit, upload or download through the file manager
- Pixel Draw projects, saved infrared remotes and pulse captures
- The list of Flipper devices you have paired, and their connection state
- All application settings and preferences
There is no account, no sign-in, no cloud sync and no backup service. If you uninstall the app, this data goes with it, subject to whatever your operating system's own backup settings do (Android auto-backup, iCloud, Time Machine and the like are outside our control and governed by your OS vendor's policy).
3. Diagnostics and crash reporting (Sentry)
This is the only category of data that leaves your device automatically, so it is described here in full. A longer, engineering-level account is in the Telemetry & Crash Reporting notice.
3.1 What it is, and that it is on by default
qUnleashed uses Sentry (Functional Software, Inc., trading as Sentry) to collect crash reports, handled errors, application log lines, performance traces and metrics. It is enabled by default and sends automatically, from first launch, without asking first. A one-time notice is shown on first launch explaining this and offering an immediate Turn it off action; reporting is already running while that notice is on screen, which is why we call it a notice and not a consent gate.
The default is deliberate. An opt-in crash reporter on a tool with this audience collects from a single-digit percentage of installs, and that is not enough reports to track down a fault in a Bluetooth stack on a handset nobody on the project owns. Reporting is described here in full so you can decide what to do with the switch.
3.2 What is sent
| Category | Detail |
|---|---|
| Crashes and errors | Exception type, message, stack trace, and whether the failure was handled |
| Application logs | Log lines the app writes at its kept levels, after scrubbing (see 3.3) |
| Build and environment | App version, build number, release channel, platform, OS version, device model, locale |
| Connected Flipper | Device name, serial number, Bluetooth LE address and the device info dump, when a report concerns a connected device |
| Session replay | Android and iOS only. A masked recording of the seconds before a failure. See 3.4. |
| Performance | Traces and metrics for operations such as file transfer and firmware install |
The Flipper identifiers above are deliberately not removed. A bug report about a
key recovery that says recovered <redacted> for sector 3 is not a bug
report. These identify a Flipper Zero, not a person, and we treat them as technical
identifiers necessary to the report.
3.3 What is removed before sending
A scrubber runs on every event, breadcrumb, log line and trace before it is transmitted. It removes:
- GPS coordinates — latitude/longitude pairs are stripped
- Archive file names — names under
/extand/intare replaced; the file extension is kept, because the format matters to the diagnosis and the name does not - Home directory paths — an absolute path such as
C:\Users\yourname\…becomes~\…, in both the native and the URI spelling, so your account name does not leave with a stack trace - URL query strings
In addition, the Sentry SDK is configured so that:
- Personally identifying information collection is switched off (
sendDefaultPii: false) - Screenshots are never attached, and the view hierarchy is never attached
- IP address storage is disabled server-side at Sentry, so your IP is not retained with the event
- Server-side scrubbing rules run as a second layer, including on native crashes that cannot pass through the app's own scrubber
Your recovered keys and card UIDs are never sent. No log call in the MIFARE tooling writes a key or a card UID into a message, and the replay masks those surfaces outright.
3.4 Session replay, and what "errors only" really means
On Android and iOS the app records a masked replay of the interface into a rolling in-memory buffer. The buffer is discarded unless a crash arrives; only then is the preceding segment uploaded. Nothing is uploaded on a session that goes fine. We state the distinction explicitly because "errors only" could be read as "recorded only then", and that would be wrong: the recording runs continuously, the upload is what is limited to failures.
Masking is applied at capture time, so the buffer never contains the sensitive content in the first place. Masked surfaces include all text by default, plus, named individually because they paint their own pixels and no automatic rule reaches them: the hex editor, the remote-desktop screen showing your Flipper's display, the code/text editor, the CLI terminal, the pulse plotter, and the map. Deliberately left legible are buttons, navigation labels and the device info line, so a replay is readable enough to be worth having.
Replay costs roughly +13% CPU and +5% memory on Android and +6% CPU on iOS, paid by every session rather than only the ones that fail. It has its own switch for exactly that reason. Replay does not exist at all on macOS, Windows or Linux.
3.5 How to turn it off
Settings → Diagnostics → Share logs with developers — switch off.
This calls Sentry.close(). The SDK and its native crash handlers are shut
down; nothing is captured, nothing is queued, and nothing is sent later. Switching it
back on starts it again. A second switch beneath it, Session replay, turns off
the replay alone while leaving crash reports on. The replay switch is hidden on desktop
platforms, where replay does not run.
You can also turn it off straight from the first-launch notice, with its Turn it off button, without hunting through settings.
There is a real cost to switching it off, stated honestly: with it off, nothing records a failure beyond what the screen in front of you already says. There is no local log screen to copy from — that mechanism was removed when Sentry became the only diagnostic channel. If you want to report something with diagnostics off, describe it in words in a GitHub issue.
3.6 Sentry as a processor
Sentry acts as a data processor for the project under its Data Processing Addendum, and processes data in accordance with its privacy policy. Data may be processed 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 Sentry's addendum. Events are retained according to the project's Sentry plan retention, after which they are deleted automatically; the project does not export events into any other system.
Builds compiled without a Sentry DSN — including builds you compile yourself from source — send nothing at all, because there is nowhere to send it.
4. Push notifications
Notifications about new Unleashed firmware releases are optional and off until you enable them. If you enable them, the app uses Firebase Cloud Messaging (Google) and a device registration token is created and held by Google so messages can be routed to your installation. A separate opt-in governs notifications for dev-channel builds.
The token identifies an installation, not a person; the project does not attach it to any profile, because there is no profile to attach it to. Messages carry a firmware version and a release note — never any of your content. Revoking the notification permission in your OS settings, or switching the feature off in the app, ends this. Google's handling of the token is governed by the Firebase privacy documentation and Google's privacy policy.
5. Location
qUnleashed can access your device's location for two features, both of which you trigger:
- Saved Locations map — shows your current position next to pins parsed from GPS metadata already inside your own archive files, so you can see which captures were recorded nearby, with distance and bearing.
- GPS sharing to the Flipper — on firmware with the RPC GPS extension, feeds your position to apps running on the Flipper, including while qUnleashed is in the background, which is why the background-location permission is requested on iOS.
Your position is used on the device and passed to your own Flipper. It is not sent to the project, and it is stripped from diagnostics before anything reaches Sentry. On Android, location permission is additionally a platform prerequisite for Bluetooth LE scanning — Android treats nearby-device scanning as location-capable — so the permission may be requested even if you never open the map.
One caveat worth stating: map tiles are fetched from a tile server, and any tile server necessarily learns your IP address and which map squares you asked for, which approximates where you are looking. See the next section for who that is and how to change it.
6. Every third party the app can contact
The table below lists every network destination the application can reach, what triggers it and what the recipient sees. None of these receive your archive contents, your keys or your settings.
| Destination | When | What they receive |
|---|---|---|
| Sentry | Automatically, unless you turn diagnostics off | The diagnostic data described in section 3 |
GitHubgithub.com, api.github.com,
raw.githubusercontent.com, codeload.github.com |
Checking for app and firmware releases; browsing or downloading the
Flipper-IRDB infrared library |
Your IP address and the request, as with any website |
Unleashed firmwareup.unleashedflip.com, dev.unleashedflip.com |
Checking for and downloading Unleashed firmware | Your IP address and which build you requested |
Flipper Devicesupdate.flipperzero.one,
catalog.flipperzero.one, infrared.flipperzero.one |
Official firmware channel; the official apps catalog; the official infrared remote source | Your IP address and which item you requested |
| Map tile provider Carto (default), OpenStreetMap, Stadia Maps, MapTiler, Mapbox, Thunderforest, ArcGIS, or a custom URL you enter |
Only when you open the Saved Locations map | Your IP address and the map tiles requested, which approximates the area you are viewing |
| Firebase Cloud Messaging (Google) | Only if you enable release notifications | A device registration token |
The map provider is yours to choose in Settings → Map. The default is Carto. MapTiler, Mapbox, Thunderforest and Stadia Maps require you to supply your own API key, which is stored on your device and sent only to that provider. You may also point the app at any custom tile URL, including one you host. Each provider has its own privacy policy, which governs what it does with the request.
Links the app shows to Telegram, Discord, Boosty, YooMoney, Tindie, flipper.market, lab.flipper.net and similar are ordinary outbound links. Nothing is sent when you merely see them; opening one hands you to that site under its own policy.
7. Permissions, and why each one exists
| Permission | Why |
|---|---|
| Bluetooth (scan, connect) | Finding and connecting to your Flipper Zero over BLE |
| Location (fine / coarse) | Required by Android for BLE scanning; also the Saved Locations map and GPS sharing |
| Background location (iOS) | Keeping GPS flowing to Flipper apps while qUnleashed is backgrounded |
| Notifications | Firmware release alerts, and the Android foreground-service notification |
| Foreground service (Android) | Holding the BLE connection alive while the app is in the background |
| Storage / file access | Reading and writing your local archive, firmware downloads and files you transfer |
| USB device access | Connecting over a USB cable, and DFU recovery |
| Internet | Everything in section 6 |
| Wake lock, boot completed, battery optimisation exemption | Keeping long transfers and firmware installs from being killed mid-write |
Denying a permission disables the feature that needs it; it does not disable the app. qUnleashed contains no advertising SDK, no analytics SDK other than the Sentry diagnostics described above, and no advertising identifier is read on any platform.
8. Legal bases, retention and international transfers
Where the GDPR or UK GDPR applies, we rely on:
- Legitimate interests (Art. 6(1)(f)) for diagnostics and crash reporting — our interest in a working application, balanced against a dataset that carries no account, no advertising identifier, no stored IP address, no location and no key material, and that you can stop with one switch. You may object at any time, and the switch is the objection mechanism, taking effect immediately.
- Consent (Art. 6(1)(a)) for push notifications and for location access, both of which you grant and can withdraw in your OS settings at any time.
- Performance of the service you asked for for requests you initiate, such as fetching a firmware image or a catalog entry.
Diagnostic events are retained for the retention period of the project's Sentry plan and are then deleted automatically. No other personal data is retained by the project, because none is collected. Processing may take place in the United States; see section 3.6 for the transfer mechanism.
9. Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing, and to data portability. Because the app holds no account and we store no identifier that maps to you, we usually cannot locate "your" events from a name or an email address alone.
In practice:
- To stop future processing — switch off Share logs with developers. This is immediate, needs no request, and is the fastest route.
- To request deletion of past events — open a GitHub issue. To find the events we will need something that identifies them, such as a Sentry event ID shown to you, your Flipper's serial number, or a precise timestamp and app version. If we cannot identify any data as yours, we will tell you so rather than guess.
- To complain — you may lodge a complaint with your local data protection authority.
We do not sell personal information, and we do not share it for cross-context behavioural advertising, as those terms are used in US state privacy laws.
10. Children
qUnleashed is a technical utility for owners of a Flipper Zero and is not directed at children. We do not knowingly collect personal data from children. The app has no account system, no social features, no user-generated content shared with others and no advertising.
11. This website
q.unleashedflip.com is a static site. It sets no cookies, runs
no analytics, embeds no fonts, trackers, pixels or social widgets, and makes
no third-party requests other than calling
api.github.com to look up the latest release so the download button can point
at the right file. That call is made by your browser; GitHub sees it as it would any
request to GitHub.
Your language choice and the release information are cached in your browser's
localStorage so the page is fast and the API is not called on every visit.
That data never leaves your browser and you can clear it at any time through your
browser's site-data controls. Whoever hosts the site may keep standard server logs
containing IP addresses for security and operational purposes.
12. Changes to this policy
If this policy changes materially — a new recipient of data, a new category collected, or a change to a default — we will update the effective date and version at the top, note it in the release notes of the version that carries the change, and, where the change meaningfully affects what is collected, show a notice in the app. Past versions remain in the site's Git history.
See also: Telemetry & Crash Reporting · Terms of Service · Legal Notice & Licenses