Effective date: 26 August 2026
Publisher: Adam Zemancik
Contact: info@sdilejslunce.cz
Published policy: https://mmocz.github.io/app-pages/apps/topowave/privacy/
This policy describes how TopoWave processes information when you use the iOS app and its terrain-analysis service.
TopoWave is a terrain and radio-link planning app. It lets you create plans, save locations and radio settings on your device, calculate terrain profiles and coverage, and export or share results. When a production build offers Estimated RF coverage (Beta) and you choose to show it, the app sends the selected frequency, antenna heights, link-budget assumptions, and RF-environment inputs with the coverage request to the same protected services. The beta response is shown separately from Terrain visibility and is not a guarantee of reception, availability, safety, or regulatory compliance.
The app stores saved plans, saved sites and targets, equipment profiles, completed results, App Attest state, an installation identifier, and account-flow state locally. Eligible coverage results can also retain a compressed, integrity-checked radial terrain package locally so height, receiver-height, frequency, and Fresnel planning scenarios can be recalculated without sending a new terrain request. This local package contains sampled terrain and source provenance for that result, is protected by iOS file protection, and is not uploaded as a cloud cache of your coordinates or result. Exported files are created locally and are only provided to another app or service when you choose a Share or Export destination.
When you request a terrain or RF-beta calculation, TopoWave sends relevant coordinates and technical planning inputs to its Supabase-hosted account, security, allowance, and terrain gateway services and to its private terrain service. The terrain service currently supplies results from Copernicus DEM GLO-30 or GLO-90 data. The app does not send terrain-analysis requests directly to Open-Meteo, ČÚZK, or the USGS National Map. TopoWave services process an account identifier, random installation identifier, App Attest material, authentication/session information, allowance and rate-limit state, and the data needed to validate and serve a request.
TopoWave may request precise location while the app is in use after you grant permission. It is used to center the map and as a planning starting point; the app does not receive continuous background location. TopoWave requests no name or email scope from Apple. Apple handles Sign in with Apple, App Attest, and map services under its own privacy policy.
We use information to provide calculations, maintain local plans, authenticate accounts, enforce service allowances, prevent abuse, support deletion, and maintain service reliability and security. TopoWave does not sell personal information, use it for cross-app or cross-site advertising, or track you across apps or websites owned by other companies.
We disclose data only as needed to operate requested features, to Apple, Supabase, and TopoWave-operated services. Providers process information under their own terms and privacy notices. We may also disclose information when required by law or to protect service security.
Saved plans, results, and associated local terrain packages remain on your device until you delete them or remove the app. Account, device-verification, allowance, and account-linked service records are retained while the account is active. Short-lived security challenges expire after five minutes. Unfinished terrain-analysis reservations expire after five minutes, while completed reservation and allowance records remain linked to the active account for allowance enforcement and service security.
Deleting an account in the app permanently deletes its Supabase Auth identity and account-linked TopoWave records, including revocation of Sign in with Apple access where applicable. For abuse prevention, TopoWave retains only the random installation identifier and consumed allowance count until the current daily or weekly allowance resets; this retained quota hold contains no user ID, App Attest credential, coordinate, terrain request, or result. Security audit events may remain after deletion in de-identified form without the deleted user or installation identifier.
Operational service logs may contain technical connection information such as IP address, request time, response status, and safe error or timing information. Sensitive authorization and assertion headers are redacted. Operational logs and provider backups are retained according to security, reliability, log-rotation, and backup schedules, then deleted or overwritten when no longer needed, except where longer retention is required for fraud prevention, dispute resolution, or legal compliance. Removing the app does not remove files you exported or shared.
You can decline location permission, delete saved items, choose whether to sign in with Apple, and request account deletion from the Account screen. For privacy requests, contact info@sdilejslunce.cz. Service providers may process data outside your country. We may update this policy and will publish a revised effective date.