KNIGHT RIDE

Knight Ride: Privacy Policy (DRAFT, not published)

Draft by Atlas, 2026-10-28. Chris must review it. It needs the operating company's legal name, a contact address and a public URL (served by the fleet's public endpoint at /privacy once Chris decides to go public, or any static host). Not legal advice. The console replaces Knight Ride (config public.serviceName; its built-in default is a personal-use name — rebrand before any public product) and Knight Ride (config public.appName, the iPhone app's App Store name) when it renders this file.

Who we are. Knight Ride is the ride service for chauffeured vehicles operated by [Company legal name] ("we"); Knight Ride is its iPhone app. Contact: [privacy@… / postal address].

What the app collects and why

DataWhenWhyWho sees itHow long
Your live locationOnly while you have an active "Pick me up" request that you started and agreed to. It stops at pickup, when you tap Stop, when the request expires (15–60 min, you choose) or when the ride ends.So your driver can find you and navigate to you.Only the driver(s) assigned to that vehicle.We store only the latest point during the request and delete it when sharing stops. We keep no location history.
A meeting pin / pickup notes / a photo of where you areOnly if you add them.To help the driver find you.The vehicle's driver.Deleted 30 days after the ride closes. Photos are re-encoded and their embedded metadata (including GPS) is removed.
Messages (text, quick replies, shared pins, photos)When you send them.Chat between you and your driver.The participants of that ride only. Messages are never shown on the vehicle's cabin screens.Deleted 30 days after the ride closes.
Your phone numberOnly if you choose to share it. Drivers' numbers are shown to guests only if the driver turns that on.So the other party can call you.The other party of your ride.Until you remove it, or for guests, until the invite expires (plus 7 days).
Push notification tokenIf you allow notifications.To tell you about messages, pickup requests and the car arriving.Our server and Apple's push service.Until you sign out, revoke the device or turn notifications off.
Device name, app version, sign-in tokenWhen you pair or join as a guest.To recognise your device and keep the connection secure. Tokens are stored hashed.Our fleet administrators.Until the device is revoked. Guest tokens expire with the invite (24 h at most).
Vehicle position and trip ETAWhile the vehicle is in service.To show you where your car is.Authorised users of that vehicle, and a guest during their own ride.As per the operator's fleet records.

Fallback GPS (staff only). If a staff member turns on "use this phone's location for the cabin map", the phone sends its location to the vehicle's on-board system over the vehicle's local network only.

What we don't do

Security

All traffic is encrypted in transit (TLS). Data is stored on servers we operate. Access is limited to the ride's participants and our fleet administrators. Administrators see ride metadata (state, times), not message text or locations.

Your choices

You can stop sharing at any time ("Stop" on the sharing banner), deny or revoke location and notification permission in iOS Settings, leave a guest ride ("Leave ride"), or ask us to delete your data: [contact].

Children

The app is not directed to children under 13.

Changes

We will update this page and change the date below.

Last updated: [date]


App Store privacy labels (for App Store Connect, draft): Location – Precise location (App Functionality; linked to the user's ride; not used for tracking). Contact Info – Phone number (optional, App Functionality). User Content – Messages, Photos (App Functionality). Identifiers – Device ID / push token (App Functionality). Not collected: Usage data, Diagnostics, Financial, Health, Browsing. Tracking: No.