Privacy Policy
Effective Date
This Privacy Policy is effective as of the date you first use the platform.
By using the platform, you agree to the collection and use of information as described here. If you do not agree, do not use the platform.
Our Privacy Philosophy
Design principles
This platform is built with privacy by default, context-based visibility, and data minimization in mind.
We aim to:
- collect only what is necessary
- show personal information only when relevant
- automatically reduce visibility when coordination ends
Privacy is enforced primarily through system rules, not manual settings.
Information We Collect
Account information
When you create an account, we collect:
- your university-linked account ID
- your name
- your email address
- account creation time
This information is required to identify users and prevent abuse.
Profile information
You may provide or generate:
- display name
- profile photo
- phone number
- language preferences
Some profile fields may be optional, but certain features may require them.
Trip and booking information
When you post or join trips, we collect:
- trip routes and times
- booking details (seats, luggage, notes)
- payment method preferences (not payment itself)
- timestamps and status changes
This information is required to coordinate trips and enforce system rules.
Vehicle information
If you post trips as a driver, we may collect:
- vehicle make, model, color, year
- seating and luggage capacity
- license plate (limited visibility)
Vehicle information is used for coordination and safety.
System and technical data
We automatically collect limited technical data such as:
- device identifiers (for notifications)
- timestamps of actions
- system-generated events
- notification delivery status
We do not use this data for advertising.
How We Use Information
Core platform functionality
We use collected information to:
- display trips in search results
- manage bookings and trip status
- notify users of relevant events
- enforce booking rules and deadlines
- support safety and accountability
Search result visibility
To help riders make informed decisions, some driver information is shown in search results, including:
- driver name
- profile photo
- rating and completed trips
This information is intentionally limited and does not include:
- phone number
- exact addresses
- payment details
Automation and system decisions
Some data is used to power automated actions, such as:
- expiring unpaid bookings
- locking trips at cutoff times
- starting check-in windows
- auto-starting or auto-completing trips
These actions are based on timestamps and rules, not personal profiling.
Context-Based Visibility
What this means
Information visibility depends on context, including:
- whether you have an active booking
- whether a trip is ongoing or recently completed
- whether coordination is still necessary
Visibility is automatically reduced once the context ends.
Examples
A rider may see a driver’s phone number during an active trip, but not afterward.
A driver may see rider contact details only while pickup coordination is relevant.
Past trips revert to anonymized or limited views.
This reduces long-term exposure of personal data.
Location Privacy
Public-safe locations
Exact addresses entered by drivers may be processed into public-safe location labels, such as:
- neighborhoods
- landmarks
- general areas
This protects precise location privacy while keeping trips discoverable.
Precise coordinates
Precise geographic coordinates may be:
- stored for internal validation
- used to enforce pickup radius rules
- shown only when strictly necessary for coordination
They are never broadly public.
Photos and Identity
Profile photos
Profile photos may be displayed:
- in search results
- on trip pages
- during active coordination
Photos may be hidden or removed from view once coordination ends.
Names
Names may be:
- shown fully in active contexts
- partially redacted in inactive or historical views
This balances trust and privacy.
Payments and Financial Information
No payment processing
Unless explicitly stated otherwise:
- we do not process payments
- we do not store payment credentials
- we do not handle refunds
Any payment handles or methods are shared only during active coordination windows.
Data Retention
Operational records
We retain some data for:
- safety
- dispute context
- system integrity
- abuse prevention
Examples include:
- trip events
- booking status history
- vehicle snapshots at departure
Retention limits
We do not retain unnecessary personal data indefinitely.
Visibility and access are reduced automatically over time.
Data Sharing
With other users
Your information may be shared with other users only when relevant, such as:
- drivers seeing rider details during pickup
- riders seeing driver details during a booked trip
With third parties
We do not sell user data.
We may use trusted services for:
- authentication
- hosting
- notifications
These services only receive the minimum data required to function.
Security
Protection measures
We use reasonable technical and organizational measures to protect data, including:
- access control
- role-based visibility
- database constraints
- audit logging
No system is perfectly secure, but we actively design to reduce risk.
Your Choices and Rights
Access and updates
You can:
- view and update your profile
- control some notification settings
- choose whether to post trips or join them
Account deletion
If you stop using the platform, some historical data may remain for safety and integrity purposes, but will no longer be publicly visible.
Changes to This Policy
Updates
We may update this Privacy Policy as the platform evolves.
If changes are significant, we may notify users. Continued use means acceptance of the updated policy.
Contact
Questions or concerns
If you have questions about privacy or data handling, contact is available in the footer