Skip to content
nobrainersocial
PolskiOpen studio

LEGAL DOCUMENTS

Cookies and Browser Storage Policy

Version: 2026-10-20 · Published: 19 October 2026

Contents

  1. 1. In short
  2. 2. Essential cookies
  3. 2a. Analytical cookies (only with consent)
  4. 3. Marketing cookies (only with consent)
  5. 3a. Newsletter form protection (Google reCAPTCHA)
  6. 4. Browser storage
  7. 5. What we do not use
  8. 6. Cookies of other companies
  9. 7. How to change your choice and manage cookies
  10. 8. Legal basis
  11. 9. Contact

1. In short

NoBrainer.social uses three kinds of mechanisms stored in your browser:

  1. Essential ones: for sign-in, a secure contact form, completing an operation you started and remembering your cookie choice. They do not need consent.
  2. Analytical ones: Google Analytics 4. They give us traffic statistics for the site and the Studio. We turn them on only after you consent, with the "Accept" button or the "Analytical" switch in the cookie settings. Until you consent, the site does not load the Google Analytics script and sends Google no data.
  3. Marketing ones: the Meta Pixel and a cookie with the source of your visit (UTM tags). They measure how our ads perform. We turn them on only after you consent, with the "Accept" button or the switch in the cookie settings. Until you consent, the site does not load Meta’s script and does not record the source of your visit.

On the offer page the newsletter sign-up form is protected by Google reCAPTCHA (section 3a). It loads only when you start using the form and runs without asking for consent, because it keeps the form secure.

On your first visit we show a banner with "Accept", "Reject" and "Settings" buttons. In the settings you turn the analytical and the marketing category on separately. Rejecting is as easy as accepting and does not limit your use of the site or the Studio.

Back to contents

2. Essential cookies

  1. Sign-in session. Name: __Host-nbs_session (nbs_session in test environments). Purpose: keeps you signed in so you do not have to enter your password at every click. Lifetime: up to 8 hours or until you sign out. Properties: readable by the server only (HttpOnly), sent only over an encrypted connection (Secure), and not sent from other sites in most cases (SameSite=Lax).
  2. Technical support session. Name: __Host-nbs_support. We set it only for the administrators of the service, for the duration of an approved support session, for 15 minutes. Visitors and Customers do not receive it.
  1. Contact form session. At nobrainer.social/contact.php the form sets a session identifier (default name: PHPSESSID). It checks that a submitted enquiry comes from the form you opened and protects against forged requests. It follows the host’s session settings; the form code does not specify its own expiry time. Its cookie scope is /contact.php, with HttpOnly, Secure and SameSite=Lax properties. It is not used for advertising or tracking.
  1. Your cookie choice. Name: nbs_consent. Purpose: remembers whether you consented to analytical cookies and to marketing cookies, so the banner does not appear on every visit. It holds only "consent" or "no consent" for each of these two categories. Lifetime: 12 months, after which we ask again. Properties: available to nobrainer.social and its subdomains (including studio.nobrainer.social), so one choice applies on the offer page and in the Studio; sent only over an encrypted connection (Secure), SameSite=Lax. It is necessary to respect your choice, so it does not need consent.

Without the session cookie you cannot sign in to the Studio. Blocking the form session may prevent sending an enquiry; you can email us instead.

Back to contents

2a. Analytical cookies (only with consent)

We measure traffic on nobrainer.social and in the Studio at studio.nobrainer.social with Google Analytics 4, a service of Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland).

  1. When it runs. Only after you consent to the "Analytical" category in the cookie banner. Without that consent the site does not load the Google Analytics script and sends no request to Google.
  2. What we measure. Views of public pages: the offer page, the legal documents and the Studio sign-in and sign-up pages. In addition, three events: creating an account (sign_up), starting a payment (begin_checkout) and a purchase (purchase, with the net value, the currency and a random identifier of the payment attempt). We do not send Google any content from inside the Studio, your email address, your name or any other identifier we hold about you. We remove parameters from page addresses, except UTM tags. Google signals and ad personalisation are turned off in our Google Analytics service.
  3. Google consent mode (Consent Mode v2). At the start all Google consent signals, analytics_storage, ad_storage, ad_user_data and ad_personalization, are set to "denied". Consent to analytical cookies switches only analytics_storage to "granted". The ad_storage, ad_user_data and ad_personalization signals stay denied unless you also consent to marketing cookies (section 3).
  4. Cookies. _ga distinguishes browsers and _ga_<container-id> keeps the session state (<container-id> is the identifier of our Google Analytics service). Google's default lifetime for both is 2 years; this is Google's default, not a setting of ours. The cookies are set for the nobrainer.social domain, so one measurement covers the offer page and the Studio. Google Analytics may add a _gl parameter to links between nobrainer.social and studio.nobrainer.social, which carries the measurement identifiers between the two addresses.
  5. How long Google keeps the data. Event-level data is kept in Google Analytics for at most 14 months. Aggregate statistics that do not identify you may remain in reports for longer.
  6. Withdrawing consent. When you turn the "Analytical" category off in "Cookie settings", measurement stops and we remove the _ga and _ga_<container-id> cookies from your browser.

Google acts as our processor for this. The Privacy Policy describes transfers to the United States and the other details.

Back to contents

3. Marketing cookies (only with consent)

  1. Visit source (UTM). Name: nbs_attribution. Purpose: when you arrive from an ad or a tagged link, we record where the visit came from, so we know which ads bring customers. Content: the utm_source, utm_medium, utm_campaign, utm_content and utm_term tags, Meta’s ad click identifier (fbclid), the landing page address without parameters and the time of the visit. We store only these tags, with a limited number of characters and without special characters. Lifetime: 30 days from the last visit with tags. Properties: available to nobrainer.social and its subdomains, Secure, SameSite=Lax. If you create an account during that time, we pass these tags, together with the new account's email address, to the administrator of the Service in the email about the new account. The Privacy Policy describes the details.
  2. Meta Pixel. A script of Meta Platforms Ireland Limited (4 Grand Canal Square, Grand Canal Harbour, Dublin 2, Ireland), loaded from connect.facebook.net. Purpose: measuring how our ads on Facebook and Instagram perform. It sends Meta information about events: a view of the offer page, the legal documents or the Studio sign-in page, creating an account, starting a payment and a purchase (with the net amount and currency). With each event Meta receives the address of the page, your IP address, browser and device data and the identifiers from cookies. We do not send Meta your email address, name, phone number or other form data (we do not use so-called advanced matching). Cookies the pixel sets on our domain: _fbp (browser identifier, 90 days) and _fbc (ad click identifier, 90 days). If you are signed in to Facebook or Instagram, Meta may link the events to your account using its own cookies on its own domains, as described in Meta’s Privacy Policy.

If you also consent to analytical cookies, marketing consent also switches the ad_storage, ad_user_data and ad_personalization signals in Google Analytics to "granted" (section 2a).

When you withdraw consent, the pixel stops sending events and we remove the nbs_attribution, _fbp and _fbc cookies from your browser. We cannot delete data Meta already received from its systems; you can exercise your rights with Meta, including through Meta’s ad preferences.

Back to contents

3a. Newsletter form protection (Google reCAPTCHA)

On nobrainer.social and nobrainer.social/en the newsletter sign-up form is protected by reCAPTCHA, a service of Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland).

  1. When it runs. The invisible reCAPTCHA script (www.google.com/recaptcha) loads only when you start using the newsletter form: when you click into it, move to one of its fields or start typing, and at the latest when you submit it. Simply viewing the page sends Google nothing. The check whether a person is signing up happens when the form is submitted. reCAPTCHA does not run in the Studio or on the legal document pages.
  2. Purpose. Protecting the form against spam, bots and abuse, for example mass sign-ups of other people’s addresses.
  3. What data Google processes. According to Google: your IP address, browser and device data (including browser type, language, screen resolution and time zone), the page address, how you use the page (for example cursor movements and time on the page) and Google cookies. Google may set or read the _GRECAPTCHA cookie on its own domain (up to 6 months) and read cookies of its services if they are in your browser. reCAPTCHA sets no cookies on our domain.
  4. Legal basis. Our legitimate interest in protecting the form against abuse (Article 6(1)(f) GDPR). We treat reCAPTCHA as necessary for the secure operation of the form you are using, so the banner does not ask for consent to it. Rejecting marketing cookies does not turn reCAPTCHA off.
  5. More information. Google’s Privacy Policy describes Google’s processing, and the Google Terms of Service govern the service. If you do not use the newsletter form, Google does not receive this data. You can also block scripts from www.google.com in your browser; the form then cannot be sent, while the rest of the page works.

Back to contents

4. Browser storage

The application saves a few small pieces of information in your browser. They are necessary and are not used for tracking.

  1. Tab session storage (disappears when you close the tab). It holds a temporary key for signing in with Google, an invitation token after you open an invitation link, and the state of an operation you started: generation, a file upload, approving a post or a purchase. That way, if you refresh the page, the operation is not repeated.
  2. Local storage (up to 14 days). If you tick the acceptance of the Terms of Service and the Privacy Policy when you create an account, we save in the browser the version numbers you accepted together with your email address. After your first sign-in we record that acceptance on your account and delete the entry from the browser.

Back to contents

5. What we do not use

We do not use analytics tools other than Google Analytics 4 described in section 2a, advertising pixels other than the Meta Pixel, or external fonts and widgets that set their own cookies, except Google reCAPTCHA described in section 3a. If that changes, we will update this policy and ask for consent where the law requires it.

Back to contents

6. Cookies of other companies

When you go to the sites of other companies, for example the Stripe payment page, the Google sign-in page or Meta, those companies set their own cookies on their own domains, under their own rules. We have no control over them.

Back to contents

7. How to change your choice and manage cookies

You can change your choice at any time with the "Cookie settings" button in the footer of the site and the Studio. Withdrawing consent is as easy as giving it and does not affect the lawfulness of anything done before the withdrawal.

You can also block or delete cookies in your browser settings. Blocking the session cookie makes it impossible to sign in to the Studio. You can clear tab storage by closing the tab. You can remove local storage and the other cookies in your browser’s site data settings. If you delete the nbs_consent cookie, the banner asks for your consent again.

Back to contents

8. Legal basis

Necessary mechanisms without which we cannot provide the service you asked for, and remembering your choice, do not need consent under Article 399 of the Polish Electronic Communications Law of 12 July 2024 (Prawo komunikacji elektronicznej). We treat Google reCAPTCHA as necessary for the secure operation of the newsletter form; the data Google receives with it is processed on the basis of legitimate interest (Article 6(1)(f) GDPR). We store and read analytical and marketing cookies only on the basis of your consent (Article 399(1) of that law), and we process the personal data collected with them on the basis of consent (Article 6(1)(a) GDPR). The Privacy Policy describes the details, including the roles of Google and Meta and transfers outside the European Economic Area.

Back to contents

9. Contact

Questions: arkadiusz@mastalerz.it.

Back to contents

  • Terms of Service
  • Privacy Policy
  • Cookies
  • Contact and company details