Skip to content
Summary: We collect information needed to operate RideFresh, connect drivers and vendors, process requested services, and protect the platform. We do not sell personal information. Text-message consent is optional and is not required to purchase or use the Service.
01

Information We Collect

We collect account, professional-driver eligibility, vehicle-type, service/check-in and support information you provide. Phone numbers are optional for email-based driver signup; vendors may provide business contact details. Optional uploads include profile and vendor business images. Account/session identifiers, notification tokens when enabled, and diagnostic events support operation and security. Stripe processes card entry; handling payment details through a provider is still part of the service's data processing.

02

How We Use Information

We use information to operate car-wash discovery and requests for working rideshare, delivery, taxi, black-car/limo and fleet drivers, display vendor-funded offers with their terms, maintain service history, process authorized payments, respond to requests and prevent abuse. New RideFresh-funded rewards/referrals are inactive and credit redemption is paused; historical records remain protected. Personally owned vehicles used for eligible work are welcome.

03

When We Share Information

We may share information with service providers that help us operate the Service, including payment, hosting, communications, analytics, and support providers; with partner vendors when needed to provide a requested service; and when required by law or necessary to protect rights, safety, or the integrity of the Service. Separately, foreground location can trigger conditional approach or arrival notices to partner stations, as described under Location Collection. These notices can include a driver account identifier, approach or arrival status, and distance, even before a service request or check-in. Providers may process information under their own terms and privacy policies.

04

Service Providers and Permissions

Stripe processes payments; Mapbox supports maps and station discovery; Sentry supports diagnostics; Expo and platform services support push delivery when enabled. Authentication providers, including Clerk for configured web sign-in, and email and hosting providers process information for configured features. Provider SDK practices and permissions also apply. QR camera capture and optional image uploads are distinct features. Email-based signup and recovery do not require SMS. No audio-recording feature is implemented; current native configuration blocks microphone permission.

05

Location Collection

Check-in can use a one-time location reading or supported temporary station presence proof. Raw check-in coordinates are processed transiently rather than written to check-in or fraud records; derived check-in proximity results and available distance measurements are retained as fraud and security evidence. Separately, when a driver is signed in with location permission, the native app sends repeated foreground location updates, including coordinates and available heading, speed and accuracy. RideFresh stores the latest driver position and makes live location information available to authorized RideFresh administrators. The watcher pauses in the background and stops on sign-out; it does not collect background location. Foreground updates also generate stored proximity-event records linking a driver account identifier, station, event type, and distance. Conditional approach or arrival notices to partner stations can include a driver account identifier, approach or arrival status, and distance. Current approach and arrival thresholds are about 500 and 150 meters, subject to event eligibility and notification controls. Notices can occur before a service request or check-in, without a completed service request. These derived notices are distinct from raw coordinates and check-in records; they do not confirm check-in, staff acceptance, payment, or completed service. Mapbox processing also depends on permissions and configuration. This is not a claim that all location data is transient or used only at check-in.

06

Retention and Deletion

You may request deletion using Account > Delete My Account, the Delete Account page or Connect@RideFresh.co. Authorized in-app closure records the request, deactivates access and revokes sessions. It does not immediately erase all personal data. Historical transactions, entitlements, fraud, dispute and audit evidence may remain protected; final disposal requires retention and hold checks. A web request is not confirmation of completed erasure. Contact us for the status of a verified request.

07

Your Choices

You may update information through available account settings, unsubscribe from non-essential email communications, opt out of promotional text messages by replying STOP, and request access, correction, or deletion by contacting us. We may need to verify a request before acting on it.

08

Security and Third Parties

We use reasonable administrative, technical, and organizational safeguards, but no method of transmission or storage is completely secure. The Service may link to third-party services, including payment providers and partner locations; their practices are governed by their own privacy notices.

09

Contact and Policy Updates

Questions about privacy should be directed to Connect@RideFresh.co. RideFresh Solutions LLC, Long Island, New York. We may update this Privacy Policy by posting a revised version with a new effective date. Material changes will be communicated as required by applicable law.