Privacy without an account
NavOSS is operated by Yassin Soliman as an individual developer in Alberta, Canada. It is an account-free Calgary navigation technical beta.
Foreground location
When permission is granted, precise foreground location shows your position, chooses a route origin, matches progress to an active route, detects rerouting and arrival, and checks whether an official safety camera is ahead.
The current alpha does not request background location and does not maintain an in-app trip-history database.
Search and routing
Search text and, when available, an approximate search origin are sent in an encrypted request body to the NavOSS API. Route requests send origin and destination coordinates. An automatic reroute sends the latest route origin and destination. Nominatim search and Valhalla routing run on the operator-controlled server in Alberta.
These values are processed in memory for the response and then discarded. They are not written to a NavOSS database, access log, or backup. Active route matching and camera eligibility run on the phone.
No advertising or cross-app tracking
NavOSS has no account system, ads, advertising identifier, data broker integration, or cross-app tracking. Location is not used for advertising or user profiling.
Map and camera data
The phone requests map styles, tiles, fonts, and sprites directly from OpenFreeMap. The requested resources can indicate the viewed map area. OpenFreeMap says regular logs omit IP addresses, while it may retain incident IP logs for up to 30 days. Camera records come through NavOSS from Calgary Open Data; the phone does not send location to the City of Calgary.
Providers and retention
Cloudflare provides DNS, TLS, traffic delivery, and the outbound tunnel. It processes client IP and network/request metadata on its global network under its policy. NavOSS does not enable raw Cloudflare request-log export. Map delivery uses OpenFreeMap; TestFlight feedback uses Apple; and user-initiated support may use GitHub.
NavOSS keeps operational, SSH, and firewall logs for no more than seven days. Routine HTTP access logging is disabled. Logs exclude request bodies, search text, and route coordinates. The currently disabled report database has 14-day backups; route and search requests never enter those backups.
Operational logs may contain timestamps, service identity, severity, lifecycle or health events, error names, and random request IDs. SSH and firewall logs may contain source IP and port, local account, action, and outcome. Cloudflare applies its own variable network and security retention. OpenFreeMap says anonymized logs may be retained indefinitely and incident IP logs for no more than 30 days.
Your choices and deletion
You can deny or revoke location permission in iOS Settings and can stop an active trip with End navigation. Search and map browsing may remain available, while current-position routing and active guidance will be limited.
Because NavOSS has no account and does not retain search, route, or trip records, it normally has no history to export or delete. A rights request may identify a support message or recent security event, but NavOSS may be unable to associate a transient, IP-only request with a person. Requests about provider-controlled data may also need to be directed to that provider.
Security and international processing
App-to-API traffic uses HTTPS through Cloudflare. The Alberta origin uses an outbound tunnel rather than a public inbound port, key-only SSH, a default-deny firewall, least-privilege containers, security updates, bounded logs, and read-only filesystems where practical. No security measure can guarantee absolute protection.
The NavOSS origin is in Alberta. Cloudflare, OpenFreeMap, Apple, and GitHub may process data outside Canada as described in their policies.
Children and changes
NavOSS is a general-audience navigation utility and is not directed to children. It does not create profiles or knowingly maintain children's personal information. A parent or guardian should supervise a minor's use of navigation and support channels.
Material changes will appear here with a revised effective date. During beta testing, material data-use changes will also be identified in TestFlight release notes before the changed feature is tested.
Contact
Use the repository's
public issue tracker only for
non-sensitive questions. Use
private vulnerability reporting
for a security issue or sensitive privacy request. Internal testers may also use
TestFlight feedback. Never publish a private address or precise trip history. The planned
address navoss@yassin.app is not presented as active until delivery and reply
handling are tested.