Legal information

Cookie Policy

Which cookies nantenamar.com uses, what they are for, who receives the data, and how to refuse them.

Edition of 28 July 2026. A new edition is published on this page with its date. The current version is always available at this address.

Section 1

What cookies are

1.1. Cookies are small text files that a website, or a service connected to it, stores in your browser. On the next request the browser sends them back, and the site recognises your settings — for instance, the language you read it in.

1.2. Some cookies are set by the site itself. Others are set by third-party services connected to it: Google Analytics, Google Ads, Meta Pixel. Everything actually used on nantenamar.com is listed below, with its purpose and retention period.

1.3. Beyond cookies, the site keeps a few values in your browser's local storage. Technically those are not cookies, but the data still stays on your device — so they are described separately, in section 6.

Section 2

Essential and functional cookies set by the site

2.1. These cookies are set by the site itself. Without them it either does not work as intended or loses a function you have already used:

  • NEXT_LOCALE — remembers the language you chose: Russian, English or Ukrainian. Category: essential. Retention: from the session up to one year, depending on the browser.
  • zs_offer_exp — stores the end of the discount window for the course «Consciousness Protection». The server checks the same value when the order is placed, so the price on the page and the price on the invoice always match. Category: essential, functional. Retention: 30 days.
  • do_offer_exp — the same for the course «Spiritual Weapon»: the end of the discount window. Category: functional. Retention: 30 days.

2.2. These cookies are not shared with advertising networks and are not used to build a profile of you. There is no separate switch for them: they are the mechanism by which the language choice and an honest discount deadline work. You can delete them through your browser — see section 7.

Section 3

Analytics cookies

3.1. Traffic analytics runs on Google Analytics 4, which sets two files:

  • _ga — distinguishes browsers so that visits can be counted as distinct people. Set by Google. Category: analytics. Retention: up to 2 years.
  • _ga_W8YB6XLE20 — keeps the session state for this site's specific measurement stream. Set by Google. Category: analytics. Retention: up to 2 years.

3.2. We use analytics for aggregate numbers: how many people opened a page, where they came from, how long they read. We do not use it to identify you, and we do not link its data to your name, email or phone number.

3.3. Our second traffic counter — Vercel Web Analytics — works without cookies and without cross-site identifiers, which is why it is not in the list above.

Section 4

Marketing cookies

4.1. These files are set by advertising services. They exist so we can tell which advertising brings people in and which one merely spends the budget:

  • _gcl_au and other files of the _gcl_ family — connect a click on an advertisement with what happens on the site afterwards. Set by Google Ads. Category: marketing. Retention: up to 90 days.
  • _fbp — a browser identifier for Meta's advertising systems: Facebook and Instagram. Set by Meta Pixel. Category: marketing. Retention: 90 days.
  • _fbc — an advertising click identifier, written when you arrive through a link carrying a Meta advertising tag. Set by Meta Pixel. Category: marketing. Retention: 90 days.

4.2. The data from these files goes to Google and Meta as independent recipients, and they process it under their own rules — including to show advertising and measure its performance.

4.3. Some events — opening a course page, submitting a form — are additionally sent to Meta's server directly, without the browser. Such an event carries the same identifier as the browser one, so a single action is not counted twice. This gives us no more data about you than the page itself holds, but it keeps the statistics from breaking when scripts fail to load.

Section 5

Why Google's scripts load from our own address

5.1. The Google Analytics and Google Ads scripts are not loaded from Google's domains directly, but from addresses on our own domain: /nn-kernel.js, /nn-kernel-ads.js, and the /nn-kernel path used to send data. This is our proxy: the request reaches our server, and the server forwards it to Google.

5.2. We did this because for a large share of our audience ad blockers and private DNS resolvers cut off Google's domains entirely. The counter then breaks silently, and we lose even basic visit statistics.

5.3. To be plain about it: the address is ours, but the data still goes to Google. The proxy changes the route of the request, not its recipient. The cookies in sections 3 and 4 are set by those very same Google and Meta scripts, and those companies' rules apply to them in full.

5.4. One side effect of this route: Google sees our server's IP address rather than yours, so the geographic data in the reports is approximate.

Section 6

Browser data that is not a cookie

6.1. A few values are kept in your browser's local storage. Unlike cookies they are not sent to the server automatically with every request, but they do stay on your device until cleared:

  • nn_attribution_v1 — remembers the link you first arrived through: campaign tags, the advertising click identifier, the landing page. It lets a purchase be matched to its traffic source. Kept for 30 days. It contains no name, email or phone number.
  • zs_offer_v2_expires, do_offer_v1_expires, femina_offer_expires — the end of the discount window for the courses «Consciousness Protection», «Spiritual Weapon» and «Awakening Femina».
  • webinar_zs_registered_v1 — a marker that you have already registered for the webinar, so the form does not ask you to register again.

6.2. These records are erased together with the site data in your browser settings. In private browsing they are removed when the window is closed.

Section 7

How to refuse

7.1. Cookie controls are built into your browser. The same place lets you delete files and site data already stored, including local storage:

  • Chrome — Settings → Privacy and security → Third-party cookies and site data.
  • Safari — Settings → Privacy → Manage Website Data.
  • Firefox — Settings → Privacy & Security → Cookies and Site Data.
  • Edge — Settings → Cookies and site permissions.

7.2. Advertising cookies can also be turned off on the services' own side: in the ad-preference settings of your Google account and in the ad settings of your Facebook or Instagram account. Blocking third-party cookies in the browser, or any ad blocker, likewise stops the files listed in sections 3 and 4.

7.3. What changes once you refuse: the language will not be remembered between visits, a discount window may restart or count as expired, and the webinar form will no longer know that you already signed up. The core of the site — articles, course pages and payment — works without analytics and marketing cookies.

7.4. There is no separate consent banner on the site at the moment: until one appears, the only way to refuse analytics and marketing cookies is your browser settings or a blocker. We plan to add a banner that will let you switch these categories on and off on the site itself. This section will be updated when it ships.

Section 8

Who is responsible for the data and how this policy changes

8.1. The controller of personal data is Darina Frein. Questions about cookies, a request to delete data, or any other enquiry on this subject — write to info@nantenamar.com.

8.2. The set of services on the site changes over time. If a new counter, pixel or feature that stores data in the browser appears, we will update this page and change the edition date at the top.

Questions about this policy — write to info@nantenamar.com.

How we process personal data is described in a separate document — Privacy Policy.