Festetics Fénypark · Back to the website

✧ Legal information

Privacy Notice

Download text

How the website currently operates

The visit planner processes visitor numbers and the selected day in the browser. The plan is downloaded locally; this action alone does not send the plan to the organiser or create a booking.

The language selection is stored in a local storage entry named festetics-language until the browser data is cleared. Google Analytics 4 starts only after separate statistical consent. Meta Pixel starts after separate marketing consent; details are provided in the Meta supplement. Newsletter subscription is not operational. The hosting platform's data processing requires separate examination.

There is no direct contact form on the website. You can contact us by email at info@festeticsfenypark.com or by telephone.

The embedded Google Map loads only after permission is given. When it loads, Google may receive technical data, such as an IP address and browser data. The choice applies to the current browser session and can be withdrawn through “Cookies and settings”. Notice: https://policies.google.com/privacy?hl=hu

The technical hosting platform for festeticsfenypark.com is ChatGPT Sites (OpenAI); the website is publicly accessible. No migration to a separate hosting provider is currently planned.


1. Who processes the data, and what does this notice cover?

Controller: MusicKing Pro Kft., organiser of Festetics Fénypark and operator of the festeticsfenypark.com website. Registered office: 1141 Budapest, Szugló utca 125/E, A. épület, C. lépcsőház, 015. ajtó. Tax number: 32918683-2-42. Company registration number: 01-09-449438. Data protection contact: event.musicking@gmail.com. Requests by post may be sent to the same registered office. Telephone: +36 30 836 0271.

1.1. This notice covers enquiries concerning the website and the event, ticket administration and admission carried out by the Organiser, invoicing, refunds, complaint handling and the enforcement of claims. The controller is the person determining the purposes and the essential means of processing; a processor, by contrast, acts on documented instructions.

1.2. The online ticket sales platform is operated by JEGYx1 Zrt. It publishes a separate notice about data processing within its own system. This document does not automatically cover all independent processing by the Ticket Seller and does not replace notices provided by other independent service providers.

1.3. Admission to the event without giving a name may also be possible: a visitor does not become an identified person merely by entering the park. However, the ticket identifier and purchase and usage data that can be linked to a person may constitute personal data.

1.4. We process closed enquiries unrelated to a contract, complaint or legal dispute for no more than 6 months, and operational ticket and admission data until the ticket's validity expires and for no more than 30 days thereafter. Complaint records, accounting documents, data subject requests and evidence relating to specific legal claims may be retained for different purposes for the periods specified in sections 6–9. Section 15/A applies to photographs and videos. The time limits must be applied by purpose, not to all customer data at once.

1.5. Data protection contact: event.musicking@gmail.com. Questions about data processing and data subject requests may both be submitted at this address. Providing a contact address does not constitute the appointment of a data protection officer.

2. Data processing principles and legal bases

2.1. We process only the data necessary for the particular matter, for a defined purpose and for as long as necessary. Processing required to fulfil a purchase is not based on marketing consent. Acceptance of the Terms and Conditions or acknowledgement of the Privacy Notice is not general consent.

2.2. Article 6(1)(b) GDPR concerns processing necessary for the performance of a contract or for preparatory steps at the data subject's request; point (c) concerns compliance with a legal obligation; point (f) concerns a documented and properly balanced legitimate interest; point (a) concerns freely given, specific and informed consent.

2.3. Consent may be withdrawn at any time, free of charge, without affecting the lawfulness of prior processing. Where processing is based on legitimate interests, the data subject may object on grounds relating to their particular situation; the controller then examines whether overriding compelling grounds or a legal claim remain. Following an objection to direct marketing, the data may no longer be used for that purpose.

2.4. The following sections specify separately the data, sources, legal basis and retention associated with each purpose. Longer retention of an invoice does not automatically justify storing all correspondence, admission logs or marketing data for the same period.

3. Contact and visit enquiries

Purpose and data categories: answering enquiries and preparing a visit or group offer. Data processed: name or form of address, email address, callback telephone number provided by the data subject, the question and reply, requested date and time, number of visitors and information needed for the arrangements. We do not request lists of children's names, copies of identity documents or medical reports for a simple enquiry.

Source and legal basis: the enquirer provides the data directly. For an enquiry preparing a private individual's own contract, Article 6(1)(b) GDPR applies; for general information and an organisation's contact person, Article 6(1)(f) applies, our legitimate interest being to respond appropriately to enquiries and maintain business communications.

Retention: for a closed enquiry unrelated to a contract, complaint or dispute, no more than 6 months from closure. In the event of a contract, complaint or legal claim, only the relevant, necessary data are transferred to the appropriate record, with its separate retention period.

Provision of data: voluntary, but we cannot send a personalised reply without at least one contact detail and the question. This notice does not authorise audio recording of telephone conversations; introducing audio recording requires separate prior information.

4. Ticket purchases, administration by the organiser and notifications

Purpose: performing the event service provided by the ticket, checking the purchase, providing necessary visiting information, and notifying cancellations or material changes. Such service notifications may not be used as a newsletter combined with advertising.

Data categories: insofar as actually processed, the purchaser's name and email address, order and ticket identifiers, ticket type, quantity, value, validity, time of purchase, payment status and necessary administrative correspondence. Invoice data are used only for invoicing; a telephone number only where necessary for the process and actually collected. The Organiser does not request full bank card numbers, CVV codes or online banking passwords.

Source: the data subject for direct administration, and for online ticket purchases the JEGYx1 ticket sales system, within the access provided to the Organiser. The Organiser may process only data lawfully made available to it and necessary for the particular administration. The rules governing the organiser's access are set out in section 11.2 .

Legal basis: Article 6(1)(b) GDPR for performance of the event contract with the purchaser. For an organisation's contact person acting on another's behalf, the legitimate interest in necessary business communications, Article 6(1)(f). Where the relevant conditions apply, we also provide information under Article 14 GDPR about data obtained from another person.

Retention: operational administration continues until the ticket's validity expires, and then for no more than 30 days for administrative closure. Thereafter, only invoicing, refund, complaint or minimal claims-enforcement data requiring separate retention under sections 6–9 remain; the entire customer profile is not automatically retained.

Provision of data and recipients: the online purchase concerned cannot be fulfilled without the data needed for ticket delivery and the contract. Authorised administrative staff of the organiser and the service providers performing the particular task under section 11 may access the data. JEGYx1's own notice also applies to online purchases.

5. Admission, discounts and free visits

5.1. Admission checks: the ticket code, ticket type and validity and, where necessary, usage status and time of entry may be processed. The purpose is to enable use of the ticket and prevent repeated or unauthorised entry. Article 6(1)(b) GDPR applies to performance of the purchaser's contract; Article 6(1)(f), a documented legitimate interest, applies to necessary checks on other ticket holders and the prevention of misuse.

Retention: until validity expires, then for no more than 30 days for operational reconciliation. In the event of specific misuse, a complaint or a legal dispute, only the extract necessary as evidence in the matter may be retained longer on the appropriate separate legal basis. *

5.2. Checking discounts: age, student or pensioner eligibility may be checked by viewing the necessary part of the relevant evidence. The Organiser does not copy documents or record identity document numbers, facial images or birth details more precise than the age group required. At most, the discounted category appears on the ticket. The purpose and legal basis are performance of the discounted contract or, for other ticket holders, the legitimate interest in checking eligibility.

5.3. Children: as a general rule, quantity and age group suffice for purchasing a family or child ticket; the child's name, exact date of birth or a copy of their document is not required. Communication takes place with the purchaser or accompanying person.

5.4. We do not request medical evidence from visitors with disabilities or record diagnoses, disability data or copies of identity documents. Free admission records may use only a general free-admission category that is not linked to a person and does not identify a health condition. Different processing may not be introduced on the basis of this notice.

6. Invoicing, accounting and refunds

6.1. Documents: invoice and accounting data required by law may be processed, including name, billing address, business tax number where necessary, service description and value, performance and issue dates, document number and necessary transaction reference. The source is the data subject, the purchasing system or the payment service provider, as appropriate to the actual process.

Legal basis and period: Article 6(1)(c) GDPR, compliance with tax and accounting obligations. Accounting documents must be retained for at least 8 years under section 169 of Act C of 2000 on Accounting. This obligation does not automatically extend to all marketing or admission data.

6.2. Refunds: the order identifier, reason for and amount of the refund, payment status, contact details and, where reimbursement cannot be made using the original payment method, the account holder's name and bank account number may be processed. Administering the payment is necessary to settle the contract, Article 6(1)(b) GDPR; related accounting documents are processed under a separate legal obligation pursuant to Article 6(1)(c).

Retention: until the operational refund case is closed, then for no more than 30 days; the accounting document for the statutory period, and necessary legal evidence under section 9. There is no reason to request full bank card details or passwords.

For online purchases, the purchaser receives the invoice from JEGYx1 using the Számlázz.hu invoicing software. Számlázz.hu is provided by KBOSS.hu Kft. According to the organiser's information, JEGYx1 Zrt. appears as the seller on the invoice and JEGYx1 Zrt. also handles on-site invoicing.

6.3. Recipients: the actual invoice issuer, the accounting service provider, the bank or payment service provider concerned and authorities authorised by law, within the necessary scope of data. *

7. Handling consumer complaints

Purpose and data categories: investigating complaints and providing the legally required response. Necessary data: name, residential address or electronic contact details as appropriate to the procedure, content of the complaint, place, time and method of submission, related order, necessary portions of evidence, and the business's position and response. For a written record, additional data required by law may be recorded, together with a signature where necessary for a complaint recorded in person and an identifier for a complaint made by telephone.

Source and legal basis: the complainant, the service provider involved and our own order/admission records. Article 6(1)(c) GDPR, section 17/A of Act CLV of 1997 on Consumer Protection. We retain complaint documents and a copy of the substantive response for 3 years. For a separate pending legal claim, section 9 may also apply to the necessary evidence.

Complaint handling email: info@festeticsfenypark.com. Administration: as a general rule, we respond to written consumer complaints within 30 days; this is not the same as the one-month deadline for GDPR requests. Complaints may be submitted at the ticket office, through the channels listed on the website, and at the contact address in this notice.

Recipients: the organiser's employee authorised to assess the complaint and, to the extent necessary, the service provider concerned, legal representative, authority, conciliation board or court. We request data concerning another person or a child, or medical documents, only where genuinely necessary for the particular matter; we do not generally request complete copies of identity documents.

8. Handling data subject requests

Purpose: responding to requests for access, rectification, erasure, restriction, objection, data portability and other data protection requests. Data processed: name and reply address, content of the request, outcome of necessary identity checks, and documentation of the action taken and response.

Legal basis: Article 6(1)(c) GDPR, obligations under Articles 12–22 GDPR. After the case is closed, minimal evidence of compliance may be retained on the basis of the legitimate interest in demonstrating lawful handling, subject to a separate balancing test. Unnecessary supporting documents and working copies must be deleted.

Retention: for no more than 3 years after the data subject's case is closed, we retain only the necessary record of the request and response. This is the organiser's retention rule, not a deadline imposed by the GDPR for every request. We review necessity at least annually; unnecessary working copies and surplus identification data are deleted when the case is closed. Further retention requires a documented balancing of interests; if there is no justifiable retention purpose or appropriate legal basis, the data must be deleted sooner.

9. Legal claims, damage incidents and investigations of misuse

Purpose: establishing, exercising and defending specific contractual or other legal claims, and investigating substantiated misuse. Data categories: order and contractual data essential to the particular matter, case files, correspondence, necessary portions of evidence, contact details of the data subject and witnesses, and the outcome of the case.

Legal basis: Article 6(1)(f) GDPR, the legitimate interest in enforcing lawful claims and defending against claims. Where health data are exceptionally essential to a legal claim, Article 9(2)(f) GDPR must also be examined; this is not general permission to collect health data. For disclosures to authorities, Article 6(1)(c) may apply on the basis of the particular obligation.

Retention: we retain the minimum evidentiary data necessary for a specific legal claim for no more than 5 years from the date the claim becomes due, having regard to the general civil limitation period. This does not require five-year storage of all data. Any longer retention justified by pending proceedings or suspension or interruption of limitation is documented individually. We review necessity at least annually and when the matter is finally settled; data no longer needed as evidence are deleted.

Recipients: legal representative, insurer, expert, conciliation board, court or authority, solely to the extent justified by the matter. An objection may be lodged against processing based on legitimate interests.

10. Technical operation of the website and cookies

10.1. Technical logging. Servers and security systems may also process operational data that can be linked to a person. * Listing them does not mean that the website collects all of them.

Proposed purpose and legal basis: the legitimate interest in maintaining operation and IT security, Article 6(1)(f) GDPR, with documented necessity. Proposed retention: no more than 30 days, with separate retention of necessary data relating to a verified security incident. Actual log settings must follow the stated period.

10.2. Cookies and similar technologies. Strictly necessary operational technologies must be distinguished from statistical, advertising and third-party embedding solutions requiring consent. A tool requiring consent must not start merely because the website is opened or browsing continues. Refusal and subsequent withdrawal must be easily accessible.

The verified storage inventory for the website's own code is available on the Cookies and settings page. The choice can be changed at any time using the Privacy settings button. Google Analytics 4 may be used with separate statistical consent; refusal does not prevent use of the website. Details appear below. Meta Pixel starts after separate marketing consent; details are provided in the Meta supplement.

10.3. Visit planner. Visitor numbers and the visit date are processed in browser memory. The plan and calendar entry are downloaded to the visitor's device. The planner does not send the plan to the organiser, create a booking or send an email.

10.4. External content. Maps, videos, social modules and external fonts may transmit data as soon as they load. The technical assessment must cover these and server-side tracking solutions, not just traditional cookies.

11. Who may access the data?

11.1. Organiser's access: authorised staff handling administration, admission, finance and complaints, to the extent necessary for their duties and subject to confidentiality and access rules. We do not make personal data public merely because a ticket has been purchased.

11.2. JEGYx1 – ticket purchase data and access

JEGYx1 Zrt., 1139 Budapest, Forgách utca 37.; info@jegyx1.hu. Its own notice identifies it as a controller. Source: JEGYx1 Privacy Notice, checked: 1 October 2026.

The ticket seller's data and service providers: section II describes processing of names, email addresses and purchase dates; it also mentions residential address, telephone number, company name, tax number and gender as additional information that may be provided. Its records name Számlázz.hu for invoicing, K+J Számviteli Szolgáltató Kft. for accounting, and Rackforest and ATW Internet Kft. for storage of registration data. These are the service providers identified by JEGYx1.

JEGYx1 retention: section V specifies 24 months for personal data provided at purchase, extended until conclusion in the event of a legal dispute; it specifies at least 8 years for invoices and 5 years for contractual data. The periods vary by processing purpose; the 24-month limit does not apply to all data.

Access request: the purchaser may request information about and a copy of their own data and, subject to the applicable conditions, rectification, erasure, restriction or data portability at info@jegyx1.hu ; sections VI–VII also describe the right to object.

Organiser's access and use of data: MusicKing Pro Kft. may process personal data relating to ticket sales solely to the extent necessary to hold the event, verify admission entitlement, handle ticket-related matters, handle complaints and comply with statutory obligations. Access may take place within the scope of the agreement with JEGYx1 and the permissions actually provided.

Only staff authorised to perform the relevant task may access the data, to the extent necessary for their duties. Data may be downloaded or transferred only for a defined purpose, with an appropriate legal basis and limited to the necessary data categories. Customer data may not be used solely on the basis of a ticket purchase for newsletters or other marketing activities requiring a separate legal basis.

Sections 4–9 of this notice define the purpose, legal basis and retention period for data actually received by the Organiser. The ticket seller's notice governs processing within JEGYx1's own system. This provision establishes an access rule; it does not in itself mean access to the entire customer database.

11.3. There is no direct contact form on the website. You can contact us by email at info@festeticsfenypark.com or by telephone.

11.4. ChatGPT Sites – the website's hosting platform

The website is served by ChatGPT Sites (OpenAI). The website is publicly accessible; the Organiser has not specified a separate hosting service. A move to another provider is not currently planned.

OpenAI's general privacy policy: https://openai.com/policies/privacy-policy/. This link alone does not establish the contracting legal entity, data processing agreement, log retention, backups or storage countries associated with the particular Sites hosting service. These must be recorded on the basis of the contractual terms of the service used. *

The website's own application code does not store contact form messages or visit planner configurations in a database. This does not mean there is no technical processing at hosting-platform level. The current data flow for messaging is described at the beginning of this notice.

11.5. Other service providers: the actual accountant, invoicing provider, payment service provider, website maintenance provider, IT provider or admission service provider may process the data necessary for their tasks. * Service providers for another website cannot automatically be regarded as MusicKing's partners.

11.6. A processor may process data within its assigned task only under an agreement compliant with Article 28 GDPR. Disclosure to an independent controller requires an appropriate legal basis and information. In response to an authority's request, we disclose only data justified by the request and the law. The operator of the palace does not automatically receive a complete customer list either.

12. International data transfers

12.1. Where data are transferred to a recipient outside the European Economic Area, or access is provided from there, the conditions of Chapter V GDPR must also be met. Such transfers cannot be ruled out without verification, given the use of email, cloud services and external website modules.

12.2. An appropriate legal solution may be a valid adequacy decision within the scope applicable to the recipient, or appropriate safeguards, such as standard contractual clauses with the necessary assessment and supplementary measures. These are not interchangeable justifications that can be listed arbitrarily: they must be matched to the actual recipient and data flows.

* The final notice must not state “no international data transfers” without verification.

13. Data security and erasure

13.1. The controller must apply technical and organisational measures appropriate to the risks of processing: appropriate access management, removal of unnecessary access, secure data transfers, multi-factor access where necessary, staff information and documented incident handling. This list is an expected operational framework, not an independent security certification.

13.2. The management of MusicKing Pro Kft. is responsible for compliance with retention deadlines, assisted by the employee assigned to implementation and the service provider concerned. We assign an erasure deadline to the data and erase or irreversibly anonymise them no later than that date. We check compliance with deadlines weekly. To verify erasure, only the necessary record of the data category, period, date of the operation and person carrying it out may be retained, not a copy of the erased content. When restoring from a backup, erasures already due must be performed again before the restored data are used. The actual expiry periods for external providers' backups form part of the provider consultation.

13.3. In the event of a personal data breach, we assess the risk and, where necessary, notify the supervisory authority and inform data subjects in accordance with the GDPR. Not every technical error requires individual notification, but mandatory information may not be omitted.

14. Data subjects' rights and the request procedure

14.1. Information and access: you may request confirmation of whether we process personal data, access to the data and the prescribed processing information, and a copy. The rights of other persons must also be respected when providing copies.

14.2. Rectification, erasure and restriction: inaccurate data may be corrected and incomplete data completed. Erasure is not unconditional: for example, accounting documents that must be retained by law cannot be erased merely on request. Subject to the GDPR's conditions, restriction of processing may also be requested, for example where accuracy is disputed or an objection awaits assessment.

14.3. Data portability: in cases specified by the GDPR, data provided by the data subject and processed by automated means on the basis of consent or a contract may be requested in a structured, commonly used and machine-readable format. This is not a general right to export data applying to every processing activity.

14.4. Objection and withdrawal of consent: where processing is based on legitimate interests, the data subject may object on grounds relating to their particular situation; consent may be withdrawn without giving a specific reason. An objection to processing for direct marketing must be honoured unconditionally with respect to any further use for that purpose.

14.5. Automated decisions: for these basic processes, we do not plan decisions based solely on automated processing that produce legal effects concerning the data subject or similarly significantly affect them. Technical ticket-validity checks may be challenged and human review requested. *

14.6. Submitting a request: event.musicking@gmail.com or the registered office's postal address. A request need not cite legislation; it is sufficient to state clearly what action you request. Identity checks take place only to the extent necessary and proportionate.

14.7. Deadline: we provide information on action taken without undue delay and no later than one month after receiving the request. In view of the number or complexity of requests, the deadline may be extended by a further two months, but information about the extension and its reasons must be provided within the first month. This is not an automatic three-month handling period.

14.8. As a general rule, the procedure is free of charge. For a manifestly unfounded or excessive request, a fee or refusal is permissible only under the GDPR's narrow conditions, and the controller must substantiate the grounds. Where a request is refused, we also provide information about remedies.

15. Complaints to the supervisory authority and judicial remedies

You may also contact us directly with a data protection question, but this is not a prerequisite for an administrative or judicial remedy. You may lodge a complaint in particular with the supervisory authority in your habitual place of residence, place of work or the place of the alleged infringement.

Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH)

Registered office: 1055 Budapest, Falk Miksa utca 9–11.

Postal address: 1363 Budapest, Pf. 9.

Telephone: +36 1 391 1400

Email: ugyfelszolgalat@naih.hu

Website: naih.hu.

The data subject may also bring proceedings before a court under the GDPR and applicable procedural rules. This notice does not establish exclusive jurisdiction in Budapest and does not restrict the lawful pursuit of compensation or damages for infringement of personality rights.

15/A. Organiser's photographs and videos

Photographs and videos are taken by the organiser, MusicKing Pro Kft., to present Fénypark and for publication on the event's social media pages. Images and videos must be created from the outset so that visitors are neither recognisable nor identifiable by reasonably combining them with other data. No close-up portraits are taken. We check every recording before publication; material depicting a person identifiable by their face, voice, clothing or other circumstances may not be published under this rule.

We retain raw photographs and videos for selection and editing for no more than 30 days from creation, then delete them. If a raw recording nevertheless contains an identifiable person, it must be deleted or irreversibly anonymised immediately upon discovery; the 30-day maximum does not authorise storage of recordings of recognisable persons without a legal basis.

Published recordings that cannot identify a person may remain available for as long as necessary to present Fénypark. We review their relevance at least annually and remove outdated or unnecessary material from channels under our own management. The organiser cannot always delete independent copies held by social media providers and other users.

The organiser of Festetics Fénypark does not operate a separate security-camera surveillance system and does not record or store such footage. This statement does not cover any separate system the palace operator may have. Entry, acceptance of the Terms and Conditions or an information sign does not in itself constitute consent to use a person's likeness.

16. Effective date and amendment of the notice

The organiser's rules apply from: 1 October 2026. Consolidated version: 1 October 2026, version 1.1. When new processing is introduced or a substantive change is made, data subjects must be clearly informed in advance as appropriate to the circumstances. An amendment does not in itself extend previously given consent to a different purpose.

The version of the notice currently applied is available on the website; the Organiser retains earlier versions to demonstrate compliance. Separate operational modules – newsletters, photography by the organiser, camera surveillance – may be introduced only subject to the appropriate separate information and legal-basis requirements.

Clarification dated 1 October 2026

The online ticket purchase provider is JEGYx1 Zrt.; details of customer data processing are set out in its own privacy notice published on the ticket purchasing platform. This does not replace the description of data actually received or independently processed by MusicKing Pro Kft.

Google Analytics – settings supplement (1 October 2026)

Google Analytics 4 – consent-based visitor measurement. Legal basis: Article 6(1)(a) GDPR, the visitor's consent. Its purpose is to aggregate website use and clicks leading to the JEGYx1 ticket page. Opening the ticket page does not establish that a purchase took place. Measurement may start only after separate statistical consent; refusal does not prevent use of the website. Consent may be withdrawn using the Privacy settings button in the footer.

After statistical consent, Google may receive technical data (such as browser and device data and the network connection's IP address), a cookie identifier and usage events. Our own event transmission provides the page title, its URL without query parameters or fragments, the referring page's origin and the ticket-page click. It does not transmit names, email addresses, message text or visit planner data. Google's measurement library may also process basic session and activity events.

Under the settings of 1 October 2026, Google Signals, user-provided data collection and enhanced measurement are disabled. The organiser confirmed that ads personalisation is disabled in all regions, that user and event data are retained for 2 months, and that resetting the retention period upon new activity is disabled. The 2-month period is not the cookie lifetime and does not apply to most aggregated reports; because of Google's deletion cycle, it does not mean deletion on an exact day for all data.

Statistical cookies used after consent: _ga (visitor identifier) and _ga_985H70LVH6 (session state). Our own measurement code sets a cookie lifetime of 180 days, without automatic extension on each visit. The browser may restrict this. Our own measurement code does not create these cookies before consent or where consent is refused.

Google's data processing terms were accepted in the account on 1 October 2026; MusicKing Pro Kft. is recorded as the legal entity, together with its primary contact. Google and its subprocessors may process data outside the EEA, including in the United States. Transfers are subject to the safeguards under section 10 of the Google Ads Data Processing Terms and section 7 of Appendix 3A: the applicable adequacy mechanism or, in its absence, standard contractual clauses (SCCs). Terms and safeguards: https://business.safety.google/adsprocessorterms/ ; https://business.safety.google/adsdatatransfers . Meta Pixel starts after separate marketing consent; details are provided in the Meta supplement.

Google sources: https://support.google.com/analytics/answer/7667196?hl=hu ; https://support.google.com/analytics/answer/3379636?hl=hu ; https://policies.google.com/technologies/partner-sites?hl=hu

Meta Pixel – settings supplement (1 October 2026)

Meta Pixel (ID: 1092178340229647) loads only after separate marketing consent. Its purpose is to measure the results of Facebook and Instagram advertising and support reaching previous visitors again. Legal basis: the visitor's consent, Article 6(1)(a) GDPR. Refusal does not prevent use of the website; consent may be withdrawn at any time using the Privacy settings button in the footer.

Our own code sends PageView (page view) and TicketClick (click through to the JEGYx1 ticket page) events. A click is not a purchase; we do not transmit purchase amounts. Meta may also receive technical data such as IP address, browser and device data, page URL and referral data, cookie identifiers and event time. It may combine these with its own data. Our own code does not send names, email addresses, message text or visit planner data; it does not transmit advanced matching data and does not enable automatic event configuration. The website does not use a server-side Conversions API integration.

After consent, Meta may use the _fbp browser identifier cookie and, where there is an appropriate advertising referral, the _fbc click identifier cookie; according to Meta's cookie policy, their lifetime is 90 days. The browser may restrict this. This differs from retention of data sent to Meta's systems: the Business Tools Terms specify a maximum of two years for event data. Withdrawal stops future event transmission by our own code and deletes accessible cookies on our own domain; it does not automatically erase data already sent.

The provider is Meta Platforms Ireland Limited. The Business Tools Terms and Controller Addendum define the responsibilities of MusicKing Pro Kft. and Meta Ireland for collection and transmission falling within joint controllership. Data may be transferred outside the EEA, including to the United States. The safeguards and terms applied to international transfers are described in Meta's privacy policy and European data transfer addendum: https://www.facebook.com/legal/EU_data_transfer_addendum . Meta's privacy policy governs its further processing, international transfers and the exercise of data subject rights. The data subject may contact both the organiser's data protection contact and Meta.

Meta sources and detailed terms: https://www.facebook.com/privacy/policy/ ; https://www.facebook.com/privacy/policies/cookies/ ; https://www.facebook.com/legal/technology_terms ; https://www.facebook.com/legal/controller_addendum .

Consultations required for finalisation

This version contains the retention and operational rules that the organiser can determine. The service provider facts marked with an asterisk have not yet been verified, so the Privacy Notice remains a consultation version until they are resolved.

Setting a retention deadline for the Organiser does not in itself change the external provider’s settings.