How CityRide App LLC collects, uses, shares, and keeps information for the CityRide rideshare service.
Coming SoonEffective date: October 13, 2026. Last updated: October 13, 2026. CityRide is coming soon in Salt Lake City, Utah. This policy describes the rider app, the driver app, and this website. It is the privacy policy we will link from the Apple App Store and Google Play listings. You can read it without creating an account.
CityRide App LLC ("CityRide," "we," "us") will offer a rideshare platform that matches riders with drivers. We decide why and how personal information is used for that service. This policy applies to people in the United States, including Utah and California.
We collect the following categories when you use the site or, after launch, the apps.
Phone number, name, and profile photo. Email address if you give one to us, including when you email support. We use the phone number to create the account, sign you in, and contact you about a trip or the account.
Precise location and a coarser area derived from it. Pickup and drop-off places you enter are sent for search and routing. Details are in the location section below.
Trip date and time, pickup, drop-off, route, fare, cancellation, the rider and driver on the trip, ratings, and in-app actions such as requesting a ride or going online. Place searches you type are used to find an address.
Rider charges are processed by Stripe. Driver payouts are processed by Stripe Connect. We receive payment status, amount, a limited payment reference, and payout status. We do not store your full card number. Stripe may collect payout and tax information, such as a tax identification number, directly from a driver during Connect onboarding. That collection is described in Stripe's own privacy notice.
For people who apply to drive: driver's license, proof of insurance, vehicle registration, vehicle details, and the result of a background check. The check is done by [TODO: background check vendor]. [TODO: background check scope, lookback period, and whether the vendor uses biometrics]. We do not collect biometric identifiers ourselves.
During a trip we show the other person your name, profile photo, and an approximate location so you can meet. The rider also sees the vehicle description shown in the app, which includes make, model, and color. [TODO: whether the rider is shown the license plate]. We do not show your phone number to the other person for ordinary trips.
The product includes safety monitoring and trip anomaly alerts. We process signals such as trip path compared with the expected route, cancellation patterns, device and app information, ratings, and reports you or the other person send to support. We use those signals to investigate fraud, unsafe conduct, and account abuse. We do not use them to advertise to you.
Device model, operating system, app version, a device or installation identifier, and crash or performance data if the app sends them. [TODO: crash or diagnostics vendor, if any other than the app itself]. This website is hosted on Cloudflare. Cloudflare processes IP address, browser data, and security logs to deliver and protect the site. We do not use this website for third-party advertising, and we do not drop advertising cookies on it.
Messages and call details you send to support, and lost-item or payment questions you ask us to handle.
We do not collect health or fitness data, your contacts or address book, your browsing history on other sites, or calendar data. Profile photos are pictures you provide for the account. [TODO: whether the app asks for camera access, photo library access, or both, when you add a profile photo]. We do not use Apple's advertising identifier to track you across other companies' apps and websites. [TODO: confirm before launch that the apps do not access the advertising identifier].
The table below is the set of disclosures we will use for Apple's App Privacy details and Google Play's Data safety section. Purposes are app functionality, safety, fraud prevention, and customer support. We do not use these categories for third-party advertising or for tracking across other companies' apps and websites.
| Category | Examples | Collected | Shared |
|---|---|---|---|
| Contact info | Name, phone number, email if you provide it | Yes | Name is shown to the other person on a trip. Phone number is not. |
| Precise and coarse location | GPS while the app is in use; driver location while on duty, including in the background | Yes | Approximate location with the other person on the trip; route points with the map and routing providers below |
| Sensitive info | Precise location; driver's license and other government ID needed to drive | Yes | License and background-check data with the check vendor. Precise location as described above. |
| Financial info | Payment status and ride charges via Stripe; driver payout status via Stripe Connect | Yes, with card numbers held by Stripe | Stripe |
| Purchases | Ride history and fares | Yes | Not sold. Shown in your account. |
| User content | Profile photo, ratings, support messages | Yes | Photo and rating context with the other person on a trip, as the app displays them |
| Identifiers | Account ID and a device or installation ID | Yes | Service providers who secure or host the service |
| Usage data | Trip requests, place searches, going online, cancellations | Yes | Not sold |
| Diagnostics | App version, device model, crash and performance data | Yes | [TODO: diagnostics vendor, if we add one] |
| Health, contacts, browsing history | Not used for CityRide | No | No |
Riders: we collect precise location while you are using the app, so you can set a pickup, see the car, and follow the trip. We do not collect rider location in the background.
Drivers: CityRide collects location to match rides and navigate even when the app is closed or not in use, only while you are on duty. On duty means you are online and available, or you are on a trip. When you go offline, background collection for that session stops. We use that location to offer nearby trips, navigate, share an approximate position with the rider, and support safety monitoring.
The operating system will ask you to allow location. You can turn it off in system settings. The apps cannot match or navigate a trip without the location the feature needs. Place search uses Nominatim and routing uses OSRM, both with OpenStreetMap data. Those services receive the places and coordinates needed to search or draw a route. [TODO: whether Nominatim and OSRM are operated by CityRide or by a named host].
Riders pay fares through Stripe. Drivers are paid through Stripe Connect. The coming soon site describes instant driver payouts. [TODO: confirm payout speed, any minimum balance, and any payout fee]. The fare shown before you confirm a ride is the charge for that trip, including any CityRide fee that is disclosed in the app. [TODO: fare structure, CityRide service fee, and driver share]. We do not store full card numbers on CityRide servers.
Before a driver can go online we review a valid driver's license, proof of insurance, vehicle registration, and a background check from [TODO: background check vendor]. We keep the documents and the check result so we can confirm eligibility and handle a later safety or legal question. Drivers must keep those documents current. We do not sell them.
After a trip, the rider and the driver may rate each other. We use ratings, reports, cancellation history, and the safety signals described above to protect people and to limit or remove access. [TODO: rating threshold that affects access, and whether written comments are shown].
Cancellation fees, if they apply, are shown in the app before you confirm the action that incurs them. [TODO: free-cancellation window, cancellation fee amounts, and any no-show fee]. We keep cancellation records as part of ride history and, when needed, as a fraud or safety record.
We share personal information only in these ways:
We do not sell personal information. We do not share it for cross-context behavioral advertising.
When you give us a phone number and ask for a code, you agree that we may send you autodialed or prerecorded text messages for one-time passcodes, trip updates, and account security. A verification text is required to create and protect an account. Message and data rates may apply. Message frequency varies with your trips. Reply STOP to opt out of texts that are not required to sign in or keep an active trip safe. Reply HELP for help, or contact support@cityrideapp.com. We do not send marketing texts unless you give separate written consent. [TODO: SMS provider name, and the short code or sender ID].
We keep personal information only as long as we need it for the purpose we collected it, and then we delete it or de-identify it. Where a period is not fixed by law, the specific number of days is still open and is marked below.
| Information | How long we keep it |
|---|---|
| Account profile, phone number, and photo | While the account is open. After a verified deletion request, removed from active systems except for the retained items in this table. |
| Precise location and driver background location | For the trip, then for [TODO: number of days GPS traces are kept before they are reduced to the route stored in ride history]. |
| Ride history | While the account is open. Deleted with the account unless a tax, safety, fraud, or legal hold below applies. |
| Payment and tax records | As long as tax, accounting, and payment-network rules require. [TODO: confirm the retention period with counsel]. Stripe keeps its own payment records under Stripe's policy. |
| Driver documents and background check results | While the driver is approved, and then for [TODO: period after the driver stops driving], or longer while a safety or legal matter is open. |
| Support messages and safety or fraud files | For as long as needed to finish the request, investigate, meet a legal duty, or defend a claim. [TODO: outer limit for support tickets and for safety or fraud files]. |
| Cloudflare and SMS logs | [TODO: CityRide log retention period]. Cloudflare and the SMS provider also keep logs under their own schedules. |
| Backups | Deleted data can remain in backups until those backups roll off. [TODO: backup rotation period]. |
We use HTTPS for data in transit, limit access to people and vendors who need it, and require drivers to pass the document and background review described above before they go online. No method of storage or transmission is perfectly secure. [TODO: security certifications, if any].
We are based in the United States and the launch market is Salt Lake City, Utah. Cloudflare and Stripe may process information in the United States and in other countries where they operate. Where information is transferred internationally, we use the safeguards those providers offer and the contracts we have with them. [TODO: list of countries and the transfer mechanism counsel wants named].
You may ask us to access, correct, or delete personal information, or to provide a portable copy. You may appeal a denial by replying to our decision. We will not discriminate against you for making a request. We will verify the request using the phone number on the account or another reasonable check. You may use an authorized agent if you give the agent written permission and we can verify you.
We respond within 45 days. We may extend that once, by another 45 days, when the request is complex, and we will tell you if we do. Access requests cover the 12 months before the request unless a longer period is required. If we deny an appeal, you may contact the Utah Attorney General or, if you are a California resident, the California Privacy Protection Agency.
The launch market is Utah. If you are a California resident, this section also applies. In the last 12 months we collect, or at launch will collect, the categories in this policy: identifiers, customer records (name and phone), commercial information (rides and fares), internet or device activity, precise and coarse geolocation, professional or employment information only to the extent a driver application includes eligibility documents, profile photos, and inferences drawn for safety and fraud, not for advertising. Sources are you, your device, the other person on a trip, Stripe, the background-check vendor, and automatic logs. We use them to provide rides, take payment, pay drivers, keep people safe, and meet the law.
Sensitive personal information we handle is precise geolocation, a driver's license or other government identification, and account log-in through your phone number and one-time passcode. We use that information to provide the service you request, for safety, and to meet legal duties. You may still email support@cityrideapp.com with the subject "Limit the Use of My Sensitive Personal Information," and we will confirm whether any use goes beyond providing the service.
The Utah Consumer Privacy Act applies only to controllers that meet its size thresholds. We will honor Utah rights whether or not those thresholds are met: access, deletion, a portable copy, and opt-out of sale and of targeted advertising. We do not sell personal information and we do not use it for targeted advertising. You may appeal a denial as described above.
CityRide App LLC does not sell personal information for money and does not share it for cross-context behavioral advertising. There is no sale or share to opt out of today. You may still email support@cityrideapp.com with the subject "Do Not Sell or Share." We will record that request and honor it if our practices ever change. We will not start selling or sharing for advertising without updating this policy and providing this choice first.
CityRide is not directed to children under 13. We do not knowingly collect personal information from anyone under 13. The account holder must be 18 or older. If we learn we have collected information from a child under 13, we will delete it. Email support@cityrideapp.com if you believe a child has created an account. An adult account holder may travel with their own child. We do not create a profile for that child.
You can delete the account in the app from the menu by choosing Delete account, or by email. The steps, the timeline, and what is deleted or retained are on the delete account page. We do not offer Sign in with Apple. If we add it later, deletion will also revoke that token.
We will post changes on this page and change the effective date. If a change materially affects how we use personal information, we will also notify you in the app or by email or text if we have a way to reach you. Continued use after the new effective date means you accept the update, except where the law requires a separate consent.
Mailing address: CityRide App LLC, 544 Foxboro Drive, North Salt Lake, UT 84054, United States.
Email support@cityrideapp.com or call +1 (682) 298-4272. Support hours: Monday to Friday, 9:00 AM to 5:00 PM Mountain Time (closed US federal holidays). For a safety emergency, call 911.
The coming soon website also lists info@cityrideapp.com for general questions. Privacy requests, account deletion, and support go to support@cityrideapp.com.