Last updated: 27.08.2026
Cookie Policy
This page contains the full Cookies Policy. The Polish version is the official and legally binding version.
Company: ATN TENNIS, Sp. z o.o.
NIP: 9512645383
REGON: 544402697
Registered address: ul. ZYGMUNTA VOGLA nr 28 lok. 02.177, 02-963 Warszawa, Polska
Contact email: info@atntennis.com
Contact phone: +48 571 037 277
Data Protection Officer (DPO): No dedicated DPO appointed at this time
Update your cookie choices here. Necessary cookies remain active and cannot be disabled.
1. General provisions
- 1.1. This Cookies Policy explains what cookies and similar technologies are used on the ATN TENNIS platform, available at https://www.atntennis.com (the “Platform”), for what purposes, and how the user may manage their settings.
- 1.2. The operator of the Platform is ATN TENNIS, Sp. z o.o., address: ul. ZYGMUNTA VOGLA nr 28 lok. 02.177, 02-963 Warszawa, Polska, e-mail: info@atntennis.com.
- 1.3. Questions related to cookies and consent settings may be sent to: info@atntennis.com.
2. What cookies are
- 2.1. Cookies are small text files stored on the user’s device when visiting a website or using a web application.
- 2.2. We may also use similar technologies, including local storage, pixels, SDKs and other identifiers, if they are used as part of the operation of the Platform.
3. Why we use cookies
- 3.1. To ensure the proper operation of the Platform.
- 3.2. To maintain the User’s session, login and account security.
- 3.3. To protect the Platform against abuse, fraud and technical attacks.
- 3.4. To remember selected settings, such as interface language and cookie consent settings.
- 3.5. To analyse how the Platform is used and improve its operation, if the User has given consent.
- 3.6. To measure the effectiveness of marketing activities and advertising campaigns, if the User has given consent.
- 3.7. To provide selected external services, such as maps or embedded video content, if the User has given consent where such consent is required.
4. Categories of cookies
- 4.1. Necessary cookies: required for the operation of the Platform and the functions requested by the user, including login, session maintenance, security, language selection and cookie settings selection.
- 4.1.1. Currently, these may include technologies related to authentication and the Platform’s backend, including solutions used within Supabase.
- 4.2. Functional / Media cookies: storing user settings and enabling embedded services, such as maps and video content — activated only after consent.
- 4.3. Analytics storage and SDKs: PostHog EU Cloud and Google Analytics 4 delivered through Google Tag Manager — activated only after the user’s analytics consent.
- 4.4. Marketing technologies: Meta Pixel delivered through Google Tag Manager and the server-side Meta Conversions API are used only after the User gives Marketing consent. Meta Pixel measures browser events, while the Conversions API may send a completed-registration event from the Platform server for campaign measurement, conversion attribution and Meta ad optimization. The Google Ads tag is not currently active.
- 4.5. External services: Google Maps, YouTube embeds — activated only after the user’s consent, where required by law.
5. External services and third parties
- 5.1. The Platform may use third-party services which, depending on configuration and the User’s consent, may store information on the User’s device or access such information.
- 5.2. Current analytics providers are PostHog EU Cloud and Google Analytics 4 delivered through Google Tag Manager. Google Maps and YouTube may provide external embedded content. The current Meta marketing tools are Meta Pixel and Meta Conversions API (Meta Platforms Ireland Limited), used only after Marketing consent. Meta Pixel is delivered through Google Tag Manager, while Conversions API events are sent server-side. No Google Ads tag is currently active.
- 5.3. Before obtaining the User’s consent, optional technologies should not be loaded or install cookies or similar identifiers, except in cases permitted by law.
- 5.4. Some third-party services may involve the transfer of data outside the European Economic Area, including to the United States.
- 5.5. Such data transfers may take place on the basis of mechanisms provided for by applicable law, including adequacy decisions, SCCs or other lawful transfer mechanisms.
- 5.6. Detailed information on the data processing rules of individual providers may be found in their own privacy policies.
6. Technical infrastructure of the Platform
- 6.1. The Platform uses technical infrastructure and backend service providers who may process data related to the operation of the service, security, hosting, login and data storage.
- 6.2. Such providers currently include, in particular: Vercel for hosting and frontend infrastructure, and Supabase for backend, database, authentication and technical functions.
- 6.3. Information regarding the role of these providers and the rules for processing personal data is indicated respectively in the Privacy Policy and — to the extent applicable — in this Cookies Policy.
7. Table of categories of cookies and similar technologies
- 7.1. Below are examples of categories of cookies that may be used on the Platform. The actual list may be updated as the technologies used change.
- 7.2. The exact names of individual cookies, their storage period and technical configuration may depend on browser settings, the Platform’s configuration and the provider of the relevant technology.
- 7.3. In the event of a significant change in the categories, tools or providers used, the relevant information will be updated in this Policy and/or in the consent management mechanism.
| Category | Example / type | Purpose of use | Storage period |
|---|---|---|---|
| Necessary | login, session maintenance, security, remembering language and cookie settings | login, session maintenance, security, remembering language and cookie settings | until the end of the session or for a period justified by the technical purpose |
| External services | Google Maps / YouTube embed cookies | operation of embedded maps and video content | usually up to 24 months, depending on the tool |
| Analytics | PostHog EU Cloud (SDK, local storage and token-dependent cookies) | usage and product analytics, navigation analysis, interface-problem detection and consent-based Session Replay | according to the PostHog project configuration and Platform settings; a minimal opt-out marker may remain after refusal |
| Analytics | Google Analytics 4 delivered through Google Tag Manager (configuration-dependent Google storage) | traffic, navigation, source, device and aggregate usage analytics after Analytics consent | according to Google and the final GA4 property/container configuration; no fixed storage name or retention period is stated |
| Marketing | Meta Pixel via Google Tag Manager and Meta Conversions API server-side | campaign effectiveness measurement, conversion attribution, deduplication and Meta ad optimization after Marketing consent | according to Meta's configuration and applicable policies; no single fixed retention period is stated by the Platform |
8. Consent management
- 8.1. During the first visit to the Platform, the User is shown a consent banner for the use of cookies and similar technologies.
- 8.2. Through the banner, the User may: accept all optional categories, reject all optional categories, or customise categories individually.
- 8.3. Necessary categories remain active if they are genuinely required for the operation of the Platform or for a function explicitly requested by the User.
- 8.4. The User may change their settings or withdraw consent at any time through the “Cookie Settings” section available on the Platform.
- 8.5. Withdrawal of consent does not affect the lawfulness of the use of cookies and similar technologies before the withdrawal.
- 8.6. The User’s cookie choice may be stored together with the date of the decision, the version of this Policy and the source of the choice.
9. Browser and device settings
- 9.1. The User may also manage cookies independently through their browser or device settings.
- 9.2. Restricting or blocking necessary technologies may cause some Platform functions to work incorrectly, in particular login, session maintenance or remembering settings.
10. Changes to the Cookies Policy
- 10.1. The Operator has the right to update this Cookies Policy.
- 10.2. The current version is always published on the Platform.
- 10.3. Significant changes concerning cookie categories, tools used, providers or consent management rules may additionally be communicated to the User in the Platform interface and/or by displaying the cookie banner again.
11. Contact
- 11.1. For matters related to cookies and consent management, the user may contact us at: info@atntennis.com.
12. Language of the document
- 12.1. The official and legally binding version of this document is the Polish-language version.
- 12.2. Versions prepared in other languages are provided for informational purposes only.
- 12.3. In the event of any discrepancies between language versions, the Polish version shall prevail.
13. PostHog EU Cloud analytics and Session Replay
- 13.1. PostHog runs only after the User has consented to the Analytics category. It is used for usage analytics, navigation and product analysis, detecting interface problems, and improving the product and interface.
- 13.2. With that consent, Session Replay may reconstruct navigation, clicks and scrolling. It does not use the camera or microphone. Sensitive inputs are masked, and designated authentication, private-message, payment and sensitive administrative areas are excluded from capture.
- 13.3. Analytics may be rejected or consent may be withdrawn at any time through Cookie Settings. Collection stops after withdrawal and PostHog-owned analytics persistence is cleared where appropriate. A minimal opt-out marker may remain solely to remember the refusal.
- 13.4. PostHog traffic uses the EU endpoint at https://eu.i.posthog.com. More information about PostHog's privacy practices is available at https://posthog.com/privacy.
- 13.5. PostHog storage identifiers and cookie names may depend on the project token, and retention depends on the PostHog project configuration; therefore this Policy does not state fixed names or a fixed retention period.
14. Google Analytics 4 through Google Tag Manager
- 14.1. Google Analytics 4 (GA4) is delivered exclusively through Google Tag Manager (GTM) and is used for analytics of traffic, navigation, visit sources, devices and browsers, and aggregate use of the Platform. GTM is the tag container; it does not constitute a separate analytics purpose.
- 14.2. The Platform uses Basic Google Consent Mode v2. Before consent to the Analytics category, the GTM script is not loaded and the Platform does not initiate Google measurement requests. Analytics consent controls analytics_storage. Marketing consent separately controls ad_storage, ad_user_data and ad_personalization; these three states remain denied without Marketing consent. Necessary and External-services consent grants none of these four Google states.
- 14.3. After Analytics consent is withdrawn, the consent state is updated immediately and analytics collection for subsequent activity is disabled. Google code already downloaded after an earlier grant may remain in browser memory until the page is closed or reloaded, and technical consent-state communication may still be possible; this does not reactivate future analytics collection.
- 14.4. The Platform does not intentionally send account names, email addresses, phone numbers, private messages, payment details, passwords, verification codes or authentication tokens to the GTM data layer. GA4 may nevertheless process online identifiers and technical usage information.
- 14.5. Google storage names and retention periods depend on Google and the final GA4 property/container configuration, so this Policy does not state fixed names or a fixed retention period. More information: https://policies.google.com/privacy and https://support.google.com/analytics/answer/12017362.
15. Meta Pixel and Meta Conversions API
- 15.1. Meta Pixel is delivered through Google Tag Manager and is activated only after the User gives consent to the Marketing category. The server-side Meta Conversions API is also used only when Marketing consent is present. Without Marketing consent, ATN TENNIS does not intentionally send marketing measurement events to Meta through either channel.
- 15.2. Meta Pixel is used to measure advertising effectiveness, record and attribute conversions and optimize Meta advertising. Browser events may include page views and completed registrations. The current server-side Conversions API implementation sends the CompleteRegistration event when a registration is completed.
- 15.3. Depending on the technical context, Meta Pixel may process data such as IP address, browser and device information, page URL or referrer, cookie or similar identifiers and event timestamps. For the server-side CompleteRegistration event, ATN TENNIS may send IP address, browser user-agent, event timestamp, source URL, Meta browser or click identifiers such as _fbp, _fbc or a value derived from fbclid when available, and a pseudonymous event ID. The same event ID may be used by browser and server events so Meta can deduplicate the same conversion.
- 15.4. ATN TENNIS does not intentionally send account names, e-mail addresses, phone numbers, private messages, payment data, passwords, verification codes or authentication tokens to Meta through Meta Pixel or the current Conversions API implementation.
- 15.5. The provider is Meta Platforms Ireland Limited. Processing, storage periods and any transfers outside the EEA are governed by Meta's applicable policies and lawful transfer safeguards. More information: https://www.facebook.com/privacy/policy/.
- 15.6. The User may withdraw Marketing consent at any time in Cookie Settings. After withdrawal, the Platform stops sending further Meta Pixel and Conversions API marketing measurement events unless consent is given again.