This is a translation of the Polish original. In case of any discrepancy between the two versions, the Polish text prevails.

1. What this document covers

This document describes the cookies and browser local storage used by the pointmoa.eu website. It expands on §4 of the Privacy Policy — that section gives the summary, this one the full list of exactly what is stored and why.
The document concerns the website only. The pointMoA Android app uses neither cookies nor advertising identifiers; the data it keeps on the device is described in §5 of the Privacy Policy.
The data controller is Eryk Kozłowski, contact: kontakt@pointmoa.eu.

2. What cookies and local storage are

A cookie is a small record a site leaves in the browser, which the browser sends back with subsequent requests.
Local storage (localStorage) is a second way of keeping data in the browser. It differs in that it is never sent to a server — only the site's code running in the User's own browser can read it.
The law treats both mechanisms the same way: what matters is that something is stored on the terminal device, not which technology does it.
On this website the distinction matters in practice: whatever the User types into the site's tools stays in their browser's local storage and never reaches the Controller.

3. What the website does not do

The website uses no:

analytics or visitor statistics,
advertising, ad networks or advertising identifiers,
tracking tools, pixels or profiling,
social network plugins,
third-party cookies — every record described below is first-party.

The site's typeface is downloaded at build time and served from the pointmoa.eu domain, so the User's browser makes no request to any external server, not even for fonts.

4. List of cookies

The website stores one cookie.


Name	`NEXT_LOCALE`
Type	first-party, strictly necessary
Content	the chosen language code: `pl` or `en`
Purpose	keeping the chosen language while moving between pages, without repeating the choice on every page
Lifetime	until the browser is closed — it is a session cookie with no expiry date and does not survive to the next day
If blocked	the site works; the language follows the browser's settings on every visit and the choice must be repeated

5. List of local storage records

Every record below is created only when the User actually uses the tool in question. Merely opening a page creates none of them. None is sent to a server.

Record	What it holds	What for
`pointmoa:kalkulator:v1`	the data typed into the Calculator and the Targets: muzzle velocity, bullet weight and ballistic coefficient, optic data, weather conditions, distance	so the same data need not be entered separately in the Calculator and on each Target, and survives a page refresh
`pointmoa:kalkulator:kolumny:v1`	which columns of the results table are visible	so the table setting survives moving to another page
`pointmoa:patent:postep:<set>:v1`	the numbers of questions marked as mastered, separately for each of the three sets	so flashcard learning can be continued later
`pointmoa:patent:egzamin:<set>:v1`	the state of an unfinished mock exam: the drawn questions and the answers given	so closing a tab by accident does not end the exam
`pointmoa:cookies:v1`	nothing but a marker that the information bar (§7) has been read	so the bar does not reappear on every visit

Lifetime: local storage has no expiry date — the records last until the User deletes them (§8) or clears the site's data.

Scope: the records belong to one specific browser on one specific device. They do not travel to another device and do not link visits made from two different browsers.

6. Legal basis, and why the site does not ask for consent

Storing information on a terminal device requires the User's consent, except where it is strictly necessary to provide a service explicitly requested by the User — as set out in Article 5(3) of Directive 2002/58/EC and its Polish implementation in the Electronic Communications Law.
🔴 Every record described in §4 and §5 falls within that exception, so the website does not ask for cookie consent and displays no consent dialog. The language cookie is required for the site to show its content in the right language at all. The records in §5 hold what the User typed in themselves and come into being solely through the User's own action — keeping one's own data on one's own device is precisely the service the User asked for by opening the tool.
This is not a gap; it follows from how the site is built. A consent dialog makes sense where there is something to refuse: analytics, advertising, tracking. The site has none of these (§3), so the question "do you agree to cookies?" would carry no meaning and a "reject" button would have nothing to switch off. Consent demanded where it is not needed teaches people to click without reading and weakens consent where it genuinely matters.
Instead of a consent dialog the site shows a one-off information bar (§7) — it informs, rather than asking for a consent it does not need.
⚠️ Should the website ever introduce analytics, advertising, tracking tools or embedded third-party content, point 2 will stop being true. At that moment — before any such tool goes live — the site will introduce a real consent mechanism: an equally weighted "accept" and "reject", no pre-ticked boxes, the ability to withdraw consent at any time, and the strictly necessary records from §4 and §5 kept outside that choice. This document will be amended together with the tool going live, not afterwards.

7. The information bar

On the first visit a bar appears at the bottom of the page, stating briefly what the site stores in the browser and linking to this document.
The "I understand" button closes the bar and writes a single marker to local storage (pointmoa:cookies:v1, §5) so that the bar does not return on every visit.
🔴 Closing the bar is not consent to anything — it confirms that the information was displayed. It does not change the scope of what the site stores, because there is nothing to switch on or off (§6).
The bar blocks no content and requires no click: the site can be used without closing it.
If the browser refuses to write to local storage (private mode, blocked site data), the bar is not shown at all — the site would have no way to remember that the User had already seen it, and a bar returning on every click would be both irritating and pointless.

8. How to delete or block these records

Cookies and local storage are deleted and blocked in the browser's settings, under site data. In most browsers the path is: Settings → Privacy and security → Cookies and other site data.
Data belonging to pointmoa.eu alone can be removed without touching other sites — search the site list for pointmoa.eu.
The site works once every record is deleted or blocked. The consequences are limited and reversible:
- the language has to be chosen again on every visit,
- data entered in the Calculator and on the Targets does not carry between pages and does not survive a page refresh,
- learning progress and an unfinished exam in the Shooting Licence module are not remembered,
- the information bar (§7) appears again.
Clearing site data is the only way to erase these records, and it rests entirely with the User. The Controller has no access to them and can therefore neither read them nor delete them.

9. Changes to this Policy

This document may change, in particular in connection with the release of new modules or changes in law. Amended text is published on the website together with the date of update and the version. Any change to what the site stores is introduced together with an update of this document, not after it.

This Policy was drawn up in Polish. In the event of any discrepancy between language versions, the Polish version prevails.