Cookie Policy
A complete register of what the website stores in your browser. Essential files are always active, while analytics and advertising tools start only after you consent — without your consent, none of them is created.
This is an English translation provided for convenience. If there is any discrepancy, the Polish version of this document prevails.
1. At a glance
You can change your decision at any time — refusing is as easy as consenting and does not restrict access to any part of the website.
2. Register of files and data
The table below reflects how the website actually operates. It also covers data kept in localStorage, even though formally it is not a cookie — what matters is the effect on your browser, not the name of the technology.
| Name | Provider | Type | Purpose | Lifetime |
|---|---|---|---|---|
| alstre_session | Alstre | HTTP cookie | Keeps the signed-in session. The content is encrypted, and the cookie has the httpOnly flag (inaccessible to scripts) and sameSite=lax, and in the production environment also secure. | Until the browser is closed; with “remember me” ticked — 30 days |
| alstre_consent | Alstre | localStorage | Remembers your consent decision together with the content version and a timestamp — this is our proof that consent was given. It is deliberately not a cookie: this way the decision is not sent to the server with every request. | Until browser data is cleared |
| Name | Provider | Type | Purpose | Lifetime |
|---|---|---|---|---|
| _ga | HTTP cookie | Distinguishes returning browsers for visit statistics. | 2 years | |
| _ga_* | HTTP cookie | Keeps the state of the measurement session for a specific GA4 data stream. | 2 years |
| Name | Provider | Type | Purpose | Lifetime |
|---|---|---|---|---|
| _fbp | Meta | HTTP cookie | Distinguishes browsers for measuring ad performance and building audiences. | 90 days |
| _fbc | Meta | HTTP cookie | Stores the ad click identifier. It is created only when you reach the site from an ad — it is not set when you arrive from a search engine or by entering the address directly. | 90 days |
We use the Meta pixel to measure ad performance and to build audiences. We do not pass form data through it: the automatic advanced matching option, which would read the addresses you type in, is switched off on our side. The name of the session cookie may differ if a custom one has been set in the installation's configuration.
3. How consent works
2026-09-1. Any extension of the scope of processing — a new tool, a new purpose, a new recipient — bumps the version and invalidates earlier consents. We will then ask you again.Technically, this is implemented with Google Consent Mode v2. The signals sent to the tag container look like this:
| Signal | Default | After consent |
|---|---|---|
| analytics_storage | denied | granted — after analytics consent |
| ad_storage | denied | granted — after marketing consent |
| ad_user_data | denied | granted — after marketing consent |
| ad_personalization | denied | granted — after marketing consent |
| functionality_storage | granted | granted — essential category |
| security_storage | granted | granted — essential category |
4. What happens before you consent
We say this plainly, because most policies leave it out. The Google Tag Manager container loads when the page opens, before you have made your decision. This means a connection to a Google server, and therefore passing it your browser's IP address.
In the refused state, the container runs in a restricted mode, which means it:
- does not store any cookies or other data in the browser
- does not assign an identifier and does not recognise you on your next visit
- removes advertising data from the requests it sends (ads_data_redaction)
- sends only signals stripped of identifiers, from which Google estimates the overall number of visits
This is a deliberate trade-off: in return, the statistics cover all traffic, not only the people who clicked “Accept”. So we do not claim that nothing happens before consent — we claim that we do not store files and do not identify you.
With the Meta pixel we do the opposite, and more strictly. It has no equivalent of the restricted mode, so once loaded it would set a cookie straight away. That is why its script does not appear on the page at all until you consent to marketing — and when you withdraw that consent, it stops sending anything.
5. What we don't do
- we do not store any advertising file until you consent to marketing
- we do not pass to Meta what you type into forms — automatic data matching is switched off
- we do not link data from advertising tools to your account in the system
- we do not sell or share cookie data with data brokers
- we do not use a cookie wall — refusing does not block access to any content on the website
- we do not pre-tick consents or treat a lack of response as acceptance
6. Third-party services without cookies
The website loads typefaces from Google Fonts, and the measurement map view in the system uses OpenStreetMap tiles. Such a connection passes the browser's IP address to the provider, but does not store any cookies on our domain.
If you want to limit these connections, block external fonts in your browser settings or with an extension — the website will remain fully readable; only the typeface will change.
7. Managing cookies in your browser
Regardless of our banner, you can delete and block cookies in your browser settings — in Chrome, Edge and Firefox this is done in the privacy and security section, in Safari in the “Privacy” tab.
One caveat: blocking the session cookie will make it impossible to sign in to the system. Without it, the server cannot recognise the signed-in user between requests — this is a technical limitation, not our business decision.
8. Changes and contact
Extending the scope of processing updates this document and bumps the consent content version, which means we will ask you for consent again. Purely editorial changes do not change the version.
Questions about cookies and personal data: rodo@alstre.com. A broader description of processing can be found in the privacy policy, and the rules on entrusting data in the GDPR document.
