| Operator | MM prosta spółka akcyjna (MM P.S.A.), a simple joint-stock company incorporated under Polish law, with its registered office in Warsaw, Poland |
|---|---|
| Address | ul. Przasnyska 2 lok. 8, 01-756 Warsaw, Poland |
| KRS | 0001253975 |
| NIP | 5253098322 |
| REGON | 545262117 |
| Contact | [email protected] | [email protected] | [email protected] | [email protected] |
| Version | 1.1 - legal and editorial status as at 14 July 2026; effective upon publication on the Platform |
| Your choice matters Essential technologies are used only to the extent necessary for security and the service requested by the User. Analytics, marketing and other non-essential technologies are activated only after the consent required by applicable law. Users can change their choices at any time through the consent panel. |
|---|
§ 1. Scope and definitions
1. This Policy explains how MeetMentor uses cookies and similar technologies on websites, applications, panels and other services that refer to it.
2. Cookies are small text files stored on a device or read by a website. Similar technologies may include local storage, session storage, pixels, tags, SDKs, device identifiers and server-side event identifiers.
3. First-party technologies are set or controlled by the Platform. Third-party technologies are provided by external providers integrated with the Platform.
4. Session technologies generally expire when the browser or application session ends. Persistent technologies remain for a specified period or until removed.
5. The current technical list of active technologies, providers, purposes and retention periods is available in the consent-management interface where that interface is deployed.
6. This Policy should be read together with the Privacy Policy, which explains personal-data processing and User rights.
§ 2. Categories of technologies
| Category | Purpose | Consent approach |
|---|---|---|
| Strictly necessary | login, authentication, security, fraud prevention, load balancing, checkout, booking, payment flow, consent storage and core Platform operation | used without optional consent only where necessary for a service requested by the User or another legal exemption applies |
| Preferences / functional | language, time zone, interface settings, accessibility, remembered choices and convenience features | consent where required; some preferences may be necessary for a specifically requested function |
| Analytics / performance | traffic measurement, feature use, error analysis, performance, conversion measurement and service improvement, including Google Analytics where enabled | activated after consent where required |
| Marketing / advertising | campaign measurement, attribution, remarketing, audience creation, ad personalisation and cross-service marketing | activated only after the consent required by applicable law |
| Security and abuse prevention | bot detection, rate limiting, fraud signals, unusual-login detection and protection of the Platform and Users | used where necessary for security or with consent where the technology exceeds what is necessary |
| Embedded third-party content | video, maps, social media, calendars, payment widgets or other externally hosted components | may require consent before loading where the provider sets non-essential technologies |
§ 3. Strictly necessary technologies
1. Strictly necessary technologies may be used to keep a User signed in, protect the Account, maintain a shopping or booking flow, remember privacy choices and provide payment or communication functions requested by the User.
2. These technologies are not used for unrelated advertising merely because they are classified as necessary.
3. Blocking them in a browser or device may prevent login, checkout, security controls or other core functions from operating correctly.
4. Where a third-party provider is essential to a requested payment, video or authentication function, the provider may process technical information necessary to deliver that function under its own or processor role as described in the Privacy Policy.
5. The Operator regularly reviews whether a technology remains necessary and removes or reclassifies it where appropriate.
§ 4. Analytics and Google Analytics
1. The Platform may use Google Analytics to measure traffic, understand use of features, identify technical problems, assess campaigns and improve services.
2. Google Analytics may use cookies or similar identifiers, including cookies commonly named _ga and _ga_<container-id>, depending on the configuration used at the time.
3. Google Analytics is activated only in accordance with the User's analytics-consent choice where consent is required.
4. The Operator configures data collection, retention, advertising integrations and available privacy settings in line with the implemented use case and applicable law.
5. Analytics data may include page and screen views, approximate region, device and browser information, referral source, events, performance and pseudonymous identifiers. The Platform should avoid sending unnecessary directly identifying information to analytics tools.
6. The current provider details and configured retention information are displayed in the consent panel or a provider notice where required.
7. Withdrawing analytics consent prevents future analytics storage or access to the extent technically and legally applicable but does not retroactively erase aggregated statistics already lawfully created.
§ 5. Marketing, attribution and advertising technologies
1. Marketing technologies may be used to measure advertising effectiveness, attribute registrations or Orders to campaigns, limit ad frequency, create audiences, conduct remarketing or personalise advertising.
2. They are activated only after the consent required by the applicable law and according to the categories selected by the User.
3. Consent to marketing technologies is separate from consent to receive email, SMS, telephone or push marketing. One consent does not automatically create the other.
4. A refusal of marketing cookies does not prevent use of the Platform, although advertising may be less relevant and some campaign attribution may be unavailable.
5. Referral links may use short-lived identifiers or storage for Attribution under the Referral Programme. Where consent is legally required for that storage or access, it is used only after the relevant choice.
6. The Operator does not permit Participants to use cookie stuffing, forced redirects or hidden identifier placement.
§ 6. Consent management
1. On the first relevant visit, the User is provided with a consent interface that allows acceptance of all optional categories, rejection of non-essential categories and granular choice.
2. Rejecting optional technologies should be as accessible as accepting them and must not require unnecessary steps.
3. Optional categories are not pre-selected and inactivity is not treated as consent.
4. The consent interface stores the choice, version, date and technical proof needed to demonstrate and respect the User's decision.
5. The User may change or withdraw consent at any time through the “Cookie settings” or equivalent link available on the Platform.
6. Withdrawal is effective prospectively and does not affect processing already lawfully carried out before withdrawal.
7. Where a User clears browser storage, uses another browser or device or blocks the consent cookie, the Platform may need to ask for choices again.
8. The Operator may refresh consent where purposes, providers or categories materially change or where legally required.
§ 7. Browser and device settings
1. Most browsers allow Users to view, block, delete or limit cookies and to control site permissions.
2. Mobile operating systems and applications may provide additional controls for identifiers, tracking permissions, notifications and storage.
3. Browser “Do Not Track”, Global Privacy Control or similar signals are handled to the extent required by applicable law and technically supported.
4. Blocking all cookies may impair login, Account security, checkout, preferences and other requested functions.
5. Instructions differ by browser and device and should be obtained from the relevant provider's current support information.
§ 8. Retention and deletion
1. A cookie or similar identifier is retained for the period shown in the current consent panel, provider information or technical register.
2. Session technologies expire at the end of the session unless a shorter or longer period is technically required for a disclosed purpose.
3. Persistent technology duration is limited to what is reasonably necessary for the relevant purpose and is reviewed periodically.
4. Consent records may be retained after a choice changes for the period needed to demonstrate compliance and defend claims.
5. Deleting cookies from a device does not necessarily delete server-side records already created lawfully, which are retained under the Privacy Policy.
6. The Operator may shorten retention or disable a technology without updating these Terms where User rights are not reduced.
§ 9. Third parties and international transfers
1. Third-party providers may receive technical, usage or consent information when their technology is activated.
2. Some providers may process data outside the European Economic Area. Transfer mechanisms and safeguards are described in the Privacy Policy or provider-specific information.
3. The Operator seeks to load non-essential third-party content only after the relevant consent where required.
4. External providers may act as processors, joint controllers or independent controllers depending on the service and configuration.
5. Users should review the provider information available in the consent panel for current details.
6. The Operator may replace, remove or add providers and will update the consent interface before activating a materially new optional purpose.
§ 10. Updates and contact
1. This Policy may be updated to reflect legal, technical, provider or Platform changes.
2. Material changes affecting optional processing are reflected in the consent interface and, where necessary, new consent is requested.
3. The current version and effective date are published on the Platform.
4. Questions about cookies may be sent to [email protected]. General enquiries may be sent to [email protected].
5. The English version is intended for Users who choose English. The consent interface presented to a User should be available in the language selected for the Platform where reasonably supported.