Your device. Your receiver.
Privacy policy
Last updated: 2 October 2026. Covers WTFreq Airband (RTL-SDR) (dev.rafaldot.wtfreq.airband), its on-device interaction with OpenSDR Radio Host (dev.rafaldot.opensdr) and the information website at wtfreq.app.
This policy explains how WTFreq Airband and wtfreq.app handle information, how long it is kept and how to contact the publisher about privacy. The separate receiver application has its own OpenSDR Radio Host privacy policy.
1. What happens on your device
No application account is required. The current apps contain no advertising, analytics or automatic third-party crash-reporting SDK. The developer does not operate an application telemetry backend. This does not mean that online maps, Google Play, hosting or reports you choose to send involve no data processing.
WTFreq Airband
With your Android permission and GPS setting enabled, location is used for nearby-object searches, distance/direction calculations and map centering. Periodic position updates follow the selected interval. You may instead enter a manual position. The app stores preferences, last position/selection, user frequencies and notice acknowledgements locally.
Location calculations run on the device, but displaying an online map requests tiles for the displayed area. These requests can reveal the area being viewed. Do not interpret local GPS processing as a promise that the map area never leaves the device.
OpenSDR Radio Host
The Host accesses supported USB receivers after Android grants permission. It processes receiver samples into audio and spectrum locally and stores receiver preferences and recent tuning history. Receiver audio comes from USB, not the microphone. The current Host does not request location, microphone, camera or internet permissions.
WTFreq and the Host exchange receiver settings, frequency, status and diagnostics through an on-device Android service connection. This is not a cloud connection.
2. Maps and other external services
WTFreq includes an offline aviation database. Online map layers use OpenStreetMap tile services, which can receive IP address, request time, normal network headers and tile coordinates. See the OpenStreetMap Foundation privacy policy. Dark map appearance is applied locally to the same tiles; it does not contact a separate provider. Older app versions offered CARTO layers, governed by the CARTO privacy notice.
Google Play and Android process installation, update, account and platform information under Google's policies. Opening an external store, repository or support link uses the chosen browser or application and that service's privacy practices.
3. Import, export and backups
User frequencies are stored locally. Import and export use the file location or document provider you select. A cloud-backed document provider may upload your exported file under its own settings. Neither app automatically sends frequency backups to the developer.
Automatic Android cloud backup and device-to-device extraction are configured to exclude app data. Use WTFreq's explicit export flow for user-frequency backups. Exported files remain at your chosen destination until you delete them there, including after uninstalling the app.
4. Reports you choose to share
Diagnostics are not automatically uploaded. Sharing a problem report opens Android's share chooser; you choose the recipient and application. Reports can contain frequencies, receiver settings, device/USB identifiers, technical logs and, for WTFreq, location or search context. Review and remove information you do not want to send.
For private support, use the developer contact details on Google Play. If you send a message or report, the publisher receives your message, attachments and contact information to investigate and reply. Email and other services you choose process the transmission. Public GitHub issues are public: do not post private information there. The publisher does not sell these reports.
Support correspondence is handled through Gmail, provided by Google. Messages you send to the publisher, including your sender address, message contents and attachments, are processed and stored through that service. See Google's Privacy Policy and Google's data-retention information. Using Gmail for support does not mean that the app automatically sends diagnostics, location or receiver audio to Google.
Google may process support correspondence outside your country, including outside the European Economic Area. Its privacy policy describes international processing and links the legal frameworks it uses for transfers. This is not a promise of EU-only storage.
To request deletion of correspondence held by the publisher, use the support and privacy contact below. Uninstalling the app does not delete messages already sent to support.
Technical support correspondence
Ordinary support messages and attachments are kept while the request is being investigated, answered and any reported fix is being verified. The basis is the publisher's legitimate interest in providing support and resolving technical problems (GDPR Article 6(1)(f)). When that work is complete and the correspondence is no longer needed for it, the publisher deletes it or removes personal information so that it is anonymous, unless the tax-record or dispute rules below apply. Ordinary technical reports are not automatically retained for six years.
Tax and accounting records
Only correspondence and attachments that actually form part of tax or accounting documentation are retained to meet applicable legal obligations (GDPR Article 6(1)(c)). Where Polish tax law applies, tax records are generally kept until the tax liability becomes time-barred: normally five years from the end of the calendar year in which the tax payment was due, with extensions where required by law. Applicable accounting duties may set different periods. This is not a fixed six-year period starting on the date of every email, and it does not make unrelated support reports tax records.
Technical documentation can also be evidence that a service was performed. For example, an agreed scope of work, delivery records, technical reports or acceptance messages may support a transaction or the performance of a service. Where needed for tax/accounting records or a legal claim, the relevant material follows that retention category, even if it originated in a technical support conversation. Only the parts and personal information necessary for that purpose are retained; unrelated correspondence is not automatically included.
Disputes, claims and proceedings
Relevant correspondence may be kept for as long as necessary to establish, exercise or defend a specific legal claim, taking account of the applicable limitation period and any ongoing proceedings or enforcement. The basis is the publisher's legitimate interest in protecting legal rights (GDPR Article 6(1)(f)), or a legal obligation to preserve records where one applies (Article 6(1)(c)). Retention is limited to material needed for that purpose and ends when it is no longer necessary, unless another applicable legal duty requires it.
These rules apply to correspondence and attachments held by the publisher in Gmail and any copies under the publisher's control. Provider-managed backups and deletion processing are subject to the provider's applicable procedures; requesting deletion does not guarantee immediate removal from every provider backup. A deletion request may be limited where retaining particular records is legally required or necessary for legal claims.
5. Local deletion and privacy requests
You can revoke location permission, switch to manual location, change settings, delete user frequencies, clear app storage or uninstall. Clearing data or uninstalling removes app-private state; it does not delete files exported elsewhere or messages already sent to a recipient.
No app account exists to delete. For information sent to the publisher, use the support and privacy contact below to request access, correction or deletion, and exercise other rights available under applicable law. You may object to processing based on legitimate interests on grounds relating to your particular situation. You may also contact your competent data-protection authority.
6. Current and future payments
The current release has no in-app purchases or purchase-verification backend. Optional paid WTFreq features, such as scanning and recording, are planned but not available. Before introducing purchases or new data processing, this policy and the Google Play declarations will be updated to explain the actual implementation. Nothing here authorizes undisclosed future collection.
7. This website
The website's own code contains no analytics or advertising and does not set tracking cookies. Fonts, styling, images and the small video-loading script are served with the site. Links to other websites open only when you follow them.
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.
Website hosting
wtfreq.app is hosted by Cloudflare. The publisher uploads the site's static files to Cloudflare. Cloudflare processes website requests to deliver and protect the site. These requests may include your IP address, request time, requested URL and browser information. The publisher can view website traffic and security information made available in the Cloudflare dashboard. This processing serves the legitimate interest in operating and protecting the website (GDPR Article 6(1)(f)). See Cloudflare's Privacy Policy for its data-handling practices, including international processing. This concerns visits to the website, not automatic uploads of app location, receiver audio, frequencies or settings.
Log availability and retention depend on the Cloudflare service, log category and account settings. Cloudflare distinguishes customer-accessible logs from other network data it processes. Its documented Security Events and Security Analytics retention periods differ; neither is a retention promise for every type of website data or any separately exported copy. The correspondence retention rules above do not set a retention period for website logs.
Depending on the protection features enabled, Cloudflare may add browser security checks and cookies to defend against bots and attacks. See Cloudflare's cookie documentation. The uploaded site files alone do not establish which protections the hosting service uses.
Cloudflare may process information outside the European Economic Area, including in the United States. Its published privacy policy describes reliance on the EU-U.S. Data Privacy Framework for covered transfers and Standard Contractual Clauses where applicable. Its Data Processing Addendum describes safeguards for customer data processed on a customer's behalf. These links explain the provider's published framework; they do not promise EU-only processing.
8. Audience and policy changes
These are hobby radio applications, not products directed to children. Changes to data practices will be reflected in this policy before the relevant features are released.
9. Publisher and contact
Publisher/data controller: Rafał Czeczótka, publishing under the Google Play developer name Rafał DOT.
For support and privacy inquiries, open WTFreq Airband (RTL-SDR) on Google Play, expand App support and use the developer contact details listed there. The section name may vary by language. This is the publisher's contact, not Google Play customer support.
Use that private contact for requests about your personal information. Do not post personal information in public reviews or GitHub issues.