Back to home

// LEGAL // PRIVACY & DATA

Privacy Policy & Telemetry Data Practices

How Transit Wave collects, processes, protects, and discloses account, location, and device telemetry data.

Official legal documentPlain text source
================================================================================
               PRIVACY POLICY & TELEMETRY DATA COLLECTION PRACTICES
================================================================================
LAST REVISED: SEPTEMBER 2026
LEGAL COMPLIANCE: CYBER SECURITY AND DATA PROTECTION ACT [CHAPTER 12:07]
AUTHORITY: POSTAL AND TELECOMMUNICATIONS REGULATORY AUTHORITY (POTRAZ)

THIS PRIVACY POLICY DETAILS HOW WE COLLECT, PROCESS, SECURE, AND DISCLOSE 
DEVICE TELEMETRY, LOCATION COORDINATES, AND HARDWARE METRICS THROUGH OUR 
SERVICES, PASSENGER ADVERTISING PLATFORMS, AND MOBILE APPLICATION APIS.

--------------------------------------------------------------------------------
1. CORE PRINCIPLE: PRIVACY BY DESIGN & ZERO COMMUTER SURVEILLANCE
--------------------------------------------------------------------------------
Our platform is fundamentally engineered around non-invasive data practices:
  (a) WE DO NOT RECORD, CAPTURE, OR STORE PASSENGER FACES OR VIDEO;
  (b) WE DO NOT RECORD, STREAM, TRANSCRIBE, OR SAVE CABIN CONVERSATIONS;
  (c) WE DO NOT OPERATE PUBLIC WI-FI SNOOPING OR NETWORK PACKET INSPECTION;
  (d) WE DO NOT PROFILE, TRACK, OR HARVEST PERSONALLY IDENTIFIABLE INFORMATION 
      (PII) FROM PASSENGERS COMMUTING IN PARTICIPATING VEHICLES.

--------------------------------------------------------------------------------
2. TECHNICAL DISCLOSURE: MICROPHONE USAGE & ACOUSTIC VERIFICATION
--------------------------------------------------------------------------------
To satisfy corporate advertising audit requirements without invading in-cabin 
privacy, the driver application utilizes Android AudioRecord permissions under 
a strictly constrained technical specification:

  2.1 TRANSIENT, VOLATILE-MEMORY (RAM) SAMPLING ONLY
  When a commercial sponsor spot executes, the app polls the microphone buffer 
  in short, transient intervals strictly to calculate the mathematical 
  Root-Mean-Square (RMS) amplitude and cabin sound pressure level in decibels:
    RMS = sqrt((1/n) * sum(x_i^2))
    dB  = 20 * log10(RMS)

  2.2 ZERO DISK WRITES & ZERO AUDIO STREAMING
  At NO point is the incoming microphone PCM buffer encoded, compressed, 
  transcribed, stored to internal flash memory, written to SQLite databases, 
  or transmitted over cellular/Wi-Fi networks. The numerical decibel float 
  is processed directly in volatile device RAM and instantly discarded.

  2.3 PURPOSE OF PROCESSING
  The decibel metric is collected solely to verify that vehicle auxiliary speakers 
  are active and have not been unplugged or muted. The system does not analyze 
  human speech patterns, verbal content, or passenger dialogue.

--------------------------------------------------------------------------------
3. LOCATION & VEHICULAR TELEMETRY COLLECTION
--------------------------------------------------------------------------------
When a driver initializes a route shift, the application accesses fine and 
background location hardware (GPS, GNSS, Network Provider):

  3.1 TELEMETRY CAPTURED
  The application records vehicular transit coordinates (latitude, longitude, 
  altitude, bearing, ground velocity, and atomic GNSS timestamps).
  
  3.2 PURPOSE OF LOCATION DATA
  Location metrics are strictly used to:
    (a) Calculate geofence triggers within specified radii of advertiser nodes;
    (b) Verify physical transit corridor movement for driver compensation;
    (c) Detect location fraud (such as stationary idling or mock GPS apps).
  
  3.3 RETENTION & ANONYMIZATION
  Raw GPS coordinates are linked to vehicle identifiers and shift tokens. 
  Aggregated route analytics supplied to advertisers are anonymized and 
  presented purely as corridor traffic counts and playback verification maps.

--------------------------------------------------------------------------------
4. DRIVER & ADVERTISER ACCOUNT INFORMATION
--------------------------------------------------------------------------------
For registered Users, we collect and store:
  (a) Identity & Contact: Full Legal Name, National Identity Number, Mobile 
      Phone Number, and Google Account OAuth profile information;
  (b) Financial Routing: Registered EcoCash wallet numbers or bank account 
      coordinates used strictly to disburse compensation or settle invoices;
  (c) Operational Logs: Shift start/end times, scanned dashboard QR identifiers, 
      and verified corridor assignments.

--------------------------------------------------------------------------------
5. DATA DISCLOSURE & REGULATORY COMPLIANCE
--------------------------------------------------------------------------------
We do not sell personal data, phone numbers, or driver records to third-party 
data brokers or marketing organizations. We disclose data only under the 
following controlled scenarios:
  (a) LEGAL MANDATES: When required by a valid court order, warrant, or 
      regulatory directive issued by the High Court of Zimbabwe, POTRAZ, or 
      competent law enforcement under the Cyber Security and Data Protection Act;
  (b) PROOF-OF-PERFORMANCE: Advertisers receive delivery logs containing 
      timestamps, corridor coordinates, and audio verification flags. These 
      reports contain zero driver identity profiles or passenger PII;
  (c) FINANCIAL PROCESSING: Account numbers and phone IDs are transmitted via 
      secure, encrypted APIs to mobile money payment gateways (e.g., EcoCash) 
      strictly to disburse verified driver earnings.

--------------------------------------------------------------------------------
6. DATA SECURITY & CRYPTOGRAPHIC SEALS
--------------------------------------------------------------------------------
All local telemetry logs stored temporarily on edge mobile devices are sealed 
within isolated application databases. Uploaded telemetry packages are 
transmitted using TLS 1.3 encryption and validated via cryptographic HMAC-SHA256 
signatures to prevent middle-man interception, database modification, or 
telemetry manipulation.

--------------------------------------------------------------------------------
7. PASSENGER NOTICE REQUIREMENTS (FLEET OBLIGATION)
--------------------------------------------------------------------------------
All participating vehicles are issued a dashboard QR plaque. This plaque 
provides direct legal notice to commuters that the vehicle utilizes automated 
spatial route utility software and decibel-metered acoustic verification, 
providing a scannable link to inspect this Privacy Policy directly.
================================================================================