Privacy and Cookie Policy of MB Partner and On Time Taxi
This is a translation of the published Polish version. You can display the Polish original by selecting the document language.
Contents
Privacy and Cookie Policy of MB Partner and On Time Taxi
The effective date is indicated in the published version. The description of planned new mobile application features applies from their actual release.
1. Controllers, Joint Account, and Scope of the Policy
The policy describes the processing of data of candidates, drivers, couriers, referrers, clients, and individuals contacting us. It applies to the websites mbpartners.pl and ontimetaxi.pl, portals kierowca.mbpartners.pl and portal.ontimetaxi.pl as well as proprietary mobile applications of MB Partner and On Time Taxi for Android and iOS. The transport and delivery platforms you collaborate with have their own privacy information.
- MB PARTNER MARCIN BOHDANOWICZ, ul. Rewolucji 1905 r. 82 lok. 6, 90-223 Łódź, NIP 8882894528, REGON 361683930, contact: kontakt@mbpartners.pl, is the data controller for its own account and own cooperation processes, agreements, settlements, taxes, insurance, license management, and claims.
- ON TIME TAXI LIMITED LIABILITY COMPANYul. Nad Rzeką 2, 26-067 Chełmce, KRS 0001060100, NIP 9592065735, REGON 526477901, contact: kontakt@ontimetaxi.plis the data controller with respect to its own agreements, fleet and platform account, promotions, receivables, damages, taxes, carrier obligations and claims.
- The controller of a document or activity is the entity conducting the specific process. Check the agreement page, promotion organizer or information provided with the specific service. Both companies may have their own agreements; using the OTT brand does not automatically transfer all MB payer obligations to OTT.
- MB PARTNER operates a joint CRM, API infrastructure and technical account support, decides on onboarding and verification in processes it handles, and coordinates privacy matters. The account and password are shared; each application can have a separate session, phone registration, and push settings. Logging into another portal does not create a second account or a new data use purpose by itself.
- MB technically and accountingly processes OTT-commissioned processes as a processor under its documented instruction. OTT conducts its own fleet, leasing, and promotion processes. Necessary data for each company's own settlement, damage, or obligation may be exchanged between separate controllers. For each action, we distinguish the controller's own purpose from the commissioned service; CRM ownership and contract name do not determine all roles.
- OTT services are performed by employees of MB PARTNER who also handle MB matters and have access to the entire shared CRM; access is not limited to OTT services only. In MB matters, they operate within assigned tasks, and MB in OTT-commissioned processes operates on its documented instruction. Access to the entire database does not entitle use for any purpose; health, criminal record, and legalization documentation requires proper authorization and protection. Delegation between companies and authorizing a specific employee are separate elements of this process.
- MB PARTNERS CARS SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄul. Nad Rzeką 2, 26-067 Chełmce, KRS 0001034777, NIP 9592062151, may appear as the app publisher in the App Store. According to the accepted scope, this corresponds to app publication, without this company having access to driver data. The publisher's name in the store does not change the controller of your agreement or documentation.
- No data protection officer has been appointed. Privacy matters are coordinated by MB PARTNER at the address provided above. You can also contact OTT directly regarding its processes.
2. Sources and categories of data
We receive data from you upon submission, registration, document submission, contract conclusion, order, contact, or use of services. In the context of a given process, we also receive data from transportation and delivery platforms, from the second controller MB/OTT, payment and delivery operators, authorized bodies, and public registers. Data not directly received from you includes, among others, platform results and activity, settlements, vehicle data, and information necessary to handle a specific agreement. Information about the appropriate source and scope is available during the process or upon your request.
- Identification and contact data: first name, last name, date of birth, PESEL or appropriate identifier, citizenship, address, phone, email, and city.
- Account, application, contract, and cooperation status data; signatures and confirmations, history of changes relevant to service, referrer and referred person data.
- Billing data: bank account, income and remuneration, time of contract performance, contributions, taxes, PPK, invoices, balance, fees, deposits, receivables, and payments. For a given function, also fuel card and transaction data.
- Identity documents, driving license, permissions, and licensing documentation; vehicle data, policies, rental or lending, reservation, damages, and returns. The scope of documents depends on the service performed.
- Documents confirming student status or insurance, parental/guardian consent for a relevant activity, and residency and legal work delegation documents for a foreigner.
- In the TAXI process: required medical and psychological certificates on the presence or absence of contraindications and documents concerning non-criminality within the scope allowed by law. We do not need full diagnoses, raw test results, or medical histories for the normal operation of an account.
- Activity and settlement data obtained from platforms: orders, acceptances and cancellations, revenues, and indicators used to present results, manage cooperation terms, or explain abuse.
- Content of contacts, reports and complaints, communication metadata, and call recordings if the call is recorded and you have been informed of this beforehand.
- Pseudonymous User-ID associated with the account — if the GA4 measurement implemented indeed uses it and you consent to analytics; the scope is described in point 12.
Mobile applications and technical data
Applications provide access to the account, documents, contracts, settlements, invoices, payments, fuel cards, reservations, fleet, orders, and appropriate promotions. MB Partner also includes thermal bag orders; OTT includes activity summaries and program terms. Access to a given function depends on permissions and actual account data.
We process information about the session and login, IP address, request technical data, language, and trusted device identifier. For push notifications additionally: installation identifier in our system, FCM token, application brand, platform, notification permission, registration activity, message title and content, and the result of the sending attempt. The proprietary installation identifier differs from the Firebase Installation ID (FID) processed by Google.
You enable the camera to take a photo of a document. Instead, you can indicate an existing file. The application sends the selected files, not the entire gallery. In the described scope it does not use the phone's GPS, contact book, microphone, or biometric logging. Platform data may contain city and transport activity information, regardless of phone permissions.
On Android, Google SMS User Consent can, upon your one-time permission, complete the login code from a single SMS. It does not provide access to SMS history. You may refuse and enter the code manually. The current attempt is listened to for 5 minutes; this is not the period for retaining logs on the server side.
3. Purposes and legal bases for processing
The indicated basis relates to a specific purpose and administrator. We do not use all bases interchangeably for every piece of information. Bases from Art. 6 GDPR do not replace additional requirements for health, criminal records, or access to information on the device.
Documents are not assigned to a single contract. Cooperation documentation is protected by any active contract; its retention period begins after the latest termination of all contracts. A regular copy of an identity document, a selfie, and a screenshot of a partner change have separate short terms from the end of verification or partner change, even with an active contract. A foreigner's identity document required for work legalization has its own rule. Dates are calculated on an ongoing basis taking into account separate obligations and blocks of specific cases.
| Purpose | Basis and scope |
|---|---|
| Consideration of the application, taking actions at your request, account, and contract execution | Art. 6 sec. 1 lit. b GDPR — data necessary for appropriate pre-contractual actions or contract execution; includes appropriate order, rental, reservation, and settlement. |
| Taxes, accounting, contributions, and payer documentation | Art. 6 sec. 1 lit. c GDPR in connection with appropriate obligations including the Tax Ordinance, Accounting Act, tax laws, Social Insurance System Act, and the Act on Pensions and Disability Pensions from FUS. Concerns documentation actually subject to a given obligation. |
| Confirmation of order hours and appropriate PPK duties | Art. 6 § 1 letter c GDPR in connection appropriately with Art. 8a–8c of the Act on the Minimum Wage and the Employee Capital Plans Act, if applicable to the person concerned. |
| Legal employment of a foreigner | Art. 6 § 1 letter c GDPR in connection with the relevant obligations of the Act of 20 March 2025 on the conditions of admissibility of employment of foreigners in the territory of the Republic of Poland, particularly Art. 4–5, considering the appropriate procedure and exceptions. |
| Required licenses and criminal record checks for taxi drivers | Art. 6 § 1 letter c GDPR and, for criminal record data, Art. 10 GDPR in connection with the relevant scope of the Road Transport Act, particularly Art. 6 § 1 point 2 letter b and Art. 8 § 3 point 4. This requirement also includes non-employed persons personally performing transport services for the carrier; it does not automatically apply to all couriers. |
| Required assessment of the driver's ability to perform transport | Art. 6 § 1 letter c and additionally Art. 9 § 2 letter b GDPR within the scope of statutory obligations for work capability assessment, with Art. 39j–39m of the Road Transport Act. Art. 39l § 1 point 3 letter b provides for retaining copies of the required judgments throughout the driver's employment period; Art. 39m requires the appropriate application of these requirements to others personally performing transport. |
| Participation and settlement of a specific promotion | Art. 6 § 1 letter b GDPR with regard to the terms of the program you join; letter c for required tax settlements. The organizer is responsible for their program. |
| Contact, handling matters and complaints | Art. 6 § 1 letter b GDPR when the matter relates to your contract or actions on your request; for other necessary handling, Art. 6 § 1 letter f — interest in providing a response and ensuring continuity of service. For requests regarding data — letter c in connection with GDPR. |
| Account security, logging in, preventing abuses and explaining incidents | Art. 6 § 1 letter f GDPR — protection of accounts, individuals, data, and correctness of settlements, in a necessary and proportional scope; specific data protection obligations also arise from GDPR. |
| Establishment, exercise, or defense of specific claims | Art. 6 § 1 letter f GDPR — protection of rights in a specific case, with scope and time limitation. For necessary health data additionally Art. 9 § 2 letter f; this does not constitute a general authorization to retain criminal record data disregarding Art. 10. |
| Activity summaries, wages, and analysis of correctness | Art. 6 § 1 letter b concerning the fulfillment of established conditions and presentation of your result; Art. 6 § 1 letter f for necessary discrepancy explanations, quality control, and protection against abuses. The basis does not include arbitrary use of data in advertising. |
| Email or SMS about offers and new services | Prior consent is required for the specific purpose, entity, and channel, considering Art. 6 sec. 1 letter a GDPR and Art. 398 Electronic Communications Law. Consent is voluntary and can be withdrawn. |
| Voluntary request for feedback via TrustMate | Separate prior consent for the specified controller, purpose, and chosen channel — Art. 6 sec. 1 letter a GDPR and, as applicable to specific communication, Art. 398 ECL. Familiarity with the policy does not provide this consent. |
| Optional activation of push channel and delivery identifiers | Separate user choice and prior information; where consent is required, Art. 6 sec. 1 letter a GDPR and Art. 399 ECL apply. Android/iOS permission to display messages is not consent for all other Google purposes or marketing. |
| Operational push content concerning your case | Basis of specific information: Art. 6 sec. 1 letter b for contract execution, letter c for proper obligation, or letter f for necessary security and services. Disabling the optional channel does not remove the mandatory information obligation. |
| Optional chat, analytics (including implemented User-ID), and website advertising identifiers | Appropriate functional, analytical, or marketing consent — Art. 6 sec. 1 letter a GDPR and Art. 399–400 ECL for terminal operations; subsequent handling of voluntarily initiated case is based on relevant content. |
4. Voluntariness of data provision
Providing data when reporting is voluntary, but the lack of data needed for contact or verification may prevent service. Data indicated as necessary for contract conclusion or execution, settlements, or fulfillment of a specific legal obligation is required in this process. We indicate its purpose by the field or document; you should not send more documentation than required.
Refusal of marketing, optional push, analytics, or device does not block basic account functions. Refusal of device allows indicating an existing file. Currently, we do not run a separate newsletter; information sent by email/SMS may, however, have a marketing purpose, depending on the content.
In some courier services, cooperation with a person from 16 years of age is considered according to the specific service, law, and platform requirements. Parental/guardian consent for an activity related to the contract is separate from consent for optional data processing. It does not mean permitting a minor to perform TAXI or the right to collect all documents of an adult driver. We limit the guardian's data to the needs of demonstrating authorization and the required consent for the activity.
5. Data recipients
The scope of sharing depends on the purpose. Personnel receive data needed for the assigned task, and the external recipient — the scope appropriate for the service. An entity acting on our behalf requires appropriate entrustment conditions; other recipients may process data as separate controllers.
| Recipient or category | Purpose and scope |
|---|---|
| MB PARTNER and ON TIME TAXI and the personnel servicing both companies | Processes described in section 1, including cooperation and personnel of MB, vehicle, platform account, promotion, settlement or damage of OTT, and commissioned service. MB employees also servicing OTT have access to the entire shared CRM. The use of data requires a proper task, purpose, and authorization, without freely using the entire database for OTT's own purposes. |
| Transport and delivery platforms, e.g., Uber, Bolt, FreeNow, and appropriate courier platforms | Registration, activation, and cooperation support on the selected platform; required documents, identifiers, and settlements within the appropriate process. Platforms have their own rules. |
| cyber_Folks S.A. | Hosting/VPS and CyberStorage space for the account, database, and documentation; technical access related to the service and its protection. |
| Google Workspace | MB and OTT mail: recipients, senders, message contents, and attachments. We do not use Google Vault according to the adopted configuration. |
| Thulium | Telephone contact, recordings, notifications, and chat; the MB account handles matters for both brands. The person is informed about recording before it begins. |
| SMSAPI | Phone number, message content, and technical data necessary to deliver SMS and manage the sending. |
| MailerLite | Messages related to launch and activation, tutorials, and information about new services; recipient data, appropriate content, and technical campaign data. We assess the purpose and consents according to the content of the message. |
| TrustMate S.A. | At the request of the appropriate administrator, handling voluntary invitations, reminders, and thanks regarding opinions, only after a separate selection. We provide contact appropriate for the selected channel and minimal information necessary for the invitation after the service. We do not provide document scans, health data, KRK or settlements for this purpose. For its own service and issued opinion, TrustMate operates according to its own rules described in section 14. |
| SumUp | Payment handling. In the reported sales process, we provide the customer's email; the operator may independently obtain the payer's data and payment instrument according to its service. We do not receive full card data for this reason. |
| InPost and DPD | First name, last name, phone number, and address or relevant delivery point — execution of the ordered shipment. |
| Google Firebase Cloud Messaging and Firebase Installations; Apple APNs on iOS | Identifiers and technical data of installation/connection and the title and content of the message for push delivery. Our API handles logging, documents, and billing, not Firebase Auth/Firestore/Storage. |
| Google reCAPTCHA Enterprise and SMS User Consent | Security of registration and password reset and optional one-time SMS code entry on Android; scope described in sections 2 and 15. |
| OpenAI — corporate ChatGPT Business | Support for authorized employees in statistics, calculations, performance analysis, and abuse. Input scope and reports require minimization and human verification; we do not assume anonymity of every set solely due to the removal of the name. |
| Accounting, legal services, public authorities, courts, and authorized institutions | Proper documents for accounting, contributions, legalization, licenses, control and claims, in accordance with the law and the case handled. |
Enova is a local HR-accounting database. The mere use of the software does not imply the transfer of the database to its manufacturer. Paper documents remaining with accounting have limited access and a term appropriate for their category. Airtable is currently not used according to the owner's declaration; the scope of historical records, attachments, and copies must be separately explained.
6. Data transfer outside the European Economic Area
Our VPS cyber_Folks is located in Gdańsk, Poland, according to confirmed organizational configuration. This does not mean all data with Google, Apple, OpenAI, and other recipients remain in Poland or the EEA. Transfer outside the EEA may also result from remote access or further processing, irrespective of the main database location.
Firebase Cloud Messaging operates on Google's global infrastructure. Proper locations and security of external services depend on the actual agreement and configuration. Information on specific transfer and a copy of appropriate safeguards can be obtained at the MB PARTNER contact address.
7. Document storage and retention period
The period is determined separately for the document, purpose, controller, and payer. Contract termination, document expiry, account blocking, operational data deletion, and archive deletion are different events. We do not apply a single rule of "5 years after any contract" or "a year without logging in" for all individual's data.
In our process for an order constituting a title for insurance, the date of reporting to ZUS corresponds to the day of signing the relevant contract. We determine the first relevant order in the history of the given payer. This does not change statutory events initiating the retention of ZUS reports and pension-insurance evidence described below.
If a document is genuinely needed for multiple purposes, it remains until the end of the longest relevant obligation; unnecessary scope is subject to limitation. Active cooperation protects the necessary documentation of this cooperation; after the termination of all agreements, its organizational period is counted from the latest end. A new agreement does not replace statutory dates relevant for other evidence, such as tax, ZUS report, or time confirmation.
| Category | Period or event determining the deadline |
|---|---|
| Basic candidate account without starting cooperation | Up to 12 months from the actual activity aimed at continuing the application, provided there is still a justified need; earlier if the purpose is withdrawn or expires earlier. A technical change, import, cron, and outgoing message do not renew the deadline. Waiting for an office or platform requires an assessment of the specific case. Scans do not automatically inherit this period. |
| Identification card or passport used solely for ordinary identity verification | The last day of storing the copy is the date of confirmed completion of verification + 30 calendar days, also during active cooperation. After this day, the unnecessary copy is removed in the next retention task cycle; earlier if the purpose ceases — without undue delay. A minimal verification result remains if needed to document the process. This rule does not apply to a document required for the legalization of a foreigner's work or a document retained for a specific case. |
| Driver's profile picture, required equipment photo, and vehicle photo used for account service in the app | For the required period of cooperation and generally up to 30 days from the termination of all contracts constituting cooperation. If the purpose ceases earlier, unnecessary photos are removed without undue delay. The profile photo is not a verification selfie. Evidence of a specific event, damage, or case is separated into appropriate documentation. |
| Technical documentation of the vehicle and signage in fleet service or license | For the period of use and required service, then organizationally accepted 2 years from confirmed vehicle withdrawal or closure of service document, depending on the actual purpose. Documents required further for the device, settlement, or specific case retain an appropriate separate period. The expiration date, import, or modification does not replace the date of completion of the purpose. |
| Agreements and reservation settlement documentation of the vehicle | Until the execution of the agreement and closure of the case, or until the termination and final settlement of the reservation, then generally up to 6 years after the end of the year of this event, within the necessary evidential scope. A longer applicable obligation or a specific unresolved case takes precedence; the justification for retaining the case documentation is checked every 3 months. |
| Signature material and document copies | The signature material is retained for the necessary period appropriate for the documents it records signing, considering a longer applicable obligation. Unnecessary working copies are removed after confirming the retention of signing evidence. We do not apply the usual photo period to the signature material. |
| Selfie with document | The last day of storage is the date of confirmed completion of verification + 7 calendar days, also during active cooperation. After this day, the unnecessary image is removed in the next retention task cycle; earlier if the purpose ceases — without undue delay. A specific necessary incident evidence is separated into the appropriate case. |
| Screenshot of partner change/previous cooperation | The last day of storage is the date of confirmed completion of partner change + 7 calendar days, also during active cooperation. After this day, the unnecessary image is removed in the next retention task cycle; earlier if the purpose ceases — without undue delay. A specific necessary settlement or incident evidence is separated into the appropriate case. |
| Abandoned activation scans | After 90 days without candidate action on the application, we conduct a review. For redundant scans, the last storage day is the date of confirmed closure of the application plus 7 calendar days; deletion occurs after this day in the next retention task cycle. The threshold of 90 days does not automatically close an application awaiting a device/platform and does not renew the period. A separate necessary evidence of proceedings has its own category. |
| Driver’s license, extracts, and other ordinary TAXI licensing documentation | The adopted organizational period of the limited archive is 2 years from the termination of all contracts constituting the person's cooperation, without assigning each file to a single contract. For ongoing cooperation, we retain the necessary documentation; unnecessary data is removed earlier after the purpose ceases. A separate obligation or specific case may specify the appropriate, documented period. |
| Copies of driver medical and psychological certificates | During the cooperation period, we retain required copies of certificates, in accordance with the applicable obligations of the Road Transport Act. After cooperation ends, we retain them as necessary to establish, pursue, or defend claims related to the performance of transport services, especially as proof of having the required certificates during the execution of the contract. The basis of this archive is Art. 6 sec. 1 letter f in connection with Art. 9 sec. 2 letter f of GDPR, after documenting the necessity. Standardly, no longer than 6 years from the end of the year the entire cooperation ends; necessity is subject to annual review, and unnecessary data is removed earlier. This is an internal organizational period, not a statutory obligation to store for six years. We retain only copies of certificates, including those replaced by subsequent examinations, if they document an earlier period of work; not medical treatment documentation or test results. For cooperation terminated on 12 October 2026 r., the standard last day is 31 December 2032 r. |
| Documents of a specific accident, damage, claim, or proceedings | We determine the scope and period individually, until the case ends and the justified need for evidence ceases, taking into account appropriate limitation periods and specific regulations. We do not automatically delete documents covered by such a block after six years. Access is limited to authorized persons and the justification for retention is reviewed. |
| Certificate of no criminal record in the documentation of an ordinary TAXI carrier | We process it within the scope of the appropriate statutory requirement and Art. 10 GDPR. Unnecessary copies are deleted when closing the documentation of completed cooperation, if there is no separate basis for further retention; we do not apply a general additional archive of two or six years. The KRK certificate does not have a general validity period: the requirement of up-to-dateness at a given verification is separate from the deletion deadline. |
| Residence documents and legal employment documents as well as appropriate language versions of the contract | For documents covered by Art. 4–5 of the Act from 20 March 2025 r. — the work period and 2 years from the end of the year in which the appropriate legal relationship ceased, taking into account exceptions and separate longer obligations. A historical document requires qualification according to the appropriate state and purpose. |
| Payslips, payroll cards, and other proof to establish the pension/disability insurance basis of a contracting party | For a person reported to a given payer after 31 December 2018 r. — 10 years from the end of the year employment with this payer ended. For appropriate earlier periods, including reports from years 2017–2018 without shortening based on ZUS reports — basically 50 years from the end of employment with the given payer. Basis: Art. 125a sec. 4–4b of the Act on Pensions and Disability Pensions from FUS. The rule applies to qualified evidence, not all account documents. |
| Proof of student/pupil status and other insurance | We retain the minimal evidence affecting the settlement until the end of the payer's appropriate obligation, generally until the limitation of the contribution liabilities (usually 5 years from enforceability), considering events that change the course and the appropriate longer tax/pension purpose. The expiration of the card's validity does not remove the need to demonstrate settlement; a full scan requires necessity. |
| Participation and PPK instructions | Through cooperation being the basis of the given Employee Capital Plan (PPK) and 10 years from the end of the year of its termination, unless a specific document requires a longer appropriate period. This is an adopted rule for PPK documentation, without extension to other scans. |
| Tax and payer documentation | Until the expiry of the limitation period for the relevant tax obligation; as a rule 5 years from the end of the year in which the tax payment deadline expired, taking into account legally anticipated events affecting the limitation period. We do not always count from the end of the contract or file submission. |
| Other accounting records | According to the appropriate category of Art. 74 of the Accounting Act, usually 5 years, starting from the appropriate beginning for the given documentation. Contracts, claims, and longer obligations of a specific record require separate assessment. |
| Copies of declarations, ZUS reports, and their corrections | 5 years from submission to ZUS in accordance with Art. 47 sec. 3c of the Social Insurance System Act. This does not shorten the retention period of separate pension and disability documents. |
| Documents confirming the method and number of order hours | 3 years from the due date of remuneration if Art. 8a–8c of the Minimum Wage Act applies. Evidence needed additionally for taxes or benefit basis has an appropriately longer period. |
| Contract agreements, B2B, lease/lending, preliminary agreements, and evidential annexes | To the necessary extent during cooperation, then standardly no longer than 6 years from the end of the year of termination of the entire cooperation. This is an internal organizational period for justified settlement archiving and claims protection; necessity and scope are subject to annual review, and unnecessary data is removed earlier. The proper longer obligation takes precedence, including 10/50 years for a document genuinely needed to determine the pension/disability basis, considering the appropriate payer and regime described above. Not every contract agreement automatically falls under this longer period. The end of cooperation is an organizational point, not a universal start of any claim’s limitation period. For termination on 12 October 2026, the standard last day is 31 December 2032. Active cooperation, an undetermined longer goal, or a block on a specific case does not allow the removal of necessary evidence based solely on the deadline. |
| Other promotional, complaint, settlement, and claim documents | During case handling and then to the necessary extent of the proper settlement, obligation, or specific claims. Tax/wage due dates and submission of the ZUS report maintain their own significance; we do not replace them with the end of any contract. Specific proceedings or damage may set an individual period and block only the needed scope. |
| Document retained for specific dispute, incident, or inspection | Only the necessary scope, for the time of the specific basis. An authorized employee records the reason and condition for release; review occurs every 3 months. After the block is lifted, we verify the other appropriate periods without recalculating the entire retention from the date of unblocking. |
| Company mail MB/OTT | Ordinary messages after 730 days are directed to the trash for 30 days, then deleted according to the adopted rule. Necessary evidence of a contract, settlement, or case requires isolating into proper documentation before mail deletion. The rule does not mean that all technical copies of the provider disappear after this period. |
| Thulium recordings | Up to 365 days according to the declared configuration; the deletion of a customer account includes unnecessary recordings, with the assessment of individual exceptions. The recording period is separate from the reporting time and metadata. |
| History of reports and telephony metadata Thulium | 24 months from the closure of the case, and for a conversation without a separate case — from the end of the conversation. The necessary evidence of a specific contract, complaint, or dispute is separated into documentation with the appropriate period. |
| Marketing profile and activity history MailerLite | Up to 3 years from the last documented activity of the recipient related to this purpose, earlier after the cessation of the purpose or the appropriate request. Automatic sending of campaigns, synchronization, and technical changes do not renew the term. Withdrawal of consent stops marketing immediately; the minimum evidence of objection has a separate scope. After qualification, we order permanent deletion; the provider carries out the further cycle up to 30 days. Removing the contact from the current list is not equivalent to the permanent deletion of history. |
| Email invitations for opinions TrustMate | In the absence of an opinion, the invitation data is deleted by the provider after 60 days from sending, in accordance with § 14 para. 4 of its regulations. Earlier withdrawal of consent and cessation of the purpose are handled separately; the public opinion has its own rules and does not automatically disappear after withdrawal of consent to invitations. |
| SMS content and numbers with SMSAPI | Up to 12 months according to the confirmed organizational rule. Own logs and necessary evidence of a specific notification have a separate purpose and period. |
| Consents, withdrawals, and objections | The minimum evidence of choice for the time needed to demonstrate the basis and protection of rights; entry blocking further contact — for the justified time of respecting the objection, with a review. This does not include further marketing or keeping entire records. |
| Usual technical logs and logins | Up to 180 days from the event. The minimum evidence of a specific incident is separated into the appropriate case. The validity of a session or code is not a storage term for all logs. |
| Selected metadata of operation audit | Up to 24 months from the operation, in the necessary scope. A document constituting tax evidence, a signed contract, hours, or specific proceedings has its own period. The audit does not retain the full content of deleted scans. |
| Working conversations and files of company ChatGPT Business | We order deletion up to 30 days from the end of the case/analysis, separately for the conversation and saved files in Library/Space or the project. The needed result is previously saved in CRM with the category appropriate for the case. This is our operation execution period, separate from the further cycle and exceptions of the provider described in point 18. Revoking employee access does not delete their content. |
| Historical Airtable | It is not currently used. Required historical evidence is subject to the original term of the appropriate category; unnecessary copies require removal after inventory. Import into CRM does not initiate a new multi-year period. |
| GA4 | Event data: set period of 14 months with a monthly Google deletion cycle thereafter. User ID data: 14 months with reset enabled upon new activity. This also includes User-ID data in the actually implemented scope. This does not mean renewing the age of every old event. Age, gender, and interest data: separate 2 months according to Google. Standard aggregate reports, exports, and advertising lists have separate rules described in point 12. |
| Minimum acknowledgment of the policy in the portal | Confirmation of the current version is kept until it is replaced by the next publication, and then for 24 calendar months from actual replacement. The period does not run from clicking on the current version. The record includes the person’s identifier, version, and document hash, time, and portal; it does not record IP or user-agent. This is an organizational period for accountability of information. The published content itself remains in history. |
Phone registrations and push history — adopted new release schedule
A registration without authenticated activity of a given installation for 30 days does not qualify for a new dispatch and is directed for removal in the next push cycle. The push removal process is scheduled twice a day; with a functioning schedule and effective processing of all overdue packages, the accepted execution time is up to the next 24 hours. An error or backlog requires retrial and is not marked as completed removal. An attempt to send, employee action, and cron does not renew activity. Upon disconnection, we immediately stop qualifying for new shipments; a disconnected or canceled registration is cleared after 30 days from the first disconnection, with the same rule of execution. A new correct registration may reactivate its record.
The content and attempts of push are stored for 6 calendar months from the message creation; beyond this limit, the message is not available in the operational history and together with attempts is removed in the next push cycle, under the execution principles described above. A removal request includes data unnecessary earlier. These are internal periods of our system, separate from Firebase, APNs, and copy policies.
Archive, derivatives, and backups
The system calculates the document storage period on an ongoing basis based on its type and relevant event. We do not assign collaboration documentation to a single contract: an active contract protects this documentation, and its period runs after all contracts have ended. A regular identity copy, selfie, and partner change screenshot have separate short terms described in the table, even during active cooperation; a foreigner's document has its rule of legalization. The Chief Accountant is responsible for accounting and Social Security documentation, Taxi License Administrator for license documents, and Database Administrator for technical execution and deletion records. Employees explain deficiencies and handle justified exceptions and blocks. Upon initiation, the retention task deletes documents after the proper period and re-check of current sources, blocks, and handled copies; reading or publishing the policy is not proof of deletion execution.
For a file, we indicate the initial event, the last day of storage “to,” and separately the “deletion from” date — the next calendar day. For example, for verification completed 11.10.2026, a regular identity document copy has the last day 10.11.2026 and goes into deletion from 11.11.2026; for a selfie verified 11.10.2026 these are respectively 18.10.2026 and 19.10.2026. Deleting handled copies occurs in the nearest retention task cycle after the last day when the document is qualified, not blocked, and the operation ends successfully. An error requires repetition; the expiration of the date is not confirmation of deletion. With ongoing proper cooperation or case, the date dependent on its conclusion is not yet known; the absence of the end of another unrelated contract does not extend this document. We do not re-provide the file after its successful deletion from current systems.
CyberStorage is a primary document storage space, without its own backup according to the accepted configuration; it is not a temporary safety copy. Every file, version, thumbnail, and confirmed export require an appropriate data term. A retained identifying PDF still constitutes personal data even after a surname is removed from the profile or pseudonymization of connections.
The server backup has a declared rotation of 28 days. Data deleted from the current system may remain in the backup until its expiration; backups are intended for emergency recovery and have limited access. After recovery, deletions and objections must be reapplied before resuming normal use. The rotation of this backup does not determine document retention in CyberStorage or all copies at external providers.
After all relevant purposes have ceased, we either delete the data or truly anonymize it. A hash, interface concealment, or the removal of just the first name does not guarantee anonymity. With continued statutory retention, we limit use and access to the relevant purpose.
8. Hosting, security, and data on the phone
The system uses HTTPS, session control and permissions, as well as account security and auditing. Access to archives, health documents, and criminal records should be granted to individuals who need it for specific duties. Passwords, SMS codes, or full documents should not be sent via a channel that does not require them to handle the matter.
In applications, session tokens and trusted device secrets are stored in a secure system store. Language and instructional preferences are also retained, and when the push function is used, the channel setting and own installation identifier. Logging out removes local session tokens and main account data from memory; it is not a confirmation of the removal of every preference, cache, or file stored by you outside the app space.
The access token is valid for 24 hours, the refresh token for 30 days with rotation upon renewal, the SMS login code for 10 minutes, and device trust for 180 days. These are the validity periods of permissions, separate from the record and log retention periods. Revocation or expiration is to prevent further use of the permission.
Optional operational notifications
New releases have a push channel enabled and disabled separately in each app and on each phone. Refusal does not block documents and billing in the app or portal. The channel is used for information about your account, document, or billing. We do not plan advertising, new offers, or marketing through push; the setting is not marketing consent.
Google receives the delivery token, title, content, and technical message identifiers; on iOS, the delivery is shared with Apple APNs. A notification may be visible on the lock screen. Details requiring protection should be read after logging in; the message should be general, e.g. "A new bill is available. Check the app," without PESEL, diagnoses, criminal information, and confidential amounts.
We do not plan our own measurement of push opens or clicks. The technical history differentiates receiving the request by FCM, error, and omission; acceptance by the provider does not prove delivery or reading. The technical data of the service at Google may exist despite the lack of self-analytical openings.
Disabling the channel should stop new sends after receiving this information. An offline operation may only reach after connection; a message already passed to the provider cannot be associated with a new send after disconnection. Removing registration in CRM or the FCM token does not automatically delete the Firebase Installation ID. Google describes data expiration after a successful request to delete FID from current systems and backups within 180 days; this is the provider's period upon request, separate from our 30 days and 6 months.
9. Cookies and similar technologies
Cookies store information in the browser; local storage, tags, pixels, and identifiers may serve a similar function. The mechanism distinguishes necessary and security categories, functional, analytical, and marketing. Optional categories require appropriate selection. Session cookies or privacy choices are not consent for advertising.
The scope of tools depends on the site. The confirmed organizational scope includes GA4, Google Ads, and Meta on mbpartners.pl and ontimetaxi.pl. We do not automatically extend it to all portals or app screens. Transition from the app to a site or WebView means using the mechanisms of that site; it does not mean the operation of a web pixel on every native screen.
10. Consent Panel and Consent Mode
The “Cookie Settings” panel allows for a separate functional, analytical, and marketing selection, rejection of optional categories, and subsequent changes. In the described portal mechanism, the choice is remembered in host-only cookie mbpartner_cookie_consent for 180 days or until the deletion/change of the relevant version of information. Host-only refers to a specific host, so the choice is not automatically shared with all subdomains.
For Google, the analytical choice controls analytics_storage, and the marketing choice controls ad_storage, ad_user_data, and ad_personalization. The default state before making a choice is denied. Tags from other providers require their own appropriate conditions for activation; merely including Consent Mode does not control all external scripts.
Withdrawing consent is free and does not affect the legality of prior processing. Withdrawal is to halt operations dependent on that consent; previously acquired data requires separate implementation of appropriate rights and retention. Changing the category or purpose requiring a new choice is not automatically approved by the old cookie record.
11. Advanced Consent Mode and Signals upon Denial
In Advanced Consent Mode, the container and Google tags can connect with Google in the denied state, before making a choice or after refusal. According to Google documentation, limited signals may include consent status, event time, browser information, referrer, limited page address, and campaign identifiers; transmission is associated with an IP address. The lack of an optional cookie does not mean no data transmission.
Statistical modeling and ad measurement are separate from cookie recording and personalization. Addresses and parameters transmitted to tools must be limited, without login tokens, PESEL, contract data, balance, and document content. Data shared with conversion measurement tags require separate information and a proper basis; their scope is not determined solely by opting out of contact list imports.
12. Google Analytics, Google Signals, and Google Ads
Google Analytics 4 is used for analyzing site usage, and Google Tag Manager for tag management. Measurements may include browser, device, approximate location derived from IP, visit source, pages, and events. Goals and analytical and advertising choices are separate.
The adopted GA4 configuration includes Google Signals, detailed device and location data, and ad personalization, along with the Google Ads connection. Google Signals can combine visit information with Google user information having the appropriate personalization settings, for cross-device analysis and advertising features. These are not exclusively anonymous visit counters. Service settings do not replace the visitor's proper consent and do not mean application access to the phone's GPS.
In GA4 services where the User-ID function is implemented, we can combine the activity of a logged-in user across devices, browsers, and sessions using a pseudonymous identifier assigned to their account. This is used for analyzing site and portal usage and limiting multiple counts of the same person. It concerns measurements within the same GA4 service and services covered by its actual implementation. Selecting User-ID in the reporting panel does not cause the identifier to be transmitted – its provision by the site or portal is also required.
Use of User-ID is conditioned on consent to analytics. We do not transmit the identifier before such a choice or upon refusal; after withdrawing consent or logging out, we stop assigning new events to the account identifier. Measurements without cookies in Advanced Consent Mode do not constitute consent to send User-ID. Analytical consent does not itself activate advertising purposes, which require the proper marketing choice.
The User-ID does not include the first name, last name, email address, phone number, PESEL, or identity document data. We also do not use an email or phone hash or FCM notification token for this purpose. Since we can associate the identifier with an account, this is pseudonymization, not anonymity. We distinguish User-ID from browser/device identifiers, Google Signals, and form data used for enhanced Google Ads conversions. The description of User-ID applies to websites and portals; it does not change the described scope of mobile Firebase.
GA4 event data has a 14-month period, and user identifier data 14 months with a reset upon new user activity. The reset does not renew the age of each old event. After the period, Google deletes the data on a monthly cycle. For age, gender, and interests, 2 months are applied. This same period covers the collected User-ID data when the function actually receives an account identifier. We do not use GA4 exports to BigQuery. Retention does not automatically limit standard aggregate reports.
Google Ads is used for conversion measurement, remarketing, and evaluating the effectiveness of campaigns within the scope of appropriate marketing choice, separate from analytics. Enhanced conversions may use email, phone, first name, last name, city, and country from the registration form for conversion matching and campaign optimization. Data may be normalized and hashed; hashing is not automatically anonymization. Merely creating an account does not express consent for this purpose. Without a proper marketing choice, the portal does not provide tags with these form data.
We do not pass scans, health data, KRK, PESEL, or confidential contract documents to Google Analytics. Information: Google Privacy Policy, GA4 data retention User-ID function and enhanced conversions Google Ads.
13. Meta Pixel and ad recipients
Meta Pixel, with proper marketing consent, can process visits and actions on the site, IP, browser, device, referrer, cookies, and advertising identifiers. It is used for advertising effectiveness measurement, audience groups, remarketing, and personalization.
The registration tag, after appropriate marketing consent, may use advanced matching with email and phone for advertising effectiveness measurement. The identifier hash can still be used to match individuals; we do not consider it anonymous statistics. Account registration and analytics choice do not replace marketing choice.
Information: Meta Privacy Policy and Meta Cookie Policy.
14. Contact, chat, call recordings, and voluntary feedback
Thulium is used for MB/OTT contact, query handling, and calls. The optional chat widget is activated according to the proper functional choice; refusal does not limit contact via email. The chat can process session identifier, IP address, device information, and voluntarily submitted content. Do not send passwords, one-time codes, diagnoses, or unnecessary identity scans.
If a telephone conversation is recorded, you receive information before the recording starts. The purpose, basis, and alternative contact available should be indicated for proper service. Recordings have a declared maximum period of 365 days. We store reports and metadata for up to 24 months after the case is closed, and metadata of the call without a separate case—from its end. Necessary evidence of a specific case is separated with appropriate justification and period.
Separate consent for opinion requests via TrustMate
Invitations concern the services of MB PARTNER Marcin Bohdanowicz. ON TIME TAXI does not operate this invitation channel. With your separate, voluntary consent, MB PARTNER Marcin Bohdanowicz may instruct TrustMate S.A. to send an email requesting an opinion, reminders, and thanks. We do not use the SMS channel in this process. The choice indicates the administrator, purpose, and email channel; it is not pre-selected. Refusal, lack of opinion, or withdrawal of consent do not affect the contract or settlements. Consent for offers or familiarization with the Policy does not replace this choice.
When sending invitations, MB PARTNER is the data controller, and TrustMate acts on its behalf as a processor under an entrustment agreement, which may be concluded electronically. We provide an email address and minimal data necessary for the invitation after the service, without identity documents, health data, criminal records, and settlements. Consent can be withdrawn through the provided opt-out mechanism or by contacting MB PARTNER. Upon receiving withdrawal of consent, we stop further messages for this purpose, including already scheduled reminders in TrustMate. The service is performed by authorized personnel; withdrawal of consent does not affect the lawfulness of prior processing.
If you do not provide feedback within 60 days of the invitation being sent, TrustMate, in accordance with § 14 section 4 of its regulations, deletes the data provided for this purpose. This does not replace prior handling of consent withdrawal or cessation of purpose. If you provide feedback, it may be displayed publicly, also on the partner's sites and in the search engine. Within its service and opinions, TrustMate acts as a separate controller. Withdrawal of consent for invitations does not automatically remove the public opinion.
TrustMate S.A., ul. Bartoszowicka 3, 51-641 Wrocław: privacy policy, terms of services and public entrustment agreement. The period of 14 days for the deletion of entrusted data after the company's contract termination with the supplier is separate from the withdrawal of the recipient's consent and from the public opinion rules.
15. Form protection — reCAPTCHA
We protect registration and password reminder forms through Google reCAPTCHA Enterprise; in applications, the appropriate security page is displayed in an embedded view. Google evaluates technical signals, such as IP, browser, device, time, and manner of interaction, and the verification token reaches our API. This is neither Firebase Authentication nor revenue analytics.
The purpose of account security and limiting automatic submissions may be based on art. 6 section 1 letter f of the GDPR concerning necessity and proportionality. For storing/reading information on the device, a separate assessment of art. 399 of the Telecommunications Act and the actual necessity is needed; the name of the security itself does not establish an exception for all Google operations.
If you encounter a problem with the form, you can contact us directly via email. Google's information: privacy and terms of services.
16. Key cookies and similar identifiers
The table separates the duration of the identifier on the device from data retention on the provider's side. Names and periods for external cookies are typical; the final table requires confirmation on each domain.
| Name or type | Purpose and category | Period or criterion |
|---|---|---|
| CookieConsent on main company pages | Remembering category selection — necessary | 1 year, or earlier deletion or re-selection required |
| Privacy choice cookie on the portal | Remembering category and version — necessary | 180 days or earlier deletion or change of the appropriate version |
| Session and form protection | Login, session maintenance, and request protection — necessary | Proper session or security period; exact configuration requires confirmation |
| _ga, _ga_* | Browser differentiation and measurements — analytical | Typically up to 24 months depending on configuration; separately GA4 data 14 months with user reset |
| _gcl_au, _gcl_* | Measurement of ads and conversions — marketing | Typically up to 90 days depending on configuration, without automatic determination of the advertising list period |
| _fbp and used Meta identifiers | Measurement and adjustment of ads — marketing | Typically up to 90 days, pending verification in the function used |
| Chat identifiers | Support for selected widget — functional | Session or time specified in the actual provider configuration |
| reCAPTCHA identifiers and risk signals | Form security | According to the actually implemented service and proper assessment; to be confirmed |
| Session tokens and trusted device app secret | Authentication and security | The validity of 24 hours / 30 days / 180 days described in item 8 is not automatically the deletion period for all records |
| Own installation identifier, FCM and FID | Optional operational push channel | Own registration: rule 30 days + next cycle up to 24 hours; Google data and local preferences have separate rules |
17. Change of privacy choice
Use the "Cookie Settings" panel on the appropriate page to reject, change, or withdraw optional consents. You can also remove cookies and site memory in your browser settings. Blocking a necessary session may prevent logging in; refusal of an optional category should not block basic account service.
You disable push notifications in the appropriate app or phone settings; setting one app or installation does not automatically change the choice on another phone or in another brand. You report the withdrawal of email/SMS marketing through the provided mechanism or by contacting the appropriate administrator.
Removing the app, cookie or withdrawing permission does not mean deleting all data previously obtained by the controller and providers. A request regarding such data is considered according to point 19. The marketing choice, getting acquainted with the policy, and parent's consent to the agreement are separate actions.
18. Analysis, profiling and human participation
We analyze activity and settlements to present results, control correctness, and explain abuses. OTT may present order acceptance/cancellation indicators, revenues, and day and hour comparisons. Data may come from platforms and settlements; this does not require phone GPS. Historical listing or forecast is not a guarantee of future earnings.
Authorized MB employees use the integration of corporate ChatGPT Business for statistics, calculations, and reports concerning performance or abuses. The tool's mere reading provides information; it does not prove settlement execution, approval, deletion, or status change. The AI result requires checking by an employee capable of changing it before applying consequences.
The company declares the use of statistical and settlement data without personal data; however, the actual level of aggregation requires verification. An amount or rating associated with a person's ID, device, or potentially relatable case may be personal data. For ordinary analysis, entire scans, PESEL, health certificates, or KRK should not be forwarded. Analysis of identifiable performance/risk may be profiling despite human participation.
OpenAI indicates that Business data is not defaultly used for model training. This does not mean the absence of storage. Removing a workspace member does not automatically remove conversations, files, and canvas documents; according to published Business rules, they may remain indefinitely. Chat deletion is a separate operation, intended for permanent removal usually within 30 days and with legal, security exceptions, or earlier de-identification described by the provider. Separately saved files and projects have their own rules. Information: user access cycle and OpenAI security and retention.
Our accepted rule requires ordering the deletion of its working conversations and separately saved files in Library/Space and projects within 30 days from the conclusion of the case/analysis. We transfer the necessary result earlier to the CRM with a period appropriate for that result. Deleting the conversation itself does not remove the separate file in Library/Space, and deleting the project, disconnecting the integration, or revoking employee access does not replace checking all copies. The deletion order to the provider and its further cycle are separate from our term 30 days.
Google/Meta advertising profiling is separate from operational analysis and subject to the description in points 12–13 and appropriate choices. Calculation rules apply contract or program terms; you may report a doubtful result via email for manual verification, receive an explanation, and challenge the data. A complaint after the result is not proof of human participation before the decision.
19. Your rights and deletion of a joint account
Within the scope provided by GDPR, you can access and copy data, correct it, request deletion or restriction, and when conditions are met, transfer data. You can object to processing based on a legitimate interest for reasons related to your situation and at any time object to direct marketing, including associated profiling. You can withdraw consent without affecting the legality of prior actions.
Direct the request to kontakt@mbpartners.pl; for OTT also to kontakt@ontimetaxi.plMB coordinates the service and handover to the appropriate data controller, which does not exempt him from responsibility. In case of justified doubts, we verify identity to the extent necessary to protect against unauthorized operations.
We respond without undue delay, generally within one month of receiving the request. For justified complexity or number of requests, the deadline can be extended by another two months; we inform about the extension and the reasons in the first month. In case of refusal, we explain the reason and available protection measures. You can file a complaint with the President of UODO: uodo.gov.pland seek judicial protection.
Deletion of the MB Partner / On Time Taxi account
You submit a request through Menu → Delete account in the app, through MB Partner portal, OTT portal or email. It covers the joint account of both brands. Uninstalling the app does not delete the account.
With active contracts, you receive information about the effects and the possibility to report their termination. The employee handles the termination according to the contract; the declared operational standard 7 days is not a guarantee of deleting all data. Deregistration from ZUS has its statutory deadline counted from the cessation of the insurance title.
Access blocking, contract termination, and data deletion or anonymization are separate stages. The request does not remove the obligation to retain specific tax, insurance, or necessary case evidence, but an active contract does not block the removal of data unnecessary to it and the disabling of optional channels. Remaining data have a range, basis, and term appropriate for the category in item 7.
The response should indicate separately: deleted operational data, retained documents and their bases/periods, individual exceptions, operations at recipients, and extinguishing copies. The retained identifying original in the archive does not allow for total data anonymization. Technical queuing, backup, or waiting for contract termination do not replace the response to the request in the GDPR deadline.
20. Publication, historical versions and notification of change
The policy informs about data; reading, retrieving, or confirming its receipt is not consent to marketing, any new purpose, or automatic acceptance of contract changes. A purpose requiring separate consent is not initiated by mere publication of the policy.
A new version after publication has a number and date. Portals provide the currently published policy and historical versions with date and status marks; existing MB and OTT documents remain in history. An employee draft does not replace the current public version. The main company pages should direct to the appropriate portal policy in accordance with the publication configuration, and applications provide its link.
We inform about significant changes in the portal, and for the selected email channel, also active individuals via email. After logging in, the window shows the version and description of changes and a link to the full content and history. The "I have read" button records confirmation of a specific version, and "Later" postpones the information without confirmation and without blocking the portal. Sending the message, its acceptance by transport, and clicking confirmation are separate states; mere display or sending does not prove acquaintance. Confirmation for MB/OTT is joint for the same person and publication. We store confirmation of the current version until its replacement, then 24 months; it is not consent to marketing or TrustMate.
Translations PL/EN/UK/RU/BE refer to the designated source version and require consistency of meaning. A translation correction does not independently change the processing purpose. You can clarify doubts by contacting the administrator.
21. Contact
Coordination of a joint account, documents, applications, security, and requests: MB PARTNER MARCIN BOHDANOWICZ, ul. Rewolucji 1905 year 82 unit 6, 90-223 Łódź, NIP 8882894528, kontakt@mbpartners.pl.
Own contracts, fleet, promotions, and OTT processes: ON TIME TAXI LIMITED LIABILITY COMPANY, ul. Nad Rzeką 2, 26-067 Chełmce, KRS 0001060100, NIP 9592065735, kontakt@ontimetaxi.pl.
The current published policy and history are available on the MB Partner portal and On Time Taxi portal. For specific company operations, you can contact them directly.