Last updated: October 26, 2026 | Effective: October 26, 2026
Washington residents: in addition to this Privacy Policy, please read our Consumer Health Data Privacy Policy, which governs "consumer health data" under RCW 19.373.
Open Road records drives and offers social features. This policy covers our apps, website and support.
Our Consumer Health Data Privacy Policy also applies where stated in that policy.
OpenRoad LLC is the controller of your personal data. Our address is 5941 39th Ave SW, Seattle, WA 98136, USA. Our contact is openroad2026@gmail.com.
EU privacy contact and representative: people in the EU can contact us at privacy@openroaddrive.com. Messages there go to Mikita Shylai in Poland, who is being appointed as our EU representative under Article 27 of the GDPR, and to the company. This does not limit your right to contact a supervisory authority.
Drive records can include GPS positions, speed at each point, heading, altitude, accuracy, timestamps, distance, duration, acceleration and other motion readings. They can also include the vehicle, drive name, notes, photos and calculated scores or statistics. Location may be collected in the background while drive recording or enabled driving features are running.
Drives are recorded on your device. When you are signed in, cloud sync is on by default. It uploads a drive summary, route geometry with per-point speeds, approximate area and account identifier. It also uploads an untrimmed raw-readings file, including location, speed and motion samples. Raw files are restricted to your account in the app; authorised operators and infrastructure providers can access server data as described in sections 4 and 5. Optional private iCloud sync is separate.
Cloud storage and social posts are different. The raw-readings file is not shown to other users. A shared post contains a separate route, selected statistics and any content you include. On iOS, Friends is the initial sharing selection. Saving or closing the post-drive screen can apply that selection. You can change the default or choose Private for a drive. Changing a shared drive to Private removes its post, but cannot remove copies other people already saved.
Shared routes normally have their start and end trimmed and privacy-zone areas removed. Controls can change the trim and allow the real start and end to appear on a particular post. These controls do not trim the private raw backup. Route protection reduces exposure; it does not guarantee that a location cannot be inferred.
We collect account and sign-in identifiers, the email or name supplied by your sign-in provider or by you, profile details, vehicle information and photos. We also process friend connections, invitations, blocks, convoy membership, comments, reactions, reports and notification tokens. Some information comes from other users, such as invitations, mentions or abuse reports about your account.
If you join public leaderboards, your profile and ranked driving statistics are visible to other users. Rankings and driving scores are calculated from activity data. Community markers, zones, routes and related attempts or results can be visible to their selected audience.
Live presence can share your exact location with friends or convoy members. Nearby-driver presence has Hidden, Anonymous and Open settings. Anonymous hides your displayed identity, but still exposes an exact position. Open also displays your identity and speed. A name-free location is not necessarily anonymous personal data. iOS public presence starts Hidden. The Android onboarding default has been Anonymous; check your current setting before driving. Privacy zones suppress presence within those zones.
Waves contain sender and recipient identifiers and a timestamp. Notification systems also process device tokens, delivery information and notification preferences.
Profile, vehicle and drive-post photos may be uploaded to our storage. Their visibility depends on the feature and your sharing choices.
Car pictures (Pro). If you ask for a picture of your actual car, the photo you choose is sent to OpenAI, an AI image service, to create a side view of your car. We use the photo only for that. We never ask for your number plate. Someone at Open Road checks the finished picture before it appears. The photo is deleted when you delete your account. This feature is available on iOS from version 5.1. We send you a push notification when your car picture is ready if notifications are allowed.
If you request a missing vehicle model, we retain the request with your account. We export requests to a team computer for processing and use vehicle names or descriptions to generate catalog images with OpenAI or Higgsfield. We do not need your drive history or source photos for those catalog requests.
LiveKit carries real-time voice audio and processes room, participant, connection and authentication information. Open Road does not record calls. No recording does not mean no connection metadata.
We store locations, creator identifiers and related content for markers, zones and reports. Shared community objects may remain available after their creator leaves. We remove account links where appropriate, but a retained location or free-text report can still contain personal information. Private privacy-zone settings are also stored to apply your location controls.
With permission, Open Road reads now-playing information for its music display and controls. Track title and artist are used on the device for this feature.
Android's notification-listener permission supports the now-playing display. It is a broad system permission. Open Road uses it for music information, not to collect your other notifications. You can revoke it in Android Settings.
Motion and activity-recognition signals help detect driving. Location, background-operation and notification permissions support recording and related features. You can change permissions in device settings. Denying location prevents GPS drive recording; denying microphone access prevents voice participation. Optional analytics and car-image generation are not required for basic drive logging.
We receive acquisition or referral information, onboarding answers and progress, and account activity. At signup, we use the connection's IP address to estimate city, region and country and save the approximate place with your account. The signup processing queue temporarily holds the IP address while that lookup is completed. This is separate from GPS and from the country-only team alerts below.
Apple and Google provide purchase and subscription information, including transaction identifiers, plan, price, currency, market, status, trial, renewal and refund events. We link records to accounts to provide access and reconcile purchases.
If you turn off auto-renew or open subscription management, we may ask an optional cancellation question. You can skip it. If you answer, we save your answer and its date with your account, even if analytics is off. For a detected cancellation, we also link it to the subscription episode. We use these links to understand repeat feedback across annual subscription cycles and improve Pro. You can object or ask us to delete your answer at openroad2026@gmail.com.
When you contact support, we receive your email address, message, attachments and any account or diagnostic information needed to investigate.
Where GDPR applies, we use the following purposes and legal bases:
| Purpose | Basis |
|---|---|
| Accounts, requested drive recording and sync, subscriptions, requested social and voice features, and requested car-image processing | Performance of our contract with you, to the extent necessary for the feature |
| Optional live-location sharing and processing for which local law requires consent | Consent |
| Non-essential analytics in the EU/EEA and other places where prior consent is required | Consent |
| Analytics elsewhere, service diagnostics, security, abuse prevention, support and operational alerts | Legitimate interests in operating, securing and improving Open Road, subject to local consent rules and your rights |
| Preparing the community heat map from eligible synced drives | Legitimate interests in providing the community map, subject to applicable consent rules and your objection rights |
| Understand optional cancellation feedback across subscription cycles | Legitimate interests in improving Pro, subject to your rights and applicable consent requirements |
| Required records and responses to binding legal demands | Legal obligation where applicable; otherwise an applicable basis for necessary claims or recordkeeping |
Retention follows the purpose of each activity. Where GDPR applies, research or statistical retention uses Article 89 safeguards, such as minimisation and pseudonymisation, and non-identifying data where possible.
Device permissions and agreement to our Terms do not provide blanket consent to every use of data. Where we rely on consent, you can withdraw it. We explain materially different uses before starting them and obtain consent where required.
The providers and recipients relevant to this service include:
Providers may act as processors for some activities and as independent controllers for others. We do not describe every provider as acting only on our instructions.
We use Apple install-attribution signals, Apple Search Ads attribution where available, referral codes and store campaign parameters to understand how people find Open Road. While analytics is on, the iOS app also tells Meta when it is installed or opened and when a trial or subscription starts (plan, price and currency), so we can see which of our Meta ads bring people in. We do not ask for Apple's tracking permission and do not send your advertising identifier. In US states whose privacy laws require it, Meta receives these events under its Limited Data Use setting. These are different from permission to track people across unrelated apps. We do not use personal data for cross-context behavioural advertising.
Telegram alerts go to a private chat used only by our founders. Alerts can include the download number of the day, platform, country only, never city, acquisition source, onboarding answers and progress, drive count, paid or trial status, plan and price, and purchase events. These events can be linked to an account in our systems even when the message does not show a name.
Telegram is an external recipient of the alert content. Deleting a database record does not automatically retract an already-delivered message.
We use Claude from Anthropic and OpenAI assistants to help read support requests, investigate issues and prepare replies. Relevant message content, attachments and account details may therefore be processed by those providers. We use OpenAI and Higgsfield for the car images described in section 2.3.
These providers receive relevant content to perform those tasks. We explain material changes to these uses before starting them.
Authorised personnel can access server-side accounts, synced routes and raw readings, uploaded images, social data, purchase records, support messages, operational alerts and logs. We use access for service operation, support, debugging, security, moderation and the purposes explained here.
We do not browse accounts out of curiosity. We do not sell user data to advertisers, data brokers, insurers or government agencies. We disclose data to the providers in this policy and to the audiences you use in the app. Government requests are covered in section 7.
Data that stays only on your device is not available to us through our servers. This does not include data you sync, share or send to support.
Synced drives, including drives kept Private in the social feed, can contribute to the community heat map. Route contributions are trimmed and privacy-zone areas are excluded. The published map combines activity into map tiles rather than showing named drive records. It does not publish your speed or account identifier.
These protections reduce identification risk; they do not guarantee that no inference about a person or place is possible. Email us if you want your drives excluded. Changes to published tiles require a rebuild and may not appear immediately.
We do not provide user data in response to informal or voluntary requests from authorities. We may disclose data where a binding legal requirement compels us to do so. We assess the validity and scope of a demand, provide only what it requires, and notify you where legally permitted. We can disclose only data we hold.
Firebase Analytics receives app usage events and installation or account identifiers. These records are not anonymous. Events and properties can cover screen and feature use, onboarding, experiments, app and device information, language and region settings, acquisition source, subscription status, vehicle type and aggregate activity such as drive count and distance. Our app filters precise coordinates, routes and addresses from custom analytics events. Google can also derive approximate location from network information.
When analytics is allowed, we also keep account-linked trial usage records. These include days you open the app, minutes per trial day, Pro features used or tapped while locked, and views of the post-drive summary. At trial start, we save your app version, how you found us, notification permission and experiment groups. We relate these records to purchases to compare trial use and later subscription outcomes across annual cycles and improve Pro. Cancellation events and skipped questions are also recorded only when analytics is allowed. Optional answers are handled separately as explained in section 2.9.
Starting with app version 5.1, Open Road asks EU/EEA users before non-essential analytics starts. Declining keeps that collection off. You can change the choice in Settings under Privacy. Prior consent also applies wherever local law requires it. Elsewhere, analytics may start by default and can be turned off. Turning analytics off does not delete your account, purchase records or data needed to provide requested features.
Firebase Remote Config supports feature configuration and experiments. Crashlytics processes crash traces, device and app information and installation identifiers. It is separate from the analytics switch in the current app. We do not describe crash reports as anonymous merely because we do not attach your account ID.
Our website processes network and browser information to serve pages and handle requests. Referral pages use an or_ref cookie lasting seven days and an or_cid visitor cookie lasting one year. Referral logs can include the code, visitor identifier, platform, browser user agent and time. Store-button taps record the campaign or referral code, selected store and time. Apple or Google receives campaign parameters when you follow the store link.
Invitation pages use local storage for invitation details. Creator tools can store drafts in your browser and send usage counters, selected deck details and feedback when those features are used. Administrative sign-in uses session cookies. Clearing browser storage removes local cookies and drafts, not records already sent to our servers.
OpenRoad LLC is based in the United States. Our providers and authorised team members may process data in the United States, Poland and other countries where they operate. Those countries may have different privacy laws.
Where a transfer needs a legal safeguard, it must be covered by an applicable adequacy decision or another valid arrangement, such as the appropriate contractual clauses. A provider's participation in the Data Privacy Framework covers only eligible transfers to that provider. It does not certify Open Road or all of its other recipients. Contact us for information about the recipients, locations and safeguards applicable to your data, or a copy of relevant safeguards.
We keep your account, profile, drive history and raw readings, saved vehicles and images, relationships, posts and comments while your account exists and they remain needed to provide the features you use. We do not delete them because you have been inactive. You can remove content or ask us to delete it at any time.
Signup and referral records, onboarding answers, team alerts, support messages and AI working copies are kept as long as we need them to understand and improve how people find, start and keep using Open Road, to follow up requests, to investigate incidents, or to meet the obligations below. We review these records, and we use information that does not identify you wherever that serves the same purpose. The queue records behind our team alerts are deleted automatically about 90 days after they are created.
Catalog car-request records are kept with your account for up to 24 months from the request date, so we can process your request and follow up on it. Account deletion removes them sooner.
Account-linked trial usage records are kept for up to 24 months from each record's own date. Cancellation answers are kept for up to 24 months from the answer date. These periods support comparisons across annual subscription cycles.
For these records, 24 months means a 730-day limit. Our scheduled job automatically deletes active server records once they reach that age. Updates do not restart the period. We delete records sooner when no longer needed or when an applicable deletion or objection request requires it. Account deletion also removes them. Copies and backups follow the deletion rules below. These limits concern request and analysis records, not your saved car pictures or purchase records kept for legal obligations.
Live presence normally stops displaying after about 90 seconds; friend and convoy cleanup runs every five minutes and public cleanup every minute. Waves expire after about five minutes. Voice calls are not recorded by Open Road.
Google Analytics keeps user-level and event-level data for 14 months, the longest its standard setting allows. New activity resets the user-data period. Website cookies last seven days for or_ref and one year for or_cid.
Cloud logs are kept for 30 days in the default bucket and 400 days for required audit logs. Firestore daily backups and point-in-time recovery use seven days, and deleted cloud files have a seven-day recovery window. Firebase starts removing crash traces and their identifiers after 90 days.
When you delete your account or make a deletion request, we delete the personal data concerned or irreversibly anonymise it, except for the narrow legal records below. This includes support, AI and team-message copies. Recovery copies expire on the schedule above and are never used to restore deleted data to normal use.
We keep purchase and tax records for the required period: five years for Washington tax records, and generally three years after filing for US federal income tax records, longer in specific cases. Where several rules apply, we use the longest one.
We keep evidence needed for legal claims for the applicable limitation period, generally up to six years in Washington for written contracts, and until any claim is resolved.
We keep statistics indefinitely only when they no longer identify anyone by reasonably likely means. We do not try to re-identify people from them.
For consumer health data covered by Washington's My Health My Data Act, we follow its deletion rules and notify relevant processors. Backup copies are cleared within six months of an authenticated request.
Depending on the law that applies, you can request access, correction, deletion, a portable copy, restriction of use, or object to particular processing. You can withdraw consent without affecting the lawfulness of earlier processing. You can ask us to delete data before closing your account where the law gives that right. Rights have conditions and exceptions.
Email openroad2026@gmail.com. We may need proportionate information to verify a request. You do not have to use an in-app export button to ask for your data. We do not penalise people for exercising applicable privacy rights.
Use Delete Account in the app's Settings, or follow our account deletion page. Email us if you cannot use the app.
Deletion removes the account and associated active app data through our deletion process. Some cleanup needs separate handling, including external support and AI records or Telegram messages. Backups, logs and justified retained records follow section 10. If a step fails, the request needs retry or follow-up; it should not be treated as complete merely because the app has signed out.
Deleting the app is not the same as deleting your account. Deleting your account does not cancel an App Store or Google Play subscription. Cancel subscriptions through the relevant store. Other people's saved copies and content that no longer identifies you may remain.
You may complain to your local data-protection authority. In the EU/EEA, contact your national authority. In the UK, contact the ICO. In Switzerland, contact the FDPIC. You can contact an authority without contacting us first.
California residents can contact us to request access, correction or deletion. We do not sell personal information or share it for cross-context behavioural advertising. Precise location is sensitive information. You can control location permissions and optional sharing, and request further limits where applicable law provides them.
We do not discriminate for exercising applicable rights. Where the CCPA applies, its verification, authorised-agent, response and extension rules apply. We do not dismiss Global Privacy Control merely because Open Road also has a mobile app.
Other state laws may provide access, correction, deletion, portability, appeal and opt-out rights. Scope and exceptions differ by state. Send requests or appeals to our contact email. Our separate Consumer Health Data Privacy Policy explains the additional rights it covers.
The applicable privacy law determines your rights. GDPR requests generally require a response within one calendar month. A permitted extension requires notice and reasons within that first month. UK and Swiss rules apply where relevant.
You can also object to processing based on legitimate interests. If a decision is made solely by automated processing with legal or similarly significant effects, the protections of applicable law apply. Ordinary drive statistics and leaderboard calculations do not by themselves establish that such a decision occurs.
If you live elsewhere, contact us to exercise rights under the law that applies to you. You may also contact your local privacy regulator. This policy does not limit rights provided by Canadian, Brazilian, Japanese or other applicable law.
We use encrypted connections, provider storage protections, authentication and access rules. Authorised operator access remains possible. Privacy zones and route trimming reduce exposure on relevant shared surfaces; they do not remove raw private backups or make live sharing approximate. No system can guarantee complete security.
Open Road is not intended for people under 16, or a higher minimum age required by our Terms where they live. If you believe a child below that age has supplied personal data, contact us so we can investigate and remove it as appropriate.
Apple or Google processes in-app payments. Open Road does not receive your payment card details. We do receive and store purchase and subscription records to manage access, support, reconciliation and necessary recordkeeping. See sections 2.9 and 10.
We update this policy when our practices change. The effective date appears at the top. We give additional notice of material changes where required and obtain consent where the law requires it. Continued use does not replace consent.
OpenRoad LLC, 5941 39th Ave SW, Seattle, WA 98136, USA.
See also our Terms, Community Guidelines and Consumer Health Data Privacy Policy.