COOKIES
1
Without consent: one cookie that stores your decision. Any others come from the tools you switch on yourself.
LEGAL · LAST UPDATED 09.2026
In short: our own measurement uses no cookies and no identifiers; analytics and advertising tools run only with your consent. Full text below.
COOKIES
1
Without consent: one cookie that stores your decision. Any others come from the tools you switch on yourself.
IDENTIFIER
none
We never link a visit to a person or a device.
RETENTION
3 months
Aggregate usage data is deleted after three months.
Draft translation pending legal review. The Polish version is the binding one.
version 1.1 | effective from 20 September 2026
This document covers the GapApp mobile application, website, landing page, forms, and related analytics and marketing functionalities.
Controller: Łukasz Mocarski, Nowy Dwór Gdański 82-100, ul. Sienkiewicza 27/16
Privacy and data protection contact: privacy@fillthegap.app
This Privacy Policy describes the rules governing the processing of personal data and the use of analytics technologies, cookies, similar technologies, and marketing tools in connection with the use of GapApp.
The controller of personal data is Łukasz Mocarski, Nowy Dwór Gdański 82-100, ul. Sienkiewicza 27/16 (hereinafter the “Controller” or “GapApp”). For matters concerning privacy, personal data protection, or the exercise of rights under the GDPR, you may contact: privacy@fillthegap.app.
This Policy has been prepared in accordance with Regulation (EU) 2016/679 of the European Parliament and of the Council (“GDPR”), the Polish Act of 10 May 2018 on the Protection of Personal Data, and the Polish Act of 12 July 2024 - Electronic Communications Law (“PKE”), in particular the rules concerning marketing communications and the storage of, or access to, information on a user’s device.
The scope of data processed depends on how GapApp is used and which functionalities are enabled. In particular, we may process:
GapApp does not require users to provide special categories of personal data within the meaning of Article 9 GDPR, in particular health data. Users should not include such information in free-text fields, messages, link parameters, or data transmitted to analytics or advertising tools.
| Purpose | Legal basis | Period |
|---|---|---|
| Creating and maintaining an account; providing GapApp functionalities | Article 6(1)(b) GDPR - performance of a contract or steps taken prior to entering into a contract | for as long as the account is maintained, and subsequently for the period necessary for settlements, legal obligations, and the establishment, exercise, or defence of claims |
| User or trainer profile; publication of availability and offers; searching and matching the parties | Article 6(1)(b) GDPR | for the period of use of the service and in accordance with the retention of operational data |
| Organising a training session, accepting an offer, booking, and managing status | Article 6(1)(b) GDPR | until completion of the process, and subsequently for the period justified by settlements and claims |
| Contact and handling enquiries | Article 6(1)(b) GDPR where the matter concerns a contract; in other cases Article 6(1)(f) GDPR | until the matter is closed, and subsequently for the period justified by the possibility of establishing, exercising, or defending claims |
| Security, fraud prevention, diagnostics, and service continuity | Article 6(1)(f) GDPR - the Controller’s legitimate interest | for the period necessary to achieve the purpose, taking into account periodic deletion of logs |
| Cloudflare Web Analytics - basic privacy-first analytics without cookies | Article 6(1)(f) GDPR - legitimate interest in measuring service operation and performance | in accordance with the current retention rules of Cloudflare Web Analytics; unsampled beacon data is stored for 7 days, after which data may be retained in aggregated form in accordance with Cloudflare’s retention rules |
| GapApp’s own analytics beacon without cookies or persistent identifiers | Article 6(1)(f) GDPR - legitimate interest in analysing usability and product development | raw data for up to 3 months; then deleted or retained only as aggregated statistics |
| Google Analytics 4 - additional cookie-based analytics | Article 6(1)(a) GDPR - consent; Articles 399-400 PKE with respect to access to information on the device | until consent is withdrawn; user-level and event-level data for a maximum of 14 months in accordance with GA4 configuration; cookies in accordance with Section 11 |
| Meta Pixel - advertising measurement, attribution, optimisation, remarketing, and audience creation | Article 6(1)(a) GDPR - consent; Articles 399-400 PKE | until consent is withdrawn and in accordance with identifier retention periods and Meta’s rules |
| Marketing communications by email, SMS, or marketing push notifications | Article 6(1)(a) GDPR and prior consent required under Article 398 PKE | until consent is withdrawn or the relevant marketing channel is discontinued |
| Recording consents and demonstrating compliance | Article 6(1)(c) GDPR with respect to the accountability obligation and Article 6(1)(f) GDPR | for the period necessary to demonstrate compliance, taking into account the applicable limitation periods |
| Accounting, taxes, and legal obligations | Article 6(1)(c) GDPR | for the period required by law |
| Establishment, exercise, or defence of claims | Article 6(1)(f) GDPR | until the expiry of the applicable limitation period for claims |
GapApp may use location to search for nearby trainers, training sessions, and availability. Location may be based on a place entered manually by the user, the approximate location of the device, or - after the relevant system permission has been granted - a more precise device location.
Access to device location is enabled only in connection with a feature that requires location information. The user may revoke location permission in the operating system settings. Disabling location may limit “nearby” features, but does not affect features that do not require location. A location saved in the profile as a search area or service area is retained until it is changed, deleted, or the account is deleted.
GapApp may send push notifications concerning, among other things, availability, offers, bookings, status changes, and other events related to use of the service. Operational notifications are related to the performance of GapApp functionalities. Marketing notifications are sent only after the required consent has been obtained.
A device token may be processed for the technical delivery of push notifications. The user may disable notifications in the operating system settings and, where the feature is available, also in the GapApp settings.
Commercial information and direct marketing using email, SMS, push notifications, other telecommunications terminal equipment, or automated calling systems are sent after obtaining the prior consent required under Article 398 PKE, where that provision applies to the relevant channel.
Consent to marketing is separate from consent to online analytics and marketing technologies. Refusing consent to Google Analytics 4 or Meta Pixel does not restrict access to the basic functionalities of GapApp. Consent may be withdrawn at any time without affecting the lawfulness of processing carried out before its withdrawal.
GapApp uses Cloudflare Web Analytics to obtain aggregated information about traffic, performance, and the way public pages of the service are used. In its standard model, Cloudflare Web Analytics does not use cookies or localStorage for measurement and does not create user profiles based on fingerprinting. The tool operates on a privacy-first basis and collects limited information necessary to generate statistics and measure website performance.
To the extent that data constituting personal data may be processed during technical transmission, the legal basis for processing by GapApp is Article 6(1)(f) GDPR - the legitimate interest in analysing the operation and performance of the service. Cloudflare Web Analytics is not used for remarketing or to identify specific individuals.
The provider is Cloudflare, Inc. and the relevant Cloudflare group entities providing the service to the Controller. Information about Cloudflare privacy practices is available at: https://www.cloudflare.com/privacypolicy/.
Cloudflare is also used as a provider of technical infrastructure for making the GapApp website and landing page available, securing them, and operating them, including through Cloudflare Workers. In connection with the provision of these services, Cloudflare may process technical request data, such as IP addresses and data contained in connection logs, to the extent necessary to ensure service operation, security, and diagnostics. The legal basis for processing by the Controller is Article 6(1)(f) GDPR - the legitimate interest in ensuring the security and proper operation of the service.
GapApp uses its own analytics mechanism to assess product usability. The mechanism may measure, among other things, scroll depth, time spent in individual sections, and clicks on selected interface elements.
The beacon does not use cookies, localStorage, fingerprinting, or a persistent user or device identifier, and it does not link analytics events to a GapApp account. Raw event data is retained for a maximum of 3 months and then deleted or retained only as aggregated statistics that are not used to identify users. The legal basis is Article 6(1)(f) GDPR - the legitimate interest in analysing usability and product development.
GapApp uses Google Tag Manager (“GTM”) as a technical tool for managing tags and enforcing users’ consent choices. The service provider is Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland.
GTM is not treated as an independent consent mechanism for analytics or marketing. GapApp uses a consent-first configuration: Google Analytics 4 and Meta Pixel tags remain blocked until the appropriate consent is obtained. For Google Analytics, Basic Consent Mode or equivalent technical blocking is used, under which no measurement events are sent to Google Analytics before analytics consent is given.
After consent to analytics technologies is given, GapApp activates Google Analytics 4 (“GA4”) to measure use of the service, the quality of user journeys, traffic sources, the effectiveness of interface elements, and product conversions. GA4 may collect, among other things, information about page views and events, session parameters, the device and browser, approximate location, referral source, and identifiers stored in cookies. Google states that IP addresses in GA4 are not logged or stored as data available in the Analytics service.
GA4 uses, in particular, first-party “_ga” cookies and cookies beginning with “ga”, which are used to distinguish users and maintain session state. Their default lifetime is up to 2 years, subject to browser restrictions and service configuration.
GA4 is activated only after analytics consent has been given. The legal basis for processing by the Controller is Article 6(1)(a) GDPR and the consent required under Articles 399-400 PKE in relation to storing or accessing information on the device. Consent may be withdrawn at any time in the privacy/cookie settings.
GapApp does not send to GA4 the contents of free-text form fields, special categories of personal data, or contact data such as an email address or telephone number as event parameters. Google Analytics advertising features, Google Signals, user-provided data collection, and enhanced conversions are not used in the configuration described in this Policy.
User-level and event-level data in the standard GA4 service is retained for a maximum of 14 months in accordance with the Analytics property settings. Aggregated statistical reports may remain available for longer. Information about Google’s privacy practices: https://policies.google.com/privacy.
After consent to marketing technologies is given, GapApp activates Meta Pixel - a tool provided by Meta Platforms Ireland Limited, Merrion Road, Ballsbridge, Dublin D04 X2K5, Ireland. Meta Pixel is used to measure advertising effectiveness, attribute conversions, optimise campaigns, build audiences, conduct remarketing, and better tailor advertising to user activity.
Meta Pixel may process, among other things, information about the page visited and its URL, referral source, time and type of event, browser and device data, the IP address used in transmission, identifiers stored in cookies or similar technologies, in particular “_fbp” and, where applicable, “_fbc”, as well as information about events and conversions configured in the Pixel.
Meta Pixel remains completely blocked until marketing consent is given. The legal basis for processing by the Controller is Article 6(1)(a) GDPR and Articles 399-400 PKE. Withdrawal of consent blocks the transmission of new marketing events from GapApp to Meta. Withdrawal of consent does not automatically erase data previously lawfully transmitted to Meta; further processing is governed by Meta’s rules and the rights provided for under the GDPR.
Under the configuration covered by this Policy, GapApp does not use Meta Advanced Matching or the Conversions API and does not send Meta contact data for matching purposes, special categories of personal data, health data, or the contents of free-text form fields.
With respect to the collection of event data through Meta Pixel and its transmission to Meta, the Controller and Meta may act as joint controllers pursuant to Article 26 GDPR. With respect to Meta’s further processing of data after receipt, Meta acts in accordance with its own terms and privacy policies. Information about Meta privacy practices: https://www.facebook.com/privacy/policy/.
The GapApp website may use cookies, localStorage, tags, pixels, and similar technologies. Not all technologies used by GapApp are cookie-based: Cloudflare Web Analytics and the proprietary beacon described in Section 8 operate without cookies. Google Analytics 4 and Meta Pixel are optional technologies and remain blocked until the appropriate consent is obtained.
We use the following categories of technologies:
The consent management mechanism (CMP) provides at least the following options: “Accept all”, “Reject optional”, and “Settings”. Optional categories are disabled by default. No action, closing the banner, scrolling the page, or continuing to use the service is not treated as consent. Rejecting optional technologies does not block basic access to the service.
The user may reopen the privacy/cookie settings from the service at any time and change their choice. Withdrawing consent is as easy as giving it. GapApp stores technical evidence of the consent choice to the extent necessary to demonstrate compliance, and the user’s choice itself is remembered for a maximum of 12 months, after which the service may ask the user to set their preferences again.
| Technology | Category | Purpose | Activation / period |
|---|---|---|---|
| Cloudflare Web Analytics | basic analytics without cookies | aggregated traffic and performance measurement; no cookies/localStorage | operates without cookies; unsampled beacon data for up to 7 days, followed by aggregated data in accordance with Cloudflare retention rules |
| GapApp proprietary beacon | basic analytics without cookies | scroll depth, time spent in sections, clicks; no persistent identifiers | raw data for up to 3 months |
| Google Tag Manager | technical tool | tag management and enforcement of consent states | GTM does not activate GA4/Meta tags before the appropriate consent is obtained |
| _ga | analytics - GA4 | distinguishing users | after analytics consent; by default up to 2 years |
| ga* | analytics - GA4 | maintaining session state | after analytics consent; by default up to 2 years |
| _fbp | marketing - Meta | browser identification for measurement and advertising purposes | after marketing consent; in accordance with Meta configuration, typically up to 90 days |
| _fbc | marketing - Meta | attribution of a visit following a click on a Meta advertisement, where the identifier is created | after marketing consent; in accordance with Meta configuration, typically up to 90 days |
| CMP choice identifier | necessary | remembering privacy choices and demonstrating consent | up to 12 months |
Data may be disclosed to entities supporting the Controller in operating GapApp, solely to the extent necessary for them to perform their tasks. Recipients or categories of recipients may include:
Where a provider acts as a processor, it processes data on the Controller’s documented instructions pursuant to the required agreement. Where a provider independently determines the purposes and means of further processing, it acts as a separate controller or, where appropriate, as a joint controller.
GapApp is a platform that connects users and trainers. Before an offer is accepted or a booking is made, the other party may see information necessary to assess suitability, including in particular the trainer’s name or display name, profile photo and description, specialisations, experience, service location, availability, offer parameters, and information necessary to search for or respond to a user request.
After an offer is accepted or a booking is made, the parties may receive additional information necessary to organise the training session and make contact, in particular contact details or organisational information relating to the place and time. GapApp limits data sharing to information necessary for the specific functionality.
Data obtained through GapApp does not constitute a freely available marketing database. A trainer may not use a user’s data for independent marketing without their own legal basis and without complying with the obligations arising from the GDPR and PKE.
Some technology providers may use infrastructure or processors located outside the European Economic Area, in particular in the United States. This applies primarily to certain Cloudflare, Google, and Meta services.
Where personal data is transferred outside the EEA, the Controller uses the mechanisms provided for in Chapter V GDPR, depending on the specific transfer: an adequacy decision of the European Commission, including the EU-US Data Privacy Framework where applicable to the relevant recipient, or the European Commission’s Standard Contractual Clauses together with any required supplementary safeguards. Information about the transfer mechanisms used by providers is available in their current privacy policies and data processing terms.
Data is retained no longer than necessary for the purpose for which it was collected. When determining retention periods, we take into account the nature of the service, the legal basis, tax and accounting obligations, security, and limitation periods for claims.
Under the GDPR, the data subject has, as applicable, the right to:
Requests concerning the exercise of rights may be sent to: privacy@fillthegap.app. Consent settings for cookies and optional technologies may be changed directly in the privacy/cookie settings panel available through the service.
Where specific processing is carried out under a joint controllership arrangement with Meta, rights may be exercised against either joint controller to the extent provided for under the GDPR and the applicable Meta terms.
Providing data necessary to create an account, create a profile, publish an offer, search for a training session, or use a specific functionality is voluntary, but may be necessary to enter into and perform the agreement for the provision of GapApp services. Failure to provide data marked as required may make it impossible to use the relevant functionality.
Consent to Google Analytics 4, Meta Pixel, other optional cookies, or marketing communications is not a condition for using the basic GapApp functionalities that do not require these technologies.
GapApp may use search parameters, location, availability, preferences, and operational data to sort results and match offers. These mechanisms are intended to present more relevant results and do not result in decisions being made about the user solely by automated means that produce legal effects or similarly significantly affect the user within the meaning of Article 22 GDPR.
After marketing consent is given, Meta may use Meta Pixel events to measure advertisements, create audiences, optimise campaigns, and personalise advertising in accordance with its own rules. This may constitute marketing profiling by Meta.
The Controller applies technical and organisational measures appropriate to the risk and to the nature, scope, context, and purposes of processing. These include, in particular, access controls and the principle of least privilege, transmission security, system updates, backup and recovery mechanisms, security-event monitoring, and periodic reviews of access rights and configurations.
The principle of data minimisation is applied in analytics and advertising tools. Special categories of personal data, the contents of free-text form fields, and other data going beyond the documented measurement or advertising purpose are not sent to external platforms.
GapApp is intended for persons aged 18 or over. Persons under 18 should not create an account or provide data through GapApp.
This Policy may be updated in the event of changes to GapApp functionalities, technology providers, processing methods, or applicable law. The current version is published in the app or on the GapApp website. In the event of material changes, the Controller may also inform users through the app, email, or another appropriate channel.
A change to the Policy does not automatically extend the scope of consent previously given. If a new purpose or technology requires consent, the Controller will obtain it before such processing begins.
Last updated: 20 September 2026