Security &
Data Privacy
Axiorad runs authoritative coverage calculations in your browser using a CPU worker. Coverage grids from a run are not uploaded as part of the calculation itself.
Authenticated project saves persist radar positions and RF configurations to Axiorad servers. Map tiles, elevation services, authentication (Clerk), and optional LLM datasheet parsing also use the network. Do not treat Axiorad as fully air-gapped or as "data never leaves your device."
Client-Side Processing Architecture
Coverage compute stays in the browser. Amber items cross the network — including elevation, maps, auth, and (when you save a project) radar RF configurations persisted to Axiorad.
Used locally for the active run
Authoritative browser CPU worker
Computed in-browser for the session
GeoTIFF, KML, GeoJSON, CSV
Radar RF persisted when you save
Terrain tiles (inbound only)
Mapbox imagery (inbound only)
Clerk session management
Stripe (direct, not via us)
What Stays Local, What Crosses the Network
Complete inventory of data categories and whether they leave your device. Coverage compute is local; saved project RF and several supporting services are not.
| Data Category | Leaves Device? | Destination | Notes |
|---|---|---|---|
| Coverage calculation (in-session) | NO | — | Computed in the browser CPU worker; not uploaded as part of the run |
| Exported files (GeoTIFF, KML, CSV) | NO | — | Generated client-side; downloaded directly to your machine |
| Saved project radars & RF parameters | YES | Axiorad (Postgres) | When you save a project while signed in — positions and RF configs persist server-side |
| Elevation data | YES | Mapbox / Google / SRTM | Inbound only — terrain tiles fetched by viewport coordinates |
| Map tiles | YES | Mapbox | Inbound only — standard map imagery for the visible area |
| Account information | YES | Clerk (auth provider) | Email, name, and session tokens for authentication |
| Payment information | YES | Stripe | Card details handled entirely by Stripe — never touch our servers |
| Datasheet parsing (opt-in) | YES | LLM provider (user-selected) | Only when you explicitly upload a datasheet for AI parsing |
| Contact form submissions | YES | Brevo (email) | Only the message you explicitly submit via /contact |
External Services & Compliance
Axiorad integrates with a minimal set of external services. Each has been selected for its security posture and compliance certifications. Coverage grids from a run are not sent to these providers; saved project RF is stored on Axiorad servers.
Clerk
SOC 2 Type IIAuthentication & user management
Stripe
PCI DSS Level 1Payment processing
Mapbox
SOC 2 Type IIMap tiles & elevation data
LLM Providers
Varies by provider (OpenAI, Anthropic, Google)Datasheet parameter extraction
Brevo
GDPR compliantTransactional email
Printable Security Statement
For procurement officers and IT security reviewers. This statement can be printed or saved as PDF for inclusion in security assessments.
Axiorad is a web-based radar coverage analysis and RF propagation planning tool. Coverage calculations — including propagation modeling, radar equation evaluation, and result rendering — execute primarily within the user's web browser using a JavaScript CPU worker (optional experimental WebGL GPU path). Coverage grids from a calculation run are not uploaded to Axiorad as part of the compute path.
Data that crosses the network includes: (1) terrain elevation tiles from Mapbox, Google, or SRTM; (2) map imagery from Mapbox; (3) authentication via Clerk; (4) payment processing via Stripe; (5) optional AI datasheet parsing to a user-selected LLM provider; and (6) authenticated project saves, which persist radar positions and RF configurations to Axiorad servers (Postgres) so projects can be reloaded across sessions.
Users should not treat Axiorad as fully air-gapped or as a system where radar RF configurations never leave the device. Inspect network traffic in browser developer tools during operation, and review the data classification table on this page for the current inventory.
Security FAQ
Do radar parameters and coverage results stay on my device?
Coverage grids are computed in your browser and are not uploaded as part of the calculation itself. If you save a project while signed in, radar positions and RF configurations are persisted to Axiorad's servers so you can reload them. Map tiles, elevation data, authentication, and optional datasheet LLM parsing also use the network.
Can Axiorad work on air-gapped networks?
Partially. The core calculation engine runs client-side, but Axiorad requires internet connectivity for map tiles (Mapbox), elevation data, and user authentication (Clerk). For fully air-gapped environments, contact us via the contact form to discuss on-premises deployment options.
Is Axiorad ITAR controlled?
No. Axiorad is a general-purpose RF propagation analysis tool using publicly available ITU-R standard models (Longley-Rice ITM, COST-231 Hata, ITU-R P.1812-6). It does not contain classified algorithms, controlled technical data, or export-restricted technology. Users are responsible for ensuring their own input data and results comply with applicable export control regulations.
What about datasheet parsing — does that send data to a server?
Datasheet parsing transmits user-provided content to an external LLM provider (OpenAI, Anthropic, or Google) for parameter extraction. This feature is entirely opt-in — you can manually enter all parameters instead. Separately, saving a project while signed in persists radar RF configurations to Axiorad servers.
Questions about security?
For security assessments, penetration test reports, or on-premises deployment discussions, contact our enterprise team directly.
Client-side coverage compute • Saved projects stored server-side • External map, elevation, and authentication services