Privacy Policy

Effective: 2026-10-08

Searching the directory

You do not need an account to search RoadService.app, and we do not ask a searcher for a name, phone number, or email. If you choose “use my location”, your device location is used in your browser to sort and filter nearby providers; the search URL carries rounded coordinates rather than a precise position, and we do not track your location in the background. You can search by city, state, or ZIP code instead.

Along-route search and saved contacts

Along-route search sends the origin, destination, optional current location, truck dimensions, and corridor setting to our server only to calculate that request. We do not save route coordinates or place them in the page URL. If route calculation is unavailable, we offer an explicit point-radius search instead of substituting a car route.

If you save a provider for offline use, the contact is stored locally in that browser or installed app. It is not added to a RoadService account or synchronized by RoadService. You can remove saved contacts from the app or clear them using your browser's site-data controls. The offline cache does not intentionally store search locations, route requests, or account data.

Business accounts

Existing-listing requests begin with manual review. Approved shop owners and their authorized team members use a Business Hub account to manage an approved listing. For those accounts we collect an email address, a name, the business information the owner chooses to publish, and the records needed to process a review, verification decision, and placement subscription. Public listing fields are, by definition, public. Owner email addresses, internal notes, verification records, and billing identifiers are not published in the directory.

How we use it

Directory data is used to run the public directory and to operate the Business Hub. We do not sell data or share it with advertisers, and we do not pass a searcher's contact details to a listed business — when you call a shop, you are calling that shop directly.

Provider interactions and reporting

We record limited directory events such as a sponsored-card impression, profile view, tap-to-call click, directions click, placement, and promotion interaction. These records identify the public listing, placement when applicable, page surface, event type, and time. They do not include the provider's phone number, a searcher's phone number, or the searcher's location. Providers see aggregate reporting; a tap-to-call click is not represented as a connected call, lead, repair, or revenue.

Listing reports and appeals

If you submit a listing problem or appeal, we retain the listing reference, reason, details you provide, submission time, and private review history. An owner appeal also records the authorized owner account; administrator decisions record the reviewing account. These records are available through restricted review controls and are not published or shared with the listed provider automatically. Include only relevant details, without passwords, payment information, or precise roadside coordinates. A report reference does not prove identity or grant access to a private report. We retain these records for review and audit; this workflow does not have an automatic deletion schedule. Privacy requests use the contact below.

Near and route search measurement

We record coarse first-party signals when a near or along-route search is submitted, shows an empty or nonempty first result page, or displays a categorized error. These records contain only the search-control context, service category, stage or error category, server time, and a limited bot classification. They contain no raw search text, locations, route details, provider identities, phone numbers, visitor identifiers, or attempt identifiers. They are separate aggregate counts; they do not establish unique people, completed calls, or jobs.

This measurement uses no browser storage or retry queue, sends no cookies or referring URL, and respects Global Privacy Control and Do Not Track signals for this pipeline. It stays within our existing first-party storage and is not forwarded to a new analytics service. Missing signals from privacy controls, blocked transport, or unavailable measurement are not treated as zero demand. Other analytics described below have their own controls.

Public directory activity

When this feature is enabled, a rendered search may increment a daily counter containing only the canonical city, state, and service category. The counter does not contain a person, account, device, provider, placement, phone number, raw search text, or coordinates. A city-and-service total can appear publicly only after the UTC day has been closed for another 24 hours and at least five searches have been combined. Sponsored placement cannot affect this feed.

Third-party place information

When the Google ratings feature is enabled, our server may use a listing's Google Place ID to request its current rating, review count, Google Maps link, and attribution from Google Places. RoadService.app does not use stored historical rating aggregates as a fallback. Opening a Google Maps source link takes you to Google, whose privacy policy and terms apply.

Website analytics

Our public website uses Vercel Web Analytics, provided by Vercel Inc. as our hosting and analytics service provider, to measure site use and help us improve usefulness, reliability, and security. For a page view, Vercel may process the page path or route, hostname, filtered URL query parameters, event timestamp, referring page, coarse location (country, region, and city), browser and version, operating system and version, device type, and analytics script version. The analytics location dimension is inferred from the network request; it is not a precise GPS reading collected by the analytics script.

Vercel Web Analytics does not use cookies. Vercel uses a hash generated from an incoming request to estimate daily unique visitors; Vercel states that the hash cannot track a visitor across websites or days and is reset after 24 hours. Vercel documents these analytics data points as anonymous and used for aggregate measurements rather than being associated with an identified RoadService user or an IP address.

We retain aggregate analytics only as needed to operate, secure, and improve the site, subject to our Vercel account settings, Vercel's service terms, and applicable law; we do not state a fixed retention period for those aggregate records. You can block the analytics script with browser or content-blocking controls without losing access to the public directory. For questions or requests concerning analytics data, contact privacy@roadservice.app. You can also read Vercel's Web Analytics privacy and compliance documentation.

Text messages

If a business-account holder opts in to RoadService.app text messages, we use that phone number and the messaging preferences to send account, listing, and billing notices only. We retain delivery status and opt-out records so we can honor your choices and diagnose delivery failures. SMS consent and phone numbers collected for messaging are not sold, rented, or shared with third parties for their own marketing. We share them only with service providers that deliver messages on our behalf or when required by law.

You can opt out at any time by replying STOP or by disabling SMS in your business profile. Reply HELP for help or contact privacy@roadservice.app. Message and data rates may apply; message frequency varies.

Payments

RoadService.app does not process payment for repair work. You pay the service provider directly, on whatever terms you agree with that provider.

The only payments we handle are optional placement plans a business owner buys in the Business Hub. New advertising purchases are monthly at launch. Existing annual subscriptions continue on their current billing terms and can be managed in Business Hub. Those are processed by Stripe. We retain the subscription and transaction identifiers, plan, billing interval, status, amounts, refunds, and dispute records needed to run billing and accounting. RoadService.app does not store full card numbers.

Retention

Public directory records are retained while a business is listed. Account, review, verification, billing, and audit records may also be retained where needed to operate the service, prevent fraud, resolve disputes, or meet legal obligations. Retention depends on the record and the applicable service settings and requirements. You may request deletion by emailing privacy@roadservice.app; some records may need to be retained for those purposes.

Security

We use HTTPS and account access controls to protect the service. Business-account and administrative actions require authorization, and access to private records is restricted by the application and database controls used for those records.

Children

RoadService.app is intended for commercial drivers, fleets, and business owners. We do not knowingly collect data from anyone under 18.

Your rights (California / GDPR)

You can request a copy of your data, correction of inaccuracies, or deletion by contacting privacy@roadservice.app. Requests are subject to the requirements and retention obligations that apply to them.

Changes

Material changes are posted here. Any additional notice required by applicable law will also apply.

Contact

privacy@roadservice.app · Albert Kuminhachmann, operating Roadservice.app · operations@roadservice.app · Directory support (listings & billing): 1-561-726-3111