COOKIE POLICY FOR BACHATACORE.COM

Last updated: September 27, 2026
Version: 1.1

This Cookie Policy explains how bachatacore.com (the “Service”) uses cookies, pixels, local storage, online identifiers and similar technologies. This document should be read together with the Bachata Core Privacy Policy.

As of the latest update, the Service uses: our own cookie consent banner, Google Tag Manager, Google Analytics 4, Microsoft Clarity, Meta Pixel and - in the purchase window - the Stripe payment form. The course and community are provided on the separate Skool platform. We do not currently use Google Ads, TikTok Pixel / Events API or MailerLite; if we implement them, we will update this Policy before they are activated.

1. Data controller and contact

The controller of personal data associated with the use of technologies in the Service is:

ALWAYS DANCE AWARE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
ul. Wilcza 44 lok. 1
00-679 Warsaw
Poland
NIP (Tax ID): 7011311109
REGON: 544601698

Privacy and cookie contact: privacy@bachatacore.com

2. What are cookies and similar technologies?

Cookies are small pieces of information stored in a user’s browser or on their device when they use a website. They may make it possible to remember settings, maintain a session, analyse use of the website, measure advertising effectiveness or recognise a browser during subsequent visits.

In this Policy, the term “cookies” also includes similar technologies such as tracking pixels, tags, local storage, device identifiers, advertising click identifiers.

Cookies may be first-party (set within the bachatacore.com domain) or third-party (set or read by service providers such as Google, Meta, Microsoft or Stripe).

3. Legal basis and consent rules

In Poland, the rules concerning the storage of information or access to information stored on a user’s device arise in particular from Article 399 of the Act of July 12, 2024 - Electronic Communications Law. For technologies that are not necessary to transmit a communication or provide a service requested by the user, prior information and consent are required. Data protection rules apply accordingly to such consent.

In the EU/EEA and the United Kingdom, we use a model under which strictly necessary technologies may operate without consent, while statistics and marketing technologies are activated only in accordance with the user’s choice. In other countries, the presentation of the banner and implementation of user rights may be adapted to local law, while we aim to apply a high standard of privacy by default.

Consent to Statistics or Marketing is voluntary. Refusing consent should not prevent use of the basic functions of the Service, although it may limit features that depend on external technologies.

4. Categories of technologies used in the Service

4.1. Functional / strictly necessary - always active

These technologies are necessary for the proper, secure operation of the Service in accordance with the user’s choices. They may be used, among other things, to:

• remember cookie consent settings;
• operate the consent mechanism and display the appropriate banner;
• provide security, prevent abuse and maintain a required session;
• provide functions expressly requested by the user;
• operate payments and fraud-prevention safeguards through Stripe - only after the purchase window is opened and the user proceeds to payment;
• remember the selected language version of the Service.

In the cookie banner, this category is labelled “Functional” and remains always active.

4.2. Statistics - after consent

Statistics technologies help us understand how users interact with the Service. They may measure, among other things, page views, traffic sources, devices, scrolling, clicks, on-page behaviour and usability issues.

This category includes in particular:

• Google Analytics 4 (GA4);
• Microsoft Clarity - including click maps, scroll maps and session recordings within the scope of the tool configuration.

Google Tag Manager (GTM) is a tag-management tool. It is not itself an analytics tool for the purposes of this Policy, but it is used to activate the GA4 and Meta Pixel tags. Microsoft Clarity is loaded directly by the Service and only after consent to Statistics has been given.

Without consent to Statistics, Google Analytics 4 operates in Google Consent Mode: it does not store cookies in the browser, and Google may only receive pings without user identifiers (for example information about a page view and the consent state), which Google uses to model aggregated statistics.

4.3. Marketing - after consent

Marketing technologies are used to measure advertising effectiveness, attribution, remarketing, audience creation and campaign optimisation. They may allow advertising platforms to associate actions taken in the Service with a previous interaction with an advertisement.

This category includes:

• Meta Pixel;
• advertising click and campaign identifiers (e.g. fbclid, UTM parameters) used for measurement and attribution.

We do not currently use server-side integrations (such as Meta Conversions API).

5. Consent management

We use our own cookie consent banner, integrated with Google Consent Mode, to manage consent. On a first visit, the user sees a cookie banner allowing them to accept all categories, reject non-essential categories or customise their settings.

In the detailed settings:

• Functional - always active;
• Statistics - can be enabled or disabled;
• Marketing - can be enabled or disabled.

After preferences are saved, your choice is stored in the browser’s local storage (localStorage) to remember your settings. The user may later change or withdraw consent by reopening the cookie settings in the Service. Withdrawal of consent does not affect the lawfulness of actions carried out before its withdrawal.

We may periodically ask the user to make a choice again, for example after a material change to this Policy, a change of providers or expiry of the consent-retention period.

6. Tools and providers

6.1. Cookie consent banner

The cookie consent banner manages consent categories and storage of user preferences. Consent choices are stored in the browser’s local storage (localStorage, key “bc_consent”), holding the consent status for each category and the time the choice was made. If the user selects a language version of the Service, it is remembered in localStorage under the key “bc_lang”. This data is not sent to our server and remains in the browser until the choice is changed or browser data is cleared.

6.2. Google Analytics 4 and Google Tag Manager

GA4 is used to analyse traffic and use of the Service. Google may receive, among other things, an IP address, device and browser information, the URL of the page visited, online identifiers and event data. Google states that the main GA4 cookie, “_ga”, is used to distinguish users and may normally remain active for up to 2 years. GA4 cookies are stored only after consent to Statistics has been given (see section 4.2).

GTM is used to deploy and manage tags. Its configuration is linked to the consent-management system so that individual tools are activated in accordance with the relevant consent category.

6.3. Microsoft Clarity

Clarity is used to analyse how the website is used, including the creation of click maps, scroll maps and - depending on configuration - session recordings. Microsoft describes cookies such as “_clck”, “_clsk”, “CLID”, “ANONCHK”, “MR”, “MUID” and “SM”. Clarity uses pseudonymous identifiers to link page views and create aggregated analyses. In the EEA, UK and Switzerland, full Clarity functionality requires a valid consent signal.

6.4. Meta Pixel / Meta

Meta Pixel is used to measure the effectiveness of Meta campaigns, event attribution, remarketing and audience creation. It may use online identifiers, device information, IP address, data about pages visited, clicks and events, as well as - depending on configuration - cookies and identifiers associated with Meta advertising.

Meta Pixel stores, among others, the “_fbp” cookie (normally about 90 days) and may read the “_fbc” cookie associated with an ad click.

6.5. Stripe

Stripe processes payments and subscriptions for Bachata Core. The Stripe payment form (Stripe Embedded Checkout) is displayed in the purchase window directly in the Service. The Stripe.js script is loaded from js.stripe.com only after the user clicks a purchase button, selects a plan and proceeds to payment - Stripe technologies are not activated before that.

From that moment, Stripe may store the security cookies “__stripe_mid” (usually around 1 year) and “__stripe_sid” (usually around 30 minutes) in the Service’s domain, used among other things for fraud prevention, and - within the payment form frames - its own Stripe and Link cookies. These technologies are necessary to process the payment requested by the user. Stripe’s own privacy and cookie rules also apply.

6.6. Skool

After leaving Bachata Core for the Skool platform (e.g. from the invitation emailed after purchase), the user uses a separate service. Skool may use its own cookies necessary for login, security, platform operation, analytics and other purposes described in its documents. Cookies set directly on Skool are managed in accordance with that platform’s rules.

7. Illustrative list of cookies and identifiers

The list below is provided for information purposes. The exact set may change as the Service, providers and configuration are updated. Up-to-date information about the cookies and services used is available in the cookie settings in the Service.

8. How can you change or withdraw consent?

You can change your preferences at any time by reopening the cookie settings available in the Service. After preferences are changed, the consent banner will send the appropriate signals (Google Consent Mode) to integrated tools in accordance with the configuration.

You may also delete or block cookies in your browser settings. Please note, however, that deleting cookies may remove saved preferences and require you to make a new choice.

Browser settings may also allow you to block third-party cookies, limit tracking or use privacy signals. To the extent required by applicable law, we may honour properly transmitted opt-out signals such as Global Privacy Control (GPC).

9. International transfers

Providers such as Google, Meta, Microsoft, Stripe or Skool may process personal data in various countries, including outside the European Economic Area. If personal data is transferred outside the EEA or UK in connection with cookies or similar technologies, legal mechanisms described in more detail in the Bachata Core Privacy Policy are used, such as adequacy decisions, the Data Privacy Framework, Standard Contractual Clauses or other permitted safeguards.

10. Children’s and minors’ data

The Service and marketing technologies should not be used to profile children in a manner contrary to applicable law. For younger users, we apply the rules described in the Bachata Core Privacy Policy. Advertising features, remarketing and similar technologies are activated only to the extent permitted by law and in accordance with required consents.

11. Changes to this Cookie Policy

This Policy may be updated if we change how the Service operates, implement new tools, change providers or if applicable law changes. The current version is published in the Service together with the date of the latest update.

The list of specific cookies may change more frequently than this document because third-party providers may update their technologies. For this reason, current information available in the cookie settings panel supplements this Policy.

12. Contact

For matters relating to cookies, consents or privacy, you may contact us at:

ALWAYS DANCE AWARE SPÓŁKA Z OGRANICZONĄ ODPOWIEDZIALNOŚCIĄ
ul. Wilcza 44 lok. 1
00-679 Warsaw
Poland
privacy@bachatacore.com

13. Useful information about providers

Detailed information on how third-party providers use cookies and data is available in their current policies and documentation. In particular, you may wish to review the policies of Google, Microsoft Clarity, Meta, Stripe and Skool.

This Cookie Policy supplements the Bachata Core Privacy Policy. In the event of any inconsistency regarding the processing of personal data, applicable law and the current Privacy Policy prevail.