Privacy Policy
[1.2 DRAFT – NOT IN FORCE. Before publishing, delete this block and the [1.2 – NEW] / [1.2 – CHANGED] markers in the text.] Changes compared to version 1.1:
- New section 4.10: browser (push) notifications – what data, why, how long, who delivers them.
- Section 4.2: we record the device type and operating system of purchases (statistics).
- Section 1.2: scope extended to notifications.
- Section 4.6: notification prompt events in internal analytics (consent only).
- Section 4.7: new local storage item and the notification background script.
- Section 5: consent and legitimate interest purposes extended.
- Section 6: new recipients – browser push services (including transfer to third countries).
- Section 7: new retention periods.
- Sections 4.6, 4.7 and 6: advertising pixels – OpenAI (ChatGPT ads) and Meta (Facebook, Instagram) – only with consent in the “Advertising” category; joint controllership for the Meta pixel.
- New section 4.11: email campaigns – open and click measurement, purchase and unsubscribe after the email, targeting by purchase/city/last play, subject variants (A/B); partner and influencer emails. Sections 4.8, 5 and 7 were also extended.
PRIVACY POLICY
CityCode – urban adventure game platform
https://citycode.hu
1. Introduction
1.1. This Privacy Policy (hereinafter: Policy) describes what personal data the operator of the CityCode online platform (hereinafter: Platform) processes, for what purpose, on what legal basis, for how long, and what rights data subjects have. 1.2. [1.2 – CHANGED] The Policy covers data processed while using the Platform, registering, purchasing, playing, getting in touch, subscribing to the newsletter and subscribing to browser (push) notifications. 1.3. The Platform is available at https://citycode.hu.
2. Details of the controller
Name of the controller: Zelles Botond, sole proprietor (egyéni vállalkozó) Registered office: 9700 Szombathely, Niké utca 2., Hungary Registration number: 62746436 Tax number: 92328095-1-38 Email / data protection contact: contact@citycode.hu Phone: +36203322089 Web: https://citycode.hu The controller is a VAT-exempt (KATA) taxpayer.
3. Definitions
Personal data: data relating to an identified or identifiable natural person. Processing: any operation performed on personal data (e.g. collection, storage, use, erasure). Data subject: the natural person the personal data relates to. Processor: a service provider processing data on behalf of the controller (e.g. hosting, payment, email).
4. What data do we process?
4.1. Registration and account Signing in and purchasing require registration. The password is stored by the authentication provider in a non-readable form. Data Source Email address You provide it Password (encrypted) You provide it Display name (optional) You provide it Profile picture / avatar (optional) You choose or upload it Time the account was created and signed in to System
4.2. Purchase and invoicing The Platform does not store card details. Payment is handled on Barion's secure interface; card details are handled by Barion directly. Data Source Email address Account / payment process Buyer's name (optional) You provide it Mission(s) purchased, price, discount Transaction Coupon or gift card code (if used) You provide it Purchase identifiers, game code, spectator link token System Acceptance of the GTC and the Privacy Policy (time, version) You tick it Barion payment transaction identifier Barion [1.2 – NEW] Device type (phone, tablet or computer) and operating system (e.g. Android, iOS, Windows) – derived from the identification string sent by the browser; we do not store the string itself, the IP address or any other device identifier for this System Billing name and address (country, postal code, settlement, street, house number) – only if you request an invoice You provide it Type and serial number of the document issued System
4.3. Gameplay and statistics During play we record the progress of the game (current station, hints, start/finish time), solve times, active play time (ms), and, when someone joins as a spectator, the spectator's data.
4.4. Device data – location, camera, microphone Some features of a Mission (GPS navigation, puzzles) may ask permission for location, camera or microphone. The Platform neither transmits nor stores these on the server; processing happens solely on the device, with your permission.
4.5. Barion Pixel and fraud prevention To ensure secure card payment and to prevent abuse, the Platform embeds the base version of the Barion Pixel. Purpose: Solely the prevention of fraud and abuse (Barion does not use this data for marketing purposes). Data processed: Device and browser identifiers, and data about the pages viewed on the Platform before and during a purchase. Processor: Barion Payment Zrt. Legal basis: The controller's legitimate interest in guaranteeing secure electronic payment (GDPR 6(1)(f)). Further information about Barion's data processing practice is available in Barion's Privacy Policy. The Platform embeds the base version only. We do not use the full (Full) version of the Barion Pixel – which would collect data for marketing purposes beyond fraud prevention; were it introduced, it would be subject to your consent and this Policy would be amended accordingly.
4.6. Analytics (only with consent) If you consent on the cookie banner, we use our own (internal) analytics (page views, mission events, checkout) and external analytics (Google Analytics 4, Plausible Analytics). This data is not collected if you accept only the Necessary cookies. [1.2 – NEW] With a separate consent in the “Advertising” category (switchable on its own in the cookie window) we also use the OpenAI ad measurement pixel, to see which of our ChatGPT ads brought visitors and purchases. The pixel sends OpenAI the pages visited, the missions viewed, adding to the cart, starting checkout and the amount of a successful purchase, and – through the provider's automatic matching – a version of the email address entered on the page that is hashed (SHA-256) in the browser. Its sole purpose is measuring the results of our ads. [1.2 – NEW] With the same “Advertising” consent we also use the Meta Pixel (Meta Platforms Ireland Ltd.). Purposes: measuring the results of our Facebook and Instagram ads, optimising ad delivery, and allowing our ads to be shown to people who have already visited our site (for example looked at a mission). The pixel sends Meta the pages visited, the missions viewed (identifier, name, price), adding to the cart, starting checkout, the amount and items of a successful purchase and the fact of registration, together with technical browser and device data (e.g. IP address, browser identifier). For the COLLECTION and TRANSMISSION of pixel data, the operator of the Platform and Meta Platforms Ireland Ltd. are joint controllers (under Meta's Controller Addendum); Meta is solely responsible for processing after transmission, as described in Meta's privacy policy. Legal basis: consent (GDPR Art. 6(1)(a)), which can be withdrawn at any time in the cookie window. [1.2 – NEW] Likewise, only with consent, we record whether our question about notifications was shown to you and how you answered it (yes / not now / allowed or blocked in the browser).
4.7. Cookies and local storage Type Content / Provider Legal basis Necessary Sign-in session, operation of the Platform Service / legitimate interest Necessary Cookie preference (vk_cookie_consent) Necessary Security Barion Pixel (fraud prevention, device identifier, browsing data) Legitimate interest Analytics GA4 / Plausible (only with consent) Consent [1.2 – NEW] Advertising Meta Pixel (_fbp: 90 days, browser identifier; _fbc: 90 days, ad click identifier) Consent [1.2 – NEW] Advertising OpenAI pixel (__oppref: 30 days, ad click identifier; __obref: 365 days, random browser identifier) Consent [1.2 – NEW] Functional Time you declined the notification prompt (cc_push_prompt_dismissed_at, local storage), so we do not ask again for 30 days Legitimate interest [1.2 – NEW] Functional Notification background script (service worker, /push-sw.js) – only if you turn notifications on; it receives and displays the notification Consent
4.8. Contact, newsletter and other data Contact: Name, email address, subject, message text. Spam protection keeps the IP address in memory for about 10 minutes. Newsletter (with consent): Email address, source of the sign-up, time of confirmation/unsubscription. [1.2 – NEW] Measurement and targeting of the campaigns we send are described in section 4.11. Feedback: Text, category, page context, user identifier. Gift card: Buyer's and recipient's email address, message, card code and balance.
4.10. [1.2 – NEW] Browser (push) notifications If you say yes to our question and your browser allows it too, we send you notifications about new missions and discounted offers. A notification may appear even when the site is not open. We send at most two notifications a week, and none between 9 pm and 9 am. On iPhone the browser does not support this feature, so the question is not shown there. Data Source Subscription address (a unique address issued by your browser's push service) and the public keys needed to encrypt notifications Browser Chosen topics (new missions, offers) and language You choose them Time and place of subscribing (e.g. after a purchase, in your profile) and the version of this Policy in force at that time – as proof of consent System Device type and operating system System User identifier – only if you were signed in when subscribing System Delivery log: which notification was sent when, whether it was shown and whether it was clicked System Targeting: for signed-in users we also take into account whether they have purchased before, in which city, and whether they are currently playing (we do not send notifications during a game). This is not automated decision-making: it only affects who receives a given notification. The content of a notification passes through your browser's push service (see section 6) end-to-end encrypted; the service cannot see the content, only the data needed for delivery (the subscription address, the time and your device's connection data). Withdrawal: you can turn notifications off per topic or entirely in your profile, or block them at any time in your browser's site settings. Withdrawal takes effect immediately and does not affect the lawfulness of earlier processing.
4.11. [1.2 – NEW] Email campaigns: sending, measurement and targeting We send newsletters only to people who signed up and confirmed their subscription. We may send our partners and the content creators we work with (influencers) emails about our collaboration. Every email has an unsubscribe link at the bottom; once someone unsubscribes – whichever group they belong to – we send them no further campaign emails. Data Source Email address, and which recipient group it belongs to (newsletter, partner, influencer) System Which campaign we sent, when, with which subject variant, and whether sending succeeded System Opens: whether you opened the email, when and how many times – measured with an invisible image embedded in the email that loads from our server when the email is opened. Open tracking can be switched off per campaign; if your email program does not load images, no open is recorded. System Clicks: which link in the email you clicked and when – the links in the email redirect through our own server to the real address System Purchase after the email: whether an order was placed with your email address within 7 days of sending, and its amount (from our purchase data, aggregated per campaign) System Unsubscribe after the email: whether you unsubscribed within 30 days of sending System Purpose: to measure how useful and interesting our campaigns are, and to avoid unnecessary emails (e.g. not sending the same email twice to someone who already received it, and sending at most one reminder to someone who did not open it). We look at the results per campaign, in aggregate; the measurement is not shared with third parties and not used for advertising. Targeting: we may send a campaign to only part of the recipients, based on whether they have purchased from us before, in which city, and when they last played. We use our existing purchase and gameplay data for this and collect no new data. This is not automated decision-making: it only affects who receives a given email. Subject variants (A/B): the same email may be sent to two groups of recipients with different subject lines; the groups are assigned at random, and we only compare which subject was opened by more people. Legal basis: sending newsletters to subscribers is based on your consent (GDPR Art. 6(1)(a), Section 6(1) of the Hungarian Advertising Act); collaboration emails to partners and influencers, and the measurement of opens and clicks, are based on the controller's legitimate interest (GDPR Art. 6(1)(f)) in evaluating the effectiveness of campaigns and avoiding unnecessary emails. You can object to the measurement at any time at contact@citycode.hu; unsubscribing also stops further emails. [TO BE CHECKED: legal basis of open tracking (legitimate interest or separate consent) – legal review recommended.]
4.9. Billing data By default a receipt is issued, which does NOT carry your name or address; the electronic receipt contains only the email address needed for its delivery. If you request an invoice at checkout, providing the billing name and address is mandatory, as these are content elements of an invoice required by law (Section 169 of the VAT Act). We store this data attached to the given payment and forward it to the invoicing provider for the purpose of issuing the invoice. At checkout you can ask us, via a separate checkbox that is EMPTY by default, to save your billing data to your account and offer it pre-filled at your next purchase. Saved data can be changed or deleted at any time at checkout and in your profile, and nobody other than the account owner can access it. We do not ask for or process a tax number: we sell exclusively to private individuals. We are required to retain the issued invoice for 8 years under Section 169 of Act C of 2000 on Accounting. This is a legal obligation: deleting the account does not extend to it, and it cannot be ended by withdrawing consent.
5. Purpose and legal basis of processing
Performance of a contract (GDPR 6(1)(b)): Creating an account, selling a mission, gameplay, transactional emails. Legal obligation (GDPR 6(1)(c)): Invoicing, accounting. [1.2 – CHANGED] Legitimate interest (GDPR 6(1)(f)): Preventing abuse and fraud (e.g. the Barion Pixel), improving the platform (including statistics of purchases by device type), measuring opens and clicks of email campaigns, collaboration emails to partners and influencers (section 4.11), enforcing legal claims. [1.2 – CHANGED] Consent (GDPR 6(1)(a); for advertising messages also Section 6(1) of the Hungarian Advertising Act, Grt.): Newsletter, browser (push) notifications, web analytics (withdrawable at any time).
6. Processors (who do we pass data to?)
The controller uses the following processors (we do not sell data to third parties for marketing purposes): Supabase, Inc.: Database, authentication, backend Barion Payment Zrt.: Online payment (payment data, transaction) and fraud prevention (Barion Pixel) Resend, Inc.: Sending email Vercel, Inc.: Website hosting (technical logs, IP) Google LLC: Web analytics (with consent) Plausible Insights OÜ: Web analytics (with consent) [1.2 – NEW] Meta Platforms Ireland Ltd. (Ireland): measuring and targeting Facebook and Instagram ads (with consent); joint controller for collecting and transmitting pixel data. Data may also be processed by Meta Platforms, Inc. (USA); the transfer is based on the EU–US Data Privacy Framework (adequacy decision). [1.2 – NEW] OpenAI, L.L.C. (USA): measuring the results of ChatGPT ads (with consent); the transfer is based on the EU–US Data Privacy Framework (adequacy decision). [1.2 – NEW] Browser push services – delivering notifications (only if you turned them on). Which one is used is determined by your browser: Google LLC (Chrome, Android and most Chromium-based browsers), Mozilla Corporation (Firefox), Microsoft Corporation (Edge), Apple Inc. (Safari on macOS). These providers may also process data in the United States; the transfer is based on the EU–US Data Privacy Framework (adequacy decision). They receive the content of notifications encrypted and cannot see it. Billingo Technologies Zrt.: Invoicing; under a statutory obligation it also forwards the data of the issued invoice to the NAV Online Invoice system (the name and address of a private individual buyer are not included in that data reporting)
7. Retention (how long do we keep it?)
Account and profile data: For the lifetime of the account (anonymised on deletion). Purchase data: 8 years, due to accounting obligations. Gameplay, analytics: At most 3 years, or until the account is deleted. Contact messages: 2 years from the reply. Newsletter: 30 days after unsubscribing (log), then erasure. [1.2 – NEW] Browser notification subscription: until you unsubscribe. After unsubscribing (or if the browser ends the subscription) we close the record and send no further notifications to it; we keep it for 5 years as proof of consent, then delete it. [1.2 – NEW] Notification delivery log: 1 year. [1.2 – NEW] Email campaign sending and measurement log (recipient, opens, clicks): 2 years from sending, then erasure; on unsubscribing, further emails stop immediately. [1.2 – NEW] Device type of purchases: together with the purchase data.
8. Rights of the data subject
You have the right of access, rectification, erasure, restriction of processing, data portability and objection. You may withdraw your consent at any time. To exercise your rights or to delete your account, write to contact@citycode.hu (response deadline: max. 30 days).
9. Complaints, supervisory authority
We recommend contacting us first with a complaint. If you believe our processing infringes the law, you may lodge a complaint with the Hungarian National Authority for Data Protection and Freedom of Information (NAIH) (1055 Budapest, Falk Miksa utca 9-11., https://www.naih.hu).
10. Minors
The Platform is intended primarily for adults. We process the data of persons under 16 only under parental supervision; data provided without authorisation is deleted without delay.
11. Data security
We apply appropriate technical measures: HTTPS connection, hashed passwords (Supabase), access control, outsourcing payment to Barion's system, and admin restrictions. We do not use automated decision-making.
12. Amendment of this Policy and contact
The controller is entitled to amend this Policy and will give notice of it on the Platform. The version in force at any time is available at https://citycode.hu/legal/adatkezeles.pdf. Data protection questions, contact: Zelles Botond, sole proprietor 9700 Szombathely, Niké utca 2., Hungary Email: contact@citycode.hu Phone: +36203322089
Zelles Botond, sole proprietor
CityCode