> For the complete documentation index, see [llms.txt](https://legal.norppa.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://legal.norppa.co/cookies.md).

# Cookies Policy

Effective date: `26.06.2026`

***

### 1. The short version

We do not track you. This site sets **no analytics cookies, no advertising cookies and no tracking pixels**, and it embeds no third-party content. What is stored on your device is limited to remembering the language you chose, protecting our forms against abuse, and keeping an administrator signed in.

Every one of those items is strictly necessary to deliver the site you asked for. That is why you will not see a consent banner here: there is nothing to consent to, and a banner implying otherwise would be misleading.

***

### 2. The legal rule we follow

Under **§ 205 of the Finnish Act on Electronic Communications Services (917/2014)**, which implements **Article 5(3) of the ePrivacy Directive 2002/58/EC**, storing information on your terminal equipment — or reading information already stored there — requires your **prior consent**, unless the sole purpose is either:

* to carry out the transmission of a communication over an electronic communications network, or
* to provide a service that you have **expressly requested**, where the storage is strictly necessary for that service.

Where consent is required, it must meet the GDPR standard: freely given, specific, informed and unambiguous, given by a clear affirmative act. Pre-ticked boxes, "by continuing to browse you accept", and browser-setting-based consent are **not** valid — this has been confirmed by the Court of Justice of the European Union in *Planet49* (C-673/17) and by the Finnish Deputy Data Protection Ombudsman. Refusing must be as easy as accepting.

We have designed the site so that this question does not arise: we store nothing that falls outside the exemption.

> **Note on upcoming change.** The European Commission's Digital Omnibus proposal (November 2025) would move these rules into the GDPR itself, as new Articles 88a and 88b, and would give browser-level consent signals binding effect. As at the date of this policy the proposal is still in negotiation and the rules described above continue to apply in full. We will update this page if that changes.

***

### 3. What is stored on your device

#### 3.1 Strictly necessary — no consent required

| Name                      | Type               | Set by                  | Purpose                                                                                                                                                                                                                                | Lifetime                             |
| ------------------------- | ------------------ | ----------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------ |
| `norppa.locale`           | Local storage      | norppa.co (first party) | Remembers the language version you selected, so the site does not reset to a different language on every visit. Stores a language code only (e.g. `fi-fi`)                                                                             | Until you clear your browser storage |
| `norppa.locale.asked`     | Local storage      | norppa.co (first party) | Records that you have already answered or dismissed the prompt asking whether you would like the Finnish, Romanian or International version, so that we do not ask again on every visit. Written only after you respond — never before | Until you clear your browser storage |
| CSRF token                | Cookie (same-site) | norppa.co (first party) | Protects form submissions against cross-site request forgery. Contains a random value with no information about you                                                                                                                    | Session                              |
| `sb-<project>-auth-token` | Local storage      | Supabase                | Keeps an **administrator** signed in to the internal management area. This is never set for ordinary visitors                                                                                                                          | Until sign-out or token expiry       |

Both `norppa.locale` entries store a choice you made yourself and exist solely so that we do not override it. That is the textbook case for the "expressly requested service" exemption in § 205.

#### 3.2 Non-essential storage

**There is none.** We use no analytics, no advertising, no A/B testing, no session recording, no heatmaps and no social media widgets.

#### 3.3 What is not stored, but is worth explaining

**Country detection.** To suggest the right regional version of the site, we read the two-letter country code that our hosting provider attaches to your request as it reaches its network. No third-party service is contacted, nothing is stored on your device, and we do not keep the result. See section 4.4 of the [Privacy Policy](https://claude.ai/privacy).

**Browser language.** We read your browser's language setting to preselect a language. This value never leaves your device.

**Session storage.** We use none.

**Social media.** We link out to Facebook, Instagram, YouTube, Telegram and X. These are plain links, not embedded widgets or "like" buttons, so those platforms receive nothing from us and set no cookies here. If you click a link, that platform's own policy applies from that point on.

**Our content delivery network.** The whole site, including the files served from `cdn1.norppa.co`, is delivered through bunny.net (BunnyWay d.o.o., Slovenia), from European points of presence in Frankfurt and Stockholm. It sets no cookies and stores nothing on your device.

**Maps.** Our contact page does not embed a map. Nothing on this site loads content from Google or any other third-party host.

***

### 4. How to control what is stored

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

* **Chrome:** Settings → Privacy and security → Third-party cookies / Site data
* **Firefox:** Settings → Privacy & Security → Cookies and Site Data
* **Safari:** Settings → Privacy → Manage Website Data
* **Edge:** Settings → Cookies and site permissions

Blocking the items listed in 3.1 may mean the site forgets your language choice or that an administrator cannot stay signed in. Nothing else will break: because we run no analytics and no advertising, there is nothing else to switch off.

***

### 5. Questions and complaints

Write to **<support@norppa.co>**.

In Finland, compliance with the cookie rules in the Act on Electronic Communications Services is supervised by the **Finnish Transport and Communications Agency (Traficom)**, PO Box 320, FI-00059 TRAFICOM, [traficom.fi](https://www.traficom.fi/). Questions about the processing of personal data are supervised by the **Office of the Data Protection Ombudsman**, PL 800, 00531 Helsinki, <tietosuoja@om.fi>.

***

### 6. Changes

We will update this page whenever we add, remove or change a storage item or an embedded third-party service. The effective date at the top shows the current version.

If we ever introduce something that is not strictly necessary — an embedded map, a video player, analytics — we will implement a proper consent mechanism first, and this page will say so before the change goes live.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://legal.norppa.co/cookies.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
