Product information

Privacy.

Last updated September 13, 2026 · covers RadarDesk 1.1

RadarDesk is a Windows desktop ADS-B radar application. This page explains the types of information the application may process to provide its features.

Information you choose to provide

RadarDesk may process locations you enter, airport favorites, recent airport selections, display preferences, provider settings, and optional home-marker coordinates and orientation. In 1.1, a personal Local ADS-B receiver name and URL are also saved per user; no developer's private receiver address is shipped as a default. These preferences are stored locally on your Windows device.

Live data and third-party services

To provide live features, RadarDesk sends requests to services for aircraft data, aviation weather, map imagery and vectors, FAA chart documents, address geocoding, ZIP-code resolution, aircraft imagery, route links, and optional FAA reference-data updates. Those services receive the information needed to complete a request, such as an airport identifier, coordinates, a search term, or an aircraft identifier, along with standard request information such as your IP address. A configured local receiver receives its own requests; fallback can use online providers. Selecting an airport outside the home-centered scope's coverage can also create an additional airport-centered request.

Local application data

RadarDesk stores settings, license information, reference databases, curated aircraft-model images, cached airport surfaces, background maps, and chart PDFs on your computer. In 1.1, aircraft details check the supplied model-image catalog first; an online fallback image is temporary and is not added to that catalog.

1.1 diagnostics: RadarDesk retains recent diagnostic entries in memory rather than writing diagnostic logs or aircraft snapshot/position-history archives to files or SQLite. An optional separate Telemetry Monitor from the source repository can record diagnostics and tracking data when connected; that tool, not RadarDesk, writes its recordings. Files and historical database rows created by earlier versions are not automatically removed.

User-requested screenshots, settings backups, normal preferences, reference updates, and map/chart caches still save normally. Support bundles omit Home-marker details, but settings backups may contain personal configuration. Review any exported information before sharing it.

Licensing

RadarDesk may use a signed personal license file or Microsoft Store licensing. Store licensing is handled by Microsoft under Microsoft’s terms and privacy practices. Personal license files contain the licensing information required to validate the license.

Website

This marketing website does not include advertising trackers, analytics scripts, account registration, or a contact form. When a page displays a Microsoft Store badge, the browser requests that image from Microsoft; Microsoft receives standard request information such as your IP address, browser details, and the referring page. Your hosting provider may also retain standard web-server logs under its own terms and settings. Following a link to the Microsoft Store or another external website sends a separate request to that service.

Data retention and control

After closing RadarDesk, you can remove its local application-data folder to clear preferences, favorites, caches, reference data, and locally imported personal licenses. Back up anything you wish to keep first. Screenshots, exported settings, and recordings made by the separate Telemetry Monitor can be in other folders and must be managed separately. Uninstalling alone should not be assumed to remove all of these files.

Children’s privacy

RadarDesk is not designed to collect personal information from children and does not include child-directed accounts, social features, or behavioral advertising.

Changes

This privacy information may be updated as RadarDesk changes. The current revision date appears at the top of this page.