Cookie Policy

This document describes the cookies and similar technologies running on mcoderz.com. It complements the Privacy Policy, which covers personal data processing more broadly. The link is in the site footer. The site is run by Miłosz Gołas, trading as DIGITAL SOLUTIONS MIŁOSZ GOŁAS, Osiedle Na Lotnisku 1 lok. 29, 31-801 Kraków, Poland, NIP 6321964756, e-mail hi@mcoderz.com. MCoderZ Labs is a trading brand of this business. This document applies from 16 July 2026.

Cookies are small text files your browser stores on your device. The site can read them back later, for instance to remember the language you chose. Alongside cookies there are similar technologies working the same way: data stored in the browser (localStorage, sessionStorage). The law treats them the same, so we describe them together here. They fall into two groups: • first-party, stored by mcoderz.com • third-party, stored by the providers we use

Storing information on your device and accessing information already stored there is governed by art. 399(1) of the Polish Electronic Communications Law of 12 July 2024 (Journal of Laws 2024, item 1221). The conditions for consent are set by art. 400 of that act in connection with art. 4(11) and art. 7 GDPR. The rule is this: storing information on your device requires consent. There is an exception. Art. 399(3) of that act waives consent where the storage is necessary to deliver a service you asked for yourself. This covers files necessary for the site to work. Today every file running on mcoderz.com falls within that exception. We store nothing that requires consent, so we base nothing on consent under art. 6(1)(a) GDPR. One aside, because it causes confusion: until 10 November 2024 the basis was art. 173 of the Telecommunications Law. That provision no longer exists, the act was repealed. Policies still citing it are out of date.

The complete list. There is nothing beyond this. NEXT_LOCALE • stored by: mcoderz.com (first-party) • purpose: remembers the language version you chose, so it is not reset on every visit • category: strictly necessary • lifetime: up to one year cookieyes-consent • stored by: CookieYes Limited (United Kingdom) • purpose: remembers your banner decision and the consent record identifier, so the banner stops asking • category: strictly necessary • lifetime: 12 months, after which the banner asks again Files and data stored by hCaptcha • stored by: Intuition Machines, Inc. (United States) • purpose: telling a human apart from a bot when the contact form is submitted • category: necessary to protect the form • lifetime: up to 12 months, per the provider's policy • when they appear: only once you start filling in the form. If you are just reading the site and never touch the form, hCaptcha does not load at all That is all. We store no analytics, performance, marketing or advertising files, because we simply have no such tools.

Worth stating plainly, because an absence is less obvious than a presence: • no Google Analytics and no other analytics tool • no Google Tag Manager • no advertising pixels, including Meta Pixel • no remarketing and no marketing cookies • no cross-site tracking and no behavioural profiles • no selling of data We have also switched off the site's access to the Topics API, which browsers use for advertising profiling, along with camera, microphone and geolocation.

A fair question, so a straight answer. Since every file falls within the exception in art. 399(3) of the Electronic Communications Law, your banner decision switches nothing on or off today. There is no hidden analytics waiting for consent. The banner stays for two reasons: • it records what we asked and what you answered, so we can evidence it • should a file requiring consent ever arrive, your choice will already be recorded and honoured before any such file is stored CookieYes Limited runs the decision log. It receives a truncated IP address, country, the content and date of the decision, and a record identifier. The basis for keeping the log is art. 6(1)(f) GDPR, our legitimate interest in being able to show how the consent conversation went.

You can change the decision stored by the banner at any time: click “Cookie settings” in the site footer. The same panel you saw in the banner will open. Changing or withdrawing a decision is as easy as making it, and does not affect the lawfulness of what we did beforehand (art. 7(3) GDPR). If the panel does not open, write to hi@mcoderz.com and we will handle it for you. You can also delete and block cookies in your browser settings. Every browser puts this somewhere different, usually under privacy. That is an extra option on your side, not a way of giving or withdrawing consent. Blocking strictly necessary files may break the site: the language will stop being remembered, and the contact form may fail to send.

We update this document when what we actually store on your device changes, for instance when a new tool arrives or an old one goes. The date of the last update is at the top of the page. Should we ever introduce files requiring consent, such as analytics or marketing ones, the banner will ask for consent before any such file is stored, and the list in section 4 will be updated beforehand.

Send questions about cookies and personal data to hi@mcoderz.com. You can also write to: DIGITAL SOLUTIONS Miłosz Gołas, Osiedle Na Lotnisku 1 lok. 29, 31-801 Kraków, Poland. The wider picture, including legal bases, recipients, retention periods and your rights, is in the Privacy Policy.