StudentGo

Privacy Policy

Last updated: 17 June 2026

1. Introduction

StudentGo (“we”, “us”, “the platform”) is a student transport booking platform operated on behalf of your transport operator (the “operator”). The platform is available through our website and official mobile applications for students and drivers.

This Privacy Policy explains what personal data we collect, how we use it, who can access it, and what choices you have. By registering or using StudentGo, you acknowledge this policy.

2. Who is responsible for your data?

StudentGo is the technical platform that powers booking, boarding, payments, and notifications. Your transport operator (the organisation that schedules routes, approves drivers, sets prices, and handles support complaints) administers the service in your region.

For privacy requests, account issues, or data corrections, contact your operator through the in-app Support form in the student dashboard, or reach the platform administrator listed on your operator’s communications.

3. What data we collect

We collect only the data needed to run daily university transport:

Account data (all users): full name, phone number, password (stored as a secure hash — never in plain text), user role (student, driver, or admin), and account status.

Student profile: university, campus, home city/area, default pickup point description, pickup type (home or meeting point), and optional pickup coordinates (latitude/longitude) when you select a location on the map.

Driver application: primary work area, vehicle type, seat capacity, licence plate number, preferred route lines, and available time windows. Drivers remain inactive until the operator approves the application.

Booking & trip data: trips booked, boarding codes, booking status, payment method and payment status, boarding timestamps, cancellation records, and no-show history.

Trip execution: for active trips, drivers may transmit GPS coordinates while a trip is in progress; pickup stop order, labels, and coordinates are stored for routing and boarding.

Support & complaints: messages you submit through Support, optionally linked to a booking.

Wallet & packages: prepaid wallet balance, package purchases, and transaction history (amounts, type, status).

Technical data: session cookies for authentication (see Section 8). We do not collect email addresses, national ID numbers, or dates of birth in the current platform.

4. How we use your data

We use personal data to:

• Create and secure your account • Match you to available trips based on your university, campus, and pickup location • Process bookings, cancellations, and boarding verification • Display your QR boarding pass and share necessary details with your assigned driver • Calculate fares, wallet deductions, package usage, and driver commissions • Send in-app notifications about bookings, trips, arrivals, and account events • Let drivers navigate routes, mark arrivals, and confirm passenger boarding • Handle support complaints and operator administration • Enforce platform rules (cancellation windows, no-show limits, booking caps)

We do not sell your personal data to third parties for advertising or marketing.

5. Who can see your data

Students can see their own bookings, QR passes, wallet balance, and trip tracking for active rides.

Drivers assigned to your trip can see information needed for pickup and boarding: your name, phone number, pickup location, and boarding status for that trip. They cannot browse unrelated student profiles.

Operators (admins) can access user, booking, payment, complaint, and fleet data required to run the service, approve drivers, resolve disputes, and configure routes and prices.

Other students cannot see your personal details except where necessary in shared trip contexts managed by the operator.

6. Location data

Students may provide a home or meeting-point pickup location (coordinates) during registration or profile update. This is used to plan stops and show drivers where to collect you.

Drivers transmit live GPS coordinates only while a trip status is “started”. Coordinates are stored on the trip record and used for live tracking, route optimisation, and proximity alerts (for example when a driver is approaching your stop). Location updates stop when the trip ends.

You can update your pickup details in your student profile at any time.

7. Payments & financial data

Depending on what your operator enables, you may pay by cash to the driver at boarding, prepaid wallet balance, ride packages, or online methods (such as Whish Money or Sofort Pay when activated).

Wallet top-ups and online payment attempts create transaction records (amount, currency, status, timestamps). We do not store full payment card numbers on our servers. Online payment integrations, when enabled, are processed according to the payment provider’s own terms and security standards.

Cash payments are confirmed by the driver at boarding through the platform; we record payment status but do not process card data for cash trips.

8. Cookies & session security

We use an HTTP-only session cookie named “studentgo_session” to keep you signed in on the website and mobile app. The cookie contains a signed token (JWT) with your user ID, name, phone, and role — not your password.

Session cookies expire after seven days. In production, cookies are marked Secure on HTTPS connections and use SameSite=Lax protection.

You can end your session at any time via Logout. Clearing cookies or uninstalling the app removes local session data on your device.

9. Third-party services

To provide routing and navigation, the platform may use:

• GraphHopper or OSRM routing services to calculate driver routes and optimise stop order • Google Maps links for external turn-by-turn directions (opening Google Maps does not automatically share your StudentGo data with Google unless you use their app directly) • Online payment providers (e.g. Whish Money, Sofort Pay) when enabled by your operator

These services process data only as needed for the feature you use. We do not use third-party advertising or analytics trackers in the current codebase.

10. Data retention & deletion

We retain account, booking, and transaction data for as long as your account is active and as needed to operate the service, comply with operator records, resolve disputes, and enforce policies (including no-show and cancellation history).

If you wish to request access, correction, or deletion of your data, submit a request through in-app Support or contact your operator. Deletion may be limited where records are required for legal, safety, or financial audit purposes (for example completed trip and commission records).

Passwords are stored using industry-standard bcrypt hashing and cannot be recovered — only reset.

11. Your rights & choices

Depending on applicable law in your region, you may have the right to:

• Access the personal data we hold about you • Correct inaccurate profile information (university, campus, pickup details; name updates are available on mobile) • Request deletion or restriction of processing, subject to operator and legal requirements • Withdraw consent by closing your account, where processing is consent-based • Lodge a complaint with a data protection authority in your country

Phone numbers cannot be self-changed in the app after registration; contact your operator for phone number updates.

12. Security

We protect data using HTTPS in production, hashed passwords, role-based access control, and server-side validation of every booking and boarding action. No system is perfectly secure; please use a strong password and do not share your QR boarding pass or account credentials.

Report suspected unauthorised access immediately through Support.

13. Children

StudentGo is designed for university students. If you are under the age required to enter a binding agreement in your jurisdiction, you may use the platform only with permission from a parent or guardian and under your operator’s enrolment rules.

14. International regions & time zones

The platform may be deployed for different service regions (for example Lebanon or other configured areas). Trip dates, cancellation cutoffs, and “today” calculations follow the active region time zone (e.g. Asia/Beirut for Lebanon deployments).

Your data is processed on servers operated for the platform deployment your operator uses.

15. Changes to this policy

We may update this Privacy Policy when features, payment methods, or legal requirements change. The “Last updated” date at the top will reflect the latest version. Continued use of StudentGo after changes constitutes acceptance of the updated policy.

Material changes may also be communicated through in-app notifications where appropriate.

16. Contact

For privacy questions or data requests:

• Students: open Support in your student dashboard • Drivers: contact your operator through the approval or fleet contact channel provided during onboarding • General: use the contact details published by your transport operator

Platform: StudentGo — student transport booking for university routes.