Cookies
Last updated: July 25, 2026
This page explains how KPZ uses cookies and similar browser storage technologies.
KPZ is a small fan-run project. The goal is not to track you aggressively or serve you ads. Use of cookies and browser storage is minimal and transparent.
1. What are cookies
Cookies are small text files stored on your device when you visit a website.
Alongside standard cookies, sites may also use similar technologies — local storage (localStorage), session storage (sessionStorage) and IndexedDB. They work slightly differently but serve a similar purpose: helping the site remember certain information.
KPZ uses a minimal set of these technologies — only for purposes directly related to how the site works.
2. What KPZ uses
When you visit the site, the following information may be stored:
2.1. HTTP cookies
The application itself does not set cookies directly. However, the hosting infrastructure or framework may place technical cookies:
- next-intl (language management) may set a NEXT_LOCALE cookie if you switch language — it helps remember your last language choice;
- Firebase (Google) may place technical cookies related to authentication or hosting infrastructure.
Specific HTTP cookies can be verified in your browser's DevTools → Application → Cookies.
2.2. Local storage (localStorage)
Local storage is similar to cookies, but is stored only in your browser and is not automatically sent to the server.
| Key | Contents and purpose | Type | Duration |
|---|---|---|---|
| kpz_cart | Cart items — productId, title, price, quantity. Persists the cart between sessions. | Necessary | Until browser storage is cleared |
2.3. Session storage (sessionStorage)
Session storage is automatically cleared when you close the tab or browser window.
| Key | Contents and purpose | Type | Duration |
|---|---|---|---|
| kpzCommunityRulesAccepted | Records that the user has read the community listing rules. Prevents them from being shown repeatedly within the same session. | Functional | Until tab/browser is closed |
| cookies.sessionRow2Key | Prevents counting repeated views of the same item within a single session. Helps keep impression statistics accurate. | Functional | Until tab/browser is closed |
2.4. IndexedDB — Firebase Auth
Firebase Authentication stores sign-in data (auth token) in IndexedDB under the firebaseLocalStorageDb database. This is needed so you stay signed in between visits. It is managed entirely by Firebase (Google) and is deleted when you sign out.
3. Analytics
KPZ does not currently use analytics tools such as Google Analytics, Firebase Analytics, Mixpanel, Plausible or similar. No information about your behaviour on the site is collected via cookies or similar tracking technologies.
4. Third-party services
KPZ uses the following technical services, which may store data in your browser:
| Service | Purpose | Browser storage |
|---|---|---|
| Firebase (Google) | Hosting, database, authentication, image storage | IndexedDB (auth token), potentially technical cookies |
| Resend | Sending system emails | Does not set browser cookies |
Firebase (Google) is operated by Google LLC. Their privacy policy applies to data processed through their infrastructure.
5. How to manage storage
5.1. Through your browser
You can delete cookies, localStorage, sessionStorage and IndexedDB through your browser settings (DevTools → Application → Clear Site Data).
Be aware that if you clear this data:
- your cart will be emptied;
- you will need to sign in again;
- community listing rules may be shown again;
- impression counters for items will reset for your current session.
5.2. Signing out
When you sign out, Firebase clears the auth data from IndexedDB. Cart data in localStorage is not automatically cleared on sign-out.
6. Changes
This page will be updated if the site starts using new technologies or providers, or if the way browser storage is used changes.
7. Contact
If you have questions about cookies or personal data:
Email: info@kpz.bg