Privacy Policy.

01 · Scope and structure of this PolicyScope and structure of this Policy

This Policy explains how Rideshare Cooperative ("RIDE," "we," "us," or "our") collects, uses, shares, and protects information. RIDE is in the middle of a two-stage rollout, and this Policy is written to cover both stages without pretending the second stage has already begun.

Phase 1 labels mark practices RIDE follows today, while it operates only a pre-launch driver waitlist and informational website. Phase 2 labels mark practices RIDE plans to follow only after it launches a full ride-hailing marketplace, dispatching rides, processing driver payouts, and running the other services described in Section 12. A Phase 2 label is a forward-looking description, not a statement of current practice.

If a provision carries no phase label, it applies at every stage. RIDE will update the date at the top of this Policy each time it makes a material change, and Section 14 explains how RIDE will notify waitlist participants before a material change affecting information RIDE already holds takes effect.

02 · Who we areWho we are

RIDE is a driver-founded rideshare cooperative-in-formation, based in the United States. During Phase 1, RIDE operates exclusively as a driver waitlist and informational website; it does not yet dispatch rides, process driver payments, or run background checks.

"Founding Member" means a waitlist participant who accepts RIDE's Founding Member terms, published separately from this Policy. Founding Member status affects how long RIDE keeps certain waitlist information (Section 7.1) today, and RIDE's marketing materials describe additional governance and equity rights that will attach to Founding Members once the cooperative structure described in Section 12.5 is in place.

03 · Information we collectInformation we collect

"Personal Information" means information that identifies, relates to, or could reasonably be linked with a particular person or household. This Section 3 lists every category of Personal Information RIDE collects.

3.1 Phase 1 — Information we collect today

RIDE collects the following categories of information directly from a visitor:

• Email address. Required to join the waitlist and to receive launch updates.
• Zip code. Required, so RIDE can notify a visitor by region and rank launch-market priority. If a visitor selects a suggested zip code from an autocomplete list, the matching city or state may also be recorded; RIDE never asks for city or state directly.
• Name and message content. Collected only if a visitor emails support.

RIDE also collects the following automatically:

• Hashed IP address. Used only to rate-limit signup attempts (a maximum of five attempts per hour per hash). RIDE does not store the raw IP address from this process and does not use it for geolocation or launch-market ranking.
• Standard hosting technical logs. IP address, browser, device, and pages requested, collected by RIDE's hosting provider in the ordinary course of serving the website.

3.2 Phase 1 — Information we do not collect today

RIDE does not collect a driver's license number, vehicle information, payment details, Social Security number, or background-check information during Phase 1.

3.3 Phase 2 — Forward-looking categories

Once RIDE launches its ride-hailing marketplace, it expects to collect additional categories of information, described here so this Policy can be extended without a structural rewrite. None of the following is collected today.

• Precise location data. Real-time GPS location of drivers and riders during an active ride, described further in Section 12.1.
• Payment and payout information. Card or bank details needed to charge a rider and pay a driver, described further in Section 12.2.
• Driver eligibility information. Driver's license number, vehicle registration, insurance information, and the results of a background or motor-vehicle-record check, described further in Section 12.3.
• In-app messages. Messages a rider and driver send each other through the RIDE app, described further in Section 12.4.
• Membership and equity records. Records of cooperative membership, voting, and equity or "stake" accounts, described further in Section 12.5.
• Support and dispute records. Records created when a rider, driver, or Founding Member contacts customer support or disputes a charge, described further in Section 12.6.

04 · How we use informationHow we use information

4.1 Phase 1 — Current purposes

RIDE uses the information in Section 3.1 to:

• send launch updates to a waitlist participant;
• rank launch cities by demand;
• reply to a support email;
• keep the website secure, including rate-limiting signup attempts; and
• comply with applicable law.

4.2 What we do not do

RIDE does not use waitlist information to build an advertising profile, does not sell information to a data broker, and does not use information to serve targeted advertising.

4.3 Phase 2 — Forward-looking purposes

Once RIDE launches its ride-hailing marketplace, it expects to use the additional categories of information described in Section 3.3 to dispatch and complete rides, process driver payouts, run driver eligibility checks required by law or by RIDE's insurer, operate in-app messaging between a rider and a driver, administer cooperative membership and voting, and resolve customer-support requests and disputes. RIDE will not use this information to build an advertising profile, sell it to a data broker, or serve targeted advertising.

05 · How we share informationHow we share information

5.1 No sale of information

RIDE does not sell, rent, or trade information to anyone. RIDE shares information only with the categories of recipients described in this Section 5.

5.2 Phase 1 — Vendors we use today

"Service Providers" means the outside companies RIDE uses to run the waitlist. During Phase 1, RIDE's Service Providers are the five companies in the table below, each bound to use information only to provide its service to RIDE.

5.3 Disclosures required by law

RIDE may disclose information if a subpoena, warrant, or court order legally compels it to. RIDE reviews every such request for legal sufficiency, objects to a request it believes is overbroad or unlawful, and, where the law permits, publishes what it can about the request.

5.4 Phase 2 — Forward-looking categories of recipients

Once RIDE launches its ride-hailing marketplace, it expects to share information with additional categories of recipients: a payment processor, to charge a rider and pay a driver; a background-screening company acting as a consumer reporting agency under the Fair Credit Reporting Act (15 U.S.C. § 1681 et seq.), to run a driver eligibility check; a mapping or telematics provider, to dispatch rides and calculate fares; and additional cloud or messaging infrastructure providers. RIDE will name each Phase 2 Service Provider in this Policy once it is selected and under contract.

06 · Cookies and tracking technologiesCookies and tracking technologies

We use the Meta Pixel and similar analytics tools on this site. These tools collect information such as pages visited, actions taken (for example, completing the sign-up form), browser and device type, and approximate location, and share it with Meta to measure and improve our advertising. Meta may combine this with information it already holds about you under its own data policy. You can limit this through your browser settings, Meta's ad preferences, or by disabling cookies.

07 · How long we keep informationHow long we keep information

7.1 Phase 1 — Current retention schedule

• Waitlist information: kept while a visitor remains on the waitlist, and for up to two years after, to honor Founding Member terms.
• Deletion requests: honored within 30 days, unless a legal hold requires RIDE to keep the information longer.
• Support email records: kept for up to one year, then deleted.

7.2 Phase 2 — Forward-looking retention approach

Once RIDE launches its ride-hailing marketplace, RIDE expects to keep financial and tax records for the period applicable tax law requires, keep background-check and motor-vehicle-record information for the minimum period consistent with the Fair Credit Reporting Act and RIDE's insurer's requirements, and keep cooperative membership, voting, and equity ledger records for the period RIDE's bylaws require once those bylaws are finalized. RIDE will publish specific retention periods for each category before Phase 2 launch.

08 · Your privacy rightsYour privacy rights

8.1 Rights we extend to every visitor

As a matter of policy, and regardless of the state or country a visitor lives in, RIDE gives every visitor the right to:

• know what Personal Information RIDE holds about the visitor;
• correct inaccurate Personal Information;
• delete Personal Information;
• opt out of the sale or sharing of Personal Information, although RIDE does not sell or share Personal Information today; and
• not be discriminated against for exercising any of these rights.

RIDE responds to a rights request within 30 days. Extending these rights to every visitor is a voluntary policy choice; it does not mean RIDE has concluded that any particular state's or country's privacy statute applies to RIDE's current Phase 1 operations.

8.2 California and other state privacy laws

As of this Policy's effective date, more than twenty states have enacted a comprehensive consumer privacy statute, beginning with California's California Consumer Privacy Act, as amended by the California Privacy Rights Act (Cal. Civ. Code § 1798.100 et seq.; implementing regulations at Cal. Code Regs. tit. 11, § 7000 et seq.). A California resident, and a resident of any other state with a comparable statute, has the rights described in Section 8.1 under that statute if RIDE meets the statute's applicability thresholds; RIDE extends the same rights to every visitor regardless of whether those thresholds are met.

8.3 European Union and United Kingdom visitors

RIDE's Phase 1 waitlist is directed at persons eligible to drive professionally in the United States, and RIDE does not knowingly offer its Phase 1 service to, or monitor, a visitor located in the European Union or the United Kingdom. As a courtesy, and without conceding that Regulation (EU) 2016/679 (the "GDPR") or the United Kingdom's retained version of that regulation (the "UK GDPR," as amended by the UK Data (Use and Access) Act 2025) applies to RIDE, RIDE extends the rights described in Section 8.1 to a visitor located in the European Union or United Kingdom. RIDE's lawful basis for processing an email address and zip code at signup is the visitor's consent; RIDE's lawful basis for processing a hashed IP address and hosting technical logs is RIDE's legitimate interest in keeping the website secure. RIDE has not appointed a representative in the European Union or United Kingdom under Article 27 of the GDPR.

8.4 How to exercise your rights

To exercise any right described in this Section 8, email privacy@ridesharecooperative.com. RIDE may ask for information reasonably needed to verify the requester's identity before acting on a request. A visitor may name an authorized agent to submit a request on the visitor's behalf; RIDE may ask the agent for proof of authorization. If RIDE denies a request, the visitor may appeal by replying to RIDE's denial email, and RIDE will respond to an appeal within 45 days.

09 · Children's privacy and age eligibilityChildren's privacy and age eligibility

RIDE's waitlist is for adults eligible to drive professionally in the United States. RIDE does not knowingly collect information from anyone under eighteen years old. If RIDE learns that it has collected information from someone under eighteen, RIDE will delete that information. This age-gating approach is designed with the Children's Online Privacy Protection Act (15 U.S.C. §§ 6501–6506) and its implementing rule (16 C.F.R. Part 312, as amended effective June 23, 2025) in mind, even though RIDE's adults-only, professional-driver-eligible audience makes it unlikely that a child would use the waitlist.

10 · Marketing emailsMarketing emails

The one-time confirmation email RIDE sends through Resend after signup is a transactional or relationship message under 15 U.S.C. § 7702(17)(A): it confirms the visitor's own signup, so it does not carry an unsubscribe link. Every other marketing email RIDE sends through Constant Contact is a commercial email message governed by 15 U.S.C. § 7704(a). Consistent with that statute, each such email honestly identifies its sender and subject line, clearly discloses that it is an advertisement, gives a working opt-out link, includes RIDE's current postal address, and honors an opt-out within ten business days. A visitor may also request deletion of the one-time confirmation email record at any time under Section 8.

11 · How we protect informationHow we protect information

RIDE serves its website over HTTPS site-wide, limits access to information on a least-privilege basis, and reviews its access controls periodically. If RIDE confirms a breach of security that compromises Personal Information, RIDE will notify the affected waitlist participants within the period applicable state breach-notification law requires, and in any event within 30 days of confirming the breach.

12 · Phase 2 — Forward-looking practices not yet activePhase 2 — Forward-looking practices not yet active

This Section 12 describes practices RIDE plans to adopt only after it launches its ride-hailing marketplace. None of it describes a practice RIDE follows today, and nothing in this Section 12 takes effect until RIDE updates this Policy and notifies waitlist participants under Section 14.

12.1 Location data

RIDE expects to collect a driver's and a rider's precise device location during an active ride, to match a ride request, calculate a fare, and provide turn-by-turn navigation. RIDE will publish the specific retention period for location data, and the specific mapping or telematics vendor involved, before Phase 2 launch.

12.2 Payments and payouts

RIDE expects to use a third-party payment processor to charge a rider's payment method and to pay out a driver's 85% flat share of each fare. RIDE expects to receive only the last four digits of a payment card and a payout confirmation from that processor, not full card or bank account numbers.

12.3 Background and driving record checks

RIDE expects to use a background-screening company, acting as a consumer reporting agency under the Fair Credit Reporting Act (15 U.S.C. § 1681 et seq.), to run a criminal-history and motor-vehicle-record check on a prospective driver before the driver is approved. RIDE will provide the disclosures and obtain the authorization the Fair Credit Reporting Act requires before ordering a report, and will follow the Act's adverse-action procedure if RIDE denies a driver based on a report.

12.4 In-app messaging

RIDE expects to let a rider and a driver message each other inside the RIDE app to coordinate a pickup. RIDE expects to keep a record of these messages for a limited period to support safety investigations and dispute resolution, and will publish the specific retention period before Phase 2 launch.

12.5 Cooperative membership, governance, and Founding Members' equity records

RIDE expects to keep records of cooperative membership, voting, and equity or "stake" accounts, including records tracking a driver profit-sharing arrangement tied to the arrival of autonomous vehicles. This Policy addresses only how RIDE will collect, use, and protect the data underlying those records; it does not address whether the "stake" offered to a Founding Member raises a separate securities-law question, which is analyzed elsewhere.

12.6 Customer support and dispute records

RIDE expects to keep a record of a rider's, driver's, or Founding Member's support request or dispute, including a fare dispute or a safety complaint, for as long as needed to resolve the matter and to satisfy RIDE's recordkeeping obligations.

12.7 Biometric identifiers — Conditional

If RIDE later verifies driver identity using a selfie or facial-geometry match, that process would create a biometric identifier subject to statutes including the Illinois Biometric Information Privacy Act (740 ILCS 14/1 et seq.), the Texas Capture or Use of Biometric Identifier Act (Tex. Bus. & Com. Code § 503.001), and Washington's biometric identifier statute (Wash. Rev. Code ch. 19.375). RIDE does not use biometric identifier verification today. Before RIDE adopts it, RIDE will publish a dedicated notice, obtain the consent each applicable statute requires before capture, and publish a retention and destruction schedule for biometric identifiers.

12.8 Text messages and phone calls — Conditional

If RIDE later contacts a driver or rider by text message or phone call for marketing purposes, RIDE will obtain the prior express consent the Telephone Consumer Protection Act (47 U.S.C. § 227) requires before sending or calling. RIDE does not send a text message or make a marketing phone call today.

13 · International data transfersInternational data transfers

During Phase 1, RIDE's Service Providers are United States companies, and RIDE does not expect information to leave the United States. If a Phase 2 vendor processes information outside the United States, RIDE will update this Policy to describe the transfer and the safeguard RIDE applies to it before that transfer begins.

14 · Changes to this PolicyChanges to this Policy

RIDE keeps the date at the top of this Policy current. If RIDE makes a material change affecting information RIDE already holds, RIDE will email every waitlist participant before the change takes effect.

15 · Contact usContact us

Email privacy@ridesharecooperative.com with a question about this Policy or a request described in Section 8. During Phase 1, RIDE answers this address personally.