Skip to content

Privacy and Cookies Policy FLOW APPS

Current version

Version: 2026-10-19-szkic-2

Effective from: 19/10/2026

This is a translation of the published Polish version. You can display the Polish original by selecting the document language.

Privacy and Cookies Policy FLOW APPS

The effective date is indicated with the published version.

1. Controller and Scope of the Policy

The controller of personal data described in this Policy is FLOW APPS SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ, ul. Proletariacka 36 apt. 11, 93-569 Łódź, KRS 0000909050, NIP 7272850986, REGON 389306039, hereinafter “FLOW APPS” or “Controller”. For privacy matters, you can write to kontakt@flowapps.pl or to our registered office address.

The Policy applies to candidates, drivers, couriers, clients, individuals participating in referrals and promotions, and those contacting us. It includes the website flowapps.pl, portal portal.flowapps.pl and cooperation processes handled by FLOW APPS. Our portal and CRM are used for managing the Controller’s own applications, agreements, documentation, and settlements.

We are planning our own FLOW APPS mobile applications for Android and iOS. The description of the application, phone permissions, and notification delivery services applies from the launch of the respective application and the actual availability of the feature. Feature availability is indicated in the application; mere description in the Policy does not mean it is already available.

Transport and delivery platforms and selected service providers have their own privacy information. Data transfer to them occurs within the scope of a specific process. The individual role of such a recipient, including Meta’s limited role in collecting and transmitting page events described in item 13, is separate from account administration and documentation by FLOW APPS.

2. Sources and Categories of Data

We receive data from you upon submission, registration, document submission, contract conclusion, order placement, contact, or service use. We may also receive it from a person lawfully submitting you for contact, from an advertising platform form, from transport and delivery platforms, partners of the relevant service, payment and delivery operators, authorized bodies, and public registers. Data not directly obtained from you includes, in particular, activity and settlements on the platform, vehicle data, and information needed for a specific contract. We provide information about the proper source and scope 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.
  • Application and account data: contact source, selected services, contact deadlines, case status, necessary notes, person handling the application, actual contact history, and privacy choices. The application of a person who has not started cooperation may be referred to as a lead.
  • Contracts and cooperation data: parties and terms of the contract, signatures, confirmations, cooperation status, and change history needed for its service; in the appropriate program also the data of the referring and referred person.
  • Billing data: bank account, revenue, remuneration, order execution time, contributions, taxes, PPK, invoices, balance, fees, deposits, receivables, and payments; for the appropriate service, fuel card data and transactions.
  • Identity documents, driver's license, permissions, and licensing documentation; vehicle data, policies, lease or lending, reservations, damage, and return. The scope depends on the performed service and the necessary purpose.
  • Documents confirming student/pupil status or other insurance, required statements, parental/guardian consent for an appropriate activity, and documents of residence and legal employment of a foreigner.
  • In the TAXI process: required medical and psychological certificates on the existence or absence of contraindications and information on criminal records within the scope permitted by law. For regular account maintenance, full diagnoses, raw test results, or treatment history are not required.
  • Activity received from platforms: orders, acceptances and cancellations, revenues, and indicators used to present results, fulfill cooperation conditions, or explain discrepancies and abuses.
  • Content of contacts, reports, and complaints, attachments, communication metadata, and call recordings if the call is recorded and you are informed of the recording in advance.
  • Technical data: IP, time and request parameters, browser, operating system, language, session, security events, cookie choices, and campaign and device identifiers within the scope of the relevant function and choice.
  • Pseudonymous User-ID associated with the account — if the GA4 measurement is indeed used and you consent to analytics; the scope is described in point 12.

Planned mobile applications

Upon activation of appropriate features, the application will allow access to the account, documents, contracts, settlements, invoices, payments, fuel cards, reservations, fleet, referrals, and appropriate promotions. The scope available to a person will depend on permissions, selected service, and data on the account.

Application data will include session, login, technical request information, language, and trusted device identifier. Upon activation of optional push, additionally: own installation identifier, Firebase Cloud Messaging (FCM) token, platform, permission and registration status, actual installation activity, message title and content, and the result of the sending attempt. The own installation identifier differs from the Firebase Installation ID (FID) processed by Google.

The camera will serve to take a photo of a document selected by you. Instead, you may point to an existing file; selected files will be sent, not the entire gallery. The planned scope does not include phone GPS, contact book, microphone, or biometric login. Platform data may include the city and transport activity information, regardless of phone permissions.

On Android, the optional Google SMS User Consent can, with one-time permission, complete the login code from a single SMS. It does not grant access to message history. You can decline and enter the code manually. The current attempt listening lasts up to 5 minutes; this is not a server log retention period.

3. Purposes and legal bases for processing

The indicated basis applies to the specific purpose of FLOW APPS. We do not apply all bases interchangeably to each piece of information. The 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 agreement; its retention period begins after the latest termination of all contracts. A simple copy of an identity document, a selfie, and a partner change screenshot have separate short periods from the completion of verification or partner change, even with an active contract. The identity document of a foreigner required for work legalization has its own rule. We calculate dates on an ongoing basis, considering separate obligations and blocks of specific cases.

PurposeBasis and scope
Consideration of the report, actions taken at your request, account and contract executionArt. 6 sec. 1 letter b GDPR — data necessary for appropriate pre-contractual actions or contract execution; includes proper order, lease, reservation, and settlement.
Taxes, accounting, contributions, and payer documentationArt. 6 sec. 1 letter c GDPR in connection with relevant obligations including the Tax Ordinance, the Accounting Act, tax laws, the Social Insurance System Act, and the Pensions and Annuities from the Social Insurance Fund Act. Relates to documentation actually subject to a given obligation.
Confirmation of order hours and proper PPK obligationsArt. 6 sec. 1 letter c GDPR in connection accordingly with art. 8a-8c of the Minimum Wage Act and the Employee Capital Plans Act, if applicable to a given person.
Legal entrustment of work to a foreignerArt. 6 sec. 1 letter c GDPR in connection with the relevant obligations of the Act of 20 March 2025 on conditions for the admissibility of entrusting work to foreigners within the territory of the Republic of Poland, especially art. 4-5, considering the appropriate mode and exceptions.
Required licenses and criminal record of a TAXI driverArt. 6 sec. 1 letter c GDPR and, for data on criminal records, art. 10 GDPR in connection with the relevant scope of the Road Transport Act, especially art. 6 sec. 1 point 2 letter b and art. 8 sec. 3 point 4. The requirement also includes non-employed individuals personally performing transport on behalf of a carrier; it is not automatically transferred to all couriers.
Required assessment of a driver's capacity to perform transportArt. 6 sec. 1 letter c and additionally art. 9 sec. 2 letter b GDPR within the statutory obligations of work capacity assessment, from art. 39j-39m of the Road Transport Act. Art. 39l sec. 1 point 3 letter b provides for keeping copies of required declarations throughout the driver's employment period; art. 39m requires appropriate application of these requirements also to other individuals personally performing transport.
Participation and settlement of a specific promotionArt. 6 sec. 1 letter b GDPR in terms of the conditions of the program you join; letter c for required tax settlements. The organizer is responsible for their program.
Contact, case handling, and complaintsArt. 6 sec. 1 letter b of GDPR, when the matter concerns your contract or actions at your request; for other necessary services art. 6 sec. 1 letter f—interest in providing a response and ensuring continuity of service. For the realization of a data-related request—letter c in connection with GDPR.
Account security, logging in, preventing abuse, and explaining incidentsArt. 6 sec. 1 letter f of GDPR—protection of accounts, individuals, data, and the correctness of settlements, to the necessary and proportional extent; specific data protection obligations also arise from GDPR.
Establishing, pursuing, or defending certain claimsArt. 6 sec. 1 letter f of GDPR—protection of rights in a specific case, with limited scope and time. For necessary health data additionally art. 9 sec. 2 letter f; this does not constitute a general authorization to retain criminal record data bypassing art. 10.
Summaries of activity, remuneration, and analysis of correctnessArt. 6 sec. 1 letter b concerning the implementation of established conditions and presentation of your result; art. 6 sec. 1 letter f for necessary explanation of discrepancies, quality control, and protection against abuses. The basis does not include arbitrary use of data in advertising.
Email or SMS about offers and new servicesPrior consents required for the appropriate purpose, entity, and channel, considering art. 6 sec. 1 letter a of GDPR and art. 398 of Electronic Communications Law. Consent is voluntary and revocable.
Voluntary request for feedback via TrustMateSeparate prior consent for the specified controller, purpose, and chosen channel—art. 6 sec. 1 letter a of GDPR and, where applicable to the communication, art. 398 PKE. Reviewing the policy does not grant this consent.
Optional activation of push channel and delivery identifiersSeparate user choice and prior information; where consent is required art. 6 sec. 1 letter a of GDPR and art. 399 PKE. Android/iOS permission to display messages is not consent for all other Google purposes or marketing.
Operational push content concerning your caseBasis of specific information: art. 6 sec. 1 letter b for contract service, letter c for appropriate obligation or letter f for necessary security and service. Disabling an optional channel does not remove the required information obligation.
Optional chat, analytics (including implemented User-ID), and advertising page identifiersAppropriate functional, analytical, or marketing consent—art. 6 sec. 1 letter a of GDPR and art. 399–400 PKE for terminal operations; subsequent handling of a voluntarily initiated matter has a basis appropriate to its content.

Contact regarding your inquiry, request for an offer, or contract is not dependent on marketing consent. Using the contact for unrelated marketing requires separate appropriate consents. Remembering privacy choice and its minimal proof serves the implementation and demonstration of data protection obligations; does not entitle to additional analytics or advertising.

For health and criminality, we require an additional premise respectively from Art. 9 and 10 GDPR, also appropriate for a specific retention period. A required form field, platform expectation, or the mere possibility of future control does not replace the legal basis. We limit the scope of the document to data necessary for the given requirement.

4. Voluntariness of providing data

Providing data upon application is voluntary, but the lack of data needed for contact or verification may prevent its processing. Data necessary for signing or executing a contract, settlements, or fulfilling a specific legal obligation are required in the appropriate process. When collecting data, we indicate the purpose; do not send broader documentation than needed.

The refusal of marketing, invitations to reviews, analytics, or an optional notification channel does not block basic account service. An optional chat depends on the functional choice, and email contact remains available. In the planned application, refusing the camera will allow indicating an existing file.

In some courier services, cooperation with a person from 16. years of age is considered according to the requirements of the specific service, law, and platform. Parental/legal guardian consent for an act concerning a contract is separate from consent for optional data processing. It does not imply the admission of a minor to TAXI. We limit the data of the guardian to the needs of demonstrating authorization and required consent for the act.

5. Data recipients

We share data to the extent necessary for the purpose. Authorized personnel receive data needed for their assigned tasks and are bound by confidentiality obligations. A provider acting on our instructions receives an appropriate scope for the service under the terms of entrustment; a recipient conducting their own process may be a separate controller.

Recipient or categoryPurpose and scope
Transport and delivery platforms, e.g., Uber, Bolt, FreeNow, and appropriate courier platformsRegistration, activation, and handling of selected cooperation; required documents, identifiers, activity, and settlements in the scope of the process. Platforms have their own privacy policies.
cyber_Folks S.A.Hosting/VPS, database and CyberStorage space for account and documentation, along with necessary technical access and service protection.
Google WorkspaceCorporate mail: recipients, senders, message contents, and attachments needed for appropriate communication.
Thulium sp. z o.o.Telephone contact, requests, chat, and recordings if the conversation is recorded after prior information.
SMSAPIPhone number, content, and technical data needed to deliver SMS and handle delivery.
MailerLiteMessages regarding startup and activation, instructions, and service information; recipient data, relevant content, and technical campaign data. We assess the purpose and necessary consent based on the content, not the tool's name.
TrustMate S.A.Voluntary invitations, reminders, and thank-yous for reviews, only after a separate choice. We provide contact appropriate for the chosen channel and minimal information needed for invitation after service, without scans, health data, criminal records, and settlements. For its own service and reviews, the provider operates according to the rules described in point 14.
SumUp and relevant payment operators and banksPayment processing and confirmation; upon appropriate sales notification, we provide the client's email. The operator independently acquires payer and instrument data according to its service. FLOW APPS does not receive full card data from this.
InPost, DPD, and relevant delivery operatorsFirst name, last name, phone number, and address or delivery point — fulfillment of the ordered shipment.
Google Firebase Cloud Messaging and Firebase Installations; Apple APNs on iOSUpon launching the mobile function: installation/connection identifiers and technical data as well as the title and content of the push notification. Logging in, documents, and settlements will be handled by our own API, without using Firebase Authentication, Firestore, or Firebase Storage for this purpose.
Google reCAPTCHA Enterprise and, upon launching the relevant Android function, SMS User ConsentForm security and optional one-time completion of the SMS code; scope described in point 2 and 15.
OpenAI — company ChatGPT BusinessSupport of authorized employees in statistics, calculations, performance analysis, and abuse detection. Input scope requires minimization, and the result — human verification.
Accounting, tax advisors, legal services, insurers, and authorized case partnersDocuments relevant for settlements, contributions, legalization, licenses, insurance, or specific claims; scope depends on the case.
PZPA Solutions sp. z o.o. and entities associated with the FLEETCHECK registerExclusively in the cases and scope resulting from the relevant agreement, General terms of cooperation, and separate information for a given process.
Public authorities, courts, bailiffs, and other authorized institutionsRelevant data required by law or needed for a specific proceeding, control, or fulfillment of an obligation.

Enova serves local HR and accounting services. The mere use of the software does not mean transferring the entire database to its producer. Paper documents have limited access and deadlines appropriate for their category. Airtable is not part of the accepted scope of current services; historical records and attachments are subject to the provisions of point 7. We do not sell contact databases.

6. Data transfer outside the European Economic Area

Hosting and own database do not determine the location of all copies with providers. Using Google, Meta, Apple, OpenAI, and subcontractors of other services may mean processing or remote access outside the EEA, especially in the United States. Firebase Cloud Messaging uses a global infrastructure; it is not a service limited exclusively to the EEA.

For the transfer, we require security appropriate for the specific recipient and service in accordance with Art. 44–49 GDPR. This may be a European Commission decision on an adequate level of protection, including the EU–US Data Privacy Framework exclusively for the recipient and scope covered by it, or standard contractual clauses with appropriate additional measures. Simply having a data processing agreement or being acquainted with the Policy does not replace such security.

Information about Google transfers is available at Data transfer frameworks, and about Meta in Meta's privacy policy. Information about the specific recipient, country, and applied safeguards or their copy is available at kontakt@flowapps.pl, with the protection of business secrecy and security information.

7. Document storage and retention period

The period is determined separately for the document, purpose, and appropriate payer. Contract termination, document expiration, account blocking, operational data deletion, and archive deletion are different events. We do not apply a single term to all data of a person.

A document needed for several actual purposes remains until the end of the longest applicable obligation; unnecessary scope is limited. A new unrelated agreement does not automatically renew the retention of old files. Health and criminal documentation also require an appropriate special basis for further storage.

CategoryPeriod or event determining the deadline
Basic candidate account without commencing cooperationMaximum 12 months from actual activity serving to continue the application, provided there is still a justified need; earlier upon withdrawal or prior termination of the purpose. A technical change, import, cron, and outgoing message do not renew the deadline. Awaiting an office or platform requires assessing the specific case. Scans do not automatically inherit this period.
ID or passport used solely for regular identity verificationThe last day for retaining the copy is the confirmed verification completion date + 30 calendar days, even during active cooperation. After this day, the unnecessary copy is deleted in the removal process appropriate for the storage location; earlier upon prior termination of the purpose — without undue delay. A minimal verification result remains if needed to document the process. This rule does not apply to a document necessary for legalizing foreigner employment or an ID held for a specific case.
Driver's profile picture, required equipment picture, and vehicle picture used for account management in the applicationFor the necessary period of cooperation and generally up to 30 days after the conclusion of all agreements that constitute cooperation. Upon earlier termination of the purpose, the unnecessary picture is removed without undue delay. The profile picture is not a verification selfie. Evidence of a specific event, damage, or case is separated into appropriate documentation.
Technical documentation of the vehicle and markings in fleet management or licensingFor the period of use and necessary service, then the organizationally accepted 2 years from the confirmed withdrawal of the vehicle or closure of service entry, depending on the actual purpose. Documents still required for the device, settlement, or specific case maintain the appropriate separate period. The validity date, import date, or modification does not replace the purpose's end date.
Settlements and documentation of vehicle reservation settlementUntil the settlement execution and case closure, or until the termination and final settlement of the reservation, then generally up to 6 years from the end of the year of that event, within the necessary evidential scope. A longer appropriate obligation or specific unresolved case takes precedence; the justification for retaining case documentation is checked every 3 months.
Signature material and document copiesSignature material is retained for the necessary period appropriate to the documents it documents signing, considering a longer appropriate obligation. Unnecessary draft copies are deleted after confirming the retention of the signature proof. The term of a standard picture does not apply to signature material.
Selfie with documentThe last day of retention is the confirmed verification completion date + 7 calendar days, even during active cooperation. After this day, the unnecessary image is deleted in the removal process appropriate for the storage location; earlier upon prior termination of the purpose — without undue delay. A specific necessary incident proof is separated into the appropriate case.
Snapshot of partner change/previous cooperationThe last day of retention is the confirmed partner change completion date + 7 calendar days, even during active cooperation. After this day, the unnecessary image is deleted in the removal process appropriate for the storage location; earlier upon prior termination of the purpose — without undue delay. A specific necessary settlement or incident proof is separated into the appropriate case.
Scans of abandoned activationAfter 90 days without action from the candidate regarding the application, we conduct a review. For unnecessary scans, the last day of storage is the date of confirmed closure of the application + 7 calendar days; deletion occurs after this day through a removal process appropriate to the storage location. The 90 day threshold does not automatically close the application pending on the device/platform and does not renew the period. A separate necessary procedure record has its own category.
Driver's license, extracts, and other ordinary TAXI license documentationThe accepted organizational period of the limited archive is 2 years from the termination of all agreements constituting the person's cooperation, without assigning each file to a single agreement. During ongoing cooperation, we retain the necessary documentation; once the purpose ceases, unnecessary data is removed earlier. A separate obligation or specific matter may set the appropriate, documented period.
Copies of driver's medical and psychological opinionsThroughout the period of cooperation, we retain the required copies of judgments, in accordance with the relevant duties of the Road Transport Act. After the end of cooperation, we store them to the extent necessary for establishing, pursuing, or defending claims related to the performance of transport services, particularly as evidence of possession of the required judgments during the execution of the contract. The basis of this archive is Article 6 section 1 letter f in connection with Article 9 section 2 letter f of the GDPR, upon documenting necessity. Standardly, no longer than 6 years from the end of the year in which the entire cooperation ended; necessity is subject to annual review, and unnecessary data is removed earlier. This is an internal organizational period, not a statutory obligation to retain for six years. We retain only copies of judgments, including those replaced by subsequent examinations, if they document the previous period of work; not treatment documentation or test results. For cooperation ended on 12 October 2026, the standard last day is 31 December 2032.
Documents of a specific accident, damage, claim, or proceedingThe scope and period are determined individually, until the case concludes and the justified need for evidence ceases, considering relevant limitation periods and specific regulations. We do not automatically delete documents subject to such blocking after six years. Access is restricted to authorized persons, and the validity of retention is reviewed.
Criminal record certificate in the ordinary TAXI carrier documentationWe process it within the scope of the relevant statutory requirement and Article 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 for currency at a given verification is separate from the deletion deadline.
Documents of residence and legal employment transfer and appropriate language versions of the agreementFor documents covered by Articles 4–5 of the Act of 20 March 2025 — work period and 2 years from the end of the year of the cessation of the relevant legal relationship, considering exceptions and separate longer obligations. A historical document requires qualification according to the appropriate condition and purpose.
Payroll lists, salary cards, and other evidence for establishing the basis for the pension/disability pension of an insured contractorFor a person reported to a given payer after 31 December 2018 — 10 years from the end of the year in which work ended with that payer. For the relevant earlier periods, including reports from the years 2017–2018 without reduction based on ZUS reports — generally 50 years from the end of work with that payer. Basis: Article 125a sections 4–4b of the Act on Pensions and Disability Pensions from the Social Insurance Fund. The rule applies to qualified evidence, not all account documents.
Evidence of student/school pupil status and other insuranceWe retain the minimal evidence affecting settlement until the end of the appropriate payer's obligation, generally until the statute of limitations for the contribution dues (usually 5 years from due date), considering events changing the course and the appropriate longer tax/pension goal. The end of the validity of the card does not remove the need to demonstrate settlement; a full scan requires necessity.
Participation and PPK arrangementsThrough the cooperation forming the basis of the given Employee Capital Plans (PPK) and 10 years from the end of the year of its completion, unless a specific document requires a longer appropriate period. This is an accepted rule for PPK documentation, without extension to other scans.
Tax documentation and payer documentationUntil the limitation of the relevant tax liability; generally 5 years from the end of the year in which the tax payment deadline expired, taking into account the impact of legally provided events on the course of the deadline. We do not always count from the end of the contract or file transfer.
Other accounting evidenceAccording to the appropriate category of art. 74 of the Accounting Act, usually 5 years, with the appropriate start for the given documentation. Contracts, claims, and longer obligations of a specific document require a separate assessment.
Copies of declarations, ZUS reports and their corrections5 years from submission to ZUS in accordance with art. 47 para. 3c of the Act on the Social Security System. This does not shorten the retention period of separate pension and disability insurance evidence.
Documents of the method of confirming and the number of order hours3 years from the due date of the salary, if art. 8a–8c of the Minimum Wage Act applies. Evidence additionally needed for taxes or benefit bases has an appropriate longer period.
Contract of mandate, B2B, lease/use, preliminary and annexes retained as evidenceTo the extent necessary through cooperation, then standardly no longer than 6 years from the end of the year of the entire cooperation's completion. This is an internal organizational period for justified settlement archiving and protection of claims; necessity and scope are subject to annual review, and redundant data is removed earlier. The appropriate longer obligation takes precedence, including 10/50 years for a document actually needed to determine the basis for pension/disability allowance, considering the appropriate payer and regime described above. Not every contract of mandate automatically follows this longer period. The end of cooperation is an organizational point, not a universal start of limitation for every claim. For the termination on 12 October 2026, the standard last day is 31 December 2032. Active cooperation, unsettled longer goal or blockage of a specific case do not allow the necessary evidence to be removed based solely on the deadline.
Other promotion, complaint, settlement, and claim documentsThrough the handling of the case and then to the necessary extent of the relevant settlement, obligation or specified claims. The tax/salary due dates and ZUS report submissions retain their own significance; we do not replace them with the end of any agreement. Specific proceedings or damages may designate an individual period and blockage only for the necessary scope.
Document retained for a specific dispute, incident, or inspectionOnly 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 blocking ends, we verify the remaining appropriate periods, without recounting the entire retention from the unblocking date.
Company mail FLOW APPSOrdinary messages after 730 days are directed to the trash for 30 days, then deleted according to the accepted rule. Necessary evidence of a contract, settlement or case requires extraction to the appropriate documentation before the mail is deleted. The rule does not mean that all technical copies of the provider disappear after this time.
Thulium recordingsMaximum 365 days from the end of the conversation; deleting a customer account includes unnecessary recordings, with assessment of individual exceptions. The recording period is separate from the notification time and metadata.
History of reports and Thulium telephony metadata24 months from the case closing, and for a conversation without a separate case — from the end of the conversation. Necessary evidence of a specific contract, complaint, or dispute is allocated to documentation with the appropriate period.
Marketing profile and activity history MailerLiteMaximum 3 years from the last documented activity of the recipient related to this purpose, earlier upon the cessation of the purpose or appropriate request. Automatic campaign sending, synchronization, and technical change do not renew the term. Withdrawal of consent stops marketing immediately; minimal evidence of objection has a separate scope. After qualification, we order permanent deletion; the provider executes the further cycle up to 30 days. Removing contact from the current list is not equivalent to permanently deleting the history.
Email invitations for reviews TrustMateIn the absence of a review, invitation data is deleted by the provider after 60 days from sending, according to § 14 sec. 4 of its regulations. Earlier withdrawal of consent and cessation of purpose are handled separately; a public review has its own rules and does not disappear automatically after withdrawing consent for invitations.
SMS contents and numbers at SMSAPIUp to 12 months from sending the message according to the accepted organizational rule. Own logs and necessary evidence of a specific notification have a separate purpose and period.
Consents, withdrawals, and objectionsMinimum evidence of choice for the time needed to demonstrate the basis and protection of rights; an entry blocking further contact — for the justified time of respecting the objection, with a review. This does not include further marketing or retention of complete files.
Regular technical logs and loginsUp to 180 days from the event. Minimum evidence of a specific incident is allocated to the appropriate case. The validity of a session or code is not the retention period for all logs.
Selected audit metadata operationsUp to 24 months from the operation, within 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 BusinessWe order deletion up to 30 days from the end of the case/analysis, separately for conversation and saved files in Library/Space or project. The required result is saved earlier in CRM with a category appropriate for the case. This is our operation execution term, separate from the further cycle and exceptions of the provider described in item 18. Revoking access from an employee does not delete their content.
Historical AirtableNot part of the current service scope. Required historical evidence is subject to the original term of the appropriate category; unnecessary copies must be removed after inventory. Import into CRM does not initiate a new multi-year term.
GA4Event data: specified period of 14 months and monthly Google deletion cycle after its expiration. User ID data: 14 months with reset enabled upon new activity. This also includes User-ID data within 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 ad lists have separate rules, described in section 12.
Minimum confirmation of acknowledgment of the policy in the portalConfirmation of the current version is retained until replaced by the next publication, and then for 24 calendar months from the actual replacement. The period does not begin from the click 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 information accountability. The published content itself remains in history.

Planned push channel

Once the push is launched, the accepted rule for self-registration of installation is 30 days without actual authenticated activity of this installation. After this period, registration does not qualify for a new dispatch and is subject to removal in the process of the appropriate service. Employee action, automated task, or dispatch attempt do not renew activity. Upon receiving information about disconnection, we immediately disable qualification for new dispatches; disconnected or revoked registration is removed after 30 days from the first disconnection. A new valid registration can reactivate the record.

The content of messages and push attempts will be retained for 6 calendar months from the creation of the message; beyond this boundary, the message will not be available in operational history and, along with attempts, will be subject to deletion. The deletion request includes unnecessary data earlier. These are own system periods, separate from Google, Apple retention, and copies.

Calculation of dates, execution, and copies

In our process for orders constituting the title for insurance, the date of notification to ZUS corresponds to the day of signing the appropriate contract. In determining the archive regime, we consider the first proper order for the given payer and the entire history of cooperation. The retention periods for pension and disability evidence and copies of ZUS reports commence from the events indicated in the table, not automatically from the signing of the contract.

The system calculates the retention period of the document on an ongoing basis based on its type and the appropriate event. We do not assign cooperation documentation to a single contract: an active contract protects this documentation, and its period runs after the termination of all contracts. A regular identity copy, selfie, and partner change screenshot have separate short terms described in the table, even during active cooperation; the foreigner's document has its own legalization rule. The Chief Accountant is responsible for accounting and ZUS documentation, the Taxi License Administrator for licensing documents, and the Database Administrator for technical execution and deletion records. Employees explain deficiencies and handle justified exceptions and blocks. Once launched, the retention task deletes documents after the appropriate period and re-checking current sources, blocks, and handled copies; reading or publishing the policy is not proof of deletion.

The last day of retention "until" is the date of the event plus the appropriate period; deletion is due "from" the next calendar day. For a common verified identity document 11.10.2026 these are 10.11.2026 and 11.11.2026; for a selfie 18.10.2026 and 19.10.2026 respectively. When appropriate cooperation or case is ongoing, the date dependent on its end is not yet known. After the cessation of the actual purpose and period, we instruct or perform deletion in the system and with relevant suppliers without undue delay. The lapse of the date or the instruction itself does not confirm the completion of the operation; an error requires repetition.

CyberStorage is a document storage space, not a short-term backup. Every file, version, thumbnail, and export requires a period appropriate for the contained data. An identifiable PDF remains personal data even after removing a name from the profile or pseudonymizing the connection.

The adopted server backup rotation is 28 days. Data deleted from the current system may remain until the backup expires. Backups have limited access and are used for emergency recovery; after recovery, deletions and objections are reapplied before regular use. This period does not define the retention of documents in CyberStorage or all copies at external providers.

Historical Airtable and exports are subject to inventory: necessary evidence retains the original deadline of the appropriate category, and an unnecessary copy is designated for deletion. Transfer to CRM does not start a new period. This rule does not mean that all old copies have already been deleted.

Once all appropriate purposes have ceased, we delete the data or genuinely anonymize it. A hash, record concealment, or the removal of a first name alone does not guarantee anonymity. For continued statutory retention, we limit access and use to the appropriate purpose.

8. Hosting, security, and data on the phone

The service and CRM are maintained on the cyber_Folks infrastructure. Logs may contain IP, request time, resource, response code, referrer, and information about the browser and device. We use encrypted HTTPS connections, password protection, session and permission control, logging of significant operations, backups, and updates. Access to health, criminal records, legalization, and archives is related to a necessary task and authorization.

Do not send passwords, SMS codes, full documents, or special data through a channel that does not need them for a case. In case of a breach, we take actions required by GDPR, including proper notifications to the authority and data subjects.

Planned application security measures

Upon starting the application, session tokens and a trusted device secret will be stored in a secure system storage. The app will also save language and tutorial preferences and, when using push notifications, channel settings and a unique installation identifier. Logging out will remove local session tokens and main account data; it does not mean deleting every preference, cache, or file saved by you outside the app space.

The adopted validities are: access token 24 hours, refresh token 30 days with rotation upon renewal, login SMS code 10 minutes, and device trust 180 days. The validity of the permission differs from the record and log retention period. An withdrawn or expired permission will not allow further authentication.

Optional operational notifications

The planned push channel will be enabled and disabled separately on each phone. Refusal will not block documents and settlements in the app or portal. The channel will be used for information about your account, document, or settlement; we do not plan advertisements or new offers via push. Its activation is not marketing consent.

Google will receive the delivery token, title, content, and technical message identifiers; on iOS, Apple APNs participates in the delivery. The notification may be visible on the lock screen. Protected details will be available after logging in, and the message should be general, e.g., “A new settlement is available. Check the app,” without PESEL, diagnosis, criminal information, and confidential amounts.

The planned scope of Firebase includes push delivery and installation identifiers. It does not include mobile Firebase Analytics or Crashlytics; documents, login, and settlements are handled by its own service. We do not plan to measure opens or clicks of pushes on our own. Acceptance of the request by FCM does not confirm delivery or reading of the message.

Disabling the channel will stop new shipments after the information reaches the service. A change made offline may arrive after reconnecting; a message already transmitted to the provider cannot be equated with a new shipment after disconnection. Android/iOS permission concerns notification display and does not preclude SDK initialization or consent for all Google purposes.

Removing registration in your own system or FCM token does not automatically remove the Firebase Installation ID. According to Google information on Firebase privacy the removal of FID data from current systems and backups may take up to 180 days from the effective request for its deletion. This is the provider's period after the request, distinct from our 30 days and 6 months.

9. Cookies and similar technologies

Cookies store information in the browser; similar functions are performed by local storage, tags, pixels, and identifiers. Cookies can be session-based or remain for a set time. They originate from the visited site or an external provider.

  • Necessary and security — login, session, request protection, and remembering privacy choices, within the scope of actual necessity.
  • Functional — optional additional features, including the Thulium widget.
  • Analytical — measurement of site usage using GA4.
  • Marketing — ad measurement, remarketing, audience groups, and personalization using Google Ads and Meta Pixel.

The scope of tools depends on the site and enabled features. A session or privacy choice cookie does not constitute consent for advertising. Web cookie rules do not mean pixel operation on every screen of the planned application; navigating to a page or WebView is subject to that page's mechanisms.

10. Consent panel and Consent Mode

On pages with the “Cookie Settings” panel, you can separately choose functional, analytical, and marketing categories, reject optional categories, and later change your selection. The choice is remembered for 180 days in a cookie assigned to a specific host or until earlier removal or change of the proper version of the information. It is not automatically shared with all subdomains. The record does not contain a password, balance, contract data, or form content.

For Google services, the analytical choice controls the analytics_storage parameter, and the marketing choice controls ad_storage, ad_user_data, and ad_personalization. The default state before selection is denied. Tags from other providers require their own conditions to launch; Consent Mode itself does not control all external scripts.

Withdrawing consent is free and does not affect the legality of prior processing. It halts operations dependent on that consent; previously obtained data are subject to appropriate rights and retention. You can delete cookies previously saved in your browser. A goal change requiring a new choice is not approved by the old record.

11. Advanced Consent Mode and signals upon refusal

The service uses Advanced Consent Mode. In this mode, the Google container and tags can be loaded and connect to Google in the denied state, before a choice or after refusal. This does not imply activation of optional cookies or personalization; however, it might mean sending limited signals. The lack of cookies is not equivalent to the absence of a connection, data transfer, or automatic anonymity.

According to Google documentation the signals may include consent status, event time, browser, referrer, limited address of the site, random value for the visit, and campaign identifiers; transmission is also associated with IP. Google uses specific limited signals for statistics and modeling. Measurement, modeling, and advertising remain separate purposes from technically remembering the choice.

We limit addresses and parameters transmitted to tools: they cannot contain login tokens, PESEL, balance, document content, contract data, or form content. Campaign parameters do not serve to transmit personally identifiable information. On pages containing one-time authentication tokens, external tracking is disabled.

The bases and choices from points 3 and 10 relate to specific purposes and operations. The mere designation of a signal as "cookie-less" or setting denied does not establish a legally justified interest or an exception from device access requirements. If you want to technically block connections to external domains, you can use browser settings or a resource blocking tool; this does not replace the Administrator's obligations.

12. Google Analytics, Google Signals, and Google Ads

Google Analytics 4 is used for analyzing site usage, and Google Tag Manager for tag management. Measurement may include browser, device, approximate location derived from IP, visit source, pages, and events. Analytical and advertising goals and choices are separate.

The adopted configuration GA4 includes Google Signals, detailed device and location data, and ad personalization, along with the connection to Google Ads. Google Signals might combine visit information with information from Google users who have relevant personalization settings, for cross-device analysis and advertising functions. These are not solely anonymous visit counters. The service setting does not replace proper visitor consent and does not imply application access to phone GPS.

In GA4 services where the User-ID function is implemented, we can connect the activity of a logged-in user on various devices, browsers, and sessions using a pseudonymous identifier assigned to their account. This serves to analyze site and portal usage and reduce multiple counting of the same person. It applies to measurements within the same GA4 service and services covered by its actual implementation. The mere selection of User-ID in the reporting panel does not result in the transfer of the identifier — it also needs to be provided by the site or portal.

The use of User-ID is conditioned on analytics consent. 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. Analytics consent does not automatically activate advertising goals, which require proper marketing choice.

User-ID does not contain first name, last name, email address, phone number, PESEL, or identity document data. We do not use email or phone hash or FCM notification token for this purpose either. Since we can link the identifier to the account, it is pseudonymization, not anonymity. We distinguish User-ID from the browser/device identifier, Google Signals, and form data used for Google Ads enhanced conversions. The description of User-ID applies to sites and portals; it does not change the described mobile Firebase scope.

GA4 event data have a retention period of 14 months, and user identifier data 14 months with a reset upon new 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 apply. The same period covers collected User-ID data when the function indeed receives an account identifier. We do not use GA4 export to BigQuery. Retention does not automatically limit standard aggregate reports.

Google Ads is used for conversion measurement, remarketing, and campaign effectiveness assessment in terms of proper marketing choice, separate from analytical. Enhanced conversions can use email, phone, first name, last name, city, and country from the registration form for conversion matching and campaign optimization. The data may be normalized and hashed; hashing is not automatically anonymization. Merely creating an account does not express consent for this purpose. Without the appropriate marketing choice, the portal does not share these form data tags.

We do not transmit scans, health data, KRK, PESEL, or confidential contract documents to Google Analytics. Information: Google privacy policy, GA4 data storage User-ID feature and enhanced conversions Google Ads.

13. Meta Pixel and advertising audiences

With proper marketing consent, Meta Pixel can process visits and actions on the site, IP, browser, device, referrer, cookies, and advertising identifiers. It is used for measuring ad effectiveness, audience groups, remarketing, and personalization.

The registration tag, with appropriate marketing consent, may use advanced matching with email and phone to measure ad effectiveness. The hash of the identifier can still be used for person matching; we do not treat it as anonymous statistics. Account registration and analytical choice do not replace the marketing choice.

In terms of event data collection and transfer using Meta Pixel, FLOW APPS and Meta Platforms Ireland Limited may act as joint controllers in accordance with Meta Business Tools terms and administrator appendix. This pertains to this stage and data, not the entire FLOW APPS account, documentation, or settlements. Further processing by Meta is subject to its own terms. You can exercise rights with FLOW APPS or Meta; contact for FLOW APPS: kontakt@flowapps.pl.

Information: Meta privacy policy and Meta cookies policy.

14. Contact, chat, call recordings, and voluntary opinions

Thulium serves for handling contact, inquiries, and conversations. The optional chat widget is activated according to functional choice; refusal does not limit email contact. The chat may process session, IP, device information, and voluntarily submitted content. Do not send passwords, one-time codes, diagnoses, or unnecessary identity scans.

Before recording a conversation, you receive information about recording, purpose, and available alternative contact. The appropriate basis depends on the case handling described in item 3. Recordings are stored for a maximum of 365 days from the end of the conversation; inquiries and metadata up to 24 months from case closure, and conversation metadata without a separate case—from its end. Necessary evidence of a specific case is distinguished with appropriate justification and period. Revocation of the widget choice does not automatically delete the case history.

Separate consent for feedback requests by TrustMate

Invitations pertain to services of FLOW APPS sp. z o.o. With your separate, voluntary consent, FLOW APPS sp. z o.o. may commission TrustMate S.A. to send an email with a request for feedback, reminders, and thanks. We do not use the SMS channel in this process. The choice indicates the controller, purpose, and email channel; it is not pre-selected. Refusal, lack of feedback, or withdrawal of consent does not affect the agreement or settlements. Consent to offers or reviewing the Policy does not replace this choice.

When sending invitations, FLOW APPS is the data controller, and TrustMate acts on its behalf as a data processor based on a data processing agreement, which can be concluded electronically. We provide the email address and minimum data needed 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 contact with FLOW APPS. Upon receipt of consent withdrawal, we stop further messages for this purpose, including reminders already scheduled in TrustMate. The service is performed by authorized personnel; withdrawal of consent does not affect the compliance of prior processing.

If within 60 days from sending the invitation you do not provide feedback, TrustMate, in accordance with § 14 para. 4 of its regulations, deletes the data provided for this purpose. This does not replace prior handling of consent withdrawal or termination of purpose. If you provide feedback, it may be publicly presented, including on the partner's pages and in the search engine. Within the scope of its service and feedback, TrustMate acts as a separate controller. Withdrawal of consent for invitations does not automatically delete public feedback.

TrustMate S.A., ul. Bartoszowicka 3, 51-641 Wrocław: privacy policy, service regulations and public processing agreement. The 14-day term for deleting entrusted data after the company's agreement with the provider ends is separate from the recipient's consent withdrawal and the rules of public feedback.

15. Form protection — reCAPTCHA

Google reCAPTCHA Enterprise is used to protect public registration forms and password reminder forms from automated abuse. Google evaluates technical signals, such as IP, browser, device, time, and interaction method; the verification token is sent to our service. This is not Firebase Authentication or earnings analysis. After activating the appropriate function, the application may display the protection page in an embedded view.

We base our security purpose on art. 6 sec. 1 letter f of GDPR to the necessary and proportional extent. The exception from consent for saving or reading information in the device from art. 399 of the Polish Telecommunications Law applies only to truly necessary security operations for the requested service; it does not automatically include all Google operations or a separate advertising purpose.

In case of a problem with the form, you can contact us directly via email. Google information: privacy and terms of service.

16. Key cookies and similar identifiers

The lifespan of the identifier in the device differs from server data retention. The table presents the mechanisms of the Service and typical periods of external service cookies; a provider or setting of a specific function may specify a shorter time.

Name or typePurpose and categoryPeriod or criterion
CookieConsent on main company pagesRemembering category choice — necessary1 year, or earlier removal or required re-selection
Privacy choice cookie in the portalRemembering category and version — necessary180 days or earlier removal or change of the relevant version
Session and form securityLogin, session maintenance, and request protection — necessarySession time or the validity period of the appropriate function's security
_ga, _ga_*Browser distinction and measurements — analyticalTypically up to 24 months according to the setting; separately GA4 data 14 months and described user data reset
_gcl_au, _gcl_*Advertisement and conversion measurement — marketingTypically up to 90 days according to the setting; this is not the period for each audience or report group
_fbp and used Meta identifiersAdvertisement measurement and matching — marketingTypically up to 90 days according to the used function
Chat identifiersSupport for the selected widget — functionalSession or time appropriate for the used provider function
reCAPTCHA identifiers and risk signalsForm securityTime appropriate for the operation of the used reCAPTCHA version; we evaluate voluntary and necessary purposes separately
Planned session tokens and trusted device secretApplication authentication and securityThe validity of 24 hours / 30 days / 180 days described in item 8 does not automatically determine the retention period for all records.
Planned own installation identifier, FCM and FID.Optional operational push channel.Own registration: rules described in item 7 30 days; history 6 months. Google data and local preferences are subject to separate rules.

17. Change of privacy choice.

In the "Cookie Settings" panel on the appropriate page, you can reject, change, or withdraw optional consents. You can also delete cookies and page memory in your browser. Blocking an essential session may prevent logging in; refusing an optional category does not block basic account services.

You can disable marketing emails/SMS and TrustMate invitations independently via the provided opt-out mechanism or by contacting FLOW APPS. Once the app is provided, push notifications can be disabled in the app or phone settings; a choice on one device does not automatically change the setting on another.

Deleting the app, cookies, or withdrawing permission does not delete all data previously obtained by the Controller and providers. Such a request is considered according to item 19. A marketing choice, consent to an opinion, familiarization with the Policy, and parental consent to the contract are separate actions.

18. Analyses, profiling, and human involvement.

We analyze activity and settlements for performance presentation, cooperation terms application, correctness control, and abuse clarification. Reports may include order bookings and cancellations, revenues, and comparisons of days and hours from platform data. This does not require phone GPS. Historical results or forecasts do not guarantee future earnings.

Authorized employees use the company ChatGPT Business for statistics, calculations, and reports. Simply reading the tool does not constitute settlement execution, approval, deletion, or status change. An employee checks the AI result and may change it before applying consequences in the person's case.

We limit access to what is needed for analysis and, where possible, aggregate data. A person's ID, device, or a potentially related case may still identify a person; the absence of a name does not ensure anonymity. Ordinary analysis does not require full scans, PESEL, health assessments, or criminal records. Assessment of identifiable performance or risk may constitute profiling despite human involvement.

OpenAI indicates that Business data is not by default used for model training. This does not imply no storage. Revoking an employee's access does not delete their conversations or files. Deleting a chat is a separate operation; according to the provider's rules, it is usually designated for permanent deletion within 30 days, with legal, security, or prior de-identification exceptions. Separate files in Library/Space and projects require separate handling. Information: user access cycle and OpenAI security and retention.

Our rule requires commissioning the deletion of working conversations and separately saved files within 30 days from case or analysis completion. We record the necessary result in CRM earlier with a category and term appropriate for the case. Disconnecting the integration, revoking access, or deleting a conversation does not replace checking other copies. Our commissioning term differs from the provider's further cycle.

Google and Meta advertising profiling is separate and subject to items 12–13 and privacy choices. Ordinary calculations apply the contract or program terms; you can report a doubtful result for manual verification, obtain an explanation, and contest the data. We do not treat the AI result as a standalone basis for a decision with legal effect or similarly important. AI serves as an aid to the employee and does not independently make decisions of legal or similarly important effect regarding the driver.

19. Your rights and account deletion

Within the scope provided by the GDPR, you may access and obtain a copy of your data, rectify it, request deletion or restriction, and if conditions are met, data portability. You may object to processing based on legitimate interests due to reasons related to your situation and at any time to direct marketing and related profiling. You can withdraw consent without affecting the legality of past actions.

Direct your request to kontakt@flowapps.pl or in writing to FLOW APPS. In case of justified doubts, we verify identity only to the extent necessary to protect against unauthorized operations.

We respond without undue delay, generally within a month of receiving the request. For justified complexity or number of requests, we may extend the deadline by another two months, informing in the first month about the reasons. In case of refusal, we explain the reason and protection measures. You can file a complaint with the President of the Personal Data Protection Office: uodo.gov.pl, and seek judicial protection.

Request to delete FLOW APPS account

Submit a request through the account deletion page on the FLOW APPS portal or via e-mail. Once the appropriate app function is available, also directly in the app. Uninstalling the app does not delete the account.

With an active agreement, you receive information about the consequences and how to report its termination. Termination occurs according to the agreement and law. Deregistration from ZUS has its statutory deadline from the end of the insurance title. The request for deletion does not automatically terminate any agreement.

Access blocking, contract termination, and deletion or anonymization of data are separate stages. The obligation to retain the appropriate tax, insurance, or specific case document may limit deletion. An active agreement does not justify retaining unnecessary data and does not block disabling an optional channel. Remaining data have a scope, basis, and duration appropriate for the category in section 7.

The response distinguishes between deleted data, retained documents and their bases/durations, individual exceptions, handling at recipients, and extinguishing copies. Retained identifying originals do not allow stating total anonymization. Technical queue, backup, or waiting for contract termination do not substitute for a response to a request within the GDPR timeframe.

20. Publication, historical versions and notification of change

The policy informs about data processing. Reading, reading or confirming receipt is not consent to marketing, any new purpose or automatic acceptance of a contract change. A purpose requiring separate consent is not initiated by mere publication.

The published version has a number and an indicated effective date. On the policy page in the portal, we provide the current version and marked historical versions. An older document remains in history after the next one is published. A draft prepared by employees does not replace the currently effective public version. Links in the Service, and once launched, in apps lead to the appropriate published policy.

We inform about significant changes on the portal, and in the chosen email channel, also active users with an email message. 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 saves confirmation of a specific version, and "Later" postpones the information without confirmation and without blocking the portal. Sending a message, its receipt by transport, and clicking confirmation are separate states; mere display or sending does not prove familiarity. We store the confirmation of the current version until it is replaced, then 24 months; it is not consent for marketing or TrustMate.

The translation refers to the marked source version and maintains its meaning. Changing the translation does not independently establish a new purpose. You can clarify doubts by contacting FLOW APPS.

21. Contact

FLOW APPS LIMITED LIABILITY COMPANY, ul. Proletariacka 36 loc. 11, 93-569 Łódź, KRS 0000909050, NIP 7272850986, REGON 389306039.

Account, cooperation, documents, security, and data protection issues: kontakt@flowapps.pl.

Service: flowapps.pl. Portal: portal.flowapps.pl. Current policy and its history: privacy policy on the FLOW APPS portal.

Published version history