Jegyfutár – Cookie and Tracking Notice

ID: JF-05 · Version: v0.9 EN · Date: November 6, 2026
Effective from: the date of publication.

1. Who is responsible for the processing?

Jegyfutár is operated by YourDJ Ügynökség Kft., registered office: 2724 Újlengyel, Petőfi Sándor utca 48., Hungary; company registration number 13-09-237888; tax number 32715143-2-13; https://jegyfutar.hu; customer service: support@jegyfutar.hu. YourDJ is the controller for its own platform measurement. Privacy contact: adatvedelem@jegyfutar.hu. YourDJ has not designated a data protection officer because it is not legally required to do so.

The event Organizer determines its own measurement and marketing purposes. The Organizer’s name, address, contact details and privacy notice are shown in the event’s legal information block and cookie settings. YourDJ acts as processor for technical operations carried out on the Organizer’s instructions. Joint controllership with tag providers is described in section 7.

YourDJ’s detailed notice is the Privacy Notice for YourDJ’s Own Processing; the Organizer’s is the Organizer’s privacy notice. Links: YourDJ’s privacy notice: https://jegyfutar.hu/en/adatkezeles/; the Organizer’s privacy notice: the link shown on the Organizer’s event page and at checkout.

2. What are cookies and tracking technologies?

A cookie is a small item of data stored in your browser. Other local storage, including IndexedDB, can serve similar purposes without being called a cookie. Pixels, embedded players and server-sent conversion events can transfer personal data even without cookies. This notice therefore covers browser storage and the related data transmissions.

Cookie expiry, server-side retention and the validity of a consent choice are separate periods. Deleting a cookie does not automatically delete data previously transferred lawfully. Encryption or hashing does not automatically make data anonymous.

3. Choices and legal grounds

The consent-based statistics and marketing tools below are distinct from the limited UTM-source processing based on legitimate interest in section 5.

Necessary: storage essential to a requested function, such as a secure session, shopping cart, waiting room or planning-room membership. These items cannot be disabled in the banner; blocking them in your browser may prevent the function from working. We designate a purpose as security only for genuinely necessary, proportionate operations, not for general tracking.

Statistics: measurement of usage and performance, including visits and purchasing journeys. Marketing: campaign and conversion measurement, matching in advertising systems and, where enabled, support for targeted advertising. These categories require separate, prior and voluntary consent and are off by default. Refusal does not prevent ticket purchases. Cookie consent is not a newsletter subscription.

Storage on and access to a device are governed by electronic communications rules, including section 155(4) of Hungary’s Electronic Communications Act and Article 5(3) of the ePrivacy Directive. Personal data processing is also governed by the GDPR. An exemption for necessary storage is not itself a GDPR legal basis. Necessary processing for a requested service may rely on performance of a contract; security on a documented legitimate interest; and evidence of consent on the duty to demonstrate consent. Optional measurement and marketing rely on consent.

We identify YourDJ’s and the current Organizer’s purposes and providers separately before you choose. Visiting another Organizer’s page does not automatically authorize its tags. A previous general acceptance does not automatically extend to a new controller, new purpose or materially changed provider scope.

Settings provide separate choices by purpose and controller for YourDJ’s and the relevant Organizer’s statistics and marketing tools. The system applies those choices separately.

Under 16, you cannot consent to optional (statistics and marketing) cookies; please choose rejection – you can still buy tickets. If we learn that someone under 16 has given such consent, we treat it as invalid, stop the related measurement and delete data processed on the basis of that consent.

4. First-party functional cookies

These are first-party cookies. Every own cookie is host-only: it applies only to the host that set it (jegyfutar.hu, an Organizer subdomain or a custom domain, each separately), not to subdomains, with path / throughout. For this reason the cookie banner asks again on a subdomain or custom domain.

NamePurpose and contentLifetimeWhen necessary
jegyfutar-sessionSession and cart association; the cookie generally identifies a server-side session120 minutes of inactivityFor the requested session. HttpOnly, Secure, SameSite=Lax; campaign-source handling is described in section 5.
XSRF-TOKENProtection against unauthorized cross-site requestsSame as the sessionFor protected operations. Secure, SameSite=Lax.
jp_consentNotice version and selected categories180 daysTo remember and apply acceptance or refusal. Secure, SameSite=Lax.
queue_pass_<event>Encrypted event waiting-room passActive window: 10 minutes by default, configurable between 5 and 30 minutesIn the relevant event’s high-traffic waiting room. HttpOnly, Secure, SameSite=Lax.
jf_plan_<plan>Encrypted planning-room membership30 daysFor the room function requested by the user. HttpOnly, Secure, SameSite=Lax.
jf_themeThe chosen appearance (light / dark mode); contains no identifier1 yearOnly if you choose with the switch; no consent required. SameSite=Lax. The choice is not saved to your account.

There is no separate remember-me, remembered two-factor device, language or cart cookie. Language is indicated by the URL; the cart association is part of the session. Server-side planning-room content follows the separate rule in the Privacy Notice for YourDJ’s Own Processing: 30 days after the last selected event, or 30 days after the last activity if no event is selected.

5. Campaign data associated with the session

If you arrive through a link in an advertisement or email, the server records the link’s campaign tags (utm_* parameters) from the opened address, without a new cookie; we link this to your purchase for no more than 7 days, after which only an aggregate that cannot be linked to a person remains, for 25 months.

Legal basis and distinction from consent: legitimate interest in measuring campaign effectiveness, GDPR Article 6(1)(f). No new cookie is set for this: the server reads the campaign tag from the opened address and stores it on the server alongside the session that is used for the purchase anyway. We consider this limited, short-term processing necessary and proportionate, so we do not ask for consent to it. All other measurement depends on your consent: statistical measurement, advertising click identifiers, advertising tags (pixels) and conversion data sent to advertising systems. If you reject optional cookies, only the limited campaign-source recording described above takes place; you can still purchase.

Retention: campaign data linked to a purchase are processed for no more than 7 days from opening the campaign link, then deleted or irreversibly disconnected from you and the order. A new page view does not restart this period, and longer order retention does not extend it. Campaign aggregates that cannot be linked to a person are retained for 25 months.

Summary of the legitimate-interest balancing: our interest is to assess the short-term order results of our campaigns. We process only the campaign fields, for a short time and with restricted access; longer-term analysis uses aggregates that cannot be linked to a person. We do not track individuals across Organizers. Email addresses, customer identifiers and other unnecessary or special-category data are filtered out of the parameters, and the full address is not copied to logs. We provide the detailed balancing rationale on request.

The Organizer’s campaign purpose: on the Organizer’s event page, the Organizer may also use the campaign source to assess its own campaigns, subject to the same limits, as described in its own privacy notice.

Objection: you may object on grounds relating to your particular situation in one place, with YourDJ: adatvedelem@jegyfutar.hu. YourDJ also enforces the objection towards the Organizer. Processing then stops unless demonstrated overriding compelling legitimate grounds or legal claims apply.

Advertising click identifiers and external advertising matching require marketing consent; local retention is no more than 7 days from collection. General statistical event measurement requires statistical consent. Such events from before consent are not backfilled retrospectively.

6. Cloudflare and bot protection

Cloudflare, Inc.’s infrastructure may process security and traffic data, including IP addresses, request information and browser characteristics. Turnstile checks operate on login-link, checkout and help forms; a related domain is challenges.cloudflare.com.

TechnologyPurposePeriod and limitation
__cf_bmDetection of harmful automated trafficProvider documentation specifies 30 minutes of continuous inactivity; only where the product actually sets it
cf_clearanceRemembering a successful checkConfiguration dependent; the provider default is 30 minutes. Actual Jegyfutár setting: 30 minutes (1,800 seconds). Jegyfutár’s code does not enable Cloudflare challenges.
TurnstileFiltering automated abuseFor the necessary check period. The token is used once for server-side verification and is not stored; neither the token nor the IP address is logged. Cloudflare’s log retention: Cloudflare’s Turnstile notice states no specific retention period; signals processed for its own purposes are retained under its general privacy policy

This does not mean every form sets all listed cookies. On the jegyfutar.hu zone, Rocket Loader, Email Address Obfuscation and automatic Web Analytics injection are switched off. Turnstile runs on the checkout, login-link and help forms, with a form-bound action and server-side verification. Cloudflare Access protects the platform admin interface. The map-tile storage (tiles.jegyfutar.hu) serves public OpenStreetMap data; there is no Referer-based filtering and no custom firewall rule, either on the zone or in Jegyfutár’s code. Bot Fight Mode and WAF challenge settings: Bot Fight Mode and JavaScript detection are switched off, and there is no custom firewall rule; the zone’s Security Level is medium and Browser Integrity Check is switched on (Cloudflare Free plan). Necessary security does not authorize unlimited provider product development: Cloudflare acts as an independent controller for certain detection-development operations. The data routes and roles are described in Annex C1 of the Privacy Notice for YourDJ’s Own Processing. Using Cloudflare does not by itself mean processing remains in the EU.

7. Statistics and marketing tools

Only tools listed in the active inventory, for the identified controller and authorized purpose, may be enabled. YourDJ’s and the Organizer’s tags can operate alongside each other, potentially sending data to separate recipients.

ToolCategoryData / storageRetention
Google Analytics 4StatisticsPage/event and browser/device data, cookie and session identifiers; _ga, _ga_<identifier>Loads only after statistics consent. Provider cookie default: 2 years; the code does not change it, and browsers may limit it. The cookies are deleted on withdrawal. Event retention in the GA4 property: per the GA4 property’s data retention setting (2 or 14 months; YourDJ’s setting: 14 months)
Meta PixelMarketingPages, events, campaigns and conversions, IP/browser characteristics, _fbp, _fbc, authorized matching dataLoads only after marketing consent; the code does not change the provider’s cookie expiry; the cookies are deleted on withdrawal. Server-side Conversions API: add-to-cart, checkout-start and purchase events, with hashed contact data; local matching data are kept for at most 7 days. Event retention at Meta: per the provider’s own terms; it publishes no fixed retention period
Google AdsMarketingPage views, purchase conversion (value, currency, order ID), campaign and click identifiers, IP/browser characteristics; _gcl_*Loads only after marketing consent, through the gtag.js loader shared with Google Analytics 4; purchase conversions are sent only to IDs configured with a conversion label; the code does not change the provider’s cookie expiry; the _gcl_* cookies are deleted on withdrawal. Retention at Google Ads: per the provider’s own terms; it publishes no fixed retention period
TikTok Pixel (only as an Organizer’s tag)MarketingPages, events, campaigns and conversions, IP/browser characteristics, _ttp and other identifiers actually usedLoads only after marketing consent; the _ttp cookie is deleted on withdrawal. Server-side Events API with the same events as Meta; local matching data (ttp, ttclid) are kept for at most 7 days. Retention at TikTok: per the provider’s own terms; it publishes no fixed retention period
Google Tag ManagerStatistics and Marketing – loads only with both consentsLoads other tags; a container name is neither a purpose nor permissionAccording to each actual tag’s own entry

Active measurement inventory: five kinds of measurement code can run on Jegyfutár pages. YourDJ’s own measurement: Google Analytics 4 (statistics), Google Tag Manager (container; only if both statistics and marketing consent are given), Google Ads (marketing) and Meta Pixel with the Meta Conversions API (marketing). On the Organizer’s event pages, TikTok Pixel and TikTok Events API (marketing) may also run if the Organizer sets them up. Browser domains: www.googletagmanager.com, *.google-analytics.com, *.analytics.google.com, www.googleadservices.com, googleads.g.doubleclick.net, www.google.com, connect.facebook.net, www.facebook.com, analytics.tiktok.com; server-side delivery: graph.facebook.com, business-api.tiktok.com. YourDJ’s active IDs: Google Analytics 4, Google Tag Manager, Google Ads and Meta pixel; YourDJ will publish the measurement IDs in the next update of this notice; the Organizers’ IDs are in the Organizer’s notice. The providers’ exact legal entity, address and current notice: Google (Google Tag Manager, Google Analytics 4, Google Ads): Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), https://policies.google.com/privacy; Meta (Meta Pixel, Conversions API): Meta Platforms Ireland Limited (Ireland), https://www.facebook.com/privacy/policy/; TikTok (TikTok Pixel, Events API, only as an Organizer’s tag): TikTok Technology Limited (Ireland), https://www.tiktok.com/legal/page/eea/privacy-policy/en. Before you choose, the cookie settings show the categories (necessary, statistics, marketing) with a short description; the details of the tags and their providers are set out in this notice.

Joint controllership for tags (GDPR Article 26): for the Meta, TikTok and Google (Google Analytics) tags, the controller of the page and the provider are joint controllers for collection and transmission to the provider: YourDJ on YourDJ’s own pages, and the Organizer on the Organizer’s event pages. For the Organizer’s tags, YourDJ only provides the technical tool. The essence of the arrangement:

Organizer tags run only on that Organizer’s event, cart, checkout and thank-you pages. No measurement operates on login, password, confirmation or planning-room join pages. There is no frontend Sentry integration or browser storage for error tracking.

The GTM container loads only if you have given both statistics and marketing consent. Statistics consent alone does not enable marketing tags. We do not enable unreviewed tags. We do not send cookieless measurement signals marked “consent denied” either, because measurement requires prior permission. Server-side rendering does not create an exception.

8. Own analytics and server-side conversions

Own analytics: no separate proprietary analytics cookie or new client identifier is placed. However, a one-way HMAC index derived from a session can link events. Such intermediate records are treated as pseudonymous personal data. Aggregate output is anonymous only after appropriate exclusion of re-linking and small groups. There is no cross-Organizer person-level analysis or global email hash for this purpose.

General statistics require statistical consent. The limited server-side UTM processing in section 5 is based on legitimate interest, with the limits described there. Personal attribution remains for up to 7 days from the campaign interaction, and UTM campaign aggregates that cannot be linked to a person for 25 months; this does not remove consent requirements for other event measurement. Marketing consent authorizes only the disclosed marketing and campaign-measurement purposes. Conversion matching data (IP, browser data, click and cookie identifiers) remain for up to 7 days from collection; daily automatic cleanup deletes the HMAC-indexed event series 30 days after capture. The hourly and daily aggregates derived from it, which cannot be linked to a person, are kept for 25 months.

Visitor statistics on the Organizer’s pages: on the Organizer’s event pages, organizer page and mini website, if you have given statistics consent, we record the steps of your visit (view, cart, checkout, purchase). The city is determined locally, from a database on our own server; we do not store the IP address or the browser’s full identification string, only the derived characteristics (city, country, source, device type, browser and operating-system family). The Organizer sees reports only about its own pages.

The Organizer can see individual visits under a serial number (for example “Visitor #482 913”): the order of steps within its pages, the time of each step to the minute, the entry city at settlement level, the device and the source. The number applies to one browsing session, uses no new cookie and is not linked to your name, your order or your IP address. We do not link your visits to each other; each new session gets a new number. This view cannot be exported.

Raw visit steps are kept for 30 days. For periods older than 30 days, cities, sources and campaigns with fewer than 10 visits are combined into an “other” row; the aggregates are kept for 25 months. When you withdraw statistics consent, we delete your visit’s serial number and its characteristics; figures already aggregated remain.

Conversion transmission: following marketing consent, the server may also send add-to-cart, checkout-start and successful-purchase events. Depending on the active integration, fields may include event and time, URL, order value and items, IP and user agent, campaign/click identifiers, and appropriately disclosed hashed email, telephone or external identifiers. Hashed contact information remains personal data. Free text, complaints, passwords, card data and unnecessary participant names must not be sent.

We check current consent before transmission; after withdrawal, queued events are not forwarded either, and expired matching data are not used for sending. The recipient's own retention is separate. _ttp and ttclid are identifiers for the TikTok server-side connection; they are not transmitted to Meta.

9. Embedded and uploaded videos

YouTube/Vimeo: the preview is hosted by us. An external player loads only after a separate video-specific permission, following information identifying the provider and transfer. Before that, no external preview image, player code or preliminary connection is requested from the video provider. Allowing a video does not enable general marketing.

Loading sends the provider at least the IP and device/browser information needed to serve the request, the video reference and any page information actually transmitted. YouTube’s privacy-enhanced mode and Vimeo’s dnt setting restrict some uses but do not mean that no data or cookies are involved. Vimeo also describes receipt of existing cookies and security exceptions. Refusing playback does not prevent purchases.

The permission applies only to that video and that page view: the player loads when the play button is pressed, the choice is not stored (neither in a cookie nor in browser storage), so after reloading or for another video you need to click again. The player stops when you leave or reload the page. This does not retroactively delete data already received by the provider. A short notice per provider (YouTube, Vimeo, Cloudflare Stream) is shown next to the play button. The providers’ legal entity, country and terms: YouTube: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland), privacy terms: https://policies.google.com/privacy; for transfers to third countries Google relies on the EU–U.S. Data Privacy Framework (DPF) and, where required, standard contractual clauses (SCCs) (https://policies.google.com/privacy/frameworks); Vimeo: Vimeo.com, Inc. (330 West 34th Street, 10th Floor, New York, NY 10001, USA), EEA representative: Bending Spoons S.p.A. (Via Nino Bonnet 10, 20154 Milan, Italy), privacy terms: https://vimeo.com/legal/privacy/policy; safeguards: EU–U.S. Data Privacy Framework (DPF) and standard contractual clauses (SCCs); Cloudflare Stream: Cloudflare, Inc. (101 Townsend St., San Francisco, CA 94107, USA), as described in Annex C1 of the Privacy Notice for YourDJ’s Own Processing.

Organizer-uploaded videos – Cloudflare Stream: uploading, processing, storage and playback of Organizer-uploaded videos uses Cloudflare Stream. This is a different route from a YouTube/Vimeo embed. The uploading Organizer handles processing concerning people appearing or speaking in the video.

Only the Organizer’s own uploaded videos go to Stream: the upload goes from the browser directly to Stream, and Jegyfutár stores only the video identifier. The preview image loads from the Cloudflare Stream server (videodelivery.net), from a signed URL valid for at most 6 hours, when the page is opened; your browser’s technical data (IP address, browser data) are sent to Cloudflare for this. The player loads only when playback starts, via a signed URL. The video is also deleted from Stream when the Organizer deletes it, on data-subject erasure and when the organiser account ends; uploads left incomplete for over 24 hours are removed by an hourly clean-up. Storage and access countries, Stream analytics: Cloudflare Stream stores and delivers videos on Cloudflare’s global network; EU-only storage is available only with the Data Localization Suite, which we do not use. Cloudflare records aggregate view data (Stream Analytics) in the account. Traffic necessary for requested playback is separated from optional statistics; optional measurement starts only with separate consent.

10. Local storage in the scanning application

This section concerns the Organizer’s gate staff devices, not the ticket buyer’s browser. The PWA’s jegyportal-scanner IndexedDB database stores an offline ticket list, device token and scan log; a service worker also operates. The purpose is authorized admission checking, including during network outages. Ticket lists may contain personal data, and the token is access information.

The ticket list and scan log are deleted automatically 24 hours after the event ends, once all scans have been uploaded; an un-uploaded log remains until it is uploaded. On switching events, the previous ticket list and the already uploaded log are deleted. The “Clear device” button immediately deletes all local data, including the token and the app cache. After server-side revocation the local ticket list can no longer be used for entry and is deleted on the schedule above. We do not delete unsynchronized admission records prematurely, and we do not keep the full ticket list on the device for longer than necessary. Revoking a token on the server does not delete an offline device’s copy. Staff report a lost device immediately to the Organizer and at support@jegyfutar.hu.

The service worker cache’s actual contents and lifetime form part of this inventory. Retention of application files and participant data is different. A visitor’s marketing consent is not the legal basis for an offline ticket list on a staff device.

11. Changing or withdrawing your choice

Use “Cookie settings” in the footer at any time. The first layer offers acceptance of all optional purposes, rejection and detailed settings. Optional switches are not preselected. Scrolling, continuing to browse or closing the panel is not consent.

We remember the choice in this browser for 180 days. Deletion, expiry or a material change may require a new choice. Together with the choice we record the current version identifier of this cookie notice (release date, YYYY-MM-DD) in the jp_consent cookie; when a new version is published, the earlier choice lapses and we ask again. An old page or queued server job must not override a withdrawal.

Withdrawal stops the related optional code and further transfers immediately deletes the affected measurement cookies on our own domain (for example _ga, _ga_*, _gid, _fbp, _fbc, _ttp, _gcl_*), and the page reloads. We cannot promise to directly delete every cookie on another provider’s own domain. These can also be managed through your browser or the provider. Requests concerning data already transferred are handled by the relevant controller. After withdrawal, no new events are recorded. The own analytics event series recorded before withdrawal contain only a keyed (HMAC) hash of the session, no IP address or browser identifier, and the daily automatic clean-up deletes them 30 days after capture. The hourly and daily aggregates derived from them, which cannot be linked to a person, are kept for 25 months. The serial number and characteristics of your visit recorded on Organizer pages (section 8) are deleted on withdrawal; figures already aggregated remain. Conversion-matching data (IP, browser characteristics, click identifier) are kept for at most 7 days.

The choice (categories and text version) is stored in the browser, in the jp_consent cookie, for 180 days. On the server we record only: a keyed hash of the session, the categories, the text version, the language and the time; retention of this evidence: 395 days from when the decision is recorded; older records are deleted by a daily automatic clean-up. A 180-day browser cookie does not justify unlimited server logging.

12. Recipients and international transfers

Cloudflare is among the necessary infrastructure and security providers. Only providers listed in the active inventory under section 7 can be measurement recipients. On external payment pages, SimplePay or Saferpay may use cookies under their own notices; a Jegyfutár choice does not replace information or choices required there.

Data going to the United States or another country outside the EEA require an applicable transfer safeguard. An adequacy decision, such as the DPF for a certified US recipient and covered transfer, or appropriate SCCs with supplementary measures and a transfer assessment where necessary, must address the actual route. Cookie acceptance is not a general waiver of these requirements or an automatic GDPR Article 49 derogation. Information about safeguards and access to a copy can be requested at adatvedelem@jegyfutar.hu. The recipient inventory shows the route and the safeguard.

12.1. Providers that interact with your browser

The providers below interact with your browser. Not all of them use browser cookies. Data routes, retention and transfer safeguards for Jegyfutár’s other providers (hosting, email delivery, error tracking, invoicing, AI) are set out in Annexes C1 and C1.1 of the Privacy Notice for YourDJ’s Own Processing; the Organizer’s own recipients are set out in the Organizer’s privacy notice.

ProviderWhen does it interact with your browser?Details
Cloudflare, Inc. – proxy/CDN and TurnstileOn every page load; bot screening on login-link, checkout and help formsSection 6
Cloudflare, Inc. – StreamWhen you open a page containing an uploaded video (preview image) and when you play the videoSection 9
Google (Google Analytics, Google Tag Manager, Google Ads)Google Analytics: after statistics consent; Google Tag Manager: only after both statistics and marketing consent; Google Ads: after marketing consentSection 7
Meta; TikTok (TikTok only as an Organizer’s tag)Only after marketing consentSection 7
YouTube, VimeoOnly after separate permission for the videoSection 9
SimplePay or SaferpayOn the external payment page, under the provider’s own noticeSection 12

13. Rights, contact and changes

Depending on the processing, you may request access, rectification, erasure, restriction or portability, object to legitimate-interest processing and withdraw consent. The Privacy Notice for YourDJ’s Own Processing and the Organizer’s privacy notice explain the conditions and request handling. You can submit a request from your account after signing in or at adatvedelem@jegyfutar.hu; you are identified by signing in or by a confirmation email, and we do not automatically reject requests identified in another way. We do not collect new identifying information solely to make an otherwise unidentifiable browsing record identifiable.

Privacy contact: adatvedelem@jegyfutar.hu; customer service: support@jegyfutar.hu, or the registered office above. Email customer service operates on weekdays, 08:00–20:00, with on-call coverage outside those hours, local time in Hungary. The promised initial substantive response is within 24 elapsed hours. This neither extends nor replaces the applicable deadline for a privacy request or complaint. Continuous AI reception uses the Claude/Anthropic integration described in section 3.5 of the Privacy Notice for YourDJ’s Own Processing; human assistance can be requested. There is no telephone customer service; you can submit requests and complaints by email or via the Help form on the website.

You may complain to Hungary’s National Authority for Data Protection and Freedom of Information (https://naih.hu) or to the supervisory authority of the EU Member State of your habitual residence, place of work or place of the alleged infringement (GDPR Article 77); you can also go to court. The authority’s contact details and the court route are set out in section 10 of the Privacy Notice for YourDJ’s Own Processing. When this notice changes, the inventory is updated to reflect actual functions and purposes and, where necessary, new consent is requested. This notice does not authorize silent activation of a new provider.

JF-05 v0.9 EN – END OF COMPLETE DOCUMENT