Neighborly Rideshare Privacy Policy

Effective date: July 25, 2026

Neighborly Rideshare Inc., doing business as Neighborly Rideshare ("Neighborly Rideshare," "we," "us," or "our"), respects your privacy. This Privacy Policy explains how we collect, use, disclose, retain, and protect personal information when you use:

  • the Neighborly Rideshare Rider application;

  • the Neighborly Driver application;

  • our websites, including neighborlyrideshare.com;

  • our ride-request, scheduling, dispatch, safety, payment, support, and administrative services; and

  • other services that link to this Privacy Policy.

Together, these are the "Services."

Neighborly Rideshare facilitates ride requests and connects riders with authorized drivers. Some Services may be available only in selected service areas or to approved participants.

1. Contact Us

Neighborly Rideshare Inc.

501 N Main St, Suite 7 Bloomington, Illinois 61701 United States

Email: info@neighborlyrideshare.com Telephone: (833) 443-2863

Privacy requests: info@neighborlyrideshare.com

Account deletion: https://www.neighborlyrideshare.com/account-deletion

2. Scope

This Privacy Policy applies to personal information processed through the Services. It does not govern independent websites, applications, or services that do not link to this Policy.

Drivers may be independent service providers. This Policy describes the information Neighborly Rideshare processes through its platform. It does not replace any separate Driver Agreement or legally required driver disclosure.

3. Information We Collect

The information we collect depends on whether you use the Services as a rider, driver, administrator, prospective user, website visitor, or support contact.

A. Account and profile information

We may collect:

  • name;

  • email address;

  • mobile telephone number;

  • date of birth or age eligibility information;

  • profile photograph;

  • password-protected account and authentication information;

  • multi-factor authentication enrollment status;

  • selected service area, language, accessibility, notification, and app preferences;

  • saved pickup, stop, and drop-off locations; and

  • account role, status, and related identifiers.

Passwords and authentication tokens are handled through our authentication provider and are not intended to be visible to Neighborly Rideshare staff.

B. Rider and ride-request information

When a rider requests or manages a ride, we may collect:

  • pickup, intermediate-stop, return-trip, and destination addresses;

  • requested date and time;

  • selected ride service and ride options;

  • recurring RideWeekly itinerary information;

  • passenger count; whether the ride is for another person;

  • limited passenger contact information when dispatch alerts are requested;

  • luggage, pet, child-safety-seat, accessibility, or assistance needs;

  • driver assignment, estimated arrival time, safety PIN, and ride status;

  • wait-time, cancellation, no-show, rescheduling, and trip-event information;

  • fare estimates, discounts, promotion codes, loyalty activity, deposits, charges, tips, refunds, and payment status;

  • ratings, reviews, safety reports, and support communications; and

  • ride history and request history.

Please do not submit medical records, diagnoses, or other health information unless specifically requested and reasonably necessary to provide an accommodation.

C. Driver and vehicle information

For drivers and driver applicants, we may collect:

  • legal and preferred name;

  • contact information and profile photograph;

  • driver account and approval status;

  • vehicle make, model, color, license plate, and decal information;

  • selected service areas and availability;

  • driver location while online or completing assigned rides;

  • accepted, declined, completed, cancelled, and missed assignments;

  • arrival, intermediate-stop, wait-time, and ride-completion events;

  • rider ratings, driver notes, safety reports, and operational performance;

  • earnings, tips, fee allocations, payout preferences, and payout status;

  • driver documents, eligibility information, and information required for onboarding, safety review, tax, insurance, or legal compliance; and

  • background-screening information or results when legally permitted and operationally required.

Additional notices may apply when background checks, identity verification, or tax reporting are performed by a separate provider.

D. Payment information

We use Stripe to process supported payments and save payment methods. Stripe may collect payment-card, bank, wallet, billing, identity, fraud-prevention, and transaction information under its own privacy terms.

Neighborly Rideshare generally receives payment tokens or customer identifiers, card brand, last four digits, transaction status, amount, refund status, and related metadata. We do not intend to store complete card numbers or card security codes on our servers.

E. Location information

Depending on your role, settings, device permissions, and use of the Services, we may collect:

  • approximate location;

  • precise foreground location;

  • pickup and destination location;

  • driver location while available for requests;

  • driver background location during an active operational period;

  • timestamps, accuracy information, and route progress; and

  • location associated with safety, dispatch, arrival, stop, wait-time, or ride events.

Rider location access is generally used while the Rider App is in use to help confirm pickup, display ride progress, and support maps. Driver location may be used while the Driver App is in use and, after a prominent disclosure and permission, in the background when the driver is online, assigned to a ride, or actively completing a ride.

F. Device, app, and network information

We may collect:

  • app name, version, build number, and environment;

  • device type, model, operating system, and language;

  • IP address and general network information;

  • app installation identifiers;

  • push-notification token and notification-delivery status;

  • camera, notification, and location permission status;

  • login, session, synchronization, and connectivity events; and

  • security, fraud, and abuse signals.

G. Diagnostics, crash reports, and analytics

We may collect crash reports, application errors, performance data, screen or workflow context, recent non-sensitive events, and device metadata to diagnose problems and improve the Services. Crash and diagnostic reports may include an internal user identifier or ride-request identifier when needed to investigate an issue.

We design diagnostic reports to exclude passwords, authentication tokens, complete payment information, secret keys, and unnecessary precise location history.

H. Feedback, support, and communications

We may collect:

  • support requests and correspondence;

  • beta feedback, issue categories, severity, and internal resolution notes;

  • screenshots or attachments submitted by the user;

  • call and text-message metadata and content where legally permitted;

  • communication preferences; and

  • records of safety, fraud, dispute, or service investigations.

I. Legal, consent, and audit information

We may retain:

  • acceptance of Terms, Privacy notices, Driver Agreements, or Beta Agreements;

  • document version and content hash;

  • acceptance timestamp, platform, app version, and build;

  • account deletion requests; administrative actions and permission changes; and

  • records needed for compliance, disputes, safety, or fraud prevention.

4. How We Collect Information

We collect information:

  • directly from you;

  • automatically from your device and use of the Services;

  • from another account holder who books a ride for you;

  • from drivers, riders, authorized administrators, or support personnel;

  • from service providers such as Stripe, mapping, authentication, notification, diagnostics, hosting, and communication providers; and

  • from public or legally authorized sources when needed for driver onboarding, fraud prevention, safety, or legal compliance.

5. How We Use Personal Information

We may use personal information to:

  • create, authenticate, secure, and manage accounts;

  • determine role and service eligibility;

  • provide ride requests, native scheduling, recurring schedules, dispatch,   driver matching, intermediate stops, wait timers, and ride-status updates;

  • estimate routes, fares, arrival times, and service availability;

  • display driver progress to an assigned rider and operational personnel;

  • process deposits, fares, fees, tips, refunds, and payouts;

  • provide accessibility accommodations and safety features;

  • send account, ride, driver, payment, security, and support communications;

  • operate push notifications and SMS alerts;

  • prevent duplicate requests, charges, fraud, abuse, and unauthorized access;

  • investigate crashes, technical issues, complaints, incidents, and disputes;

  • administer beta testing and collect feedback;

  • measure service reliability and improve the Services;

  • enforce our agreements and policies;

  • satisfy accounting, tax, insurance, safety, legal, and regulatory duties; and

  • protect users, drivers, Neighborly Rideshare, and the public.

Where applicable, processing may be based on performance of a contract, your consent, our legitimate operational and safety interests, or compliance with law. The applicable legal basis depends on the information, location, and context.

6. Background Location and Live Driver TrackingDriver background location

The Driver App may request permission to access location in the background. Before the operating-system prompt, we intend to explain why the permission is needed and when tracking occurs. Background location is used to:

  • identify available drivers in an enabled service area;

  • route and match drivers with requests;

  • provide estimated arrival information;

  • support pickup, stop, wait-time, destination, and completion events;

  • help assigned riders understand driver progress; and

  • support dispatch, reliability, fraud prevention, and safety.

Tracking should begin only when the driver goes online, accepts an assignment, or enters another clearly identified workflow requiring location. Tracking should stop when the driver goes offline, completes or leaves the applicable workflow, revokes permission, or signs out, subject to technical and safety requirements.

Live driver tracking

After a driver is assigned, the rider may see a map or status display showing the driver's general or precise progress, estimated arrival, vehicle information, last update time, and safety information. Authorized operations personnel may view driver location to dispatch rides, support active trips, and respond to safety concerns.

Live location is not intended to be publicly available or visible to unassigned users.

Location retention

We intend to retain high-frequency precise location only as long as reasonably necessary for active operations, safety, dispute resolution, fraud prevention, and legal obligations. We maintain and periodically review retention practices designed to limit precise location information to the period reasonably necessary for these purposes.

7. Accessibility and Accommodation Information

Riders may provide accessibility, mobility, communication, or assistance preferences to help Neighborly Rideshare and drivers evaluate and fulfill a request. We use this information to:

  • present suitable service options;

  • communicate requested accommodations;

  • identify vehicle or assistance needs;

  • support safe pickup and drop-off; and

  • respond to support or safety concerns.

Accessibility information is shared only with personnel and assigned drivers who reasonably need it for the request, and with providers needed to operate the Services. Users should provide only information necessary for the requested accommodation.

8. Youth Riders

Certain Neighborly Rideshare services may be designed for youth riders. Youth transportation must be requested and managed by an authorized parent, legal guardian, or other authorized adult unless a separate legally reviewed program expressly permits otherwise.

For youth rides, we may collect:

  • the youth rider's name and age or age range;

  • pickup, destination, schedule, and ride history;

  • parent or guardian identity and contact information;

  • emergency, dispatch, and authorized-recipient contacts;

  • accommodation or safety instructions; and

  • consent and authorization records.

We use youth information only to operate, secure, support, and document the authorized ride. We do not knowingly permit a child under 13 to independently create a standard account or consent to this Policy. Any youth transportation program is subject to additional safeguards, including verified adult authorization, age-appropriate disclosures, restricted access, documented retention practices, and legally appropriate parental consent.

9. How We Disclose Personal Information

We may disclose personal information as follows:

A. Riders and drivers

We disclose information necessary to arrange and complete a ride. For example:

  • an assigned driver may receive the rider's first name, pickup, stops, destination, contact or dispatch instructions, ride options, and relevant   accommodation or safety information;

  • a rider may receive the assigned driver's name, profile image, vehicle, license plate, estimated arrival, live progress, and safety PIN information.

B. Service providers

Our service providers may include:

  • Supabase for authentication, database, storage, and realtime services;

  • Stripe for payment processing, saved payment methods, fraud controls, refunds, and related financial services;

  • Google Maps Platform for address search, geocoding, maps, distance,   routing, and estimated travel information;

  • Apple Push Notification service, Firebase Cloud Messaging, and Expo for   app builds, device registration, and push notifications;

  • Sentry for crash reporting, diagnostics, and performance monitoring;

  • Quo/OpenPhone or another approved communication provider for SMS and operational alerts;

  • Netlify and other hosting or infrastructure providers for websites, administrative tools, and server-side functions; and

  • Apple and Google for app distribution, platform security, permissions,   and store services. Each provider processes information under its agreement and privacy terms.

C. Business, legal, and safety disclosures

We may disclose information:

  • to comply with law, legal process, or valid governmental requests;

  • to protect rights, safety, property, or the public;

  • to investigate fraud, misuse, incidents, disputes, or violations;

  • in connection with a merger, financing, reorganization, sale, or transfer of business assets, subject to appropriate safeguards; or

  • with your direction or consent.

10. Sale, Advertising, and Data Brokerage

Neighborly Rideshare does not sell personal information for money and does not use rider or driver personal information for cross-context behavioral advertising. We do not operate as a data broker.

If our practices change, we will update this Policy and provide any legally required choices before the new practice begins.

11. Notifications and Communications

We may send:

  • account and security messages;

  • ride-request, assignment, arrival, schedule, cancellation, and payment updates;

  • safety or support communications;

  • driver opportunity and operational alerts; and

  • service announcements and legally permitted marketing.

Push notifications can generally be controlled in device settings. Operational or transactional communications may still be necessary to provide a requested service. Marketing communications include applicable opt-out instructions.

12. Data Security

We use administrative, technical, and physical safeguards designed to protect personal information. These may include:

  • encrypted network transmission;

  • secure payment tokenization through Stripe;

  • role-based access controls and row-level database policies;

  • multi-factor authentication for privileged roles;

  • secret and credential management;

  • audit logging;

  • restricted administrative access;

  • secure development and deployment practices; and

  • monitoring and incident response.

No system is completely secure. Users should protect account credentials, maintain control of their devices, and notify us promptly of suspected unauthorized access.

13. Data Retention

We retain personal information only as long as reasonably necessary for the purposes described in this Policy, including service delivery, accounting, tax, payment reconciliation, disputes, safety investigations, fraud prevention, contractual obligations, and legal requirements.

Retention depends on the data and context. Our retention practices cover, as applicable:

  • account and profile information;

  • precise and background location;

  • ride requests, ride events, and safety records;

  • transaction, refund, payout, and tax records;

  • driver onboarding and eligibility records;

  • push tokens; diagnostics and crash reports;

  • support and beta feedback;

  • agreement acceptances and audit logs; and

  • deletion requests and legal holds.

When information is no longer required, we delete, de-identify, or anonymize it using reasonable measures, unless retention is required or permitted by law.

14. Account Deletion

Riders and drivers may request permanent deletion of their Neighborly Rideshare accounts by selecting

Delete Account from the account or profile area in the applicable app or by visiting our public account-deletion page:

https://www.neighborlyrideshare.com/account-deletion

The public page is available without signing in and applies to both Rider and Driver accounts. Submitting a website form starts a deletion request; it does not automatically erase an account. We verify that the requester controls the account using a trusted email address or mobile number already associated with the account. We do not ask users to provide passwords or one-time authentication codes to support personnel.

Our standard deletion process is:

  1. The user submits a request in the app or through the public account-deletion form.

  2. Neighborly Rideshare verifies that the requester controls the account.

  3. Active rides, unpaid balances, refunds, disputes, safety matters, fraud reviews, and legal obligations are resolved or reviewed before deletion.

  4. Sign-in access, profile and contact information, saved payment methods, profile photos, push-notification tokens, and other direct identifiers are removed or anonymized.

  5. Limited pseudonymous records may be retained when reasonably necessary for payment reconciliation, fraud prevention, safety, disputes, tax, insurance, accounting, or other legal duties.

  6. Neighborly Rideshare sends confirmation when deletion is complete whenever practical.

We normally complete verified requests within 7 business days. Complex payment, safety, dispute, fraud, or legal matters may require additional time. We will explain material delays when practical and confirm when deletion is complete.

Information generally deleted or de-identified includes:

  • sign-in and authentication access;

  • name, email address, mobile number, and other direct profile identifiers;

  • profile photographs;

  • saved payment-method records maintained by Neighborly Rideshare;

  • push-notification tokens; and

  • other account data that is no longer reasonably necessary.

Information that may be retained in limited or pseudonymous form includes:

  • ride and service history;

  • payment, refund, tip, payout, chargeback, tax, and accounting records;

  • safety, fraud, abuse, and dispute records;

  • agreement acceptance and audit records;

  • records subject to a legal, insurance, or regulatory hold; and

  • the deletion request and completion audit record.

Where complete deletion is not permitted or appropriate, we restrict, minimize, de-identify, or pseudonymize retained information when reasonably possible. Deleting the mobile application from a device does not delete the associated account.

15. Privacy Rights and Choices

Depending on where you live, you may have rights to: request access to personal information; request correction; request deletion; receive a portable copy; restrict or object to certain processing; withdraw consent where processing relies on consent; or appeal a denied privacy request. We may verify identity and authority before completing a request. Authorized agents may be required to provide proof of authority. To submit a privacy request, email info@neighborlyrideshare.com or use the account-deletion page when requesting account deletion. We will not discriminate against a person for exercising an applicable privacy right.

16. Camera, Photos, and Attachments

The apps may request camera or photo-library access when a user chooses to add a profile image, upload a driver document, attach beta feedback, or submit permitted safety or support material. We do not need camera access for ordinary ride requesting. The relevant app should request permission only when the user initiates a feature that needs it.

17. Automated Matching and Administrative Decisions

The Services may use rules and automated processes to identify eligible drivers, prioritize or distribute requests, calculate estimates, detect conflicts, or flag activity for review. Drivers may accept or decline eligible opportunities, and administrators may review or override certain operational decisions where permitted. Automated processing is not intended to make a legally significant decision about a person without appropriate review where such review is required.

18. Children's Privacy

The general Services are not directed to children who independently manage an account. If we learn that a child provided personal information without appropriate adult authorization, we will take reasonable steps to investigate and delete or restrict the information as required. Youth transportation programs are governed by Section 8 and any additional parent or guardian terms.

19. International Use

The Services are currently intended for supported locations in the United States. Information may be processed in the United States and other locations where our service providers operate, subject to applicable safeguards.

20. Third-Party Links and Services T

he Services may link to partner promotions, maps, support pages, or other third-party services. Their privacy practices are governed by their own policies. A link does not mean Neighborly Rideshare controls the third party.

21. Changes to This Policy

We may update this Policy to reflect changes in the Services, law, providers, or data practices. We will post the updated version with a new effective date. When required, we will provide additional notice or request renewed consent. Material changes should be versioned in the legal-document system so acceptance can be recorded when required.

22. Contact

Questions, privacy requests, or concerns may be directed to: Neighborly Rideshare Inc. 501 N Main St, Suite 7 Bloomington, Illinois 61701 Email: info@neighborlyrideshare.com Telephone: (833) 443-2863 For urgent safety concerns, use the support method shown in the app. For an emergency, contact 911 or the appropriate local emergency service.