Privacy Policy

This Privacy Policy explains what information CampusRidez collects, why we collect it, how we use and share it, and the choices you have. It applies to the CampusRidez mobile application, website, and related services.

We designed CampusRidez around a simple principle: a ride requires sharing some information with the people you are riding with, and nothing more. Exact addresses are treated as sensitive and are tightly scoped.

We collect information you give us directly, including:

• Name and profile details.
• University affiliation and expected graduation or enrollment status.
• Ride postings, bookings, and trip details.
• Messages you send through in-app chat.
• Reports, support requests, and correspondence with our team.

We collect your phone number to verify your account, to help prevent duplicate or fraudulent accounts, and to deliver time-sensitive ride and safety messages. Your full phone number is not published in public ride feeds. It may be shared with a confirmed ride participant where that is necessary to coordinate a trip.

We collect and verify a university email address to confirm that you are a member of a supported campus community. Your university affiliation may be shown to other users, but your full email address is not displayed publicly on your profile.

We store account settings, profile photo if you add one, verification status, notification preferences, and your role preference as a driver, passenger, or both. This information helps other students decide whether to share a ride with you.

We record whether your university email and phone number have been verified, and when. CampusRidez does not perform criminal background checks or credit checks, and verification status is not a safety guarantee or an endorsement of any user.

When a driver posts a ride, we collect the general route such as origin and destination city or area, the departure date and time, the number of available seats, and any notes the driver adds. General route information is visible to verified students browsing rides.

When a passenger books a seat, we collect the number of seats requested, booking status, timestamps, and any booking notes. Booking history is retained so users can reference past trips and so we can investigate reports.

Exact pickup and drop-off addresses are treated as sensitive information. We collect them only to make a shared ride practical, and we restrict where they can appear.

• Exact booking addresses are visible only to authorized participants who need them to complete the ride.
• Exact addresses do not appear in public ride feeds.
• Exact addresses are not included in public profiles.
• Exact addresses are not included in push-notification text.
• Exact addresses are excluded from analytics events and general application logs.
• One passenger does not automatically see another passenger's exact address. Drivers see the stops they need in order to complete the route.
• Location information is retained only for as long as there is a justified operational, safety, support, or legal purpose.

We store in-app chat messages so conversations remain available to participants and so we can respond to reports and support requests. Messages may be reviewed by authorized personnel in connection with a safety report, investigation, or legal obligation. Please do not share financial account numbers or government identifiers in chat.

We collect device push tokens so we can deliver ride-status, booking, chat, and safety notifications. Tokens are used only for notification delivery and are deleted when you disable notifications or delete your account.

We collect device model, operating system version, app version, language, time zone, crash diagnostics, and similar technical data to keep the service reliable and to diagnose problems.

We collect aggregated information about which screens are used, which features are engaged, and where users encounter errors. Analytics events are designed to exclude exact addresses, chat message content, and other sensitive fields.

With your permission, we use approximate location to surface nearby and relevant rides, and precise location to support navigation and accurate pickup coordination. You can change or revoke location permissions at any time in your device settings, though some features may become limited.

We may receive limited information from providers that support verification, messaging delivery, mapping, notification delivery, and fraud prevention. For example, an SMS provider may report whether a verification message was delivered.

We collect information to:

• Verify that users belong to a supported campus community.
• Enable ride posting, discovery, booking, and coordination.
• Deliver notifications and support communications.
• Investigate reports and enforce our policies.
• Maintain security, prevent fraud, and comply with legal obligations.
• Improve reliability and product quality.

We use information to operate and improve the Platform, personalize relevant ride results, communicate with you about your account and trips, detect and prevent abuse, respond to safety reports, and meet legal requirements. We do not sell your personal information.

We share information only as described below:

• With ride participants, limited to what is needed to complete a trip.
• With service providers acting on our behalf under contract.
• For legal, safety, and security reasons as described in this policy.
• In connection with a corporate transaction, subject to this policy's protections.
• With your consent or at your direction.

Visibility is scoped to the role and the stage of the ride:

• Browsing studentssee the general route, departure time, seats available, and the driver's first name, verification status, and profile photo.
• Driverssee, after a booking is confirmed, each passenger's name, verification status, seat count, and the pickup and drop-off stops needed to complete the route.
• Passengerssee the driver's profile, vehicle details, and general route. They do not automatically see other passengers' exact addresses.

We use vetted service providers to operate the Platform. Providers are permitted to process information only to perform services for us, under contractual confidentiality and security obligations, and are not permitted to use your information for their own purposes.

We use an SMS provider, such as Twilio, to deliver verification codes and time-sensitive messages. We share the minimum information necessary, which is typically your phone number and the message content. Verification codes are single-use and short-lived.

Push notifications on iOS are delivered through the Apple Push Notification service. Notification payloads are intentionally minimal and never contain exact pickup or drop-off addresses.

We use mapping and geocoding providers to convert addresses into coordinates, display routes, and enable navigation handoff. Queries sent to these providers are limited to what is required to render the map or route requested.

Application data is stored with reputable cloud hosting and managed database providers. Data is encrypted in transit and at rest, and access is limited to authorized personnel and services.

We may disclose information when we believe in good faith that it is required by law or legal process, or that it is necessary to investigate a violation of our policies, protect the rights, property, or safety of a user or the public, or prevent fraud or a security incident.

We retain information only as long as needed for the purposes described in this policy or as required by law.

• Verification codes: minutes.
• Push tokens: until notifications are disabled or the account is deleted.
• Exact pickup and drop-off addresses: retained for a limited period after trip completion to support disputes and safety reports, then removed or de-identified.
• Chat messages and booking history: retained to support participants, investigations, and legal obligations.
• Records subject to a legal hold or open investigation: retained until the matter is resolved.

We use administrative, technical, and physical safeguards including encryption in transit and at rest, least-privilege access controls, authentication requirements, and monitoring. No system is perfectly secure, and we cannot guarantee absolute security of information transmitted to or stored on the Platform.

You can delete your account from within the app or request deletion through support. See our Account and Data Deletion page for step-by-step instructions, what is deleted, what may need to be retained, and expected timelines.

You may request a copy of the personal information we hold about you, ask us to correct inaccurate information, or ask us to delete information subject to legal limits. Contact privacy@campusridez.com. We may need to verify your identity before acting on a request.

Depending on where you live, you may have additional rights under state privacy laws, including the right to know, access, correct, delete, or obtain a portable copy of your personal information, and the right not to be discriminated against for exercising those rights. CampusRidez does not sell personal information or share it for cross-context behavioral advertising.

CampusRidez is intended for university students aged 18 and older. We do not knowingly collect personal information from children. If we learn that we have collected information from a child, we will delete it. If you believe a minor has created an account, contact privacy@campusridez.com.

CampusRidez currently operates in the United States and information is processed there. If you access the Platform from outside the United States, you understand that your information will be transferred to and processed in the United States, where data-protection laws may differ from those in your location.

We may update this policy as the Platform evolves. We will revise the "Last updated" date above and, for material changes, provide additional notice in the app or by email before the change takes effect.

For privacy questions or to exercise your rights, contact us:

• Privacy: privacy@campusridez.com
• Support: support@campusridez.com