Odyx Privacy Policy

Version of 29 October 2026.

In short.

• Odyx (called a3c before version 1.1.0) runs on your iPhone, iPad, Mac or Android device. Vehicle data, backups and the operation history stay on your device and are not sent to the developer.
• The app has no accounts or advertising and does not collect advertising identifiers.
• From version 1.1.2 the iPhone and iPad app, and from version 1.2.0 the Android app, sends usage statistics and crash reports to AppMetrica (YANDEX LLC, Russia) — you can turn them off in Settings, and in the EEA, the UK and Switzerland they stay off until you turn them on. Without the VIN or vehicle data (section 5).
• From version 1.1.0, the app asks the developer's server for update status and the catalogue, and from version 1.1.1 on iPhone and iPad also for news. The requests contain no identifiers. The server does not store IP addresses and keeps only daily counters.
• Notifications only if you turn them on yourself. Then the server stores the notification token (Apple's, or Google's or RuStore's on Android) with the platform, language and app version, and deletes it when you turn them off (clauses 4.8–4.10).
• If there is no profile for your car yet, you can suggest it: the server counts only the make, model, the model code from the VIN and the year, without the VIN. If you want to hear when it is added, the server temporarily links your notification token to that model (clause 4.11).
• If the iPhone and iPad app could not connect to the OBD adapter, it sends the developer an anonymous report: the adapter and iPhone model, versions and the exchange with the adapter during connection — without the VIN, vehicle data or identifiers. You can turn this off in the settings (clause 4.13).
• With the "Report a problem" button the app builds a report with the connection log and a truncated VIN; you decide whether to share it as a file or send it to the developer (clause 4.14).
• To deliver the Odyx Pro function maps, the app sends the server the Apple-signed transaction of your subscription, and the Android app from Google Play sends the Google Play purchase token. Without your name, Apple ID, Google account or payment details. The server only verifies them and does not store them (clauses 7.2, 7.8).
• The https://odyx.app website sets no cookies and makes no requests to Yandex or Google without your consent. Yandex Metrica (with Session Replay) and the Google Ads tag only run after you press "Accept" in the cookie banner (section 14).
• Apart from the above, the developer receives personal data only if you write to support.
• App Store payments are processed by Apple, Google Play payments by Google. If you pay for Odyx Pro by card in the Android app, Robokassa processes the payment: the controller receives your email and the payment result, but not your card details (clauses 7.4–7.7).

1. General

1.1. This Policy explains how the controller processes personal data in connection with the Odyx app for iPhone, iPad, Mac and Android (called a3c before version 1.1.0), its server, support, payment for Odyx Pro by bank card (clauses 7.4–7.7) and the https://odyx.app website (section 14). It is the controller's policy under Art. 18.1 of Russian Federal Law No. 152‑FZ "On Personal Data" (152‑FZ). For users in the EEA, the United Kingdom and Switzerland, it also provides the information required by Art. 13 of the General Data Protection Regulation (GDPR).

1.2. Terms have the meaning given in 152‑FZ and the GDPR.

2. Controller

2.1. Controller (operator) — Sergei Pavlov, private individual, self-employed (professional income tax payer, Russia), TIN (INN) 773324032650, Moscow, Russia, email: thebordev@gmail.com. The controller is personally responsible for organising the processing of personal data.

2.2. Representative in the EU (Art. 27 GDPR): not appointed.

3. Data on your device

3.1. The app stores on your device (iPhone, iPad, Mac or Android device):

• vehicle data: VIN, control-unit identifiers and versions, codings, adaptations, fault codes, parameter values;
• backups taken before writes and the operation history;
• technical logs;
• app settings;
• on Android with a Google Play subscription, the token of the last verified purchase (clause 7.8).

3.2. This data is processed only on your device. The app does not send it to the controller, and the controller has no access to it. The controller receives it only if you attach it to a support email yourself. The exceptions are the failed connection report under clause 4.13 (it contains part of a technical log — the exchange with the OBD adapter during connection — but no VIN and no vehicle data) and the problem report under clause 4.14, which you send yourself.

3.3. On a Mac, you can open the data folder via "Help → Show data folder in Finder". You can delete the data yourself; quit the app first and keep any backups you need. Deleting the app may not delete the data folder. Copies in macOS backups (such as Time Machine) are managed separately. On iPhone and iPad, the data is kept in the app's container and is deleted together with the app. It may be included in device backups (in iCloud or on a computer), which you control in the system settings. On Android, the data is kept in the app's private folder and is deleted together with the app; it is not included in Android backups or in transfers to a new device.

3.4. You enter SFD tokens yourself. The app uses them to unlock a control unit and does not send them to the controller.

3.5. iOS, iPadOS, macOS and Android permissions are used only to communicate with the vehicle, work with files and show notifications:

• Bluetooth — to communicate with a BLE adapter (on iPhone and iPad, this is the only way to connect to the vehicle); on Android, "Nearby devices";
• location — only on Android 11 and earlier, where the system allows searching for Bluetooth adapters only together with this permission. The app does not determine or send your location;
• local network — on a Mac, for Wi‑Fi adapters and DoIP connections;
• access to files you select — on a Mac, for export and import;
• notifications — only if you turn them on yourself (clause 4.8).

4. The Odyx server (from version 1.1.0)

4.1. At launch and then every 6 hours, the app sends a request to the controller's server. It contains:

• app and engine versions and the build channel (app store, test build or development);
• the list of engine capabilities;
• the major version of the operating system (macOS, iOS, iPadOS or Android) and the processor architecture;
• the interface language;
• the revision of the installed catalogue;
• a "first request of the day" flag.

4.2. The request contains no identifiers of the device or installation, no Apple ID or Google account, purchase data, serial numbers or MAC addresses, no VIN or other vehicle data, no name, email, geolocation or cookies. The separate request for Odyx Pro maps, which carries the subscription transaction or the Google Play purchase token, is described in clauses 7.2 and 7.8.

4.3. The server responds with an "update required?" status and feature flags. The app downloads the catalogue, signed with the controller's key, in separate requests: at launch, the general list of car models; when you open a model, that model's functions, their translations into the interface language and their animations. These requests contain only the catalogue schema number, the build channel, the selected model and the language — no identifiers, as in section 4.2; the server does not record them. The last response and the downloaded catalogue are stored on your device so that the app works offline.

4.4. IP address. Like any server on the internet, the server receives your device's IP address — a response cannot be sent without it. The IP address is used only in memory, to deliver the response and to protect the server from overload. It is deleted within minutes. It is not written to logs or databases, access logs are disabled, and it is not linked to the content of the request.

4.5. The server stores only daily aggregated request counters for combinations of the parameters in clause 4.1. Rare combinations are merged into an "other" category so that no individual user can be singled out by an unusual configuration. The server cannot tell whether two requests came from the same device.

4.6. Apart from the notification token under clause 4.8 and subscriptions under clause 4.11, if you have turned them on, the server does not collect or store personal data and cannot identify users. The server only verifies the Odyx Pro subscription transaction (clause 7.2) and the Google Play purchase token (clause 7.8) in memory and does not store them. Where the law of your country (for example, the GDPR) treats the brief handling of the IP address under clause 4.4 as processing of personal data, the legal basis is the controller's legitimate interest in delivering the requested data and protecting the server (Art. 6(1)(f) GDPR).

4.7. Server location: Russian Federation.

4.8. Notifications (optional). Notifications are off until you turn them on in the app's settings and allow them in the system prompt. The notification service then gives the app a token: on iPhone, iPad and Mac, the Apple Push Notification service (APNs); on Android, Firebase Cloud Messaging (Google, Google Play version) or RuStore Push (RuStore version). The app sends the controller's server a separate request with the token, the platform (iPhone and iPad, Mac or Android), the interface language and the app version. The token is a string of the notification service used to deliver notifications to this device. It does not tell the controller your name, Apple ID, Google account, email address or vehicle data, and it is not linked to them, to purchases or to other requests to the server — except the subscription to a model being added under clause 4.11, if you set one up.

4.9. The token is used only for notifications from the controller: app news and important messages about the server and updates. The controller may choose recipients by platform, language and app version and, under clause 4.11, devices subscribed to a model being added. The token is not used for advertising, analytics or profiling and is not shared with third parties other than the service that delivers the notifications (Apple, Google or RuStore).

4.10. The token is kept while notifications are on. If you turn them off in the app, the token is deleted from the server. If you delete the app or block notifications in the system settings, the controller deletes the token as soon as the notification service reports that it is no longer valid. The legal basis is your consent (Art. 6(1)(a) GDPR; Art. 9 of Russian Federal Law 152-FZ); you can withdraw it at any time with the same switch.

4.11. Suggesting a model (optional). If Odyx does not know your car, you can suggest it in the app. The app sends the make, model, platform, the manufacturer code and model code from the VIN (positions 1–3 and 7–8) and the model year — without the full VIN and without identifiers; the server only increases the counter for that model. If notifications are on and you ticked “Tell me when it is added”, the app subscribes the token under clause 4.8 to that model's topic (for example “WVW:3C”) in a separate request. This link between the token and a car model is personal data; its purpose is a single notification that the model was added. The subscription is deleted after that notification, together with the token (clause 4.10), when you cancel it in the app and no later than 12 months after it was made. The legal basis is your consent (Art. 9 of Federal Law No. 152-FZ, Art. 6(1)(a) GDPR).

4.12. Odyx news. From version 1.1.1 the app for iPhone and iPad, and from version 1.2.0 the Android app, shows news from the controller as short stories on the Car tab. The app downloads the story feed, signed with the controller's key, and its pictures in separate requests that contain only the build channel — no identifiers, as in clause 4.2. Which stories you have opened and how you answered a poll is stored only on your device. So that the controller can see which news is useful, the app sends events to the server: a story was shown, opened, watched to the end, or a button in it was tapped — with the story's identifier, the platform, the app version and the interface language, without device or user identifiers. The server keeps only daily totals of these events and deletes them after 90 days. If you vote in a poll, the app sends the chosen option and the server only increases that option's counter; the server does not know who voted.

4.13. Failed connection report. From version 1.1.1, if the app for iPhone and iPad could not connect to the OBD adapter, or the adapter answered but the vehicle did not, it sends a report to the controller's server so that the controller can fix how the app works with that adapter. The report contains: the adapter's name as broadcast over Bluetooth and its ELM327 version, the adapter's list of Bluetooth services, the step and reason of the failure, the exchange with the adapter during this connection (commands and adapter replies with timestamps; the app replaces replies from vehicle control units with a note "command and number of bytes"), the iPhone or iPad model, the iOS, app and core versions, the build channel and the interface language. The report does not contain the VIN, vehicle control unit data, device, adapter or installation identifiers, the notification token, the Apple ID or location; the server does not record the IP address (clause 4.4) and cannot link the report to a user or to other requests. The report is sent automatically; you can turn sending off in the app settings and send a report manually with a button on the connection screen. The server keeps reports for 90 days and then deletes them; it keeps counts of reports per adapter model without a time limit. If you write to support, the report number shown in the app lets the controller find your report. The Android app does not send such reports.

4.14. Problem report (on your action). From version 1.1.2 the app for iPhone and iPad, and from version 1.2.0 the Android app, has a "Report a problem" button (in the settings and on screens that show an error). When you tap it, the app builds a report, shows what it contains and lets you choose: share the file through the system menu or send it to the controller's server. The app sends nothing on its own. The report contains: the problem category and your comment (if you wrote one); the device model, the operating system, app and core versions, the build channel and the interface language; the VIN cut to the manufacturer code and the last four characters; the catalogue edition and revision; the connection type, the adapter's name and firmware, the voltage; the list of control units with part numbers, software versions and SFD status; the control units' fault codes; the core log for the chosen period (two hours or a day): events with codes, requests to control units without their contents (service, identifier, size and response code) and the exchange with the OBD adapter, where replies from control units are replaced with a note "command and number of bytes"; the latest write operations without the "before" and "after" values. The report does not contain the full VIN, control unit serial numbers or FAZIT, SFD tokens or access keys, written payloads, the notification token, the Apple ID, the Google account, device, adapter or installation identifiers or location; the server does not record the IP address (clause 4.4). You write the comment yourself, so it may contain personal data — the controller then handles such a report as a support request under section 6 (purposes, legal bases and rights are there); the app does not accept a comment containing a VIN. The server keeps the report for 30 days and then deletes it. If you write to support, the report number shown in the app lets the controller find your report.

5. Usage statistics and crash reports (AppMetrica: iPhone and iPad from version 1.1.2, Android from version 1.2.0)

5.1. From version 1.1.2 the iPhone and iPad app, and from version 1.2.0 the Android app, may send usage statistics and crash reports to the AppMetrica service. The Mac app does not. The Odyx server does not receive this data: the controller sees it as aggregated reports in the AppMetrica dashboard.

5.2. Usage statistics show which features are used and how, so the app can be improved. They are on by default, except on devices with the region set to the EEA, the UK or Switzerland: there they stay off until you turn them on. You can turn them off at any time in Settings ("Usage statistics"); sending stops immediately.

5.3. Crash reports help find and fix app errors. They are on by default, except on devices whose region is in the EEA, the UK or Switzerland: there they are off until you turn them on. You can turn them off in Settings ("Crash reports"); the change takes effect at the next app launch. If both usage statistics and crash reports are off, AppMetrica is not started.

5.4. Processor. YANDEX LLC (TIN 7736207543, 16 Lva Tolstogo St., Moscow 119021, Russia), the AppMetrica service, processes the data on the controller's behalf (Art. 6(3) of 152‑FZ; a processor under the GDPR); terms: https://yandex.ru/legal/appmetrica_termsofuse. The data is stored in the Russian Federation. The controller does not use it for advertising and does not share it with third parties.

6. Support requests

6.1. Apart from notifications (clauses 4.8–4.11), the problem report (clause 4.14), the Odyx Pro subscription check and payment (section 7), AppMetrica (section 5) and the website (section 14), this is the only case in which the controller processes your personal data.

6.2. Do not send passwords, SFD tokens or unnecessary personal data. Send the full VIN only if it is really needed for the answer. The controller does not request special categories of personal data.

6.3. Recipients. Emails are stored by the email provider Google LLC (Gmail), which processes them on the controller's behalf; under the GDPR it is a processor. Data is disclosed to public authorities only where the law requires it. The controller does not sell personal data or share it for advertising.

6.4. Storage location. The database (mailbox) is located in: the United States and other countries where Google operates data centres.

6.5. Cross-border transfer: yes — correspondence is stored on servers of Google LLC (USA).

7. Apple, Google and payments

7.1. App Store downloads, purchases, the Odyx Pro subscription and refunds are handled by Apple as an independent controller under Apple's privacy policy.

7.2. The controller does not receive card numbers, billing details or Apple Account data. The app checks the subscription on your device using StoreKit. To deliver the exact function maps that are part of Odyx Pro, the app sends the controller's server the App Store–signed transactions of your subscription (one to eight StoreKit 2 JWS strings). A transaction contains Apple's transaction identifiers, the product identifier and dates, but not your name, Apple ID or payment details. The server only verifies Apple's signature, the product and the expiry date in memory to decide whether to return the Pro maps. It does not store the transaction, write it to logs or link it to other requests. The legal basis is performance of the End User License Agreement (licence and subscription): Art. 6(1)(5) of 152‑FZ, Art. 6(1)(b) GDPR. Apple provides the controller only with aggregated sales reports that do not identify buyers.

7.3. If you have allowed sharing analytics with app developers in your device's system settings, Apple may pass crash reports and de-identified statistics to the controller under Apple's rules.

7.4. Paying for Odyx Pro by bank card (Android app). If you pay for Odyx Pro by card under the Public Offer (https://odyx.app/ru/offer/, in Russian), the controller processes: the email address you entered at payment; the order number, amount, date and payment method; the Purchase ID — a random code that the app creates and keeps on your device; the status and term of the subscription; your consent to automatic payments and its withdrawal; and receipt data. Purposes: performing the Offer (granting Pro access, automatic payments and advance notices of them, accepting cancellation, refunds) and meeting tax obligations. Legal bases: Art. 6(1)(5) and 6(1)(2) of 152‑FZ; Art. 6(1)(b) and (c) GDPR. The data is stored on the controller's server (Russian Federation).

7.5. Payment service. Payments and automatic payments are processed by ROBOKASSA LLC (Moscow, Russia) (Robokassa). You enter the card number, expiry date and CVC only on the Robokassa page. The controller does not receive or store this data. Robokassa processes it as an independent controller under its own policy and tells the controller only the payment result, without the full card number. To create a payment and a receipt, the controller passes Robokassa the order number, amount, service name and your email.

7.6. Receipt. A receipt for each payment is created in the Russian tax service's "Moy Nalog" app through Robokassa's receipt service and sent to your email. The tax service receives the amount, date and service name. Your personal data is not included in the receipt.

7.7. Retention. Subscription data is kept while the subscription is active and for 3 years after it ends (limitation period, Art. 196 of the Russian Civil Code). Payment, receipt and refund records are kept for 5 years (Art. 23(1)(8) of the Russian Tax Code). They are then deleted.

7.8. Subscription through Google Play (Android app from Google Play). Downloads from Google Play, purchases, the Odyx Pro subscription, its renewal and refunds are handled by Google as an independent controller under its own privacy policy. The controller does not receive bank card numbers, payment details or Google account data. The app checks the purchase on the device against the Google Play signature. To deliver the exact Odyx Pro function maps, the app sends the controller's server the Google Play purchase token — a string for which Google reports the subscription status. The server passes the token to the Google Play Developer API and receives the product, status and expiry of the subscription, without a name, email address or payment details. The token is not written to databases or logs and is not linked to other requests; so as not to ask Google on every request, the server keeps a hash of the token (SHA-256) and the received expiry in memory for up to one hour. The app keeps the last verified token on your device for no longer than 30 days: if a renewal has not been paid and Google grants a grace period, Google Play does not show the subscription to the app, and the server confirms it by this token. The app opens the Google Play payment window with a random pseudonymous installation identifier (a SHA-256 hash of a random number created on the device): Google uses it to spot fraudulent purchases; it is not linked to your name, account or device. The legal basis is performance of the End User License Agreement (licence and subscription): Art. 6(1)(5) of 152‑FZ, Art. 6(1)(b) GDPR.

8. International transfers (for users in the EEA, the UK and Switzerland)

8.1. The controller is located in the Russian Federation. There is no European Commission adequacy decision for Russia. When you write to support, you send your data directly to the controller in Russia yourself. This is not a transfer by an exporter in the EU, but the level of protection may differ from that in Europe. The controller applies the measures in section 10.

8.2. The email provider stores emails in the location given in clause 6.4.

8.3. AppMetrica. Usage statistics and crash reports (section 5) are stored by the processor in the Russian Federation. For users in the EEA, the UK and Switzerland this transfer is based on your explicit consent (Art. 49(1)(a) GDPR): you give it by turning on statistics or crash reports and can withdraw it by turning them off in Settings. Risk: Russia may not offer safeguards for your rights equivalent to those in Europe.

9. Your rights

9.1. Under 152‑FZ, you have the right to:

• obtain information about the processing of your data (Art. 14);
• require that your data be updated, blocked or destroyed if it is incomplete, out of date, inaccurate, unlawfully obtained or not necessary for the purpose of processing;
• withdraw consent;
• appeal against the controller's actions to Roskomnadzor or in court (Art. 17).

The controller does not make automated decisions that have legal effects for you (Art. 16). Data is not used to promote goods (Art. 15).

9.2. Under the GDPR, you have the right to:

• access your data (Art. 15);
• rectification (Art. 16);
• erasure (Art. 17);
• restriction of processing (Art. 18);
• data portability (Art. 20);
• object to processing based on legitimate interests (Art. 21);
• withdraw consent at any time without affecting the lawfulness of processing before withdrawal (Art. 7(3));
• lodge a complaint with a supervisory authority, in particular in the country where you live or work or where the alleged infringement took place (Art. 77).

9.3. How to make a request. Write to thebordev@gmail.com. To confirm that the request comes from you, the controller may ask you to write from the email address used in the correspondence. A request under 152‑FZ must contain the information listed in Art. 14(3) of 152‑FZ; an electronic request must be signed with an electronic signature.

9.4. Time limits. The controller replies within 10 working days of receiving the request. This period may be extended by up to 5 working days with a reasoned notice (Art. 14(3), Art. 20 of 152‑FZ). Under the GDPR, the reply is given without undue delay and within one month at the latest (Art. 12(3)). After consent is withdrawn or the purpose of processing is achieved, the data is destroyed within 30 days (Art. 21 of 152‑FZ). Requests are handled free of charge.

9.5. Whether you must provide data. Providing personal data is not a statutory or contractual requirement. The app works without contacting support. Without an email address we cannot reply to you. To pay for Odyx Pro by card, an email address is required to perform the Offer and issue a receipt (clause 7.4); without it, card payment is not possible.

9.6. There is no automated decision-making or profiling (Art. 22 GDPR).

10. How we protect data

Measures under Art. 18.1 and 19 of 152‑FZ and Art. 32 GDPR:

• legal: this Policy, internal processing rules, a harm assessment, a data destruction procedure;
• organisational: only the controller has access to personal data; data is processed only for the purposes in sections 4–7 and 14 and kept no longer than the stated period;
• technical: email is transmitted over an encrypted connection (TLS); the mailbox is protected by two-factor authentication; the controller's device disks are encrypted; software is kept up to date;
• minimisation on the server: requests without identifiers (except the notification token and subscriptions under clauses 4.8–4.11 and the Odyx Pro transaction or Google Play purchase token under clauses 7.2 and 7.8, which are not stored), anonymous connection reports (clause 4.13), IP addresses not recorded, access logs disabled, a signed catalogue that cannot be substituted.
• minimisation in AppMetrica: events from a closed list without the VIN, part numbers, control unit addresses or data; no advertising identifiers or location; error reports without message texts; statistics and crash reports can be turned off in Settings, and in the EEA, the UK and Switzerland they need your consent.

11. Children

The app is intended for persons over 18 and is not designed for children. The controller does not knowingly process children's data. If such data reaches the controller, it will be deleted.

12. Changes to this Policy

A new version is published at https://odyx.app with its date. The controller announces material changes in the app. If the app starts processing new data or using data for new purposes, this Policy will be updated before that happens.

13. Contact

Sergei Pavlov, thebordev@gmail.com.

14. The odyx.app website

14.1. Without your consent, the https://odyx.app website sets no cookies and makes no requests to Yandex or Google services. The website's server keeps no access logs and does not record visitors' IP addresses.

14.2. If you press "Accept" in the cookie banner, the website runs Yandex Metrica (with Session Replay, Webvisor) and the Google Ads tag. Which cookies they set and what they receive is described at https://odyx.app/en/cookies/.

14.3. You can withdraw consent at any time: with the "Cookies" button at the bottom of any page of the website (choose "Decline") or by writing to thebordev@gmail.com. After that the website stops loading Metrica and Google Ads.