Privacy Policy
RideLocal, Inc., operating as MyRideLocal. This is the current policy for https://myridelocal.com and the MyRideLocal trip SMS program.
SMS Privacy — MyRideLocal Trip Texts
RideLocal, Inc., operating as MyRideLocal, collects your mobile phone number, phone-verification status, SMS consent and opt-out records, message content, and delivery or routing information. We use this information to record your messaging preference, relay trip-related conversations between guests, hosts and support, deliver messages, route replies, and provide customer support. We use communications service providers, including Twilio, to process and deliver these messages on our behalf.
We do not sell or share your SMS opt-in data or personal information with third parties for marketing purposes.
We do not share, sell, rent, or provide your mobile phone number or messaging consent data to third parties, affiliates, or lead generators for marketing or promotional purposes. SMS consent applies only to the MyRideLocal trip messaging program operated by RideLocal, Inc.; it is not transferred to another business or sender.
All other data-sharing categories in this policy exclude text messaging originator opt-in data and consent. We share the messaging information needed for delivery only with contracted communications providers, including Twilio, that process it on our behalf, subject to confidentiality and purpose restrictions, or when required by law. Sharing trip conversation content with the participants in your trip does not transfer SMS consent or authorize them to market to your phone number.
Message frequency varies with trip activity. Message and data rates may apply. Reply STOP to opt out or HELP for help. For assistance, use your MyRideLocal trip inbox or call (318) 687-9500. For program details, see our Terms of Service.
Louisiana and Texas Launch
Version 0.6 | Revised October 6, 2026 | Published October 6, 2026 | Effective October 6, 2026
RideLocal, Inc. | 7077 Jewella Avenue, Shreveport, Louisiana 71108
RideLocal Privacy Policy
RideLocal, Inc., operating as MyRideLocal, provides the Services described in this Privacy Policy. This October 6, 2026 update clarifies our optional trip SMS program.
1. Scope and Who We Are
This Privacy Policy explains how RideLocal, Inc. (“RideLocal,” “we,” “us,” or “our”) collects, uses, discloses, retains, and protects personal data when individuals use our websites, applications, account tools, communications, vehicle marketplace, payment and booking features, support, and related services (collectively, the “Services”). It applies to Guests, Hosts, Approved Drivers, co-hosts, applicants, website visitors, and other individuals whose personal data we process. It does not govern an independent third party’s practices, including an insurer, Host, payment processor, identity-verification provider, or linked website, when that party acts under its own privacy notice.
RideLocal is the controller of personal data for the purposes described here except when we process information solely on behalf of another party. RideLocal, Inc. may be contacted at 7077 Jewella Avenue, Shreveport, Louisiana 71108, Attn: Privacy; by email at midsouthacceptancecorp@gmail.com; or by telephone at (318) 687-9500. Privacy requests may also be submitted through the Privacy Request form provided in the Services.
2. Personal Data We Collect
The information collected depends on the person’s role and activity. We may collect the following categories:
Category
Examples
Typical source
Identity and account
Name, date of birth, age, account credentials, signature, profile photo, language and preferences; no facial recognition or biometric matching
You; identity provider
Contact information
Postal address, email address, telephone number, emergency contact
You
License and eligibility
Driver’s license image, number, issuing jurisdiction, expiration, class, verification result, driving eligibility and related records
You; verification or motor-vehicle-record provider
Insurance and protection
Insurer or protection provider, policy or certificate number, coverage type, limits, effective dates, verification result, selected third-party product and claim status
You; insurer; coverage provider; administrator
Vehicle and Host records
VIN, plate, title/authority, registration, lien or lease status, recall status, inspection, maintenance, listing, pricing, availability and photos
Host; public or verification sources
Booking and transaction
Searches, requests, approvals, Trip Agreement, dates, locations, charges, refunds, payouts, taxes, deposits, tolls, tickets and disputes
You; Host; processors
Payment and tax
Payment token, card brand and last digits, billing information, bank payout details, taxpayer identifiers and forms
You; payment processor
Trip and vehicle data
Pickup/return records, mileage, fuel or charge, condition photos, incident evidence, and vehicle telematics or precise location when enabled
You; Host; vehicle or telematics provider
Communications and content
Messages, support contacts, calls where recorded with notice, reviews, ratings, reports, survey responses and uploaded content
You; other users
Device and usage
IP address, device and browser identifiers, operating system, pages and features used, timestamps, crash logs, security events, cookies and similar technology
Your device; analytics/security provider
Safety, fraud and claims
Identity match result, risk indicators, incident and police reports, witness and third-party information, estimates, invoices, claims and recovery records
Users; vendors; insurers; authorities
Inferences
Fraud, eligibility, support, ranking, reliability or service-preference inferences derived from other data
RideLocal; vendors
We generally do not need Social Security numbers from Guests. We may collect taxpayer identification information from Hosts when legally required, using restricted access and appropriate providers. Please do not place sensitive information in public listings, reviews, or ordinary messages.
3. Sensitive Data and Location; No Face Matching
Driver’s license information, precise geolocation, financial credentials, and insurance records may be considered sensitive or specially regulated. RideLocal processes sensitive data only when reasonably necessary for the Services, safety, fraud prevention, claims, legal compliance, or another disclosed purpose, and with consent where law requires.
Trip location may be collected from check-in/out, delivery, roadside, telematics, recovery, fraud, or safety tools. Precise location will be limited to the period and purpose disclosed in the app, except records may be retained for a claim, safety event, legal obligation, or dispute. Hosts must disclose lawful vehicle tracking and may not use hidden cameras or prohibited surveillance.
RideLocal does not use facial recognition, face matching, voiceprints, fingerprints, retina or iris scans, face geometry templates, or other biometric identifiers to identify users. RideLocal may collect ordinary profile, license, vehicle-condition, and incident photographs, but does not extract biometric templates from them. If RideLocal proposes biometric identification in the future, it will update its practices only after legal review, advance notice, separate consent where required, appropriate security, and a compliant destruction schedule.
4. How We Collect Data
directly from users, forms, uploads, messages, Trip activity, reviews and support interactions;
automatically from devices, cookies, security logs, app permissions, and vehicle or telematics integrations;
from Hosts, Guests, Approved Drivers, witnesses and other marketplace participants;
from payment, identity, license, motor-vehicle-record, insurance, coverage, fraud, analytics, support and claims providers; and
from public records, recall sources, government agencies, law enforcement, insurers and other lawful third parties.
5. Why We Use Personal Data
provide accounts, listings, search, booking, messaging, Trip Agreements, check-in/out, support, reviews and marketplace features;
qualify drivers, verify identity, license, insurance, vehicle authority, registration and recalls, and enforce age and eligibility rules;
process charges, authorization holds, refunds, payouts, taxes, tolls, tickets and accounting records;
issue or facilitate third-party insurance or protection when selected, verify coverage, administer roadside support, and investigate and resolve incidents and claims;
protect users, vehicles and the Services; detect fraud, theft, abuse, prohibited use, security threats and policy violations;
communicate about requests, approvals, Trips, payments, coverage, safety, support and policy changes;
operate, troubleshoot, analyze, secure and improve the Services, including measuring feature performance and service quality;
comply with laws, lawful process, insurance and car-sharing requirements, tax obligations, recordkeeping, audits and enforcement; and
establish, exercise or defend legal rights and complete a merger, financing, reorganization or business transfer subject to appropriate protections.
Where applicable law requires a legal basis, we rely on performance of a contract, compliance with law, legitimate interests that do not override individual rights, protection of vital interests, or consent. Consent may be withdrawn prospectively, but withdrawal does not affect prior lawful processing and may prevent use of a feature that requires the data.
6. How We Disclose Personal Data
The following disclosures are limited to the stated service purposes. They do not authorize sharing your personal information for third-party marketing. All categories exclude text messaging originator opt-in data and consent, except the contracted messaging providers and legal disclosures described in SMS Privacy above.
Hosts and Guests. We share booking identity, profile, communications, Trip terms, verification status, and information reasonably necessary to approve and perform a Trip. Hosts should inspect the original license at handoff but ordinarily receive only RideLocal’s verification status—not a retained credential copy. We may share additional evidence when required for a claim, legal obligation, or safety matter.
Approved Drivers, co-hosts and authorized business personnel, according to account permissions and Trip roles.
Service providers and processors supporting cloud hosting, communications, identity/license verification, payments, fraud prevention, analytics, customer service, background or motor-vehicle checks, records, tax, security and document storage, subject to contractual restrictions.
Approved third-party insurers, producers, coverage or protection providers, roadside providers, claims administrators, appraisers, repair facilities and recovery vendors when a user requests coverage or a Trip, incident, claim or recovery requires it. Those parties may act under their own privacy notices.
Payment processors and financial institutions for charges, holds, payouts, refunds, chargebacks, fraud and compliance. RideLocal should not store complete card numbers if the processor provides tokenized processing.
Government agencies, courts, law enforcement, regulators, tax authorities, insurers and other parties when required or permitted by law, valid legal process, safety, fraud investigation or protection of rights.
Professional advisers, auditors, financing sources and transaction counterparties under confidentiality protections; and
Other persons at the user’s direction or with consent.
RideLocal does not sell personal data for money and does not process personal data for targeted advertising at launch. Any future change to non-SMS advertising practices requires advance notice and any legally required preference controls. It will not permit the sale or sharing of mobile phone numbers, SMS opt-in data, or messaging consent for marketing or promotional purposes.
SMS data exception: Notwithstanding any other provision of this policy, we do not share mobile information with third parties or affiliates for marketing or promotional purposes. SMS opt-in data and consent are not sold, transferred, or shared with third parties for their own purposes. We may disclose messaging information only to contracted service providers, including Twilio, to operate and support this messaging program on our behalf, or when required by law. The general disclosure, business-transfer, analytics, and future advertising provisions in this policy do not authorize marketing use or transfer of SMS consent.
7. Cookies, Analytics, and Similar Technologies
RideLocal may use essential cookies and local storage for login, security, preferences, booking continuity and payment flow. We may use limited analytics to understand use, reliability and performance. If RideLocal deploys nonessential advertising or cross-context tracking technologies, it will provide legally required notice and preference controls before activation. Browser settings may block some technologies but can impair functionality. A browser “Do Not Track” signal is not uniformly defined; RideLocal will honor legally recognized universal opt-out signals when applicable to processing subject to such a requirement.
8. Automated Processing
RideLocal or its providers may use automated signals to detect fraud, assess identity or eligibility, prioritize support, rank search results, or flag transactions for review. RideLocal does not intend at launch to make decisions based solely on automated processing that produce legal or similarly significant effects without human review where required. Users may contact RideLocal to contest an eligibility decision and request appropriate review, subject to fraud, security and legal limitations.
9. Retention
RideLocal uses the retention schedule below. A longer period applies only when reasonably necessary for an active claim, chargeback, tax audit, fraud or safety investigation, litigation hold, court order, insurance requirement, or another legal obligation. When retention expires, RideLocal will delete, deidentify, or securely destroy the data, subject to ordinary backup rotation. These periods are conservative business and compliance choices; not every category is legally required to be kept for the full stated period.
Data group
RideLocal retention period
Account profile and contact data
While the account is open and 7 years after closure; inactive unverified applications: 2 years
License image
Delete 90 days after verification or Trip completion, whichever is later, unless needed for an active claim, fraud review, legal hold, or law
License qualification record
Keep name, address, license number, issuing jurisdiction, expiration and verification result for 7 years after the last related Trip
Insurance and protection record
7 years after the related Trip or final claim resolution, whichever is later
Trip Agreement, times, fees and Host revenue
7 years after Trip completion
Condition photos, messages and incident evidence
7 years after Trip completion; if a claim exists, 7 years after final resolution
Claims, damage, toll, ticket and dispute records
7 years after final resolution
Payment and payout records
Payment token and limited metadata for 7 years; RideLocal does not retain full card number or security code
Tax records and taxpayer forms
7 years after the end of the applicable tax year
Precise location and detailed telematics
2 years after Trip completion; 7 years when incorporated into an incident, claim, theft, fraud, or legal record
Reviews and public listing content
While published and up to 3 years after removal; longer if needed for enforcement or a dispute
Security logs and routine analytics
12 months; up to 7 years if preserved as part of a security or fraud investigation
Customer-support records not tied to a Trip
3 years after the matter closes
Biometric identifiers
Not collected or used
Backups
Removed through ordinary encrypted backup rotation within 90 days, unless subject to legal hold
10. Security and Incident Response
RideLocal uses reasonable administrative, technical and physical safeguards appropriate to the nature of the information, including access controls, encryption in transit and where appropriate at rest, logging, vendor controls, staff confidentiality, secure development, incident response and data minimization. No system is completely secure. Users should use unique passwords, protect devices, and promptly report suspected account compromise.
RideLocal will investigate suspected security incidents and provide notices to affected individuals, regulators or others as required by applicable law. Louisiana requires reasonable security and secure destruction and, when its standard is met, breach notice without unreasonable delay and generally no later than 60 days after discovery, subject to statutory exceptions and permitted delay.
11. Your Privacy Rights and Choices
Subject to applicable law, verification, exceptions and RideLocal’s ability to authenticate the requester, an individual may request to:
confirm whether RideLocal processes personal data and access that data;
correct inaccuracies;
delete personal data provided by or obtained about the individual;
obtain a portable copy of qualifying data;
opt out of sale, targeted advertising, or qualifying profiling if RideLocal engages in those activities;
withdraw consent for consent-based processing; and
appeal RideLocal’s denial of a privacy request.
Submit a request through the Privacy Request form in the Services, email midsouthacceptancecorp@gmail.com with “Privacy Request” in the subject line, call (318) 687-9500, or mail RideLocal, Inc., Attn: Privacy Request, 7077 Jewella Avenue, Shreveport, Louisiana 71108. State the right requested and the account email or telephone number. RideLocal may request information reasonably necessary to authenticate the request and may deny a request that cannot be authenticated. An authorized agent must provide proof of authority, and RideLocal may verify directly with the individual.
RideLocal will respond within the period required by applicable law and explain any denial and appeal method. RideLocal will not discriminate against a person for exercising privacy rights, but some data is necessary to provide accounts, verify eligibility, process Trips, satisfy law, prevent fraud, resolve claims or maintain security. RideLocal may retain or withhold information where an exception applies, including another person’s privacy, legal privilege, security, fraud prevention, tax, insurance, claims, or legal obligations.
12. Communications Choices
Account, booking, Trip, payment, safety, support and policy notices may be provided through the Services and other applicable channels. Trip SMS messaging is optional, and consent is not required to rent. Users can disable trip SMS in their inbox preferences or reply STOP to opt out. Users may unsubscribe from marketing email using its unsubscribe link.
For SMS data collection, use, non-sharing protections, opt-out instructions, and support, see SMS Privacy — MyRideLocal Trip Texts above. Those protections apply throughout this policy.