Privacy policy

Data controller: Orontes Drive · E-mail: [email protected]

When you delete your account or drives, data that identifies you is erased; driving data is irreversibly anonymized (endpoints removed, no link to you or between trips) and may be kept to improve our models. We retain only coarse pooled numeric feature categories supported by at least 20 distinct contributors; rare categories are discarded. No individual trip, complete route, coordinates, dates, exact timestamps, account/install/vehicle identifiers, free text, assistant messages or transcripts enter the separate training store. For eligible phone drives, the first and last 500 metres are excluded and at least 2 km must remain before deriving features; no geometry or sequences are retained at all. The app, public APIs and account export do not read this store. Raw vehicle telemetry is compressed and verified before erasure, then the identifying originals and compressed copies are removed in the deletion transaction. Small deletion/security tombstones needed to prevent late writes and unlinked App Store billing records remain separate from training data.

We process data necessary to perform the requested service under KVKK Article 5/2-c, and necessary, proportionate product reliability and road/energy improvements under Article 5/2-f legitimate interests, subject to your fundamental rights and freedoms. Signed-in Trip History, product analytics and MetricKit on supported clients, Road Intelligence sensor contribution, fleet energy contribution and Apple server speech recognition after OS permission are on by default with notice and easy off switches. Previous off choices are respected. External AI-provider sharing, proactive voice questions, community location/Bluetooth sharing and AI Connect require separate affirmative choices. Default settings do not replace statutory processing or international-transfer requirements.

If you create an account, we store the account and sign-in details needed to log you in. If you sign in with Apple or Google, we receive only the account identifier and the email address you approve on the provider's screen (with Apple this can be a private relay address), and use them only to create your account and sign you in. We never receive your Apple or Google password, contacts or other account data, and we do not use this data for advertising or sell or share it. Our use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements. Deleting your account deletes this data; you can also remove Orontes Drive's access in your Google Account (Security → Third-party connections) or Apple ID settings. A beta application stores the email address, city, vehicle description, selected test interests, language, consent time and submission timestamps needed to review and contact applicants.

Route planning, navigation and speed-limit and average-speed corridor information use your current location, origin, destination, waypoints, the route on the map, charging stops and trip progress. With background location permission, the app keeps showing speed-limit and corridor information while the phone is locked or another app is open. On Android, background location (“Allow all the time”) is optional: before the system asks, the app explains in its own dialog that it is used for speed-camera, radar and average-speed corridor warnings and guidance while the screen is locked, another app is in front or Android Auto is in use, and when automatic drive detection arms radar warnings; the system prompt opens only after you choose Continue. While navigation or passive radar runs in the background, Android shows an ongoing notification. Automatic drive detection uses Google Play services Activity Recognition (with the Physical activity permission) only to detect when a drive starts or ends; activity data stays on the device. On Android Auto, the app shows navigation and warnings on the car display using the same data as on the phone. Trip History is on by default for signed-in users and saves completed navigation and passive-radar drives to the account. Turn it off in Settings → Privacy; turning it off offers deletion of saved drives. A previous off choice is always respected. Saved places, favorites and route preferences are stored when you use those features.

Road Intelligence sensor contribution is on by default while driving, with notice and an off switch in Settings → Road Intelligence. A previous off choice is always respected. Motion and location are processed to identify road events. We receive pseudonymous derived event features, quality-checked GPS speed samples, bounded event or road-section paths, and sparse clean-passage evidence, rather than raw motion samples or complete routes. Observations, speed samples, passage evidence and interview envelopes are retained for up to 12 months; confirmed answer text is removed within 90 days. De-identified aggregate road-quality history may be retained. Proactive voice questions remain off until separately enabled. Trip History has its own off switch.

If you share a trip receipt, we create a link that shows the trip date, distance, duration, corridor averages and charge stops; it does not show your name or exact start and end points. Anyone with the link can open it until you delete the trip or your account. Referral links carry a code tied to your account so we can credit invitations. A referral reward requires the invited person to redeem the code and save a qualifying drive of at least 5 km after redeeming. Trip History is on by default for signed-in users and must remain enabled to save the drive; product analytics is not required.

Community profiles store your username, ghost, badges, points, friendships and preset pings. Map visibility and Bluetooth discovery are off until you enable them. Friends see precise location only with your permission; public map positions are approximate. Accepting a copilot invitation shares this trip’s route and driver progress until the session ends. Community reports store the reporting and reported account IDs, reason, content snapshot and review outcome until either account is deleted. Report objectionable content or users in Community; you can also block users.

If you connect Tesla or supported OBD telemetry, Orontes Drive processes the vehicle data needed for the features you enable, such as battery, range, charging, speed, location and when the vehicle connection last updated. Vehicle connection can be removed from the app. Vehicle Link to an Orontes Bridge adapter uses Bluetooth; on Android the adapter is paired through the system companion-device dialog, and the app keeps the link in a foreground service with an ongoing notification only while the paired adapter is in range. Fleet energy contribution is on by default with notice and an off switch in Settings → Energy data sharing; previous off choices are respected. It contributes pseudonymous aggregates of short road stretches and charging sessions, using a random contributor key, rounded time and at most a province, without account names, precise locations or full routes. Turning it off removes past contributions; personal energy insights remain available.

Speech is transcribed on your device where supported. Apple server speech recognition is on by default after the OS Speech Recognition permission; when on-device recognition is unavailable, audio may be sent to Apple. On Android, cloud recognition uses the configured system recognizer, including Google, after microphone permission. Cloud recognition has an off switch and a previous off choice is respected. Orontes Drive receives the transcript, not raw audio. Separately, before using Ghost, you are asked for explicit permission to send messages and relevant route, app and vehicle context to third-party AI providers, including Google and OpenAI, to answer your requests. AI-provider sharing remains off until you agree and can be disabled in Settings → Assistant Providers. Assistant transcripts may remain in your conversation history for up to one year. When location permission is on, your current location is sent with each assistant request to our server to find nearby places; it is not shared with AI providers.

Subscriptions are sold and billed by Apple through the App Store. We receive the transaction and subscription status from Apple to unlock Pro features; we never receive your card details. The Android app, distributed through Google Play, has no in-app purchases; Pro on Android comes only from promotional or referral grants.

On supported clients, product analytics are on by default with notice and an off switch in Settings → Privacy; a previous off choice is respected. The app sends usage events such as app opens, completed drives, corridors completed and shares, linked to a random app installation ID and, when signed in, your account. These records are pseudonymous, not anonymous. We do not use the advertising identifier (IDFA) and do not track you across other companies’ apps or websites. Install attribution uses Apple’s AdAttributionKit, which reports aggregated campaign results without identifying you.

On iOS, crash and hang diagnostics provided by Apple’s MetricKit are on by default under the same privacy switch as product analytics, with notice and respect for previous off choices. Reports include the app version, iOS version and device model so we can fix failures; they do not contain your location or messages. Android does not use MetricKit. On Android, crash reports are sent to Google Firebase Crashlytics only while product analytics are on, under the same switch; turning it off stops collection and deletes unsent reports. Reports include the app version, Android version, device model and a random crash-reporting installation ID; they do not contain your location or messages.

The website sets no cookies and loads no advertising or analytics trackers. It stores only your language choice (orontes-locale) in your browser’s local storage, which is strictly necessary to show the site in your language; you can clear it in your browser settings at any time. Our hosting and security provider may process technical connection data (such as IP address) to protect the site from attacks.

We keep security, error and performance logs to authenticate requests, prevent abuse and investigate failures.

Data is shared only with providers needed to run the features you enable: cloud hosting and storage (including Oracle Cloud and Cloudflare, with Cloudflare R2 storage), Apple (App Store, speech recognition, push notifications), Google (Google Play distribution, Google Maps and Places for maps and search, Firebase Cloud Messaging push tokens and notifications, Firebase Crashlytics crash reports when enabled, and the Android system speech recognizer) and providers used by the assistant (including Google and OpenAI for AI answers, and Microsoft or Google for selected cloud voices). Some of these providers process data outside Türkiye; for users in Türkiye international transfers must meet the separate KVKK Article 9 requirements and appropriate safeguards described in the KVKK notice. We do not sell personal data or share it for advertising or marketing. We require service providers receiving personal data to use it only for the agreed service and to provide protection at least equivalent to this policy, with appropriate contractual and security safeguards.

If you connect an AI assistant such as Claude, ChatGPT, Grok, Gemini, Meta Muse or another MCP client, Orontes Drive sends that provider only the data needed to answer your request, within the permissions you approved in the iPhone app. Depending on those permissions this can include your vehicle list and names, battery, charging, climate, lock state, alerts, software, drive and charge history, battery health, trip plans, and chargers, speed cameras and incidents. Your VIN is never shared.

Permissions: vehicle:read lets the assistant read vehicle status and history. vehicle:location shares your vehicle’s approximate location (about 1 km). vehicle:location.precise shares exact coordinates and is only used if you grant it explicitly. vehicle:control.comfort allows climate, charging, horn, lights and sending destinations. vehicle:control.security allows locking and unlocking, trunk, windows, sentry and remote start. trip:plan allows route and charging-stop planning and checking speed cameras and incidents.

Every tool call is recorded in an audit log (tool, vehicle, outcome, time and IP address) that you can view in the app; audit entries are kept for 180 days. Access tokens expire after 15 minutes, and refresh tokens expire after 90 days without use. You can revoke a connection at any time in the app under Settings → Security → AI Connections. Security commands trigger a push notification to your phone.

Before authorizing an external AI connection, review its provider’s privacy policy and retention rules. Sharing requires your explicit permissions and equivalent protection of the personal data described in this policy; a provider’s own terms do not remove these requirements. See the AI Connect guide for setup and limits.

Account, trip and community data are kept until you delete them or your account. Assistant transcripts are kept up to one year, analytics events up to 25 months and crash reports up to 12 months. Security logs are kept for the period required by law.

The app provides account-data export and account deletion. You can also ask for access, correction, deletion, or objection by writing to the contact below. Users in Türkiye can apply under KVKK Article 11 as described in the KVKK notice.

We use technical and organizational safeguards appropriate to the data processed. The product is not directed to children under 13.

Privacy questions and requests: [email protected]. See also the Terms of use.