Privacy information
Updated: 9 November 2026.
Local reception and observer data
WTFreq ADS-B processes received aircraft messages, aircraft identifiers and telemetry, observer positions, saved locations, comments and notification rules on your device. These support the map, replay, coverage, aircraft history and local notifications. There is no publisher-operated account, traffic-upload service or purchase-verification server.
Free reception history uses a limited memory buffer of approximately 32 MiB; the oldest entries are discarded when it fills. This history is lost when the app process restarts. Stopping reception or moving the app to the background does not itself clear it. Pro also saves valid reception history in local SQLite databases according to the selected recording profile and categories. Saved settings, locations, custom aircraft information and alert rules persist in both editions.
Browsing defaults to approximate or last-known location, using Android's location cache and a short network-location request when permission is already granted. This does not actively request GPS. Android's network provider may use Wi-Fi/cell information and a data connection under your system settings and provider's policies. Approximate locations are marked and do not replace receiver positions in recordings or Coverage. GPS is optional: use a fixed observer position instead, request one GPS fix explicitly, or select GPS following for an active reception session. With permission, GPS following during reception can continue while the screen is locked. A fixed reception site does not start GPS; Replay uses recorded positions. Android controls location and notification permissions. OpenSDR supplies radio data through an on-device connection; it is a separate application with its own privacy information.
The app does not upload received frames or observer tracks to the publisher or traffic-sharing services. Files you export are separate copies at the destination you choose; that provider and any service you later share them with handle those copies. Map requests can nevertheless reveal the area being viewed, including your approximate location when the map follows you. Bundled demo recordings are historical examples kept separate from your own reception history.
Retention and deletion
By default, saved reception history has no automatic age-based expiry. Recording & storage settings let Pro users select packet categories and how older recordings are reduced after 7–3650 days, or choose Never. The optional reminder proposes optimization for confirmation. Automatic weekly optimization is off by default and requires explicit opt-in; changing reduction rules or importing configuration disables it until confirmed again. Protected recordings are excluded. Removed packets cannot be restored without a backup. Compact database alone reclaims unused storage without removing additional packets.
- Recordings and flights: delete selected recordings in Replay, or a flight in the aircraft's history. Deletion preserves a compact record of each affected aircraft's latest known position and last contact, with up to two source packets and the observer information they reference. Those retained observations can still appear in Aircraft, exports and backups; they are not replay recordings. Packets still used by another recording are also kept.
- Older reception packets: use Settings → Data & files → Storage & maintenance → Delete data before, then preview and confirm. This cleanup does not create new retained aircraft summaries, but it does not erase summaries retained by earlier recording or flight deletion. Rebuild and VACUUM also preserve those summaries.
- Notification history: the app stores notification time, aircraft identifier, title and message text separately, without an automatic expiry. Text can include matching rules and observation information such as distance and bearing. Use Notifications → Notification history → Clear… to delete this history. Clearing it keeps alert rules and reception records. Dismissing an Android notification or deleting a recording does not clear it; Android's own notification history is controlled separately.
- Rules, saved places and custom aircraft information: these remain until edited, removed where a delete action is offered, or app data is cleared. Archiving a saved location only hides it from active choices; it keeps its information and historical references. Removing custom aircraft information does not remove received packets.
- Downloaded catalogs and caches: installed aircraft and route catalogs remain available offline until replaced or app data is cleared. Temporary download archives are normally removed after completion or cancellation. Map tiles, replay checkpoints and aircraft-detail caches may be reused or evicted according to cache headers and storage limits; there is no single retention period for all caches. Android Settings → Apps → WTFreq ADS-B → Storage → Clear cache removes cache files, but keeps installed catalogs, observations, settings and persistent coverage summaries. Data deletion can leave derived or temporary recovery copies until cleanup; it is not a promise of secure physical erasure.
- All app-private user data: Android's Clear storage/Clear data action removes saved observations, retained aircraft summaries, notification history, settings, catalogs and local purchase proof. Uninstalling normally removes these stores too. The app has no separate command to erase only retained aircraft summaries. Clearing data does not cancel your Google Play purchase, remove data held by external providers, or delete exports saved outside the app.
Exports and backups
Database backups, CSV files and configuration exports are ordinary files without an app-added password or encryption. They may contain observer positions, saved place names, comments and alert criteria. You choose their destination through Android's file picker. A selected cloud-storage or sharing provider may transfer and retain them under its own terms. Copies outside the app must be deleted separately.
A database backup includes reception data, retained aircraft observations, saved locations and local aircraft/catalog information. Notification history and the separately downloaded route catalog are not included. Configuration backup includes supported settings, saved locations and notification rules, but not reception packets, downloaded catalogs or a Pro entitlement. Purchase receipts are excluded from both kinds of backup. Automatic Android backup is disabled, and the app's backup rules exclude its private data from cloud backup and device transfer.
Online services and recipients
The following connections support the app's features. Map and catalog requests use HTTPS. Providers receive network information such as your IP address and request time; the app does not attach reception history or alert rules to these requests.
- OpenStreetMap Foundation: the map library downloads tiles from the OpenStreetMap tile service, including
tile.openstreetmap.org. Requests identify tile coordinates and zoom and include an app User-Agent. They reveal the viewed area, which can correspond to a live or recorded observer location. Cached tiles can be used offline. The provider uses infrastructure and request logs to operate and protect its services; see the OpenStreetMap Foundation privacy policy. - GitHub: aircraft/type/operator catalogs are downloaded from
raw.githubusercontent.com/Mictronics/aircraft-database; routes and airports come fromcodeload.github.com/vradarserver/standing-data. Requests include the catalog path, an app User-Agent and, when available, cache-validation headers. Catalog lookups for an aircraft, callsign or airport run locally after download. Automatic catalog updates are off by default and can be enabled in Settings → Data & files → Catalogs & updates. See GitHub's privacy statement. - Planespotters and other external links: only selecting the Planespotters button opens a browser URL containing the aircraft registration. The current app does not fetch photo previews or call a photo API. The opened website and browser handle their own network requests, cookies and any sign-in; see the Planespotters privacy policy. Store, source and support links likewise open the chosen external service.
- Google: Google Play handles Pro purchase, restore and acknowledgement requests. The Billing library also includes diagnostic reporting to Google. Technical reports can contain billing operation/results, app and SDK versions, Android/device build information, locale and network characteristics. These support billing reliability and security; they are distinct from the app's local diagnostic report and from website analytics. Google's privacy policy and retention information describe its processing and controls.
Provider logs and payment records have their own retention rules; clearing the app cannot remove them. Requests can be processed outside your country, including outside the EEA, through providers' international infrastructure. The linked policies explain their locations, safeguards, retention and privacy-request routes. The app does not set a single retention period for all providers.
Purchases and offline Pro
adsb_pro is a one-time purchase through Google Play, not a subscription. Google handles payment details under its terms; the app does not receive card numbers or your Google account password. It receives purchase status and a signed receipt containing an order identifier, purchase token, product/package identifiers, purchase time and state. A pending payment does not activate Pro.
The app verifies the signed receipt locally, acknowledges completed purchases through Google Play and stores its proof privately in Android's no-backup storage. Scheduling timestamps, a token hash and purchase-verification status are stored separately there. These records, and any activated reviewer code, are encrypted with installation-specific Android Keystore keys. Copying app files does not transfer those keys. After upgrading from older unprotected storage, reinstalling or losing a key, restore the purchase through Google Play or re-enter the reviewer code. Recordings and settings are preserved. These files are excluded from database/configuration exports and Android backup; scheduling metadata alone cannot grant Pro. There is no publisher-operated receipt-verification server.
Previously verified Pro stored for this installation remains available offline without a quarterly online requirement. While you use the app, automatic checks are due weekly during the first month after purchase, then every 30 days until 90 days after the verified purchase date. Manual restore checks immediately; failed checks can be retried when connectivity returns. Network failures preserve locally verified access.
The private purchase record is synchronized with results returned by Google Play. Clearing app data or uninstalling the app removes the local copy. Google keeps its transaction records separately. Use Restore purchases with the purchasing Google Play account to regain access on a compatible device.
Purchase diagnostics are kept as a limited in-memory log. A report is shared only if you choose to copy or send it; it contains technical status, timestamps and a short token hash, not raw purchase tokens or signed receipts. Purchase details shown elsewhere in the app can include the order identifier and purchase time. The app does not automatically send these diagnostic reports to the publisher.
This website
Fonts, styling, images and the small video-loading script are served with the site. Cloudflare Web Analytics may be provided through the hosting configuration as described below. Following external links opens the corresponding service.
This site is served over HTTPS at wtfreq.app/adsb/ using the same Cloudflare hosting as the WTFreq website. See section 7, “This website”, in the WTFreq website privacy information for hosting requests, logs, security features and international processing. These website requests do not upload your app recordings or observer positions.
Optional YouTube video
The demo preview uses a local image. No YouTube player or connection to Google is loaded until you press Play. That action loads the embedded player from youtube-nocookie.com using YouTube's privacy-enhanced mode and requests playback. A direct Watch on YouTube link is also available.
After you activate the player, Google receives network and playback information, such as your IP address, browser information and the origin of this website, and may use browser storage or cookies to operate its service. Privacy-enhanced mode does not mean no data is processed. See YouTube's embedding and privacy-enhanced mode information and Google's Privacy Policy. Following a link to YouTube uses that service's own privacy practices.
Cloudflare Web Analytics
Cloudflare Web Analytics may be enabled for the WTFreq Airband and ADS-B pages on wtfreq.app to measure visits and page performance. When enabled, your browser loads Cloudflare's JavaScript measurement beacon and sends website measurements to Cloudflare. The publisher uses aggregated reports to improve the site's content and responsiveness.
Reports can include page views and visits, page paths and referring websites, country, device type, browser, operating system and page-load performance measurements. See Cloudflare's documentation on report dimensions and data collection.
For this analytics product, Cloudflare states that measurements use neither cookies nor browser localStorage, and that it does not use fingerprinting to recognize individual visitors. See its measurement and privacy explanation. As with other website requests, Cloudflare receives network connection information while serving the script and receiving measurements. The hosting, security and international-processing information above also applies.
These measurements concern website visits. They do not read the Android apps' recordings, GPS tracks, saved locations, notification rules, receiver settings or purchase receipts. The publisher does not combine these reports with individual app histories or Google Play purchases. This section covers Cloudflare Web Analytics; app telemetry or additional analytics tools would require a separate description.
Publisher and contact
Publisher/data controller: Rafał Czeczótka, publishing under the Google Play developer name Rafał DOT. For support and privacy requests, email rafal.dot.dev@gmail.com or use App support on Google Play. Use this private contact for requests about your personal information; do not post it in public reviews or issues.
Support correspondence is handled through Gmail. The WTFreq support and correspondence information describes handling and retention of messages you choose to send.