Demo policy details. Operator/contact information must be completed before publication.
Demo version 2026-10-28-demo-1 · Prepared 28 October 2026 1. Who handles information DEMO OPERATOR DETAILS — legal entity name, postal address, privacy/grievance contact and public support email will be added before publication. HillRide currently uses Innovative Archive branding. This notice covers the app and website. It explains current intended operation; it is not a claim that every provision of a privacy law has commenced or that the service has been certified compliant. Public privacy/grievance contact details must be completed before publication. Use Support tickets for demo privacy requests. 2. Information collected and purposes Account information includes name, email, mobile number, role and authentication/session information, used to provide accounts and contact access. Supabase Auth handles sign-in credentials. Ride information includes pickup/destination pins and labels, schedule, passenger count, vehicle preference, instructions/photos, fare, assigned drivers, PIN verification outcome, status actions and timestamps. We use it for matching, pickup, ride operation and resolving questions. A private ride PIN supports pickup confirmation. Driver information includes vehicle/plate, uploaded document photo, approval, subscription/payment-reference records, availability and service permissions. UPI setup includes an ID and uploaded QR image, which may contain an account name. Recorded passenger receipts include amount, method, receiving driver and time; they are not bank verification. Route-change, transfer and support records preserve the participants' recorded actions. We do not collect bank passwords or UPI PINs. 3. Location and device choices Service-area verification checks a fresh location when needed for booking. The server retains the verification time, expiry, session, platform and boundary version, rather than the raw verification coordinates. A valid session confirmation avoids repeated location requests for up to three hours, with occasional earlier rechecks before new bookings. Existing ride location sharing is separate. Failed verification does not remove access to support or policies. Drivers share location while online or assigned. Riders can choose live sharing with their assigned driver during an active ride. The booked pickup pin remains separate. Android uses a visible location-service notification and may continue updates when minimized or locked; device permissions, GPS/network and OS limits apply. Location is not intended to track offline drivers with no assignment or riders without an active sharing choice. Stop sharing through the ride control, go offline where applicable, sign out or revoke device permissions. A driver on an active ride may still need to end that assignment to stop duty tracking. Web location may stop outside the visible browser. Push tokens and notification preferences support alerts. You can control notifications in device/browser settings. Policy acceptance is not permission to access device location or photos. 4. Who receives information Assigned participants see information needed for the ride: name, vehicle details, booked pins, pickup instructions/photos as permitted, and current shared positions. Direct calls and WhatsApp may reveal personal numbers; they can remain in phone history and cannot be remotely erased by HillRide. Accepted handoff drivers can access each other's numbers for coordination and settlement. Current assignment access to live positions and rider contact ends on handoff/end; already shared information cannot be recalled. A passenger can access the booking's driver QR/payment details. Emergency contacts are optional and private from ride partners; the app does not automatically alert them or detect accidents. Call/SMS sharing occurs only when you choose it, and the external phone/SMS app completes the action. Obtain the contact person's permission to add their details. Support tickets are visible to their owner and authorized admins, not automatically to the other ride participant. Authorized admins access relevant operational and complaint information. Private emergency contacts and PIN secrets are not ordinary admin-facing records. 5. Providers, hosting and device storage The service uses Supabase for accounts/database/private files; Google Maps/Places/Routes for maps and routing; Firebase Cloud Messaging for push; and web hosting infrastructure. Their processing may involve other countries and their own terms/notices. We must verify provider configurations and applicable transfer requirements before publication; this draft makes no data-localisation promise. Phone, WhatsApp and UPI apps process information under their own policies. Saved sessions and notification preferences use app/browser storage. Operational provider logs may include device/network information. No advertising tracker or sale of personal information is part of the current app implementation; do not infer that every provider retains no logs. 6. Retention and security Ride-position access is restricted to the current participants and position rows are cleared on ride end, release or reassignment, with a cleanup fallback; last driver coordinates may remain in the driver profile for availability/freshness checks. Account, booking, payment, uploaded files and support records may remain for operation, resolving issues and applicable obligations. No universal automatic deletion deadline has been implemented for these records; retention periods and deletion procedures must be finalised before publication. Backups and provider logs may persist separately. Access controls/private storage reduce risk but cannot guarantee absolute security. Do not upload unnecessary identity or financial data. 7. Requests, withdrawal and complaints Use Support tickets to request access, correction, deletion/account closure, information about use, or withdrawal of an optional sharing choice. These requests require admin review and appropriate identity checks; the current app does not provide automatic account deletion or automatic refunds. Some records may need to be retained for applicable obligations or disputes; the admin should explain any limitation. Withdrawal can affect features that need the information. You may use rights and complaint routes available under applicable law; these terms do not waive them. Public privacy/grievance contact details and request-handling procedures remain publication prerequisites. 8. Children and updates Accounts/independent bookings are intended for adults aged 18 or over. Do not create a child account; responsible adults must arrange and accompany children and avoid unnecessary child data in notes/photos. Report suspected misuse to support. Material privacy changes require a new notice and any consent required by applicable law. Acceptance records retain the document version and server-recorded time. This demo notice needs legal/operator review before public use.