Cookies
Cookie Policy
Version 1.0 · in force from 27 July 2026
This page is an annex to the Privacy Policy: a named list of everything appwave.dev stores in your browser, with retention periods. If you only want to change your choice, click “Manage cookies” in the footer.
1.What cookies are, and why we also cover browser storage
A cookie is a small text file that a site writes to your browser and reads back on your next visit. Alongside cookies we use the browser’s local storage. It works similarly, but it does not expire on its own and it is not sent to the server with every request.
The law treats both the same way. Article 398 of the Polish Electronic Communications Law of 12 July 2024 requires your consent to store or read any data on your device, with one exception: where it is strictly necessary to deliver the service you asked for. That is why the tables below give the kind of entry as well as its name.
2.Three categories and what they actually mean
The consent banner has three toggles, and those are the only categories we use.
| Category | Default | What happens when enabled |
|---|---|---|
| Necessary | Always on | Remembering your consent choice and language, keeping the assistant conversation going, and recording that the form before a file download has already been filled in |
| Analytics | Off | Google Analytics 4 and PostHog start storing an analytics identifier; PostHog may record a session and show a short survey |
| Marketing | Off | Google Ads can connect a visit to an ad click; Meta Pixel measures ad performance on Facebook and Instagram |
Until you click in the banner, every optional category stays off - we do not use implied consent. Closing the banner with the X is recorded as a refusal.
Refusing consent does not restrict access to any content on this site. We do not use “consent or pay” walls.
3.Necessary cookies
These work without consent, because without them the site could not do what you are asking it to. None of these entries reaches a third party.
| Name | Kind | Set by | What for | How long |
|---|---|---|---|---|
| appwave-cookie-consent | Local storage | appwave.dev | Remembers what you agreed to in the banner. Without it the banner would ask on every visit | Until you clear browser data |
| NEXT_LOCALE | Cookie | appwave.dev | Remembers your language choice: Polish or English | 12 months |
| appwave.gatedDownload.* | Local storage | appwave.dev | The date the quote file was unlocked, so we do not ask for the same data again | 30 days |
| bcx_chat_list and other bcx_ entries | Local storage | BetterCX assistant | Keeps your conversation going after a page refresh. Only written once you open the chat | Until you clear browser data |
4.Analytics cookies
Written only after you enable the “Analytics” category. They show us which content works and where visitors get lost.
| Name | Kind | Set by | What for | How long |
|---|---|---|---|---|
| _ga | Cookie | Google Analytics 4 | Distinguishes browsers so unique visits can be counted | 24 months |
| _ga_[measurement id] | Cookie | Google Analytics 4 | Maintains the measurement session state | 24 months |
| _gid | Cookie | Google Analytics 4 | Distinguishes visitors within a single day | 24 hours |
| _gat_gtag_[measurement id] | Cookie | Google Analytics 4 | Throttles the number of requests sent to Google | 1 minute |
| ph_[token]_posthog | Cookie | PostHog, via appwave.dev/ph | Analytics identifier: ties events into one session and one path | 12 months |
| PostHog session data | Local storage | PostHog | Event buffer, session identifier, record of surveys already shown | 12 months |
If you refuse this category, PostHog stores nothing on your device but still records the visit itself - with no identifiers and no way of linking it to you. We explain this in section 7 of the Privacy Policy. You may object to it.
5.Marketing cookies
Written only after you enable the “Marketing” category.
| Name | Kind | Set by | What for | How long |
|---|---|---|---|---|
| _gcl_au | Cookie | Google Ads | Lets us attribute an enquiry to the specific ad you clicked | 90 days |
| _fbp | Cookie | Meta Pixel | Identifies the browser for the purpose of measuring Meta ad performance | 90 days |
| fr | Cookie on the facebook.com domain | Meta Pixel | Serving and measuring ads on Facebook and Instagram | 90 days |
| IDE, test_cookie | Cookie on the doubleclick.net domain | Google Ads | Measuring and targeting ads across the Google network, if we run a remarketing campaign | IDE: 13 months. test_cookie: 15 minutes |
6.How to change or withdraw consent
- On this site: click “Manage cookies” in the footer. The same panel you saw on your first visit opens, and the change takes effect immediately.
- After you withdraw analytics consent we delete the Google Analytics files (_ga, _gid, _gat) from your browser, and PostHog stops storing an identifier.
- In your browser: you can block and delete files in the settings - Chrome, Safari, Firefox, Edge.
- With the providers: you can turn off personalised advertising in Google Ad Settings, Meta Ad Preferences and via Your Online Choices.
- Deleting the necessary entries will make the site forget your consent choice and your language, and the banner will return on your next visit.
Withdrawing consent does not affect the lawfulness of the processing we carried out beforehand on that basis (Article 7(3) GDPR).
7.Keeping this list current
We review this list whenever the tools on the site change. Lifetimes are quoted after the providers - in practice they may be shorter if you clear your browser earlier, but never longer.
If you find a file from the appwave.dev domain that is not listed here, tell us at office@appwave.dev - we will add it to the list or remove the file.
8.Contact and the full notice
The full information about our processing - purposes, legal bases, recipients, transfers outside the EEA and your rights - is in the Privacy Policy.
Controller: AppWave sp. z o.o., ul. Kolumny 147E/1, 93-611 Łódź, Poland. Contact: office@appwave.dev, +48 538 441 413.