HillHop DOCUMENTATION

HILLHOP KNOWLEDGE CENTRE

Every journey,
clearly documented.

Guidance for riders, drivers and HillHop operators—from booking and safety to final billing, privacy and release testing.

Controlled public testing · Last reviewed 1 October 2026
Use the current screen for the final decision.

Fare, cancellation, consent and payment details shown for a specific booking take priority over general guidance here. Legal notices are linked below and remain the public source for those subjects.

01PRODUCT

Product & roles

HillHop supports riders, verified drivers, administrators and temporary family viewers across mobile and web.

Read workflow
  1. Account and role selection
  2. Booking request and fare review
  3. Driver assignment and vehicle check
  4. Start OTP and live trip
  5. Final bill, payment and support

No screen should claim that a person, payment or approval is verified until the recorded check completes.

02RIDER GUIDE

Book and complete a ride

Enter locations, compare the available vehicle and fare, verify the assigned vehicle and pay after completion.

Rider checklist
  1. Sign in with your own account.
  2. Enter pickup/drop, passengers and bike or cab preference.
  3. Review capacity, estimate, AC charge and exclusions.
  4. At pickup, match driver, vehicle and registration.
  5. Share the Start OTP only with the correct driver.
  6. Review the completed bill before paying.
03DRIVER GUIDE

Register and operate safely

Submit current documents, use the registered vehicle, follow recorded fare controls and protect rider information.

Driver checklist
  • Keep licence, registration, insurance, permit and fitness records current.
  • Review pickup, drop, passengers, luggage and vehicle need before accepting.
  • Collect the Start OTP at pickup, never in advance.
  • Add only incurred, supportable toll or parking charges.
  • Stop location sharing after completing the ride.
04OPERATIONS

Admin controls

Use individual admin accounts, least-privilege access and an audit reason for manual decisions.

Daily operations
  • Review driver applications, safety tickets, failed payments and refunds.
  • Verify documents and record approval/rejection reasons.
  • Preserve an audit trail for fare, cancellation, toll and refund changes.
  • Reconcile completed rides, payments and driver amounts daily.
07PRIVACY & SECURITY

Collect less. Protect more.

Authenticated access, row-level security, private storage and server-side secrets protect sensitive workflows.

Data rules
  • Never place keys, passwords, OTPs, identity files or customer records in source code.
  • Verify people before data export, correction or deletion.
  • Retain data only for the documented service, safety, accounting or legal purpose.
  • Contain, investigate and document suspected security events.
08RELEASE TESTING

Test the whole journey

A release must cover rider, driver, admin, payment and privacy boundaries—not only screen appearance.

Release gates
  • Booking, assignment, OTP, tracking, family revoke, completion and final payment.
  • Cancellation, refund, support and lost-item paths.
  • Android network/location transitions and phone/desktop web layouts.
  • Cross-account access, admin authorization and invalid payment rejection.
09SYSTEM

Architecture overview

Flutter and Cloudflare Pages are clients; privileged decisions stay in Supabase and payment-provider services.

Components

Clients: Flutter app, booking site, driver workspace and admin UI.
Services: Supabase Auth, Postgres, Storage, Edge Functions and Realtime; Razorpay checkout; Gemini assistant through a server function.

Client visibility is never authorization. Price finalisation, payment verification and document access require server enforcement.

10LAUNCH STATUS

Evidence before claims

HillHop is in controlled public testing. Registration, licensing or approval claims require supporting records.

Commercial-launch checklist
  • Publish confirmed legal entity, office, CIN, GSTIN and grievance details as applicable.
  • Complete applicable transport, consumer, tax, contract, insurance and store requirements.
  • Keep renewal evidence for company, driver, vehicle, payment and security records.

This operational checklist does not replace advice from qualified Indian professionals or authorities.

ALL CUSTOMER PAGES

Open the right page.

Public travel and policy pages remain open. Private rider and driver data appears only after the correct secure sign-in.

HomePublic Book a ridePublic · rider sign-in to book Trip plannerPublic · rider sign-in to save Destination guidesPublic Package detailsPublic Corporate travelPublic Driver registrationSecure applicant sign-in Driver workspaceDriver password or email link My bookingsRider password or email link Ride trackingRider account or temporary family link DocumentationPublic Privacy & data rightsPublic Terms of servicePublic Launch & legal statusPublic Photo creditsPublic

NEED HELP?

Use a verified support channel.

Include your booking code and issue. Never send your password, OTP, card details or API key.

WhatsApp supportEmail support