Table of Contents
How It Works
This platform helps UIUC students coordinate rides in a safe, transparent, and structured way.
Note
This is not a traditional rideshare or taxi service. Drivers post trips they are already planning to take, and riders request to join those trips under clearly defined rules.
What This Platform Is
The system is designed to:
- Minimize uncertainty before meeting
- Protect personal information
- Create clear records of what happened
- Reduce misunderstandings through automation
Who Can Use This Platform
University-only access
Access is restricted to users who sign in with a UIUC Microsoft account.
This ensures everyone on the platform belongs to the same university community.
There are no guest accounts and no public posting without login.
Account Creation & Profile Basics
Automatic profile creation
When you log in for the first time:
- A basic profile is created automatically
- No sensitive information is public by default
- You can use the platform immediately
What your profile contains
Your profile may include:
- Display name
- Profile photo
- Rider and/or driver statistics
- Optional phone number
Your phone number and other sensitive fields are never public by default.
Privacy-First Profile Design
Relationship-based visibility
Your full profile details are only visible to:
- People you currently have an active booking with
- People you very recently completed a trip with (short grace period)
- Yourself
Strangers browsing the platform:
- May see a name preview (partially redacted)
- Will not see phone numbers
- Will not see precise locations
Permanent records vs temporary contact
The system distinguishes between:
- Identity history (who you rode with — permanent)
- Contact access (phone/payment — temporary)
Contact information automatically expires after trips end.
Vehicles & Driver Requirements
Registering a vehicle
Drivers must register vehicles before using them for trips.
Each vehicle includes:
- Make, model, color, year
- Seat count
- License plate (never public before departure)
Why vehicles are required
Vehicle information is essential for:
- Safety
- Pickup coordination
- Dispute resolution
Trips cannot safely start without an assigned vehicle.
Posting a Ride (Drivers)
Core trip details
When posting a trip, drivers provide:
- From / To locations (public-safe text)
- Departure time
- Price
- Available seats
- Optional notes
Exact addresses are not made public.
Public-safe location text
The system automatically converts exact addresses into:
- Neighborhoods
- Campuses
- General areas
This protects privacy while still enabling discovery.
Trip Rules & What They Mean
Luggage limits
Drivers specify how much luggage is allowed per rider.
Pickup & drop-off radius
Drivers define how far they are willing to deviate from their route for pickup or drop-off.
Riders must choose locations within this radius.
Departure time flexibility
This defines how early or late a trip may realistically start.
Payment methods & payment window
Drivers list accepted payment methods.
If payment is required:
- Riders must act within the defined time window
- The system automatically expires unpaid bookings
Auto-accept
When enabled:
- Bookings are accepted immediately
- Payment window starts automatically
When disabled:
- Driver manually approves each booking
Templates (Designed for Speed & Consistency)
Rule templates
Drivers can save frequently used rule configurations and reuse them across trips.
Trip templates
Drivers can save full trip setups (route + rules) and quickly post recurring trips.
Templates help reduce mistakes and ensure consistent expectations.
Searching for Trips (Riders)
What search looks at
Search considers:
- Pickup proximity
- Drop-off proximity
- Departure time closeness
- Seat availability
- Filters (price, luggage, payment method, auto-accept)
Ranking philosophy
Trips are ranked by a combined score balancing:
- Time difference
- Distance deviation
This avoids showing trips that are technically valid but impractical.
Booking a Trip (Riders)
Booking request states
A booking may be:
- Waiting for approval
- Accepted with a payment window
- Pending payment confirmation
- Confirmed
- Expired (automatic)
- Cancelled or completed
Payment timing
Payment confirmation is time-bound to avoid holding seats indefinitely.
What riders can see
Riders only gain access to:
- Driver contact
- Pickup details
when the booking is active and relevant.
Managing Bookings (Drivers)
Driver control
Drivers can:
- Accept or reject bookings
- Remove riders (with reason)
- See who is ready for pickup
- Mark riders as picked up or no-show
Transparency
Every status change is logged in history.
Nothing silently changes without a record.
Pickup & Check-In Flow
Check-in window
Before departure:
- Check-in opens automatically
- Riders confirm readiness
- Pickup coordination begins
Pickup locations
Riders may specify pickup notes or locations within the allowed radius.
Exact driver locations remain protected.
Trip Lifecycle (End-to-End)
Typical flow
- Trip posted
- Riders book
- Payment window (if applicable)
- Check-in opens
- Trip departs
- Trip completes
Automation safeguards
The system may:
- Lock trips at cutoff
- Expire unpaid bookings
- Auto-start check-in
- Auto-complete trips if drivers forget
Automation exists to prevent dead states.
Notifications & Alerts
In-app notifications
All important actions generate in-app notifications.
Push notifications (optional)
Push notifications:
- Are opt-in
- Respect user preferences
- Are used for time-sensitive events only
What triggers notifications
Examples:
- Booking accepted or expired
- Check-in started
- Trip cancelled or completed
- Important contact or vehicle changes
History & Records
Why history matters
Every trip, booking, and status change is recorded.
This protects both riders and drivers if questions arise later.
What is retained
- Who participated
- What rules applied
- What actions occurred
- When events happened
Safety & Trust Principles
No anonymous coordination
All users are verified through university login.
Limited exposure of sensitive info
Phone numbers, exact locations, and plates are:
- Shown only when necessary
- Automatically revoked afterward
No silent automation
System actions are logged and notified.
Proper Use Expectations
This is not a taxi service
Drivers are not obligated to accept all riders.
Riders are expected to respect rules and timing.
Abuse prevention
Repeated misuse (no-shows, removals, etc.) is visible in history. These stats will have an impact in the system in the future.
Disclaimers
This platform:
- Does not provide insurance
- Does not guarantee trip completion
- Does not mediate payments
It exists to coordinate, not enforce real-world behavior.
Final Notes
This system is intentionally designed to:
- Reduce ambiguity
- Encourage accountability
- Protect privacy
- Scale safely within a university community
If something feels “restricted,” it is usually intentional — to protect users on both sides.
