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.

Privacy Protection of Commute Endpoints: By enforcing an edge-calculated 1,000-meter exclusion perimeter around trip origins and destinations, the architecture is engineered to prevent network observers or data aggregators from correlating trip metrics with your precise residence, private workplace, or private origin.

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 engineered from first principles to comply with and exceed modern global data protection regimes, including the Personal Data Protection Act 2010 (PDPA Malaysia, including the 2024 Amendments), the European Union General Data Protection Regulation (GDPR), and the California Consumer Privacy Act (CCPA/CPRA).

Malaysia PDPA 2010 / 2024 Statutory Alignment: Under the Seven Personal Data Protection Principles (General Principle, Notice and Choice, Disclosure, Security, Retention, Data Integrity, and Access Principles), Quovella Studio limits processing strictly to real-time client-side device navigation. Because AegisWay does not establish user accounts, request identity cards / passports, record vehicle registration numbers, or retain user profiles on remote servers, Quovella Studio does not process, store, or commercialize "personal data" as defined under Section 4 of the Malaysia 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 satisfy this requirement through structural omission. No behavioral profiles, session identifiers, device fingerprints, or historical traces are ever compiled or persisted.

To maintain independence from proprietary Big Tech surveillance stacks, AegisWay leverages vetted, open-source cartographic datasets and community infrastructure:

• OpenStreetMap (OSM): Vector road networks, street names, highway exits, and points of interest are sourced from the OpenStreetMap community under the Open Database License (ODbL).
• OpenFreeMap: Dark tactical vector tiles are rendered via high-efficiency tile infrastructure (openfreemap.org).
• Photon by Komoot & OSM Nominatim: Live address autocomplete and landmark resolution utilize open geographic indexers with transparent User-Agent identification.
• Project OSRM (Open Source Routing Machine): Live road-network path calculation utilizes open routing protocols for high-performance multi-vertex polyline generation.

Transient IP Packet Routing: Standard HTTPS connections to these open infrastructure endpoints inherently involve the transient transmission of network packets (including client IP addresses) at the TCP/IP network layer to deliver requested map tiles or search responses. No user accounts, advertising IDs, or personal profiles are transmitted in these requests.

Air-Gapped Offline Protection: Drivers seeking to eliminate map tile requests entirely may download pre-compiled Regional Map Packs (e.g. Selangor & Kuala Lumpur) directly inside AegisWay Settings. Once cached, vector cartography is read 100% locally from device storage with zero cellular map streaming.

"AS IS" AND "AS AVAILABLE" DISCLAIMER: AegisWay is provided strictly on an "AS IS" and "AS AVAILABLE" basis without warranties of any kind, whether express, statutory, or implied. Quovella Studio disclaims all representations and warranties, including but not limited to the implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, system availability, or error-free operation.

LIMITATION OF LIABILITY: To the fullest extent permitted under Malaysian and international law, Quovella Studio, its developers, contributors, and infrastructure providers shall have no liability whatsoever for any direct, indirect, incidental, punitive, special, or consequential damages, including but not limited to traffic citations, monetary fines, vehicle collisions, physical injuries, loss of life, route delays, or property damages resulting from the use of, reliance upon, or inability to use AegisWay.

"AegisWay: Live Traffic & GPS" is developed and maintained by Quovella Studio. For legal inquiries, architecture audits, or developer support, contact: