TripMatch is a shared rides board for the UC Berkeley Haas community, run by a single student — not a company. This page describes exactly what it collects, why, and who can see it. It is short because the app does very little.
Who can use it
TripMatch is limited to @berkeley.edu accounts. Sign-in is handled by
Google; accounts outside that domain are rejected and no data is stored for them
beyond a record that a sign-in was refused.
What we receive from Google
When you sign in, Google gives TripMatch three things:
- Your name, as it appears on your Google account
- Your @berkeley.edu email address
- Your profile picture URL
That is all. TripMatch never receives your password, and has no access to your email, Drive, calendar, contacts, or any other Google service.
What you give us directly
- Trips you post — origin, destination, date, optional time, seat count, and notes
- Comments you write on trips
- Trips you mark yourself interested in (“+1”)
Who can see it
Your name appears next to your posts, comments, and +1s, so classmates know who to contact about a ride. That is the point of the board.
Your email address is not shown to other users and is not included in the data sent to their browsers. It is used only to identify you as the owner of your own posts, so you can edit or delete them from any device.
Activity log
To keep the board accountable and to diagnose problems, TripMatch records each action — posting, editing, deleting, commenting, +1ing, and signing in — along with the account that performed it, a timestamp, and technical request details (IP address, country, and browser user-agent string).
This log is readable only by the app's administrator. It is not shared, sold, or used for advertising or analytics.
What we don't do
- No advertising, and no ad networks
- No third-party analytics or tracking pixels
- No selling or sharing of your data with anyone
- No tracking you across other websites
- No cookies for tracking — your sign-in is kept in your own browser's local storage
Where it's stored
Data is held in a Cloudflare D1 database accessed only by TripMatch's own server code. Sign-in is provided by Google Identity Services, and the site itself is hosted on GitHub Pages. Those three providers process data on TripMatch's behalf; no one else receives it.
How long it's kept
Trip posts disappear from the board once the trip date has passed. Posts, comments, and activity-log entries are retained in the database after that so the log stays complete and a deletion can be undone if it was a mistake.
Deleting your data
You can delete any of your own posts from the board at any time. To have your account and everything associated with it removed entirely, email the address below and it will be deleted.
Changes
If what TripMatch collects changes, this page will be updated and the date at the top will change with it.
Contact
Questions, corrections, or deletion requests: eason_han@berkeley.edu