Cookie and local storage policy

Who we are

The administrator of this website and of the data described in this policy is Fundacja Enabler, based in Rumia, Poland. If you have questions about this policy, please get in touch — contact details are at the end of this document and in our Privacy Policy.

This policy covers only cookies and similar technologies (such as local storage in your browser). How we process your personal data — for example, the content of a message you send through our contact form — is described separately, in our Privacy Policy.

What cookies and local storage are

Cookies are small text files that your browser saves on your device when you visit a website. They serve various purposes — from remembering your preferences to tracking your activity across different sites.

Local storage works similarly, but is saved directly by the browser rather than being sent automatically to the server with every request. It's data that stays on your device until you delete it.

Under Article 399 of the Polish Electronic Communications Law of 12 July 2024 (which replaced Article 173 of the former Telecommunications Law), storing information or gaining access to information already stored on your terminal equipment (for example, through cookies) requires your consent — unless it is necessary to carry out the transmission of a communication, or to provide a service you have explicitly requested.

What exactly this site uses

The table below shows exactly what our site stores on your device, and which external services may be triggered while you browse it.

`a11y-font-scale`

  • Type: local storage (not a cookie)
  • Purpose: Remembers the text size you chose (larger / largest) if you change it in the accessibility panel
  • Duration: Until you clear your browser data or manually reset it
  • First-party / third-party: First-party (Fundacja Enabler)

`a11y-contrast`

  • Type: local storage (not a cookie)
  • Purpose: Remembers whether you turned on high-contrast mode
  • Duration: Until you clear your browser data or manually turn it off
  • First-party / third-party: First-party (Fundacja Enabler)

Visit statistics (Umami)

  • Type: no cookies, nothing stored on your device
  • Purpose: Anonymous, aggregate visit statistics (e.g. how many times pages were viewed), for the foundation's own use only
  • Duration: Not applicable — nothing is stored on your device
  • First-party / third-party: First-party — the tool is hosted on our own server; no data is shared with third parties

YouTube cookies (after you click "play")

  • Type: third-party cookies (Google/YouTube)
  • Purpose: Playing the embedded video; depending on your Google account settings, also content personalization under Google's own policy
  • Duration: Set and controlled by Google
  • First-party / third-party: Third-party — only starts once you click the play button

Vimeo cookies / content

  • Type: third-party iframe + cookies (Vimeo)
  • Purpose: Displaying embedded videos in some articles or project descriptions
  • Duration: Set and controlled by Vimeo
  • First-party / third-party: Third-party — only starts once you click the play button

Facebook cookies / content

  • Type: third-party iframe + cookies (Meta)
  • Purpose: Displaying embedded Facebook videos in some articles
  • Duration: Set and controlled by Meta
  • First-party / third-party: Third-party — only starts once you click the play button

Google Fonts (Manrope, Fraunces)

  • Type: third-party resource (no cookie)
  • Purpose: Displaying the typefaces used on the site
  • Duration: Not applicable — a single font file request
  • First-party / third-party: Third-party (Google) — your IP address reaches Google's servers when the page loads

Contact form (Netlify Forms)

  • Type: form submission, no dedicated tracking cookie observed
  • Purpose: Delivering your message to us; only a hidden "honeypot" field is used as spam protection, with no CAPTCHA
  • Duration: Not applicable
  • First-party / third-party: Processed by our hosting provider (Netlify) — how we handle the content of your message is described in our Privacy Policy

The Klinic Slab typeface (used in some headings) is stored on our own server and requires no contact with any external party.

How our embedded videos work

We take care that external video services don't contact your device unless there's a reason to.

YouTube videos are "blanked out" by default: you only see a cover image and a play button. Only once you click "play" does the actual YouTube player load (in its enhanced-privacy mode) — and only then does your browser connect to Google.

Vimeo and Facebook videos work the same way: you see a thumbnail with a play button, and the player — along with any cookies from that service — only loads after you click it.

Cookieless analytics

We use the Umami analytics tool, which we host ourselves on our own server. By design, Umami doesn't use cookies or any other identifiers stored on your device, doesn't track you across different websites, and doesn't build a profile of you. We only see aggregate, anonymous information — for example, which pages are visited most often.

Because this tool doesn't store anything on your device or process data in a way that requires consent under Article 399 of the Polish Electronic Communications Law of 12 July 2024, we don't show a cookie-consent banner for analytics — there simply isn't anything to consent to.

How to manage cookies and local storage

You can check, block, or delete cookies and local data in your browser settings at any time:

  • Chrome / Edge: Settings → Privacy and security → Cookies and other site data.
  • Firefox: Settings → Privacy & Security → Cookies and Site Data.
  • Safari (desktop): Preferences → Privacy.
  • Safari (iPhone/iPad): Settings → Safari → Advanced.

Deleting local data means that on your next visit the site won't remember your accessibility settings (text size and contrast mode) — you'll need to set them again. This won't affect any other feature of the site.

Changes to this policy

We may update this policy from time to time — for example, when we add a new feature or change how embedded content behaves. The current version is always available at this address.

Contact

If you have questions about this policy, please get in touch — contact details are on our "Contact" page and in our Privacy Policy.