Previously published MB Partner and On Time Taxi privacy policies — shared access
This is a translation of the published Polish version. You can display the Polish original by selecting the document language.
Contents
MB Partner and On Time Taxi privacy policies — previously published documents
A common access point for two existing policies. The MB Partner document concerns MB Partner services, and the On Time Taxi document concerns the services and processes described by On Time Taxi. The full text of both documents is preserved below, without merging their rules or changing the described roles. The dates next to the documents are their publication dates on the source websites. Making them available together on 5 October 2026 is not the effective date of a new joint policy. A draft of a new joint version has been prepared separately.
Existing MB Partner policy (5.08.2026)
Source: mbpartners.pl/polityka-prywatnosci/.
Privacy Policy
Privacy and Cookies Policy MB PARTNER
Version 5.08.2026
Publication Date: 5 August 2026.
In this document, we explain what personal data we process, for what purposes, on what basis, to whom we may disclose it, how long we store it, and how cookies, analytical tools, advertising, communication, and security tools work.
1. Controller and Scope of Policy
- The controller of personal data is MB PARTNER MARCIN BOHDANOWICZ, ul. Rewolucji 1905 r. 82 lok. 6, 90-223 Łódź, NIP 8882894528, REGON 361683930, hereinafter: “Controller” or “MB PARTNER.”
- For matters concerning privacy and personal data, you can contact by email at kontakt@mbpartners.pl or in writing at the address of the Controller's registered office.
- The policy applies to the online service available at https://mbpartners.pl/, its subpages, and the User portal available at https://kierowca.mbpartners.pl/, collectively hereinafter: “Service.”
- A detailed description of the consent mechanism and Consent Mode v2 contained in this Policy applies to those pages of the Service where this mechanism has been implemented. Internal employee or administrative systems may be subject to separate information obligations.
- The Controller is the data controller insofar as it independently determines the purposes and methods of processing. In some processes, Application providers, fleet operators, Google, Meta, PZPA Solutions, or other partners may act as separate controllers, joint controllers, or processors – depending on the specific service and agreements in place.
2. Sources and Categories of Data
We may receive data directly from you – via form, registration, phone, email, or chat – as well as from a person or entity who lawfully submits you for cooperation, from advertising platforms providing contact forms, Applications and partners participating in the service delivery, from official or public registers and automatically when using the Service.
Depending on how the Service is used, we may process:
- identification data, in particular, first name, surname, date of birth, PESEL, citizenship, document number, image, and signature;
- contact and address data, in particular, address, phone number, and email address;
- data related to employment legality, employment, business activity, social insurances, student or pupil status, and tax settlements;
- data concerning driving license, medical examinations, licenses, qualifications, vehicle, insurance, and documents required for transportation or delivery;
- data concerning concluded agreements, orders, trips, deliveries, activity in Applications, settlements, remunerations, invoices, costs, cash, cards, deposits, balances, bank accounts and obligations;
- data related to submissions or leads, in particular, first name and surname, phone number, email address, city, source of submission or campaign, selected services or Applications, date and contact history, planned date of next contact, case status, assigned supervisor, necessary notes content and information on granted consents and objections;
- content of correspondence, chat, reports, complaints, attachments, and information provided during contact with support;
- technical data, in particular, IP address, session and device identifiers, browser type and version, operating system, language, date and time of the request, visited page address, referrer, security events, and error logs;
- data concerning privacy choices, including the scope of granted or withdrawn consents, version of consent mechanism, source of update, and time of choice;
- identifiers and data of advertising campaigns, if present in the page address, in particular, utm_* parameters, gclid, dclid, gbraid, wbraid, gad_source, and gad_campaignid.
By “lead” we mean a record concerning a person who submitted an inquiry, expressed interest in an offer, or was lawfully reported for contact but has not yet started cooperation with the Controller.
If the lead's data was not acquired directly from them, the Controller provides the required processing information, including its source and data categories, during the first contact, or at the latest within the period specified in Art. 14 GDPR, unless there is a statutory exception to this obligation.
Personal data such as first name, surname, email address, phone number, PESEL, or User identifier should not be placed in advertising campaign parameters or other parts of the URL. The Controller does not use the URL as a standard way of transferring email addresses or other contact data.
3. Purposes and Legal Bases of Processing
| Purpose | Legal Basis |
|---|---|
| Registration, verification, account management, conclusion and execution of a contract, transportation, deliveries, orders, payment transactions, settlements, and payouts | Art. 6 par. 1 lit. b GDPR – taking steps at the request of the person prior to entering into a contract and the performance of the contract |
| Performing tax, accounting, insurance, transportation, employee, and other obligations arising from law | art. 6 sec. 1 point c GDPR – legal obligation of the Controller |
| Receiving, recording, and handling forms, questions, submissions, complaints, and contact with support, including providing answers and clarifying issues | art. 6 sec. 1 point b GDPR, if the contact concerns a contract or actions taken at the request of the person before its conclusion, or art. 6 sec. 1 point f GDPR – legitimate interest in conducting communication, handling submissions and ensuring continuity of service |
| Conducting the lead handling process in the CRM system, particularly creating a record, determining the source of the submission, assigning a supervisor, planning and documenting contact, updating status, verifying interest in the offer, organizing registration or onboarding, preventing duplicates, and quality control of service | art. 6 sec. 1 point b GDPR – actions taken at the request of the person before concluding a contract, and art. 6 sec. 1 point f GDPR – legitimate interest of the Controller in efficient organization of service, maintaining continuity of contact, accountability of employee actions, preventing multiple submissions and protection against claims |
| Ensuring the security of the Service, authentication, preventing account takeover, spam, fraud, and abuse, maintaining security logs, and using reCAPTCHA | art. 6 sec. 1 point f GDPR – legitimate interest of the Controller and Users in protecting systems, data, accounts, and settlements; to an appropriate extent also art. 6 sec. 1 point c GDPR |
| Establishing, securing, pursuing, and enforcing claims, debt collection, defense against claims, and documenting abuses | art. 6 sec. 1 point f GDPR – legitimate interest of the Controller or an authorized third party |
| Conducting a newsletter and sending commercial information electronically | art. 6 sec. 1 point a GDPR – consent and art. 398 Electronic Communications Law |
| Launching the Thulium chat widget and related optional browser memory mechanisms | art. 6 sec. 1 point a GDPR and art. 399 Electronic Communications Law – functional consent; after starting a conversation its handling may also be based on art. 6 sec. 1 point b or f GDPR |
| Full analytics of Service usage using Google Analytics | art. 6 sec. 1 point a GDPR and art. 399 Electronic Communications Law – analytical consent |
| Campaign measurement, remarketing, audience creation and ad personalization using Google Ads and Meta Pixel | art. 6 sec. 1 point a GDPR and art. 399 Electronic Communications Law – marketing consent; in the scope of sending commercial information also art. 398 of this law |
| Memorizing cookie decisions and demonstrating proper handling of consents | art. 6 sec. 1 point c and f GDPR and an exception concerning a solution necessary to provide the requested service mentioned in art. 399 sec. 3 Electronic Communications Law |
| Sending limited, cookie-less signals within Advanced Consent Mode when in denied state | art. 6 sec. 1 point f GDPR – legitimate interest in the technical operation of the consent mechanism, obtaining limited aggregate statistics and assessing Service effectiveness without launching optional storage and personalization |
Contact directly related to a submitted request, offer inquiry, or registration is not dependent on marketing consent. The use of a phone number or email address for unrelated direct marketing occurs only when there is a proper legal basis and the requirements of the Electronic Communications Law are met. Lack of marketing consent does not affect the possibility of handling the submission.
If another legal basis is appropriate for a specific process or additional information is required, the User will receive a separate information clause before starting that process.
4. Voluntary Provision of Data
- Providing data in a contact or submission form is voluntary. Lack of data marked as required may prevent the acceptance of a submission, contacting the interested person, or conducting registration. Signing up for the newsletter is voluntary and is not a condition for handling the submission.
- Providing data required for registration, verification, conclusion, or performance of a contract is voluntary but necessary to use the appropriate service or start Cooperation.
- Functional, analytical, and marketing consents are voluntary and independent of each other. Their refusal does not block basic account functions, except for functions directly dependent on a given consent, e.g., the Thulium chat widget.
- reCAPTCHA may be required for safe submission of a public form. If security prevention incorrectly blocks form submission, you can contact the Controller directly at kontakt@mbpartners.pl.
5. Data Recipients
Data may be disclosed only to the extent necessary to achieve the purpose:
- to persons authorized by the Controller, in particular employees and co-workers;
- cyber_Folks S.A., VPS server infrastructure provider, and other hosting, backup, mail, SMS, maintenance, and system security providers – only to the extent necessary to provide technical services to the Controller;
- Thulium sp. z o.o. – in relation to chat and communication handling;
- Google Ireland Limited, Google LLC, and their subcontractors – in relation to Google Tag Manager, Google Analytics, Google Ads, and reCAPTCHA;
- Meta Platforms Ireland Limited, Meta Platforms, Inc., and their subcontractors – in relation to Meta Pixel and Meta advertising services;
- payment operators, banks, terminal providers, and entities handling settlements;
- accounting offices, tax advisors, law firms, insurers, debt collection entities, and audit service providers;
- Applications, Fleet Companies, and other partners involved in the implementation or settlement of the selected service;
- couriers and postal operators if necessary for the shipment of documents, cards, bags, or other items;
- PZPA Solutions sp. z o.o. and entities related to the FLEETCHECK registry – only in the cases, scope, and on the grounds described in the General Cooperation Terms, relevant contracts, and separate information;
- public authorities, courts, bailiffs, and other authorized entities if the obligation or right to transfer data arises from the law.
We do not sell personal data as a contact data set.
6. Transfer of Data Outside the European Economic Area
- In connection with the use of services by Google, Meta, Thulium, or their subcontractors, data may be processed outside the European Economic Area, in particular in the United States.
- The transfer takes place, depending on the recipient and the current legal status, based on a decision by the European Commission confirming an adequate level of protection, the recipient’s participation in the EU–US Data Privacy Framework, standard contractual clauses approved by the European Commission, and additional protective measures.
- Information about the mechanisms used by Google is available in the document Data transfer frameworks, and information concerning Meta is in the Meta Privacy Policy.
- Information on the appropriate safeguards or a copy thereof can be obtained by contacting the Controller. Some documents may be provided excluding information covered by business secrecy or security requirements.
7. Data retention period
| Type of data or purpose | Period or retention criterion |
|---|---|
| Account and contract performance | for the duration of the account activity and contract validity, and then until the statute of limitations expires or longer if required by regulations |
| Tax, accounting, and insurance documentation | for the period required by the applicable regulations, generally 5 years counted according to the rules provided for the given obligation |
| Inquiries and forms not related to a contract, excluding leads described below | for the period needed to respond and conduct correspondence, and then at most until the statute of limitations of potential claims expire |
| Leads and applications that did not result in cooperation initiation | generally up to 12 months from the last actual contact with the person; if the person explicitly requested contact at a later date – up to 12 months from the agreed contact date; if no contact occurred after submission – up to 12 months from receipt of the application. Internal status change, assignment of a new custodian, or merely closing the case does not restart this period |
| Leads resulting in cooperation initiation | data needed for further cooperation become part of the account or contract documentation and are retained for the period indicated for the account, contract performance, legal obligations, and claims; unnecessary data after the acquisition process are deleted or anonymized |
| Minimal information on objection, withdrawal of consent, or request for no further contact | for the period necessary to respect the person's decision and demonstrate the Controller’s compliance with the law; such a record is not used for marketing purposes |
| Complaints, disputes, debts, and abuses | until the case is legally or finally concluded, obligations are fulfilled, and the statute of limitations of claims expire, considering archival duties |
| Newsletter and direct marketing | until withdrawal of consent or successful objection, no longer than 3 years from the last documented activity, unless earlier deletion is due to regulations or accepted procedures |
| Calls conducted through Thulium | for the period necessary to handle the case, ensure quality, and defend claims; if the call is recorded, information about recording and the specific period is provided before the recording starts |
| Technical and security logs | generally up to 12 months, and in case of an incident, abuse, or dispute – until explanations are concluded and the appropriate claims period expires |
| Cookie consent choice | 180 days from saving or reproducing the choice, until consent withdrawal or change in the consent mechanism version |
| Google Analytics data at user and event level | up to 14 months, according to service configuration; this setting does not necessarily delete previously aggregated reports |
| Data and advertising identifiers | according to consent settings, cookie table, and provider policies; campaign reports are retained no longer than necessary for analysis and settlement of the campaign, generally up to 26 months |
If a person has given separate consent for marketing, contact data and proof of consent may be retained according to the period indicated for the newsletter and direct marketing, regardless of the deletion of the inactive lead's remaining part.
After the appropriate period, data are deleted, anonymized, or access to them is restricted unless further retention is required by law.
8. Hosting, logs, and security
- The website is hosted on cyber_Folks infrastructure. Servers and network devices may automatically log containing, among others, IP address, request and response time, resource address, HTTP response code, referrer, information about the browser and device, and diagnostic data.
- Data submitted through forms and lead data are recorded in the Controller's CRM system maintained on a VPS server administered by the Controller. CRM is used for recording applications, assigning custodians, maintaining contact history, planning further actions, and updating case status. Entry in this CRM constitutes data processing by the Controller, not data transfer to a separate CRM system administrator.
- The VPS infrastructure provider provides server technical resources and may act as a processor under an agreement with the Controller. Placing data in CRM does not mean public disclosure.
- We apply technical and organizational measures chosen according to risk, in particular TLS connection encryption, password hashing, role-based permission and access control, additional authentication mechanisms, backups, event logging, administrative actions, software updates, and limiting the scope of data shared with external tools.
- Access to data in CRM is granted only to persons who need it for handling applications, supervision, settlements, security, or system maintenance and are bound by confidentiality or an appropriate agreement. Notes in CRM should be factual, related to the application, and limited to necessary information; passwords, one-time codes, or special category data should not be recorded unless there is a clear need and legal basis.
- The Controller periodically reviews inactive leads and applies deletion or anonymization rules according to item 7. Backups may be overwritten in a separate, limited retention cycle, and data from backups is not restored for regular use except in the event of failure or incident.
- No method of transmission or data storage completely eliminates risk. In case of a data protection breach, we take actions required by GDPR, including – when justified – notifying the President of UODO and the data subjects.
9. What are cookies and similar technologies
- Cookies are small pieces of information saved in the browser or device. The service may also use local browser storage, pixels, tags, and similar technologies.
- Cookies can be session-based, removed after closing the browser, or persistent, stored for a specific time or until deleted.
- First-party cookies are set by the currently visited host of the Service. Third-party cookies or similar identifiers may come from an external provider, e.g., Google or Meta.
- The consent mechanism distinguishes the following categories:
- necessary and security – required for logging in, maintaining sessions, protecting forms, security, and remembering privacy choices;
- functional – enable additional features, specifically the Thulium chat widget;
- analytical – are for fully measuring the use of the Service using Google Analytics;
- marketing – for measuring ads, remarketing, audience creation, and ad personalization using Google Ads and Meta Pixel.
- Functional, analytical, and marketing cookies are optional and are not saved or read before obtaining proper consent, subject to the Advanced Consent Mode and reCAPTCHA acting as protection for public forms as described below.
10. Consent panel and Consent Mode v2
- Before the Google Tag Manager container is launched, optional consent states are set as denied. The user can independently enable or disable functional, analytical, and marketing consent.
- For Google services, analytical consent controls the analytics_storage parameter, and marketing consent controls the ad_storage, ad_user_data, and ad_personalization parameters. Functional consent controls the launch of the Thulium widget and related functional storage.
- The choice is stored for 180 days in a host-only cookie mbpartner_cookie_consent. Host-only means the cookie is assigned to the specific host where the choice was made and is not automatically shared with all subdomains.
- The choice cookie may contain the scope of consents, the version number of the mechanism, and information needed to correctly reproduce the decision. It does not contain passwords, balances, contract data, or form content.
- After saving and reproducing the choice, the Service places portal_consent_update and portal_consent_restored events in the internal data layer. Events may contain fields such as portal_consent_functional, portal_consent_analytics, portal_consent_marketing, portal_consent_version, and the update may also include portal_consent_source. These fields should not contain User identifying data.
- After 180 days, deletion of the cookie, or change in the version of the consent mechanism, the Service may request the choice again.
- Consent can be changed or withdrawn at any time using the link or "Cookie Settings" button visible on the Service. Withdrawal of consent is free of charge and does not affect the lawfulness of actions taken before its withdrawal.
- After withdrawing functional consent, the page may be refreshed to remove the previously loaded Thulium widget. After withdrawing analytical or marketing consent, Consent Mode transmits the denied state, and tags supporting this mode stop saving and reading the corresponding optional cookies and sending complete measurement data. Previously stored cookies may remain in the browser until removed or expired, but should not be used further by correctly configured tags in the denied state.
11. Advanced Consent Mode – signals before and upon refusal
- The Service uses Advanced Consent Mode.This means that the Google Tag Manager container and Google tags may be loaded before consent is given, with a default state of denied.
- In the denied state, Google should not save or read optional analytical or advertising cookies or use data for ad personalization. However, tags may send cookie-less consent state signals and limited measurements used for statistics and modeling to Google.
- According to Google's documentation, such signals may include, among other things, the consent state, event time, User-Agent, referrer, a random value generated when the page is loaded, the presence of a click identifier, and limited information about the visited page. Network transmission also involves processing the IP address; Google indicates that in specific advertising signals, the address is truncated upon collection.
- The page address sent to GA or Google Ads is sanitized. The address and path of the page and exclusively campaign parameters such as utm_*, gclid, dclid, gbraid, wbraid, gad_source, and gad_campaignid may be retained. Other query parameters and the address fragment are removed.
- The container cannot replace the sanitized address with the full document.location or transmit email addresses, phone numbers, PESELs, account IDs, balances, contract data, form content, document data, or other information that directly identifies the User to analytics or advertising tools.
- Campaign parameters and click identifiers must not contain personal data. The Controller requires that individuals configuring ads do not place such data in the values of utm_* or other address parameters.
- Production tracking is initiated only when the request host matches the production address configured as PORTAL_URL. Local and test environments should not feed production analytics and advertising services.
- On password verification and change pages containing a one-time token, particularly at addresses /weryfikacja/?v=... and /zmiana-hasla/?v=..., external tracking is disabled, and the response uses the Referrer-Policy: no-referrer header. This aims to limit the risk of transmitting the token in the page address or referrer header.
- Native Google Analytics and Google Ads tags use built-in Consent Mode controls. Third-party and Custom HTML tags must have additional launch conditions corresponding to the appropriate category of consent.
- Cookie-less signals of Advanced Consent Mode are not equivalent to the complete lack of connection or data transfer to Google. A user who wants to technically block all connections with Google domains can use browser settings or a tool blocking external resources. They may also object to processing based on legitimate interest by contacting the Controller.
12. Google Services
12.1. Google Tag Manager
Google Tag Manager is used for managing tags and passing them the current consent state. The container itself can initiate a connection to Google. What data is then processed depends on the container configuration, the tags launched, and the consent choices.
12.2. Google Analytics 4
Upon giving analytical consent, Google Analytics may use cookie identifiers, device information, browser, approximate location derived from the IP address, visit source, visited pages, and events to create statistics and improve the Service. We do not pass data to Google Analytics that would allow Google to directly identify an individual, such as an email address or phone number.
In the absence of analytical consent, due to Advanced Consent Mode, the measurements described in pt. 11 may be sent without cookies. Google may use them for statistical data modeling.
12.3. Google Ads
Upon giving marketing consent, Google Ads may be used for conversion measurement, remarketing, audience creation, and ad personalization. Without consent, the ad_storage, ad_user_data, and ad_personalization parameters remain set as denied; limited cookie-less signals may be sent for modeling without enabling personalization.
More information can be found in Google Privacy Policy and in the description Consent Mode.
13. Meta Pixel
- Meta Pixel is loaded only upon granting marketing consent.
- Once consent is obtained, Meta Pixel may process information about visits and activities on the Service, IP address, device and browser information, cookies identifiers, referrer, and campaign identifiers. Data may be used to measure advertising effectiveness, create audience groups, remarketing, and personalize ads on Meta platforms.
- We do not transmit email addresses, phone numbers, User IDs, balances, contract data, or form content via Pixel, unless in the future, a separate function is implemented based on explicit legal grounds and it is described in advance.
- In the scope of collecting and transmitting event data using Pixel, MB PARTNER and Meta may act as joint controllers, while in other respects, Meta may act as a separate controller according to its terms.
- More information can be found in the Meta Privacy Policy and Meta Cookies Policy.
14. Thulium Chat Widget
- The Thulium widget is not loaded before granting functional consent. Refusal of consent does not limit the ability to contact the Controller by email.
- Once launched, the widget may process session identifiers, IP address, device and browser information, connection time, and any voluntarily provided data and content in the conversation.
- Do not send special category data, full identity document data, passwords, one-time codes, or data that is not necessary to resolve the issue via chat.
- Thulium sp. z o.o. may process data on behalf of MB PARTNER to provide the service and for its technical purposes, security, or legal obligations – according to its privacy policy.
- Upon withdrawal of functional consent, the Service refreshes the page to remove the loaded widget and stop its further operation.
15. reCAPTCHA
- Public forms are protected by Google reCAPTCHA to identify automated submissions, spam, misuse attempts, and attacks.
- reCAPTCHA remains active regardless of optional consents because it serves the security of the form and the Service. It is activated on pages containing a protected form, not for marketing analytics.
- The service may analyze IP address, User-Agent, device and browser information, time, manner of site use, movements and interactions, and other signals needed for risk assessment. Google indicates that reCAPTCHA sets the necessary _GRECAPTCHA cookie for risk analysis.
- The basis for processing by MB PARTNER is Art. 6 para. 1 letter f GDPR – legitimate interest in protecting forms, users, and systems. Access to information on a device is deemed necessary to securely deliver the form requested by the User.
- Use of reCAPTCHA is subject to the Google Privacy Policy and Google Terms of Service.
16. List of key cookies and similar identifiers
Exact names may change due to provider updates. The table describes known and typical identifiers for the specified configuration.
| Name or type | Provider | Purpose | Category | Maximum typical period |
|---|---|---|---|---|
| mbpartner_cookie_consent | MB PARTNER | remembering the scope of consents and version of settings | necessary | 180 days |
| session, authentication, and form security cookie | MB PARTNER | login, session maintenance, protection against unauthorized request and misuse | necessary | session or short security period resulting from configuration |
| _GRECAPTCHA and related security signals | Google reCAPTCHA | risk analysis, protection against bots and spam | essential and security | according to Google's configuration, generally up to 180 days |
| session identifiers for Thulium widget | Thulium | initiating and maintaining chat conversation | functional | session or period resulting from the current widget configuration |
| _ga, _ga_* | Google Analytics | differentiating browsers and creating usage statistics of the Service | analytical | up to 24 months |
| _gcl_au, _gcl_* | Google Ads | measuring the effectiveness of ads and conversion | marketing | generally up to 90 days |
| _fbp and associated Meta identifiers | Meta | ad measurement, remarketing, and audience creation | marketing | generally up to 90 days |
17. Managing cookies
- The most convenient way to manage consents is through the "Cookie Settings" panel available on the Service. It allows you to accept all optional categories, reject them, or make a separate choice.
- Browser settings additionally allow you to view, delete, and block cookies and site data. Instructions are available in browser documentation, particularly Chrome, Firefox, Safari, Edge, and Opera.
- Blocking necessary cookies may prevent logging in, maintaining a session, saving privacy choices, or securely submitting a form. Rejecting functional, analytical, or marketing cookies should not block basic account use.
- Deleting cookies in the browser does not automatically remove data that was previously correctly saved in the systems of the Controller or provider. To exercise rights concerning such data, follow the rules described in point 19.
18. Profiling and automated decision-making
- Upon granting marketing consent, Google and Meta may use data for advertising profiling, particularly assigning the User to audience groups, measuring conversion, and selecting ads. Detailed rules are determined by the policies of these providers.
- Advanced Consent Mode may allow Google to model statistics or conversions based on limited signals from people who have not consented to full measurement.
- reCAPTCHA automatically assesses the risk of submission. The result may lead to rejection or additional verification of the form, but the User may use an alternative way to contact the Controller.
- The CRM may automatically assign a lead to a caretaker, link it to a campaign, set the date for the next contact, or mark the status based on the source of the submission, selected services, city, and organizational rules. These actions are for workflow organization and do not constitute a decision that legally affects or similarly significantly impacts the person.
- The Controller may use automatic rules or indicators to detect abuses, assess Debt risk, and direct issues for verification by an employee. Unless separately informed, MB PARTNER does not make decisions based solely on automated processing that would have legal effects or similarly significantly affect them as understood by art. 22 GDPR.
19. Rights of the data subject
- Within the scope provided by GDPR, you have the right to:
- access data and receive a copy;
- rectify or supplement data;
- delete data;
- restrict processing;
- data portability if processing occurs automatically based on consent or contract;
- object to processing based on art. 6 sec. 1 lit. f GDPR for reasons related to your particular situation;
- object at any time to direct marketing, including related profiling;
- withdraw consent at any time, without affecting the lawfulness of processing carried out prior to its withdrawal;
- obtaining information about the safeguards applied when transferring data outside the EEA.
- The request can be sent to kontakt@mbpartners.pl. In case of justified doubts, we may ask for information necessary to confirm identity.
- We respond to requests without undue delay, generally within a month. In cases provided for in the GDPR, the deadline may be extended by another two months, of which we will inform along with the reason.
- The right to deletion, restriction, or objection is not absolute. We may still process the data to the extent required by law or necessary for determining, pursuing, or defending claims.
- You have the right to lodge a complaint with the President of the Personal Data Protection Office. Current contact details of the authority are available on the website https://uodo.gov.pl/.
20. Policy Changes
- The privacy policy is an informational document and does not require “acceptance” in the manner that terms and conditions or an agreement do.
- The Controller may update the Policy, particularly in case of changes in law, scope of services, providers, processing purposes, security measures, or cookie configuration.
- The new version will be published with a date. The Controller may additionally inform Users with an account of a change significantly affecting them via email or a message upon login.
- If the change introduces a new purpose or a new provider requiring consent, processing in this regard will commence only after obtaining appropriate consent. Lack of consent for optional analytics, marketing, or chat widgets does not in itself constitute a basis for deactivating the account.
- When changing the scope of providers, purposes, or categories of consents, the Controller should raise the consent_version, update the cookie panel, and re-obtain the User’s choice as required by law.
21. Contact
For matters concerning data protection, exercising rights, or cookies operation, contact us:
MB PARTNER MARCIN BOHDANOWICZ
ul. Rewolucji 1905 r. 82 lok. 6
90-223 Łódź
email: kontakt@mbpartners.pl
Existing On Time Taxi policy (2.08.2026)
Source: ontimetaxi.pl/polityka-prywatnosci/.
Version 2.08.2026
Publication date: 2 August 2026
In this document, we explain what personal data we process, for what purposes, on what basis, to whom we may disclose it, how long we store it, and how cookies, analytical, advertising, communication, and security tools work.
1. Controllers and Scope of Policy
- The operator of the internet service https://ontimetaxi.pl/ and the data controller insofar as it independently determines the purposes and means of processing is ON TIME TAXI SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ with registered office at ul. Nad Rzeką 2, 26-067 Chełmce, Polska, registered in the register of entrepreneurs KRS under number 0001060100, NIP 9592065735, REGON 526477901, hereinafter: “ON TIME TAXI.”
- The joint-controller of data for processes described in pt. 1.6 is MB PARTNER MARCIN BOHDANOWICZ, ul. Rewolucji 1905 r. 82 lok. 6, 90-223 Łódź, NIP 8882894528, REGON 361683930, hereinafter: “MB PARTNER.” ON TIME TAXI and MB PARTNER are hereinafter jointly referred to as “Controllers,” and each individually as an “Controller.”
- The policy applies to the internet service available at the address https://ontimetaxi.pl/, its subpages, forms, panels, and driver portal features provided in the Service or directly in connection with the ON TIME TAXI offer, collectively hereinafter: “Service.”
- For matters concerning the Service, privacy, and personal data, you can contact ON TIME TAXI at kontakt@ontimetaxi.pl or in writing to the address of its registered office. For matters subject to joint administration, you may also contact MB PARTNER at kontakt@mbpartners.pl or in writing to the address indicated in pt. 1.2.
- A detailed description of the consent mechanism and Consent Mode v2 contained in this Policy applies to those pages of the Service where this mechanism has been implemented. Internal employee or administrative systems may be subject to separate informational obligations.
- ON TIME TAXI and MB PARTNER jointly determine the purposes and means of data processing insofar as they jointly organize and manage the process of acquiring a driver to cooperate with ON TIME TAXI, their registration and onboarding, identity and document verification, creation and management of a driver account or profile, activation in the used transport applications, ongoing cooperation management, exchange of information needed for fleet management, settlements and handling of notifications, and protecting these processes against abuses.
- As part of the agreement referred to in Art. 26 GDPR:
- ON TIME TAXI is primarily responsible for running the Service, presenting its own offer, managing vehicle rentals and its own contractual relations, content of ON TIME TAXI campaigns, and fulfilling legal obligations assigned to this company;
- MB PARTNER is primarily responsible for operational and technical support of registration and driver portal, verification of submitted documents, activation support in applications, billing infrastructure, and driver support for processes assigned to them;
- Controllers are jointly responsible for transparently informing the individual about joint administration, security of data exchange, and handling requests related to processes conducted jointly.
- The User may exercise rights under the GDPR with respect to any of the Controllers, irrespective of the agreed division of tasks between them. The main contact point for the Service is ON TIME TAXI, but the choice of contact point does not limit the User's rights.
- Beyond the scope described in pt. 1.6, each Controller acts as a separate data controller concerning their own contracts, accounting, taxes, employment, or cooperation, claims, legal obligations, and activities for which they independently set the purposes and means.
- In some processes, transport application providers, fleet operators, Google, Meta, PZPA Solutions, or other partners may act as separate controllers, joint controllers, or processors — depending on the specific service and concluded agreements.
2. Sources and Categories of Data
We may receive data directly from you, from the other Controller, from an entity that submits you for cooperation, from transport applications and partners involved in service delivery, from FLEETCHECK, official or public registers, and also automatically during the use of the Service.
Depending on the way you use the Service, we may process:
- identification data, in particular, name, surname, date of birth, PESEL, citizenship, document number, image, and signature;
- contact and address data, in particular, address, phone number, and email address;
- data related to legal work status, employment, business activity, social insurance, student status, and tax settlements;
- data concerning driving licenses, medical examinations, licenses, permissions, vehicle, insurance, and documents required for transport services;
- data related to concluded contracts, vehicle rental, issue and return protocols, vehicle mileage and condition, damages, fines, orders, trips, activity in transport applications, settlements, salaries, invoices, costs, cash, deposits, balances, bank account and obligations;
- data on cooperation performance, including the number of trips, acceptance and cancellation rate, periods of activity, fulfillment of offer conditions, and indicators needed to determine commission or rental fee;
- data related to the referral program, including the identifier, code, or other linkage of the referring and referred person, submission date, program conditions fulfillment, and information about benefit accrual and payment;
- information needed to assess the risk of cooperation or vehicle provision, in particular, about unsettled obligations, damages, non-return of vehicle or property, and other events covered by FLEETCHECK rules, if processing such information has a legal basis and has been included in an appropriate informational clause;
- correspondence content, chat, notifications, complaints, attachments, and information provided during contact with support;
- technical data, in particular IP address, session and device identifiers, browser type and version, operating system, language, request date and time, visited page address, referrer, security events, and error logs;
- data on privacy choices, including the scope of consents given or withdrawn, consent mechanism version, update source, and time of choice.
- identifiers and advertising campaign data, if present in the page address, in particular the parameters utm_*, gclid, dclid, gbraid, wbraid, gad_source, and gad_campaignid.
Do not include personal data such as name, surname, email address, phone number, PESEL, or User ID in advertising campaign parameters or other parts of the URL. The Controller does not use the URL as a standard way to transmit an email address or other contact information.
3. Purposes and legal bases of processing
| Purpose | Legal basis |
|---|---|
| Registration, verification, account management, conclusion and execution of the contract, vehicle rental, transportation and course services, payments, settlements, and payouts | Art. 6 sec. 1 lit. b GDPR – taking actions at the request of the person before concluding a contract and executing the contract |
| Determining compliance with the terms of a given offer, including calculating the number of courses, acceptance and cancellation rates, and the resulting commission or rental fee | Art. 6 sec. 1 lit. b GDPR – execution of the contract and application of the terms of the selected offer; Art. 6 sec. 1 lit. f GDPR – legitimate interest in correct settlement of cooperation and preventing errors or abuses |
| Handling referral programs, linking the referring person and the referred person, verifying the fulfillment of terms, calculating and paying the benefit, and preventing multiple or fictitious submissions | Art. 6 sec. 1 lit. b GDPR – execution of program rules and taking actions at the participant's request; Art. 6 sec. 1 lit. f GDPR – legitimate interest in proper organization of the program and prevention of abuses; Art. 6 sec. 1 lit. c GDPR in the scope of accounting and tax obligations |
| Performing tax, accounting, insurance, transport, employee, and other obligations arising from the law | Art. 6 sec. 1 lit. c GDPR – legal obligation of the Controller |
| Handling forms, inquiries, complaints, reports, and contact with service | Art. 6 sec. 1 lit. b GDPR, if the contact concerns a contract or actions before its conclusion, or Art. 6 sec. 1 lit. f GDPR – legitimate interest in communication and service provision |
| Ensuring the security of the Service, authentication, preventing account takeover, spam, fraud, and abuses, keeping security logs, and using reCAPTCHA | Art. 6 sec. 1 lit. f GDPR – legitimate interest of the Controller and Users in protecting systems, data, accounts, and settlements; to a respective extent, Art. 6 sec. 1 lit. c GDPR |
| Establishing, securing, pursuing, and enforcing claims, debt collection, defense against claims, and documenting abuses | Art. 6 sec. 1 lit. f GDPR – legitimate interest of the Controller or an authorized third party |
| Assessing the risk of cooperating or providing a vehicle, verifying damages, unpaid obligations, and returning entrusted property, as well as acquiring or sharing data within FLEETCHECK, if permissible and proportional | Art. 6 sec. 1 lit. f GDPR – legitimate interest in protecting property, fleet safety, limiting abuse, and verifying the credibility of the contractor; to a respective extent, Art. 6 sec. 1 lit. c GDPR. Details, scope of data, source, and storage period should also arise from a separate clause regarding FLEETCHECK |
| Running a newsletter and sending commercial information electronically | Art. 6 sec. 1 lit. a GDPR – consent and Art. 398 Electronic Communications Law |
| Launching the Thulium chat widget and related optional browser memory mechanisms | Art. 6 sec. 1 lit. a GDPR and Art. 399 Electronic Communications Law – functional consent; after starting a conversation, its handling may also rely on Art. 6 sec. 1 lit. b or f GDPR |
| Full analytics of Service usage using Google Analytics | Art. 6 sec. 1 lit. a GDPR and Art. 399 Electronic Communications Law – analytical consent |
| Measuring campaigns, remarketing, audience creation, and ad personalization using Google Ads and Meta Pixel | Art. 6 sec. 1 lit. a GDPR and Art. 399 Electronic Communications Law – marketing consent; regarding the transmission of commercial information also Art. 398 of this law |
| Remembering cookie decisions and demonstrating proper handling of consents | Art. 6 sec. 1 lit. c and f GDPR and the exception concerning the necessary solution to deliver the requested service, as mentioned in Art. 399 sec. 3 Electronic Communications Law |
| Sending limited, cookie-less signals within Advanced Consent Mode in the denied state | Art. 6 sec. 1 lit. f GDPR – legitimate interest in the technical handling of the consent mechanism, obtaining limited aggregate statistics, and assessing the effectiveness of the Service without initiating optional storage and personalization |
Each Controller uses the appropriate legal basis concerning the process for which they are responsible either independently or jointly. If a different legal basis is appropriate for a specific process or additional information is required, the User will receive a separate information clause before the process begins.
4. Voluntary provision of data
- Providing data in the contact form or signing up for the newsletter is voluntary. Lack of data required in the form may prevent sending a response or executing the selected function.
- Providing data required for registration, verification, conclusion, or execution of the contract is voluntary but necessary to use the appropriate service or start the Cooperation.
- Functional, analytical, and marketing consents are voluntary and independent of each other. Their refusal does not block basic account functions, except for the function directly dependent on the given consent, e.g., the Thulium chat widget.
- reCAPTCHA may be required to securely send a public form. If the protection incorrectly prevents form submission, you may contact ON TIME TAXI directly at kontakt@ontimetaxi.pl.
5. Data recipients
Within processes subject to co-administration, ON TIME TAXI and MB PARTNER exchange data necessary to achieve jointly determined purposes. Each Controller may additionally disclose data only to the extent necessary to achieve the purpose:
- to persons authorized by the appropriate Controller, in particular, their employees and collaborators;
- cyber_Folks S.A. and other providers of hosting, infrastructure, backups, mail, SMS, system maintenance, and security;
- Thulium sp. z o.o. – in connection with chat and communication handling;
- Google Ireland Limited, Google LLC and their subcontractors – in connection with Google Tag Manager, Google Analytics, Google Ads, and reCAPTCHA;
- Meta Platforms Ireland Limited, Meta Platforms, Inc. and their subcontractors – in connection with Meta Pixel and Meta advertising services;
- payment operators, banks and entities handling settlements;
- accounting offices, tax advisors, law firms, insurers, debt collection entities, and entities providing auditing services;
- transport application operators, fleet entities, services and other partners involved in the implementation of transport, rental, repair, insurance or settlement of the selected service;
- postal operators, if necessary for the shipment of documents;
- PZPA Solutions sp. z o.o. and entities related to the FLEETCHECK register – only in cases, scope, and on bases described in the General terms of cooperation, relevant agreements, and separate information;
- public authorities, courts, bailiffs and other authorized entities, if the obligation or right to transfer data arises from the law.
MB PARTNER is not the processor of ON TIME TAXI in the scope where it jointly determines the purposes and means of processing. In other expressly entrusted processes, the role of MB PARTNER may result from a separate entrustment agreement.
Controllers do not sell personal data as a set of contact data.
6. Data transfer outside the European Economic Area
- In connection with the use of Google, Meta, Thulium services or their subcontractors, data may be processed outside the European Economic Area, particularly in the United States.
- Transfers occur, depending on the recipient and current legal status, based on a European Commission decision declaring an adequate level of protection, recipient's participation in the EU–US Data Privacy Framework, standard contractual clauses approved by the European Commission, and additional protection measures.
- Information about the mechanisms used by Google is available in the document Data transfer frameworks, and information regarding Meta in Meta Privacy Policy.
- Information about adequate safeguards or a copy can be obtained by contacting the Controller. Some documents may be provided excluding information covered by trade secrets or security requirements.
7. Data retention period
| Type of data or purpose | Retention period or criterion |
|---|---|
| Account and contract execution | for the duration of the account's activity and the term of the contract, and then until the end of the limitation period for claims or longer, if required by regulations |
| Tax, accounting, and insurance documentation | for the period required by relevant regulations, generally 5 years counted according to the rules set for the obligation concerned |
| Referral program data | for the duration of the program and service settlement, then until the limitation period for claims expires; accounting and tax documents for the period required by law |
| Inquiries and forms not related to a contract | for the period necessary to respond and conduct correspondence, then up to the limitation period for potential claims |
| Complaints, disputes, debts, and abuses | until the final or definitive conclusion of the matter, fulfillment of obligations, and expiration of the claims limitation period, taking into account archiving obligations |
| Verification in FLEETCHECK and data obtained in connection with risk assessment | for the period necessary to conduct verification and make a cooperation decision, and after its commencement, for the duration of cooperation and until the limitation period for pursuing or defending claims; the data retention period in the register itself is defined by a separate FLEETCHECK clause and the operator's rules |
| Newsletter and direct marketing | until withdrawal of consent or effective objection, not longer than 3 years from the last documented activity, unless earlier deletion arises from regulations or adopted procedure |
| Calls conducted by Thulium | for the period necessary to handle the case, ensure quality, and defend claims; if the call is recorded, information about recording and the specific period is provided prior to the start of the recording |
| Technical and security logs | generally up to 12 months, and in the case of an incident, abuse, or dispute – until the conclusion of clarification and the expiration of the appropriate claims period |
| Cookie consent choices | 180 days from setting or recreating the choice, until withdrawal of consent or change in the consent mechanism version |
| Google Analytics data at user and event level | up to 14 months, in accordance with the service configuration; this setting does not necessarily remove previously aggregated reports |
| Data and advertising identifiers | in accordance with consent settings, cookie table, and provider policies; campaign reports are retained no longer than necessary for analysis and settlement of the campaign, generally up to 26 months |
After the appropriate period, the data is deleted, anonymized, or access to it is restricted, unless further storage is required by law.
8. Hosting, logs, and security
- The service is hosted on cyber_Folks infrastructure. Servers and network devices may automatically record logs containing, among other things, IP address, request and response time, resource address, HTTP response code, referrer, information about the browser and device, and diagnostic data.
- We apply technical and organizational measures tailored to the risk, in particular TLS connection encryption, password hashing, access control, additional authentication mechanisms, backups, security event logging, software updates, and limiting the scope of data shared with external tools.
- Only persons and entities who need access to perform their tasks and are subject to confidentiality obligations or an appropriate agreement receive access to the data.
- No method of transmission or storage of data guarantees complete elimination of risk. In case of a data protection breach, we take actions required by the GDPR, including — if applicable — notifying the President of the UODO and the data subjects.
9. What are cookies and similar technologies
- Cookies are small pieces of information saved in the browser or on a device. The service may also use the browser's local storage, pixels, tags, and similar technologies.
- Cookies can be session-based, deleted after closing the browser, or persistent, stored for a specified time or until removed.
- First-party cookies are set by the currently visited host of the Service. Third-party cookies or similar identifiers may originate from an external provider, e.g., Google or Meta.
- The consent mechanism distinguishes the following categories:
- necessary and security – required for logging in, session maintenance, form protection, security, and remembering privacy choices;
- functional – enabling additional features, in particular the Thulium chat widget;
- analytical – used for comprehensive measurement of Service usage with Google Analytics;
- marketing – used for ad measurement, remarketing, audience creation, and ad personalization using Google Ads and Meta Pixel.
- Functional, analytical, and marketing cookies are optional and are not saved or read before obtaining proper consent, except as noted below for Advanced Consent Mode's cookie-less signals and reCAPTCHA's operation as a protection for public forms.
10. Consent panel and Consent Mode v2
- Before launching the Google Tag Manager container, optional consent states are set as denied. The user can independently enable or disable functional, analytical, and marketing consent.
- For Google services, analytical consent controls the analytics_storage parameter, and marketing consent controls the ad_storage, ad_user_data, and ad_personalization parameters. Functional consent controls the activation of the Thulium widget and related functional storage.
- The choice is stored for 180 days in a host-only cookie mbpartner_cookie_consent. Host-only means that the cookie is assigned to a specific host where the choice was made and is not automatically shared with all subdomains.
- The choice cookie may contain the scope of consents, the version number of the mechanism, and information needed to correctly restore the decision. It does not contain a password, balance, contract data, or form content.
- After saving and restoring the choice, the Service places the portal_consent_update and portal_consent_restored events in the internal data layer. These events may contain fields portal_consent_functional, portal_consent_analytics, portal_consent_marketing, portal_consent_version, and the update may also include portal_consent_source. These fields should not contain identifiable User data.
- After 180 days, removal of the cookie, or a change in the version of the consent mechanism, the Service may request the choice again.
- Consent can be changed or withdrawn at any time via a visible link or the “Cookie settings” button on the Service. Withdrawal of consent is free and does not affect the legality of actions performed before its withdrawal.
- After withdrawing functional consent, the page may be refreshed to remove the previously loaded Thulium widget. Withdrawal of analytical or marketing consent changes Consent Mode to denied, and tags operating in this mode stop saving and reading relevant optional cookies and sending full measurement data. Previously saved cookies may remain in the browser until deleted or expired, but should not continue to be used by properly configured tags when in denied state.
11. Advanced Consent Mode – pre-consent and denial signals
- The Service uses Advanced Consent Mode.This means that the Google Tag Manager container and Google tags may be loaded before consent is given, with the default state denied.
- In the denied state, Google should not save or read optional analytical or advertising cookies nor use data for ad personalization. However, tags may send cookie-less consent state signals and limited measurements to Google for statistics and modeling.
- According to Google's documentation, such signals may include, among others, the consent state, event time, User-Agent, referrer, random value generated upon page load, information on the presence of an ad click identifier, and limited information about the visited page. Network transmission also involves processing the IP address; Google indicates that in certain advertising signals, the address is truncated upon collection.
- The page address transmitted to GA or Google Ads is sanitized. The address and page path and only campaign parameters utm_*, gclid, dclid, gbraid, wbraid, gad_source, and gad_campaignid may be retained. Other query parameters and address fragments are removed.
- The container cannot replace the sanitized address with the full document.location or transmit email addresses, phone numbers, PESEL, account identifiers, balances, contract data, form content, document data, or other information enabling direct identification of the User to analytical or advertising tools.
- Campaign parameters and click identifiers cannot contain personal data. Controllers require that individuals configuring ads do not place such data in the values of utm_* or other address parameters.
- Production tracking is started only when the request host matches the production address configured as PORTAL_URL. Local and test environments should not feed production analytical and advertising services.
- On password verification and change pages containing a one-time token, especially at addresses /verification/?v=... and /change-password/?v=..., external tracking is disabled, and the response uses the header Referrer-Policy: no-referrer. This is to limit the risk of transmitting the token in the page address or referrer header.
- Native Google Analytics and Google Ads tags use built-in Consent Mode controls. Third-party tags and Custom HTML tags must have additional triggering conditions corresponding to the appropriate consent category.
- Cookie-less signals from Advanced Consent Mode are not equivalent to completely blocking connections or data transfers to Google. Users who wish to technically block all connections from Google domains may use browser settings or a tool blocking external resources. They may also object to processing based on legitimate interest by contacting the Controller.
12. Google Services
12.1. Google Tag Manager
Google Tag Manager is used to manage tags and convey the current consent state to them. The container itself can initiate a connection to Google. What data is processed subsequently depends on the container configuration, the tags triggered, and the consent choices.
12.2. Google Analytics 4
Upon granting analytical consent, Google Analytics may use cookie identifiers, device information, browser, approximate location derived from IP address, visit source, visited pages, and events to create statistics and improve the Service. We do not transfer to Google Analytics any data that would enable Google to directly identify a person, such as an email address or phone number.
Without analytical consent, due to the Advanced Consent Mode, the measurements described in point 11 may be sent without cookies. Google may use them for statistical data modeling.
12.3. Google Ads
Upon granting marketing consent, Google Ads may be used for measuring conversions, remarketing, creating audience groups, and ad personalization. Without consent, the parameters ad_storage, ad_user_data, and ad_personalization remain set as denied; limited signals without cookies may be sent for modeling, without triggering personalization.
More information is available in the Google Privacy Policy and in the description of Consent Mode.
13. Meta Pixel
- Meta Pixel is loaded only upon granting marketing consent.
- Upon obtaining consent, Meta Pixel may process information about visits and activities on the Service, IP address, device and browser information, cookie identifiers, referrer, and campaign identifiers. The data may be used for measuring ad effectiveness, creating audience groups, remarketing, and ad personalization on Meta platforms.
- We do not transfer email addresses, phone numbers, User identifiers, balances, contract data, or form contents via the Pixel unless a separate function based on explicit legal grounds is implemented and described in the future.
- Regarding the collection and transfer of event data via Pixel, ON TIME TAXI and Meta may act as joint controllers. If a campaign is conducted and utilized jointly by ON TIME TAXI and MB PARTNER, joint administration may also include MB PARTNER. In other respects, Meta may act as a separate controller in accordance with its own terms.
- More information is available in the Meta Privacy Policy and the Meta Cookies Policy.
14. Thulium Chat Widget
- The Thulium widget is not downloaded before granting functional consent. Denying consent does not limit the ability to contact the Controller via email.
- Once activated, the widget may process session identifiers, IP address, device and browser information, connection time, and data and content voluntarily provided in the conversation.
- Do not send special category data, full identity document data, passwords, one-time codes, or data not necessary for resolving the case through chat.
- Thulium sp. z o.o. may process data on behalf of the proper Controller to provide the service, and for its own technical, security, or legal purposes – in accordance with its own privacy policy.
- Upon revoking functional consent, the Service refreshes the page to remove the loaded widget and stop its further operation.
15. reCAPTCHA
- Public forms are protected by Google reCAPTCHA to recognize automated submissions, spam, abuse attempts, and attacks.
- reCAPTCHA remains active regardless of optional consents, as it serves the security of the form and the Service. It is triggered on pages where a protected form is located, not for marketing analytics.
- The service may analyze the IP address, User-Agent, device and browser information, time, site usage method, movements and interactions, and other signals needed for risk assessment. Google indicates that reCAPTCHA sets the necessary _GRECAPTCHA cookie for risk analysis.
- The basis for processing by the proper Controller is art. 6 section 1 letter f GDPR – legitimate interest in protecting forms, users, and systems. Access to information on the device is considered necessary for the secure provision of the form requested by the User.
- Use of reCAPTCHA is subject to the Google Privacy Policy and the Google Terms of Service.
16. List of main cookies and similar identifiers
Exact names may change due to provider updates. The table describes known and typical identifiers for the specified configuration.
| Name or type | Provider | Purpose | Category | Maximum typical period |
|---|---|---|---|---|
| mbpartner_cookie_consent | ON TIME TAXI / MB PARTNER, depending on the host | remembering the scope of consents and version of settings | necessary | 180 days |
| session cookies, authentication and form security | ON TIME TAXI / MB PARTNER, depending on the host and function | login, session maintenance, protection against unauthorized requests and abuse | necessary | session or short security period resulting from configuration |
| _GRECAPTCHA and related security signals | Google reCAPTCHA | risk analysis, protection against bots and spam | necessary and security | according to Google configuration, generally up to 180 days |
| Thulium widget session identifiers | Thulium | initiation and maintenance of chat conversation | functional | session or period resulting from the current widget configuration |
| _ga, _ga_* | Google Analytics | differentiation of browsers and creation of service usage statistics | analytical | up to 24 months |
| _gcl_au, _gcl_* | Google Ads | measuring advertising effectiveness and conversions | marketing | generally up to 90 days |
| _fbp and related Meta identifiers | Meta | advertising measurement, remarketing and audience creation | marketing | generally up to 90 days |
17. Managing cookies
- The most convenient way to manage consents is via the "Cookies Settings" panel available in the Service. It allows you to accept all optional categories, reject them, or make a separate choice.
- Browser settings additionally allow displaying, deleting, and blocking cookies and site data. Instructions are available in the documentation of browsers, particularly Chrome, Firefox, Safari, Edge, and Opera.
- Blocking necessary cookies may prevent logging in, maintaining a session, saving a privacy choice, or securely sending a form. Rejecting functional, analytical, or marketing cookies should not block basic use of the account.
- Deleting cookies in the browser does not automatically remove data that was previously correctly recorded in the systems of the Controller or the provider. To exercise rights regarding such data, the principles described in section 19 should be used.
18. Profiling and Automated Decision Making
- Upon giving marketing consent, Google and Meta may use data for advertising profiling, in particular assigning the User to audience groups, measuring conversions, and selecting ads. Detailed rules are specified in these providers' policies.
- Advanced Consent Mode may allow Google to model statistics or conversions based on limited signals from those who have not consented to full measurement.
- reCAPTCHA automatically assesses the risk of submission. The result may cause rejection or additional verification of the form, but the User may use an alternative contact with the Controller.
- Controllers may use automatic rules or indicators to calculate the terms of the offer, detect abuse, assess debt risk, and direct cases for employee verification. Data from FLEETCHECK or trip indicators should not constitute the sole basis for a decision causing legal effects or similarly significantly affecting a person, without ensuring a legal basis, required information, and the right to human intervention. Unless the User receives separate information, Controllers do not make such decisions solely automatically in the sense of art. 22 GDPR.
19. Rights of the Data Subject
- Within the scope provided by GDPR, you have the right to:
- access the data and receive a copy;
- rectify or complete data;
- delete data;
- restriction of processing;
- data portability, if processing is automated based on consent or contract;
- object to processing based on Art. 6 sec. 1 letter f of the GDPR for reasons related to your particular situation;
- object at any time to direct marketing, including profiling related thereto;
- withdraw consent at any time, without affecting the lawfulness of processing carried out before its withdrawal;
- obtain information about the safeguards applied when transferring data outside the EEA.
- Requests regarding the Service or joint process can be sent to kontakt@ontimetaxi.pl or kontakt@mbpartners.pl. Addressing a request to one of the Joint Controllers is effective even if its execution requires the cooperation of the other. In case of justified doubts, we may ask for information necessary to confirm identity.
- We respond to requests without undue delay, generally within a month. In cases provided for in the GDPR, the deadline may be extended by an additional two months, of which we will inform you along with the reason.
- The right to erasure, restriction, or objection is not absolute. We may continue to process data as required by law or necessary to establish, exercise, or defend claims.
- You have the right to lodge a complaint with the President of the Personal Data Protection Office. Current contact details of the authority are available on the website https://uodo.gov.pl/.
20. Policy Changes
- The privacy policy is an informational document and does not require "acceptance" in the same way as a regulation or an agreement.
- The Controllers may update the Policy, particularly in case of changes in law, scope of services, suppliers, processing purposes, responsibility distribution, security measures, or cookie configuration.
- The new version will be published with a date. For changes that significantly affect users with an account, Controllers may additionally inform by email or a notification upon logging in.
- If a change introduces a new purpose or a new supplier requiring consent, processing in this regard will begin only after obtaining the appropriate consent. Lack of consent for optional analytics, marketing, or chat widget does not in itself constitute grounds for account deactivation.
- When changing the scope of suppliers, purposes, or categories of consents, consent_version should be raised, the cookie panel updated and the User's choice re-obtained as required by law.
21. Contact
The main contact point for matters regarding the Service, data protection, rights execution, or cookie operation:
ON TIME TAXI SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
ul. Nad Rzeką 2
26-067 Chełmce, Polska
KRS 0001060100, NIP 9592065735, REGON 526477901
email: kontakt@ontimetaxi.pl
Joint Controller in the scope described in item 1.6:
MB PARTNER MARCIN BOHDANOWICZ
ul. Rewolucji 1905 r. 82 lok. 6
90-223 Łódź
NIP 8882894528, REGON 361683930
email: kontakt@mbpartners.pl
The current version of this Policy is published at https://ontimetaxi.pl/polityka-prywatnosci/. Information about independent processes of MB PARTNER is also available in MB PARTNER privacy policy.