Privacy Policy & Cryptographic Disclosures

Traditional navigation applications require user logins, collect email addresses, harvest contact books, and assign persistent Advertising IDs (AAID/IDFA) to construct behavioral dossiers of your daily commutes. AegisWay completely rejects this architecture.

AegisWay is 100% accountless. When you launch AegisWay:

• Zero Authentication Tokens: There is no Google SSO, Apple Sign-In, OAuth, email registration, or phone number verification.
• Zero Device Fingerprinting: AegisWay does not read Android IMEI, Android ID, SIM IMSI, MAC addresses, or Advertising IDs.
• Zero Third-Party Tracking SDKs: AegisWay contains zero instances of Google Firebase, Meta Graph SDK, AppsFlyer, Mixpanel, Adjust, or Google Analytics. The compiled binary is entirely free of ad-tech surveillance code.

Most navigation applications pipe your continuous location through Google Play Services Location Provider, which regularly dispatches nearby Wi-Fi BSSIDs, cell tower signals, and coarse location pings to remote servers.

AegisWay interfaces directly with the physical satellite receiver hardware via Android's native android.location.LocationManager requesting raw GPS_PROVIDER signals. Multi-constellation tracking (GPS, GLONASS, Galileo, BeiDou, and QZSS) occurs exclusively in local device memory. Satellite Signal-to-Noise Ratios (SNR/C/N0), Doppler velocities, and barometric altimeter data are computed locally in device RAM to distinguish elevated flyovers from ground-level roads without transmitting coordinate streams.

Cryptographic Protection of Commute Endpoints: By enforcing a mathematical 1-kilometer exclusion perimeter around trip origins and destinations, it is mathematically impossible for any network adversary or aggregator to infer where you sleep, where you live, or where your vehicle parks.

When drivers collaboratively report road hazards (e.g., accidents, road debris, floods) or anonymous speed deltas to calculate live traffic jams, traditional systems log the transmitting device's IP address. An IP address is personal data under GDPR Article 4(1).

To solve this, AegisWay implements IETF RFC 9458 Oblivious HTTP via a double-blind cryptographic relay:

15-Minute Epoch Quantization: All community road observations are quantized into 15-minute time buckets (epoch = currentTimeMillis / 900,000). High-resolution millisecond timestamps are discarded before encryption to prevent statistical timing correlation.

RFC 9577 Privacy Pass Hardware Attestation: To prevent malicious bot networks from flooding the community with false hazard markers, AegisWay utilizes zero-knowledge cryptographic Privacy Pass tokens. The system verifies client authenticity without linking reports to any user, device identifier, or IP address.

When you search for a route on proprietary mapping services, your origin, destination, planned stops, and deviations are sent to a remote cluster. This builds a persistent ledger of your sensitive travels (medical clinics, attorneys, private meetings).

In AegisWay, your destination NEVER leaves your phone:

• Native Valhalla C++ Routing Engine: Turn-by-turn routes are computed directly in device RAM using an embedded native C++ routing engine compiled via CMake and Android NDK. Calculations, dynamic costing, and maneuvers run 100% offline.
• Volatile Memory Clearance: Destination coordinates and navigation session states are cleared from device RAM the moment navigation concludes or the app is closed.
• Decentralized MapLibre Vector Tiles: Vector map tiles are rendered from open OpenStreetMap (OSM) cartography. Tile requests download generic geographic bounding boxes (XYZ coordinate squares) that are completely identical for every user in that region. Tile requests contain zero origin, zero destination, and zero route polyline data.
• Strict 250MB Hard-Ceiling LRU Storage: Offline vector tiles are stored in a local SQLite container with an automated Least-Recently-Used (LRU) prune cycle capped strictly at 250MB to prevent device storage bloat.

Automated Enforcement System (AES) Radar: Fixed speed and red-light enforcement cameras are pre-indexed locally on-device. Proximity detection uses an on-device 2D spatial bounding hierarchy projecting a 1,500m forward cone along your GNSS Doppler heading. No server queries occur when approaching cameras.

Local Point-of-Interest (POI) Search: Queries for petrol stations, parking, hospitals, and amenities are evaluated against embedded regional POI databases stored directly on your device. Your keystrokes and search queries are never transmitted to search-logging servers or advertising auctioneers.

AegisWay complies with the principle of Strict Least Privilege. We demand only the minimum hardware access essential for navigation:

AegisWay is designed from first principles to exceed the privacy requirements of the European Union General Data Protection Regulation (GDPR), the California Consumer Privacy Act (CCPA/CPRA), the UK Data Protection Act, and the Personal Data Protection Act (PDPA).

GDPR Article 5(1)(c) Data Minimization: "Personal data shall be adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed."

We operationalize this requirement through mathematical elimination. Because AegisWay does not store user profiles, session identifiers, IP addresses, or location histories, we hold zero personal data.

"AegisWay: Live Traffic & GPS" is developed and maintained by Quovella Studio. If you have architectural questions, wish to audit our cryptographic disclosures, or need support: