1. Overview
This Privacy Policy explains how RidePlug ("RidePlug," "we," "us," or "our") collects, uses, discloses, and protects information when you use the RidePlug mobile application and related services (the "Service"). It should be read together with our Terms and Conditions.
2. Information We Collect
2.1 Information You Provide
- Account information: name, email address, phone number, password, and profile photo.
- Driver compliance information: driver's license details, proof of insurance, vehicle identification number (VIN), vehicle registration, and vehicle inspection photos, submitted for verification before you can publish trips. Full plate numbers are treated as confidential and are only shared with a Rider once their seat on that Driver's trip is paid and confirmed. VINs remain confidential and are never shared with Riders.
- Trip and booking content: pickup/drop-off addresses, departure times, party size, and cargo details.
- Payment information: RidePlug uses Stripe to process payments. RidePlug does not receive or store your full card number; Stripe collects and processes that information directly under its own privacy policy.
- Support and safety content: messages you send to support, incident reports, and SOS activations.
- Ratings and reviews you submit about a completed trip.
2.2 Information Collected Automatically
- Location data: with your permission, we collect device location to power trip search, pickup-point guidance, and in-trip tracking. For Drivers, location is also captured at the moment a rider is marked a no-show before a trip starts, to record that the Driver was at the pickup point; that location is retained with the no-show record (see Section 5) so it can be reviewed if a Rider disputes the fee. You can disable location permissions in your device settings, though this will limit core functionality.
- Device and usage data: device model, operating system version, app version, IP address, crash logs, and in-app events (e.g., searches, bookings, screens viewed), collected via Firebase Analytics.
- Push notification tokens: used to deliver trip reminders, booking updates, and confirmations via Firebase Cloud Messaging / Apple Push Notification service.
2.3 Information From Third Parties
- Payment status and limited transaction metadata from Stripe (e.g., authorization/capture status), used to reconcile trip payments.
- Map and routing data from our mapping provider based on addresses you enter.
3. How We Use Information
We use the information above to:
- Operate the Service: match Riders and Drivers, compute trip pricing, and manage trip capacity;
- Process payments, authorizations, captures, refunds, and cancellation/no-show fees;
- Verify Driver identity, vehicle, and insurance compliance before allowing trips to be published;
- Send trip reminders, safety alerts, and service notifications;
- Provide customer support and investigate incident reports;
- Maintain safety and trust, including fraud prevention and enforcement of our Terms;
- Analyze usage to improve the Service (e.g., search relevance, booking flow, reliability);
- Comply with legal, tax, and regulatory obligations.
We do not sell your personal information.
4. How We Share Information
- Between Riders and Drivers: to complete a trip, we share the information necessary for the other party to identify and meet you — e.g., a Rider's pickup location and party size are shared with the matched Driver; a Driver's name, verified vehicle details, and (once paid) plate number are shared with the matched Rider. Full compliance documents (license, insurance, VIN) are never shared with Riders.
- Service providers: we share information with vendors who help us operate the Service, including:
- Stripe (payment processing),
- Google Firebase / Google Cloud (authentication, database, file storage, push notifications, analytics, and backend functions),
- Mapping/geocoding providers (route and address resolution),
- Push notification services (Apple Push Notification service).
These providers are authorized to use your information only as necessary to provide services to RidePlug.
- Legal and safety disclosures: we may disclose information to comply with law, respond to lawful requests, protect the rights and safety of RidePlug, our Users, or the public, or investigate suspected fraud or violations of our Terms.
- Business transfers: if RidePlug is involved in a merger, acquisition, or asset sale, information may be transferred as part of that transaction, subject to this Policy or a successor policy.
5. Data Retention
We retain personal information for as long as needed to provide the Service, comply with legal and tax obligations (including payment and dispute records), resolve disputes, and enforce our agreements. Payment ledger and compliance records (e.g., driver verification history) are retained longer than routine account data to satisfy audit and regulatory requirements. When information is no longer needed for these purposes, we delete or anonymize it.
6. Data Security
We use administrative, technical, and physical safeguards designed to protect your information, including encryption in transit, access controls on backend systems, and confidential handling of sensitive compliance documents (driver license, insurance, VIN, plate number). No system is completely secure, and we cannot guarantee absolute security.
7. Children's Privacy
The Service is not directed to individuals under 18, and we do not knowingly collect personal information from children. If we learn we have collected information from someone under 18, we will delete it.
8. Your Privacy Rights
Depending on where you live, you may have rights to access, correct, delete, or receive a copy of your personal information, and to object to or restrict certain processing (for example, under the EU/UK GDPR or the California Consumer Privacy Act). To exercise these rights, contact us at admin@rideplugapp.com. We will verify your request and respond within the time required by applicable law. You also have the right to lodge a complaint with your local data protection authority, where applicable.
9. International Data Transfers
RidePlug's service providers, including Firebase/Google Cloud and Stripe, may process and store information in the United States and other countries. Where required, we rely on appropriate safeguards for cross-border transfers of personal information.
10. Location Data
Location permissions can be managed at any time in your device settings. Disabling location access will limit or disable trip search, pickup guidance, and live trip tracking, but will not prevent you from using other parts of the Service. A Driver's location at the moment of marking a pre-start no-show is a separate, narrower use: it is recorded only for that action, attached to the no-show record as a Driver attestation of presence, and is not independently verified in real time. It is retained for as long as the associated payment/dispute record is retained (see Section 5).
11. Marketing and Notifications
We send trip-related notifications (reminders, booking updates, confirmations) as part of the Service; these cannot be fully disabled while you have active trips, as they are necessary for the Service to function. You can manage optional marketing communications and general push notification permissions in your device or in-app settings.
12. Waitlist and Website
If you join our pre-launch waitlist at rideplugapp.com, we collect your email address, city, and whether you're interested in signing up as a driver. We use this only to notify you when RidePlug launches in your area and to plan our rollout by city — we do not share or sell it. You can have it removed at any time by emailing admin@rideplugapp.com.
13. Changes to This Policy
We may update this Privacy Policy from time to time. Material changes will be communicated through the app or by email. Your continued use of the Service after changes take effect constitutes acceptance of the revised Policy.
14. Contact Us
Questions about this Privacy Policy or requests regarding your personal information can be directed to admin@rideplugapp.com.