CakeMarket Cookie Policy (Hungary)
Last updated: July 2026
This document requires legal review before publication. It reflects the Hungarian market and the current model of the Service.
Legal documentation is maintained separately per country; this document applies to the Hungarian market (hu.cakemarket.app). The Hungarian version is the source and governing text, and this English page is its 1:1 courtesy translation. The structure mirrors the Polish source documents 1:1, differing only in country-specific points. The corresponding document for the Polish market is in the Poland section.
CakeMarket is not a registered company yet. The operator's final company name, registered address, tax number (adószám) / company registration number and contact details must be completed before production publication.
§ 1. Technologies
1.1. The Service uses cookies, localStorage, sessionStorage and a PWA service worker. These technologies support login, guest sessions, security, payments, the interface language and the operation of the application.
1.2. The legal bases are the GDPR, the ePrivacy Directive and the applicable provisions of Act CVIII of 2001 on electronic commerce services (Ektv.) and Act C of 2003 on electronic communications (Eht.).
§ 2. Categories
| Category | Examples | Purpose | Consent |
|---|---|---|---|
| Essential | session token, CSRF, guest token, tracking token | login, security, orders and guest order tracking | no |
| Functional | HU/EN language, PWA preferences | remembering the settings chosen by the user | usually no, when necessary for a requested feature |
| Payment | Stripe technologies | payments, fraud prevention, payment compliance | no, when necessary for payments |
| Analytics/marketing | currently no production implementation described in the documentation | measurement or marketing, if implemented | yes, where consent is required |
§ 3. LocalStorage and the service worker
3.1. LocalStorage may store the guest token, language preferences and application settings. Deleting this data may make it harder to track guest requests or to use the application.
3.2. The service worker (sw.js) caches static assets for the PWA and offline mode. It is not used for advertising profiling.
§ 4. Stripe
4.1. Stripe may use its own cookies and similar technologies to handle payments, security and fraud prevention.
4.2. Details are available in Stripe's policies at stripe.com.
§ 5. Managing settings
5.1. Users can delete cookies and localStorage data in their browser settings. Blocking essential technologies may prevent logging in, payments, creating requests or tracking orders.
5.2. If the Service implements analytics or marketing cookies that require consent, withdrawing consent will be as easy as giving it.