Legal document

Privacy Policy

How OmniAuto processes and protects your data.

v1.4.0Current2026-09-27en

Privacy Policy - OmniAuto

Version: 1.4.0
Effective Date: September 27, 2026

1. Introduction

This Privacy Policy explains how DEVMAR Daniel Markiel (the "Administrator", "we", "us") processes personal data in connection with the use of the OmniAuto mobile application and the website available at omniauto.pl (together, the "Service").

2. Data Controller

DEVMAR Daniel Markiel
ul. Krótka 6, 43-332 Pisarzowice, Poland
Email: contact@omniauto.pl
NIP (Tax ID): 9372630363
REGON: 383741538

3. Categories of Processed Data

Depending on how the Service is used, we may process the following categories of data:

3.1 Account and identity data

  • email address,
  • name or profile label, where provided,
  • profile picture, where supplied by a login provider,
  • account identifier or external authentication provider identifier,
  • information about legal document acceptances and consent status.

3.2 Vehicle and Service usage data

  • vehicle identifiers such as VIN,
  • user-entered data such as vehicle name, registration number, mileage, fuel entries, service entries, reminders, expenses, and similar information,
  • speech input data and transcripts generated when the User uses microphone-enabled voice features,
  • technical vehicle data such as make, model, year, fuel type, drivetrain, engine, or other technical parameters,
  • vehicle diagnostic data read from an OBD adapter connected by the User (via Bluetooth), including trouble codes (DTC), their descriptions, readiness states, and selected live parameters, stored as diagnostic reports,
  • snapshots and events from the public CEPiK register (the Historia Pojazdu service) - described in Section 5.4,
  • information about sharing a vehicle with other persons: members of the User's household and Partners, with their roles (owner, editor, viewer, mechanic).

3.2a Vehicle draft data provided by a workshop or another business

Where a workshop, tyre service, vehicle inspection station, dealer, or insurance agent (the "Partner") prepares an invitation to take over a vehicle, we process the User's email address supplied by that Partner together with a vehicle draft, that is the vehicle data and any first service entry and reminder the Partner prepared before the User had an account.

The vehicle draft exists only inside the invitation. If the User accepts the invitation, the draft becomes the data of their vehicle. If the invitation expires, the draft and the supplied email address are deleted; all that remains is a record that an invitation was sent and expired, carrying nothing that identifies the recipient.

3.2b Data processed on behalf of a Partner

When a Partner uses the workshop panel, we process on their behalf, as a processor, their customers' data: name, phone number, email address, notes, vehicle data, service history, work orders and estimates, appointment dates, work-order photos, and data imported by the Partner from their own customer records (CSV). The details are set out in the Data Processing Agreement - in this scope the Partner is the controller of their customers' data.

3.3 Technical and security data

  • IP address,
  • user agent and basic device or application information,
  • session and authentication-related data,
  • push notification tokens,
  • error, crash, and security event data.

3.4 Analytics data (only with consent)

Where the User gives the separate consent described in Section 10, we additionally process:

  • a random application installation identifier or an identifier stored in a cookie, not linked to the email address or name,
  • a pseudonymous account identifier in the form of a hash, from which the email address or other account data cannot be recovered,
  • Service usage events, such as opening a screen or page, using a given feature, the way a vehicle was added (e.g. VIN scan or manual entry), or signing in,
  • basic information about the device, operating system, application version, and language,
  • approximate location at country or region level, derived from a truncated IP address.

Analytics events never contain the VIN, registration number, email address, the contents of entries, or any other data the User has typed in.

3.5 Communication data

  • contents of messages sent to the Administrator,
  • data necessary to handle complaints, requests, and responses to user inquiries.

3.6 Photos

  • Vehicle photos and invoice scans added in the mobile application are stored only locally on the User's device and are not transmitted to our servers. Their loss or removal from the device is outside our control.
  • Photos documenting workshop work orders (e.g. vehicle condition on intake, work in progress) added by a Partner are stored in an external file store. Photos the Partner marks as visible to the customer are accessible to anyone holding the direct link to the file; the others require access to the Partner's panel. Photos are deleted 90 days after the work order is closed.

4. Purposes and Legal Bases

We process personal data primarily on the basis of Article 6(1) GDPR:

  • performance of a contract or steps prior to entering into a contract (lit. b): operating the user account, enabling Service features, handling authentication, storing vehicle data and user history,
  • legal obligation (lit. c): fulfilling obligations arising from tax law, accounting rules, data protection law, and requirements related to security and accountability,
  • legitimate interests of the Administrator (lit. f): Service security, fraud prevention, complaint handling, establishment, exercise or defense of claims, statistics based on technical data, product improvement, and maintaining technical vehicle history as described below,
  • consent (lit. a): marketing communications, the Service usage analytics described in Section 10, and other activities where consent is required by law. Insofar as information is stored on and accessed from the User's device (installation identifier, cookies), consent is also given under Article 399 of the Polish Electronic Communications Law.

5. How We Use Data

5.1 Provision and maintenance of the Service

We use data to:

  • create and manage the user account,
  • store vehicle-related data and user-generated history,
  • display reminders, summaries, and other supportive Service features,
  • operate vehicle sharing with household members and Partners according to the granted roles,
  • ensure security, integrity, and proper functioning of the Service.

5.2 Automatically generated content and AI

Where a User uses service plan generation or similar AI-based features, selected technical vehicle data may be transmitted to third-party providers of such services. We aim to limit the scope of transmitted data to the minimum required to generate the result.

Where a User uses microphone-enabled voice features, the application may access the microphone and process spoken utterances into text using speech recognition capabilities provided by the device platform or an integrated speech recognition service available on that platform. The resulting transcript is used only to support the requested feature; it may be transmitted to an AI service provider together with limited context of the User's vehicles (such as vehicle name and registration number) in order to interpret the command.

In the workshop panel a Partner may dictate work-order notes - their text is analysed by an AI service provider in order to map the note onto the Partner's price-list items. The Partner is the controller of personal data contained in such notes.

Diagnostic trouble code (DTC) descriptions are translated into Polish by an AI service provider; only the code and its English description are transmitted, without personal data.

5.3 Statistics, security, and product improvement

We may use data to:

  • detect errors and failures,
  • monitor security and prevent abuse,
  • create statistics and analyses regarding the use of the Service,
  • improve existing features and plan new ones.

To analyse how the Service is used we rely on Google Analytics 4 (in the mobile application: Google Analytics for Firebase), provided by Google Ireland Limited. The tool runs only after the User has given the consent described in Section 10. We do not use Google's advertising features, we do not link analytics data with the device's advertising identifiers, and we do not share it for advertising purposes. Analytics data serves us solely to understand which features are used and where Users run into difficulties.

5.4 Verification and monitoring in the public vehicle register (Historia Pojazdu / CEPiK)

When a User asks the current owner of a vehicle to hand it over, we may verify the registration document details they supplied (registration number, VIN, and first registration date) against the public Historia Pojazdu service (historiapojazdu.gov.pl), run by the minister responsible for digitalisation as part of the Central Vehicle and Driver Register (CEPiK).

In addition, for vehicles already saved in the Service, we may query Historia Pojazdu periodically or at the User's request in order to:

  • fill in missing technical vehicle data,
  • detect changes in the register, such as sale, disposal, deregistration, odometer readings, or the vehicle being flagged as lost, and inform the User about them as signals in the application.

We make the query no more than once every 30 days per vehicle and only while the feature is enabled in the Service. The information the register returns (such as registration status, odometer readings, owner counts, inspection and OC insurance dates) is stored as snapshots and immutable events in the vehicle's history.

Register information is informational and is not an official document; in particular a vehicle flagged as lost is only a registry entry and does not by itself constitute a finding of theft. The legal basis is the Administrator's legitimate interest (Article 6(1)(f) GDPR) - Service security, completeness of vehicle history, and preventing vehicles being claimed by unauthorised persons.

OmniAuto is not affiliated with the operator of Historia Pojazdu or with CEPiK; we use the service only through its publicly available channel, on the same terms available to every citizen.

5.5 Public vehicle history report

The User may generate a link to a public report of their vehicle's history, for example for a sale listing. Anyone holding that link can open the report without signing in, so sharing the link is the User's decision and its effect is to disclose the vehicle data and service history in the report to whoever receives it.

The link is valid for a limited time, the User may revoke it at any moment, and the Administrator records how many times and when the report was opened so that the User can see what is happening with the link. The report carries neither the User's contact details nor any financial data.

We do not sell users' personal data to third parties.

5.6 Partner payments

Fees for paid workshop-panel plans are collected by the payment operator Stripe. In connection with a payment, Stripe processes the Partner's billing data under its own terms; we receive and store the subscription status, the Stripe customer identifier, and plan information, without access to full card details.

5.7 Parts supplier integrations (workshop panel)

A Partner may connect their own API accounts at parts suppliers (e.g. Inter Cars, HART). The credentials for those accounts are stored encrypted and used solely to perform ordering functions requested by the Partner. Orders and related data are transmitted to the chosen supplier on the Partner's behalf.

5.8 NIP verification

A Polish NIP (tax identification number) entered in the panel may be verified against the public API of the Ministry of Finance's VAT Taxpayer Register ("Biała lista" / White List). The query contains the NIP itself; results are kept in a short-lived cache to limit the number of queries.

5.9 VIN decoding

A VIN may be transmitted to vehicle decoding services in order to automatically fill in the vehicle's technical data. Where the full document triple is available (VIN, registration number, first registration date), the query goes first to the public Historia Pojazdu (CEPiK) service described in Section 5.4; otherwise it goes to the public NHTSA vPIC API (the US government's vehicle registry). Queries carry only the VIN and - where provided - the document triple.

6. Data Recipients

Data may be shared with entities that support us in operating the Service. These may in particular include:

  • infrastructure providers: hosting (Vercel), database and file storage (Supabase, EU region),
  • the transactional email provider (Resend),
  • the error and security monitoring provider (Sentry, EU region),
  • the provider of the Google Analytics 4 / Google Analytics for Firebase analytics tool (Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland), only after the consent described in Section 10 has been given,
  • AI providers used to generate content and to interpret speech and notes within the Service (including Groq),
  • speech recognition providers or device platform processors used to support voice input features,
  • push notification providers (Firebase Cloud Messaging),
  • authentication and social login providers where the User chooses such login method,
  • the Stripe payment operator, within the scope of Partner plan billing,
  • VIN decoding services (the public NHTSA vPIC API and the Historia Pojazdu / CEPiK service where the full document triple is available), within the scope of the VIN and the document data described in Section 5,
  • parts suppliers chosen by the Partner, within the scope of orders placed,
  • the Historia Pojazdu / CEPiK service and the Ministry of Finance VAT Taxpayer Register, within the scope of the queries described in Section 5,
  • legal, accounting, or technical service providers acting for the Administrator.

6.1 Partners the User has granted access to

Partners are a separate category of recipient: workshops, tyre services, vehicle inspection stations, dealers, and insurance agents who use the Service in the course of their own business.

A Partner gains access to a vehicle's data only where the User explicitly grants it, that is by accepting an invitation the Partner prepared or by inviting the Partner to the vehicle themselves. The scope of that access is limited by the Partner's role: it covers the vehicle data, the service history, mileage, diagnostic reports, and reminders, and it never covers fuel entries, expenses, or any amounts of money. An insurance agent may only read the vehicle data and set a reminder for a policy date.

The Partner is a separate controller of that data within its own business. The User may withdraw a Partner's access at any time in the vehicle's access settings; entries the Partner added before that remain in the vehicle's history as its documentation.

Such entities process data under appropriate agreements or under their own legal role, depending on the nature of the service.

We may also disclose data where required by law, a valid public authority request, or where necessary to establish, exercise, or defend claims.

7. Data Retention

7.1 Account and operational data

Account data and data related to active use of the Service are generally retained for the duration of the account, and thereafter for the period necessary to complete deletion, operate backups, maintain accountability and security, and comply with legal obligations.

7.2 Data after account deletion

After account deletion, the Administrator deletes the User's personal data or disconnects them from the User's identity to the extent that retention of certain information remains necessary for:

  • security and accountability,
  • establishment, exercise, or defense of claims,
  • compliance with legal obligations,
  • statistics, analyses, and development work based on technical vehicle data,
  • maintaining technical vehicle history insofar as it is no longer used for ordinary operation of the User's account.

In practice, this means we delete personal and operational data (such as reminders and expenses), remove the active vehicle records and their user-linked history, and retain only selected structured technical facts in a separate de-identified vehicle record (such as VIN, make, model, service types, mileage, and diagnostic summary counts). Free text, locations, provider details, registration numbers, and account linkage are not copied into that record. Additionally, a short-lived compliance record of the deletion request is retained separately for audit purposes before being purged.

Important: after account deletion, such data is no longer used for ordinary identification of the User or operation of the User's account. Because a VIN may in some contexts allow linking to a person, the de-identified record is not treated as fully anonymous and is protected on the same terms as other technical data. Depending on the nature of the data and applicable legal obligations, some information may remain in supporting systems, backups, or audit logs for a limited period.

7.3 Consent, security, and complaint-related data

Data related to consents, security, technical logs, complaints, or accountability may be retained for as long as necessary for the relevant purpose or to comply with legal obligations.

7.4 Analytics data

Analytics data linked to an installation or cookie identifier is retained in Google Analytics for 14 months from the last activity and then deleted automatically. Aggregated reports that cannot identify an individual User may be kept longer. Withdrawing consent stops further collection and causes a new installation identifier to be generated should consent be given again.

7.5 Notification inbox entries

Entries in the notification inbox (the mailbox in the mobile app and web panels) may contain content rendered in the User's language, including personal data such as a customer's name or a workshop's name. All entries, read and unread, are permanently deleted 90 days after creation. Deleting the account removes all entries immediately.

7.6 Workshop work-order photos

Work-order photos added by a Partner are retained for the duration of the work order and deleted 90 days after it is closed.

7.7 CEPiK registry snapshots and events

CEPiK registry snapshots and events remain recorded in the vehicle's history until the vehicle or the account is deleted. They serve to document registry changes and are not used for other purposes.

8. User Rights

To the extent provided under GDPR, the User has the right to:

  • access personal data,
  • rectify data,
  • erase data,
  • restrict processing,
  • data portability,
  • object to processing based on legitimate interests,
  • withdraw consent at any time where processing is based on consent,
  • lodge a complaint with the Polish supervisory authority, the President of the Personal Data Protection Office.

The Administrator may provide self-service tools, such as downloading a copy of data or deleting an account, but the scope and form of such tools may depend on the current technical capabilities of the Service and need not cover every category of data.

If the User wishes to object to further processing based on the Administrator's legitimate interests, they may contact us at contact@omniauto.pl. We review each request individually, taking into account the nature of the data, the legal basis for processing, and our legal obligations.

9. Marketing Consents

Where the User gives separate marketing consent, the Administrator may send information about products, new features, or other content related to the Service.

Marketing communication may in particular be conducted via:

  • email associated with the account,
  • push notifications in the mobile application, where the User has enabled that communication channel.

Withdrawal of marketing consent is possible at any time and does not affect the lawfulness of earlier processing. Withdrawal of consent does not disable system or security communications where such communications are necessary for operation of the Service.

10. Analytics Consent and Cookies

10.1 Voluntary nature

Service usage analytics is switched off by default. We enable it only after the User has given a separate, voluntary consent. Declining or withdrawing consent does not limit access to any feature of the Service.

10.2 How to give and withdraw consent

  • In the mobile application: consent may be given when accepting the legal documents, and switched on or off at any time in Settings, under Privacy and legal.
  • On omniauto.pl: consent may be given or declined in the cookie notice shown on the first visit, and changed at any time via the "Cookie settings" link in the page footer.

Withdrawing consent is as easy as giving it and does not affect the lawfulness of processing carried out before withdrawal. After withdrawal, no further analytics data is collected, and the installation identifier or analytics cookies are removed from the device.

10.3 Cookies and similar technologies on omniauto.pl

The website uses:

  • strictly necessary cookies required for the Service to work, in particular to keep a signed-in User's session, to remember the chosen language and theme, and to remember the analytics consent decision (the omni_analytics_consent cookie, kept for 12 months). These cookies do not require consent because they are necessary to provide the service the User asked for,
  • Google Analytics cookies (_ga and _ga_*, kept for up to 2 years), set only after consent has been given. They distinguish visitors and sessions and measure how the pages are used.

In the mobile application, the counterpart of analytics cookies is a random installation identifier generated by Google Analytics for Firebase, stored on the device only after consent has been given.

Cookies may also be deleted and blocked in browser settings; blocking strictly necessary cookies may make it impossible to sign in to the Service.

11. Security

The Administrator applies technical and organizational measures appropriate to the risk level and nature of the processed data, including transmission security safeguards, access controls, encryption of stored integration credentials, monitoring tools for errors and security events, and mechanisms limiting unauthorized access.

In the event of a personal data breach, the Administrator acts in accordance with the obligations under GDPR, including - where the breach may result in a risk to the rights and freedoms of persons - notifying the supervisory authority and informing the data subjects where the breach may result in a high risk to their rights and freedoms.

12. International Transfers

Data may be processed within the European Economic Area and, where justified, outside the EEA where this is connected with the use of third-party providers. In such cases, the Administrator applies appropriate legal safeguards required by applicable law.

This concerns in particular providers headquartered in or operating infrastructure in the United States, such as Google (analytics, push notifications), Stripe, the Groq AI provider, the transactional email provider, and the VIN decoding services. The current list of transfer mechanisms (adequacy decisions, standard contractual clauses) for each provider is maintained in those providers' own documentation; we will provide information on request at the contact address.

Analytics data processed by Google may be transferred to the United States. The transfer relies on the European Commission's adequacy decision for the EU-U.S. Data Privacy Framework, to which Google LLC is certified, and on the standard contractual clauses included in the Google Ads Data Processing Terms / Google Analytics Data Processing Terms.

13. Children's Privacy

The Service is not intended for persons under 18 years of age unless applicable law expressly permits a different model of use.

14. Changes to This Privacy Policy

The Administrator may update this Privacy Policy where necessary due to Service development, legal or organizational changes, or changes in the external services used.

We will inform users of material changes in an appropriate way, in particular by email, in-Service notice, or renewed acceptance where required.

15. Closure of the Service

If the Service is discontinued or the application withdrawn, the Administrator will notify users in advance by a notice in the Service and by email, indicate a period during which available data exports can be downloaded, and then delete personal data in accordance with the rules described in Section 7, retaining only data whose retention is required by law (in particular tax and accounting rules) or necessary for the defense of claims.

16. Contact

For privacy, personal data, or data rights matters, you may contact us at:

Email: contact@omniauto.pl
Address: DEVMAR Daniel Markiel, ul. Krótka 6, 43-332 Pisarzowice, Poland

17. Final Provisions

In the event of discrepancies between different language versions of this Privacy Policy, the Polish version shall prevail unless mandatory applicable law provides otherwise.


Last updated: September 27, 2026
Version: 1.4.0