This policy explains what information KSEMAI collects, why, and what control you have over it. We've tried to write it in plain language rather than dense legal text — if anything here is unclear, the contact details at the end are a genuine way to ask.
KSEMAI uses your device's location to track trips, show live weather and hazards along your route, estimate speed and driving behaviour, and (only if you turn it on) share your live position for collision-warning features. Location access is optional — the app can be used with location off, with reduced functionality — and can be turned off at any time from Privacy & My Data in the app, without affecting your other saved data.
If you enable drowsiness detection, KSEMAI uses your device's front camera to look for visual signs of fatigue (eye closure patterns, yawning) using on-device processing. Camera video is analysed on your device and is never recorded, stored, or transmitted anywhere — not to us, not to any third party. This feature is off by default and requires explicit camera permission.
If you use voice-based destination entry, audio is processed by your phone's own built-in speech-recognition engine (Apple's or Google's, depending on your device) — the same system used by any other app on your phone that accepts voice input. KSEMAI does not separately record, store, or transmit raw audio.
Used on-device to detect harsh braking, acceleration, cornering, road roughness, and potential crash events. This data stays on your device except where included in a report you explicitly choose to save, print, or share.
Trip start/destination text you enter, an emergency contact you choose to save, hazard reports you submit, and any free-text notes.
| Data | Where it lives |
|---|---|
| Trip history, driving scores, saved destinations, emergency contact, badges/streaks, app settings | Locally on your device only (browser storage). Not uploaded to our servers. |
| Reports you choose to print, download, or email | Generated on your device at the moment you request them; only leaves your device if you actively print/save/send it yourself. |
| V2P live position (only while the feature is switched on) | Sent to our server anonymously (a random session code regenerated every time you open the app — not your name, account, or a persistent device ID), used only to check for nearby users of the same feature, and automatically deleted within seconds. See §3.4. |
Some features work by sending only the specific data needed to an external service, at the moment you use that feature:
Used for place search and address lookup. We send the place name or coordinates you're searching for; no account or personal identifier is attached. Governed by OpenStreetMap Foundation's privacy policy.
Used for weather forecasts and nearby points of interest (fuel, hospitals, hazards). We send only the coordinates needed for that lookup.
See §1.3 — this is Apple's or Google's own on-device/cloud speech service, governed by their respective privacy policies, not ours.
When you explicitly enable V2P alerts, your device sends its current position, heading, speed, and general motion state (e.g. "walking" vs "driving") to our server roughly every 1.5 seconds, so nearby devices also running the feature can be warned of a possible collision path. Specifically:
KSEMAI shows sponsored placements (fuel, lodging, food, and highway services), clearly labelled "AD". Which sponsor content appears is selected using your broad region (e.g. country/state-level, from reverse-geocoding your location) — not your precise real-time position. Your location is never shared with the sponsor itself, and no ad-tracking or cross-app profiling is used to select what's shown.
KSEMAI is a driving-safety tool intended for use by licensed drivers and is not directed at children. We do not knowingly collect personal information from children under 13 (or the relevant minimum age in your jurisdiction). If you believe a child has provided us information through the app, contact us using the details below and we will address it.
Because the large majority of your data never leaves your device, your main safeguard is your own device's security (passcode, OS-level encryption). Where data is transmitted (sections 3.1–3.4), it's sent over encrypted connections (HTTPS) to the specific service performing that lookup.
If this policy changes, the "Last updated" date at the top will change accordingly. Material changes affecting how location, camera, or microphone data is handled will be reflected here before they take effect.
Questions about this policy or your data can be sent to WorldPaveAI via www.worldpaveai.com.