Privacy

Flightradarx is designed to work without user accounts. Your personal lists stay on your device.

Local-only data

Pinned flights (flightradarx.pins), alert watches (flightradarx.alerts), and map settings (flightradarx.settings) are stored in your browser’s localStorage. They are not uploaded to a Flightradarx account because none exists.

Network requests

When you use the live map or tools, the app requests aviation data from this server and from third-party APIs (OpenSky, adsb.lol, adsb.fi, adsbdb, Open-Meteo on the weather page). Those services receive standard HTTP request metadata (IP address, user agent) according to their own policies.

Cookies & analytics

Flightradarx does not set authentication cookies or load third-party analytics. The server keeps a local visit log on the machine that runs it: anonymous browser session id, approximate country (when available), client IP (from Cloudflare / proxy headers when present), coarse device type from the user-agent (mobile / tablet / desktop, plus OS and browser labels), page paths, and how long the tab stayed open. That log is shown on the operator dashboard at /admin (HTTP Basic Auth via server env credentials). Clearing site data in your browser removes local pins, alerts, and settings for this origin.

Questions

For a self-hosted copy, you control the server logs. Treat any deployed instance like other small web apps: restrict access if needed and rotate keys for upstream APIs you proxy.