Privacy policy

The controller of personal data of visitors to rowienski-interactive.pl is Mateusz Rowieński, a natural person not running a registered business, Rybie 61, 22-360 Rejowiec, Poland.

Contact for data protection matters: kontakt@rowienski-interactive.pl

The controller has not appointed a data protection officer. GDPR obligations apply regardless of whether a registered business is run - the site is made publicly available, so the exemption for purely personal or household activity does not apply.

It is easier to start with what this site does not do:

• there are no user accounts, no sign-in and no registration,
• there are no contact forms - contact goes by e-mail or on Messenger, which is outside this site,
• there is no newsletter and no e-mail addresses are collected,
• visitor data is not sold or shared with anyone,
• the site is not aimed at children and their data is not knowingly collected.

The server that sends you this page records every request: IP address, date and time, the requested address, the response code, the response size and the name and version of the browser. This always happens and is inherent to how a web server works - without it you can neither detect a failure nor tell human traffic from bots.

The logs are not combined with any other dataset, no visit statistics are built from them and they are not archived. They are overwritten in rotation: the server keeps a limited number of files of limited size and the oldest one is deleted.

The site runs on a server in Warsaw, at OVH (OVH SAS). That is the only entity with access to the infrastructure, and it acts as a processor.

Before you choose anything, the site sets no cookie at all. The first one - and for a long time the only one - appears the moment you click anything in the consent window, and it records exactly that click. The chosen language is kept outside cookies, in the browser local storage: that stays on your device and the server never sees it.

• the cc_cookie cookie - your decision from the consent window, so that the question does not return on every visit,
• the ri_lang entry in local storage - the chosen language, so that a return visit does not start over.

You can remove both at any time by clearing site data in your browser settings. The site will keep working, it will simply ask for consent again.

If you enable the "Analytics" category, Google Analytics 4 is started. The tool counts how many people visit, which pages they read, how long they stay and where they came from. The IP address is truncated before it is recorded and the tool itself shows no data by which an individual person could be identified.

The provider is Google Ireland Limited. Without your consent the Google script does not load at all - it is not part of the page code, it is attached only after you click.

Beyond page views the tool also counts scrolls, clicks on links leading outside the site and file downloads. This is the Google Analytics default, called enhanced measurement, and it is mentioned here because it is switched on.

If you enable the "Marketing" category, the Meta pixel is started. It measures whether what is published on the Facebook profile actually brings anyone to the site, and shows ads to people who have already visited this site. This is profiling within the meaning of the GDPR and it is stated here plainly.

The provider is Meta Platforms Ireland Limited. Meta acts as a joint controller for the event measurement itself and as a separate controller for the data it processes for its own purposes on its platforms.

No decision producing legal effects concerning you is taken automatically here.

• server logs and site security - the legitimate interest of the controller, Article 6(1)(f) GDPR,
• analytics and marketing - your consent, Article 6(1)(a) GDPR,
• storing information in your browser and accessing it - your consent under the Polish Electronic Communications Law; the exception is what is necessary for the site to work, that is the language and the consent record itself,
• replying to an e-mail you send - the legitimate interest of the controller in conducting correspondence, Article 6(1)(f) GDPR.

There are three recipients and each appears only within its own scope: OVH SAS as the server provider, Google Ireland Limited when analytics is on and Meta Platforms Ireland Limited when marketing is on.

Google and Meta may transfer data to the United States. This happens under the European Commission adequacy decision (EU-US Data Privacy Framework), supplemented by standard contractual clauses. The server hosting the site is in Poland and by itself sends nothing outside Europe.

• server logs - until overwritten by newer entries, with no archiving,
• your consent record - 6 months, and the language choice until you clear site data in your browser; the question also returns when the scope of what is asked about changes,
• data in Google Analytics - as configured in the account, no longer than 14 months,
• data in the Meta pixel - under Meta rules, typically up to 90 days for identifiers stored in the browser,
• e-mail correspondence - for as long as the matter requires and a reasonable period afterwards.

In relation to the controller you have the right to:

• access your data and receive a copy of it,
• rectify inaccurate data,
• erase data,
• restrict processing,
• object to processing based on legitimate interest,
• port data processed on the basis of consent,
• withdraw consent at any time, without affecting what happened before the withdrawal.

All of this is handled at kontakt@rowienski-interactive.pl. You also have the right to lodge a complaint with the President of the Personal Data Protection Office, ul. Stawki 2, 00-193 Warsaw, Poland.

The footer of every page carries a "Privacy settings" link. It opens the same window you saw on your first visit and lets you switch each category off separately.

Switching a category off is not a declaration here: the cookies set by Google and Meta are deleted, and the page reloads itself so that an already loaded script does not stay in memory. A running script cannot be removed any other way than by reloading the page - which is why the page does it.

If a new category or a new recipient appears, the consent version is raised and the question returns. Earlier consent does not cover the new scope, so it is not treated as still standing.