Jegyfutár – Privacy Notice for YourDJ’s Own Processing
Document ID: JF-03
Version: v0.15.2 EN
Date: November 6, 2026
Effective: from the date of publication.
1. Who processes the data?
Controller: YourDJ Ügynökség Kft.
Registered office and postal address: 2724 Újlengyel, Petőfi Sándor utca 48., Hungary.
Company registration number: 13-09-237888. Tax number: 32715143-2-13.
Website: https://jegyfutar.hu.
Privacy contact: adatvedelem@jegyfutar.hu.
Customer service: support@jegyfutar.hu.
There is no telephone contact; contact us by email or via the Help form on the website.
YourDJ has not designated a data protection officer because it is not legally required to do so. For privacy questions and to exercise your rights, contact us at adatvedelem@jegyfutar.hu.
This notice covers processing whose purposes YourDJ determines itself. The event’s Organizer is generally the controller for ticket sales, participant lists, admission, refunds and its own marketing. For those activities, YourDJ is a processor following the Organizer’s instructions. The event page and checkout identify the Organizer and its privacy notice.
The same technical system can process data in different roles. YourDJ uses Organizer purchase data for its own purposes only as described in this notice: to show your own orders in your account (3.1), to link guest orders technically (3.2), for security (3.4), for its own customer service (3.5), for aggregate analysis (3.9) and – if you give separate consent – for the interest profile (3.14). When YourDJ organizes an event itself, it also provides separate Organizer privacy information.
2. Principles and legal bases
We process only the data necessary for a specified purpose. We rely on GDPR Article 6(1)(b) only to the extent objectively necessary for the contract with the user or pre-contractual steps requested by them. Another Participant’s data do not automatically obtain that basis simply because the Buyer has a contract.
For legitimate interests under Article 6(1)(f), we balance necessity, less intrusive alternatives and the individual’s rights. We explain the substance of the balancing on request. Consent-based activities use Article 6(1)(a); the choice is voluntary and can be withdrawn. Reading the notice or accepting Terms is not general consent to processing. You do not have to accept this notice: registration, guest-account activation and checkout show a link to it (“Read how we handle your data here.”).
Reliance on a legal obligation under Article 6(1)(c) is linked to the rule identified for the activity concerned. A different purpose or materially new processing is not introduced simply by silently rewriting this notice.
Under-16s: we do not accept marketing consent (newsletters, electronic advertising) or optional cookie consent (statistics, marketing) from anyone under 16. When ticking the marketing-consent box you therefore also declare that you are at least 16; if you are under 16, please reject optional cookies in the cookie banner. You can buy tickets under 16; no such consent is needed for that. If we learn that someone under 16 has given such consent, we treat it as invalid: we stop the related sending and measurement and delete data processed on the basis of that consent.
3. Detailed processing activities
3.1. Platform account and authentication
Purpose: providing an account, sign-in, account protection, access to the user’s own orders, profile settings and permissions.
Data: name, email address, language, account identifier, password hash, authentication and two-factor details, activation and security events, and links to the user’s orders. Full passwords are not stored in readable form. A single-use email sign-in link valid for 15 minutes can be requested; the necessary address, token-verification data, expiry and used/unused status are processed. This differs from the 60-minute account-activation link. Sign-in links work only for accounts with a verified email address (activated accounts). If two-factor authentication is enabled or mandatory (Organizer owner, finance user, box-office manager or platform administrator), a link does not sign the user in: a password and authentication code are required. TOTP is mandatory for those roles; Buyers can voluntarily enable it in Profile, with recovery codes. Used or expired sign-in tokens cannot be accepted again; necessary security events may remain in the log under 3.4.
Legal basis: contract for operations necessary for the account service; legitimate interest under 3.4 for supplementary abuse-prevention logging.
Retention: until account closure or five years of meaningful inactivity. The purpose is to maintain account service for users who return infrequently, for example annually. This is not mandatory five-year retention derived from the Civil Code’s general limitation period. Evidence for legal claims may be retained separately in a narrower dataset.
Service warnings are sent 90, 30 and 7 days before scheduled deletion with sign-in and data-export access; the user can sign in, export data or request earlier deletion. Meaningful activity is an authenticated sign-in or account action initiated by the user. An automatic email, email open, token refresh or background task is not activity by itself. Necessary access for a valid future ticket or outstanding settlement is maintained until resolution, with notice to the individual. This does not extend retention of all old orders. An open customer-service case does not postpone deletion; the case data are handled under section 3.5. Deletion for inactivity is carried out only if the warning sent 7 days before was demonstrably delivered; otherwise the account is kept, and a new automatic cycle starts only after new activity. We send a notice when the deletion has been carried out.
Deletion for inactivity does not apply to an account that has an accepted membership with an Organizer: such an account receives no warning while the membership lasts. After the membership ends, the inactivity period runs under the rule for buyer accounts; the first warning arrives no earlier than 90 days after the membership ended.
Only a person who is at least 16 years old may open a buyer account. Direct registration, guest activation and first-time Google/Apple account creation each require a separate, mandatory checkbox, not preselected: “I am at least 16 years old.” An account cannot be created or activated without this declaration. Guest checkout remains available without an account; purchasing a ticket is not a condition of opening an account, and opening an account is not a condition of purchasing a ticket.
Age-declaration processing: the declaration, its text version, timestamp and account-creation route are used to check and demonstrate the account eligibility condition. The legal basis is verification of a contractual condition of the account service. These data are processed with the account data; after closure, only necessary contractual evidence remains under its separate retention rules. The declaration is not general consent to processing and does not replace the rules governing a minor’s capacity to contract.
3.2. Guest checkout and inactive records
A guest ticket can be received and used without account activation. The inactive identification record created in the background supports technical association of the transaction and subsequent, separately requested account activation. It is not by itself a full account agreement or marketing subscription.
The Organizer’s notice governs order data processed on its behalf. YourDJ’s own minimal technical association is based on its legitimate interest in secure access, supported by documented balancing. An inactive record with neither an order link nor accepted account terms may remain for at most 24 months after creation and is deleted earlier if its purpose ends. For a linked guest order, a never-activated guest record is anonymised by the daily automatic run once 24 months have passed since it was created and no order refers to it any more. This happens once the last linked order has also been anonymised (24 months after the event ended), so the later of the two dates applies.
3.3. Google and Apple sign-in
Users can choose an external account to sign in. A new Google/Apple connection is created only for an email address verified by the provider; subsequent identification of that connection uses the provider’s identifier. Platform administrators cannot use this sign-in method. We receive the necessary provider identifier, email address and basic profile data actually requested; Apple may provide a relay email address. YourDJ does not receive the external account’s password.
Creating and linking the account is based on performance of the requested account service. Google and Apple may act in their own roles for their authentication services, under their own notices. We email the account address when a new connection is added. Connections can be removed in account settings; this does not automatically delete data held by the external provider. Connection data remain while the connection exists; necessary security evidence follows 3.4.
3.4. Security, abuse prevention and troubleshooting
Purpose: preventing, detecting and investigating unauthorized access, mass automated attacks, data-isolation failures and service misuse.
Data: user and session identifiers, event type, timestamp, necessary IP data or truncated IP prefix, device and network signals, relevant system and permission identifiers, error code and necessary technical circumstances. Truncated IP addresses and technical identifiers can remain personal data. Filtering reduces risk; it does not automatically anonymize data.
Legal basis: legitimate interest in protecting the system and users, GDPR Article 6(1)(f). Full orders, complaint text, passwords, tokens and card data do not enter diagnostic logs.
Retention: general security and operational audit logs: at most 12 months from entry; application diagnostics: at most 30 days; MCP operational logs: 90 days. Necessary incident evidence can be isolated; the minimal incident register remains for five years after investigation closure. This does not automatically extend retention of the full log.
The website is protected against attacks and abuse by Cloudflare, which processes visitors’ IP addresses and security cookies for this purpose. The purpose is the protection of the service and its users; the legal basis is the legitimate interest above, GDPR Article 6(1)(f). Cloudflare Turnstile examines technical signals for bot screening. Necessary security and the provider’s own development purposes are distinct processing activities, separated in the recipient annex.
3.5. Own customer service and complaints
Purpose: resolving requests about platform operation and YourDJ’s service.
Data: name, contact information, case identifier, request content and necessary attachments, order reference, responses, status and handling timestamps. Do not send unnecessary identity documents, card details or health data.
Legal basis: performance of YourDJ’s own contract for necessary requests from the contracting user; legitimate interest in resolving other legitimate requests or contact-person matters. Retention of consumer complaint records and responses is a legal obligation under section 17/A of Act CLV of 1997.
Retention: general closed cases: at most 24 months after closure; a case handled as a consumer complaint is kept for three years from closure of the case, which an erasure request does not shorten, and is then anonymised. When you choose the “Complaint” category in the web form, the request is recorded as a complaint immediately and a confirmation email is sent. If you request erasure while a customer-service case of yours is open, we keep the case data (name, email address, subject, messages, attachments) until closure so that we can respond; the first daily automatic run after closure anonymises them. Cases already closed when erasure is requested are anonymised immediately, except cases handled as consumer complaints. Necessary evidence for a specific legal claim may be placed in a separate restricted file.
The Organizer does not automatically see the Buyer’s platform support ticket. Only necessary data are shared when an Organizer matter is forwarded. When correcting an order-system error on the Organizer’s instructions, YourDJ may act as processor for that operation.
Customer service is available at support@jegyfutar.hu. Official email hours are weekdays 08:00–20:00, with on-call cover outside those hours, Europe/Budapest time. The first substantive response is provided within 24 elapsed hours from receipt; a purely automatic receipt does not meet this commitment. This is not every case’s final-resolution deadline: written consumer complaints receive a substantive response within 30 days, and shorter mandatory deadlines and incident procedures apply separately. We do not operate a telephone customer service; you can submit requests and complaints by email (support@jegyfutar.hu) or via the Help form on the website.
AI customer service (Claude, Anthropic Ireland, Limited): artificial intelligence (AI) continuously receives and preprocesses incoming requests through YourDJ’s Claude API. We clearly tell you that you are communicating with AI no later than the first AI reply; you can request human handling at the same email address. AI does not make a final refusal concerning a complaint, refund or data-subject right without human review. The legal basis is the same as for customer-service handling (performance of the contract above or the legitimate interest in resolving the matter); request data are not used for model development. For platform matters, YourDJ is the controller and Anthropic its processor; the system does not itself send Organizer matters to Claude; when YourDJ’s customer service uses Claude in a case handled on an Organizer’s instructions, it does so with human review and uses Anthropic only as a further processor authorized by that Organizer. Despite the Irish contracting entity, data are stored in the US, and the model is executed globally or in the US, according to the provider’s settings, not restricted to the EU; data are therefore transferred outside the EEA. Details and the transfer safeguards are in section 5 (Annex C1) and section 6. We transmit only the text, identifiers and justified attachments needed to resolve the particular case; we do not automatically submit an entire case history or sensitive content.
3.6. Organizer contacts, contracts and YourDJ invoicing
Purpose: preparing Organizer services, contracting, permission and fee management, invoicing YourDJ’s commission and settlement.
Data: names, contact details and roles of natural-person Organizers, representatives and contacts; necessary organizational, tax and billing data; acceptances, service and settlement references.
Legal basis: contract for a natural-person contracting party; legitimate interest in business communications and verifying representation for an organization’s representatives and staff; legal obligation under section 169 of Act C of 2000 on Accounting for YourDJ’s accounting records.
Retention: contacts for the relationship and necessary subsequent settlement; former contacts’ access is closed promptly. YourDJ’s accounting records remain for at least eight years under statutory retention rules. Contract evidence: evidence of acceptance (document type, text version, language, time, source, encrypted IP address, keyed hash of the account and email address) is kept in a separate, non-modifiable register, also after data-subject erasure. Acceptance of the Organizer’s data-processing agreement is additionally kept in the audit log for 5 years. Contractual order data (order number, items, amounts, snapshot of the Organizer’s legal data) remain with the order; the buyer’s personal data are deleted 24 months after the event. Necessary evidence of DPA acceptance and Organizer instructions remains during validity and for five years after expiry. This does not mean keeping entire participant lists or AI conversations.
Invoicing to the Buyer: the Buyer pays the ticket price and the service fee through the Organizer’s own payment provider, and the Organizer issues the invoice. YourDJ invoices the Organizer for its commission, including the platform’s share of the resale fee, which appears in the monthly commission statement.
Weekly summary email: an Organizer user can request a weekly summary email about the Visitors report; the email is off by default and can be cancelled with one click.
3.7. YourDJ marketing
YourDJ sends electronic advertising to natural-person recipients about its events, offers and services only with separate, voluntary consent. Data include email address, name and language where necessary, selected communication scope, and evidence of consent and withdrawal: time, source, wording version, the IP address recorded in encrypted form at the time of the choice and a keyed hash of the email address. When ticking the marketing-consent box you also declare that you are at least 16 (section 2).
Consent to the Organizer is not consent to YourDJ, or vice versa. Purchasing, activating an account or reading a notice is not itself subscription. In YourDJ’s targeted emails we use your interest profile (3.14) only if you have consented both to profiling and to marketing messages.
Consent can be withdrawn through the unsubscribe link included in every marketing email, which works without expiry and without signing in, in the account or at adatvedelem@jegyfutar.hu, including by guests without activation. Withdrawal stops future sends without affecting prior lawfulness. The system checks current suppression before sending, not merely the earlier checkout choice.
We process your data on the mailing list until you withdraw consent or the purpose ends. Afterwards, we keep only necessary consent evidence and suppression data, separately: evidence of consent and withdrawal (type, time of grant and withdrawal, text version, language, source, encrypted IP address, keyed hash of the email address) is kept in a separate register. Records are never overwritten or deleted; a withdrawal is recorded as a new record, and on data-subject erasure the record is kept and closed by an erasure record. It is not used for marketing. A keyed email hash and encrypted IP remain personal data. Subscription is created by ticking the checkbox, without a separate email confirmation. We record the time of consent, the text version, the language, the source and the encrypted IP address. An unticked box does not withdraw an earlier subscription; withdrawal is possible any time in the account.
Newsletters are sent through the Resend (Plus Five Five, Inc.) email service from an EU (Irish) sending region; the provider’s details are in section 5 (Annex C1). We do not import address lists from other sources, so no mail is sent to imported lists. Marketing consent can only be given at checkout, on registration, on guest-account activation or on first social sign-in, with a separate checkbox.
3.8. Cookies and YourDJ web measurement
Storage necessary for sessions, security and requested functions is separated from optional statistics and marketing measurement. The latter require appropriate prior consent, withdrawable in cookie settings. You cannot consent to optional cookies if you are under 16 (section 2).
Depending on choice and actual configuration, YourDJ’s tags may process browser/device details, IP address, online identifiers, pages visited, events, timestamps, order values and items, UTM and campaign data. Marketing conversions may also transmit hashed email, telephone or external identifiers if covered by prior information and lawful consent. Hashing does not anonymize them.
For the Meta and Google (Google Analytics, Google Ads) tags, YourDJ and the relevant provider are joint controllers (GDPR Article 26) for collection and transmission to the provider; the provider is solely responsible for its own use of the transmitted data. The essence of the joint arrangement is set out in section 7 of the Cookie and Tracking Notice.
Conversion matching data (IP, browser data, click and cookie identifiers) remain for at most 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. We check current consent before sending; after withdrawal, queued events are not transmitted either, and no new events are recorded. Event series recorded before withdrawal contain only a keyed (HMAC) hash of the session, no IP address or browser identifier; they are also deleted by the 30-day cleanup above, while the aggregates remain. Measurement active on YourDJ’s own pages: Google Analytics 4, Google Tag Manager, Google Ads and Meta pixel, based on consent, as set out in the Cookie and Tracking Notice. Categories: Google Analytics 4 – statistics; Google Ads, Meta – marketing; Google Tag Manager – statistics and marketing together (loads only with both consents). The external providers’ own retention: Google Analytics 4: per the GA4 property's data retention setting (2 or 14 months; YourDJ's setting: 14 months). Meta and Google Ads: per the providers' own terms; they publish no fixed retention period. Visitor statistics on Organizer pages are described in section 8 of the Cookie and Tracking Notice. The Cookie and Tracking Notice details cookie names, expiry, categories and recipients.
3.8/A. UTM campaign source and legitimate interest
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.
3.9. YourDJ aggregate analysis and product development
Purpose: sales aggregation by event type and period, checkout failure rates, capacity and traffic planning, fees and commissions, and feature-use analysis. Tracking individuals across Organizers or training AI models on buyer data is not a purpose. The interest profile (3.14) is separate processing based on separate consent.
We primarily use aggregate data. Names, emails, addresses, complaint text, global email hashes and person-level cross-Organizer links are excluded from the analysis file. Rare events, small groups and precise timestamps are protected against re-identification.
Legal basis: legitimate interest in reliable service development, GDPR Article 6(1)(f), with documented balancing. The stage of producing the analysis that involves personal data is YourDJ’s own processing; it is not made lawful by the Data Processing Agreement concluded with the Organizer. This legal basis does not override consent-based measurement or bypass withdrawal.
Retention periods are set out in sections 3.8 and 7.1. Results that cannot be re-identified using reasonably available means are no longer personal data. The order of the event list does not depend on a personal profile; personalised recommendations are shown, separately from the list, only with separate consent under section 3.14.
General event measurement in YourDJ analytics requires statistical consent; marketing consent alone does not start it. Limited server-side UTM processing under 3.8/A is based on legitimate interest, with the limits and shorter retention described there. This does not expand other measurement or marketing events processable without consent.
3.10. YourDJ AI quick search and planning room
User-requested AI quick search transmits the entered text for processing. The planning room may send collaborative planning messages and context consisting of at most the last 30 messages to the Anthropic API. Please do not enter unnecessary personal data; pseudonymization is not anonymization.
The AI summary of the Organizer’s Visitors report sends only the report’s aggregate figures (visit and view counts, funnel, sources, device types, distribution by hour of day) to the Anthropic API to write an observation of at most three sentences for the Organizer. It sends no personal data and no buyer or visitor identifiers.
Legal basis: contract for operations you request that are objectively necessary for your service agreement, GDPR Article 6(1)(b). Data of other persons invited to the planning room (members, invitees), of persons named in messages and attachments are processed at the inviting user’s request on the basis of the legitimate interest in conducting the joint planning, GDPR Article 6(1)(f), for no more than 30 days (see Retention). Invitees receive information about this notice on the planning room’s join page. Data processed on Organizer instructions are governed by the Jegyfutár Data Processing Agreement and the Organizer’s privacy notice.
Recipient and transfer: the stated contracting entity for EEA customers is Anthropic Ireland, Limited. The service stores data in the US and executes the model globally or in the US, according to the provider’s settings, not restricted to the EU; data are therefore transferred outside the EEA. The actual model, endpoint and data route are shown in the Anthropic API row of Annex C1.1. SCCs and necessary transfer assessment apply under section 6; the Irish entity does not make all processing EEA-based.
Retention: the platform does not store quick-search text as search history; this does not mean the provider stores nothing. Planning-room local storage lasts 30 days after the last selected event or, without an event, 30 days after last activity. The function, contract, legal obligations and security investigations may create exceptions to the API’s general 30-day deletion policy; C1 records exceptions for the permitted route.
The function must not be used to submit unnecessary health, criminal-offence or other special-category data, authentication secrets or full customer lists. Buyer data are not transmitted for model training. The separate Organizer MCP connection is not YourDJ’s own Anthropic subscription; the two routes differ.
3.11. Data-subject requests and legal claims
We process identity and contact details, request content, decisions and minimal completion evidence to handle requests. The legal basis is a GDPR legal obligation; evidence necessary for a specific legal claim uses legitimate interest in legal protection.
Retention: the record of the data-subject request (type, status, requesting account, request and completion time, keyed hash of the email address) is kept after completion as evidence; it contains no content and no copy of the export. The export package is deleted on download, at the latest after 7 days; the related audit-log entry is kept for 12 months. For a specific claim, the necessary period reflecting applicable limitation, suspension, interruption and proceedings. Not all data are automatically retained for five years. Exceptions for ongoing cases are reviewed at least every 90 days. Where erasure is requested, the data of an open customer-service case are kept until closure under section 3.5.
3.12. Account-linked resale waiting list
Joining a resale waiting list requires sign-in. Ticket type and maximum price are optional event filters; without them the request covers any ticket type and any price permitted in resale. A new email is sent for each new listing matching the current settings until unsubscribe; the subscription is deleted on the 30th day after the event/performance ends. This is not a reservation or purchase priority. The ticket goes to the Buyer whose purchase first completes successfully under reservation and payment conditions. Unsubscribe is available on the event’s resale page in the signed-in account and through the unsubscribe link in the notification email. The Organizer cannot see the waiting list. The request is not general newsletter subscription.
Data: account identifier (email comes from the account), event, optional ticket type and maximum price, subscription/termination status and notification timestamps. Empty filters mean “any ticket type” or “any price”, not missing mandatory data. Purpose and legal basis: providing the user-requested, account-linked availability notification under Article 6(1)(b); not a newsletter or profiling recommendation. The Official Ticket Resale Terms and the Buyer Account Terms define the requested service. The Organizer receives no waiting-list access.
Retention: until the 30th day after the event/performance ends, when the subscription is deleted automatically. For a postponed event, the subscription is kept until a new date is set; with a new date, it is deleted on the 30th day after the new end time. For a cancelled event, the deletion period runs from the event’s last recorded end time (or start time, if there is no end time); the subscription is deleted automatically 30 days after that. On unsubscribing, notifications stop immediately, the subscription is deleted immediately, and no evidence of the unsubscription is kept.
Recipients: YourDJ’s necessary hosting and transactional-email providers under C1; the Organizer is not a recipient of the named waiting list.
YourDJ is the independent controller of this platform-operated, account-linked notification service. Organizer ticket sales and resale are separate processing.
3.13. Connecting your own AI assistant to your account
You can connect your own AI assistant (for example Claude or ChatGPT) to your account, with permission given on our approval screen (OAuth). The assistant can read the data listed on the approval screen: it can search events and see your own orders, tickets, resale listings and waiting lists, and the link to your planning rooms. It cannot be used to buy, pay, transfer a ticket or list one for resale; for these it gives a link to the website.
Purpose: providing the access you request to your own account data. Data: only your own account data within the scope above, and the details of setting up and ending the connection. Legal basis: performance of the service you request, GDPR Article 6(1)(b).
Recipient: the AI provider you choose, which processes the data passed to it under its own terms as an independent controller; its processing is described in the provider’s own notice.
Retention: the connection lasts until you end it. We log the assistant’s calls and keep the log for 90 days. You can end the connection at any time on the “AI connections” page of your account; this does not automatically delete data already held by the provider.
3.14. Interest profile
Purpose: personalised event recommendations and – if you have also consented to marketing messages – YourDJ’s own targeted emails.
Data: the main category and subcategory, from a closed two-level category list, of the events of your own paid orders and checked-in tickets, with a weight per category and the time of the last related event. Events older than 24 months are not counted. The category list contains no category indicating special-category data.
Legal basis: separate consent, GDPR Article 6(1)(a). You can give consent on the “My interests” page of your account or on the thank-you page after a purchase, with a separate checkbox that is unticked by default. Without consent no profile is created; consent is not a condition of purchase.
Display: the order of the event list does not depend on a personal profile. Personalised recommendations appear marked “Recommended for you”, separately from the list. In YourDJ’s targeted emails the profile is used only if you have also consented to marketing messages (3.7).
Access: the Organizer cannot see your profile. An Organizer can filter its own buyers by category only from its own orders; that is the Organizer’s processing.
Retention and your rights: the profile is kept until you withdraw consent; on withdrawal it is deleted immediately. You can view the profile in your account, delete it item by item or entirely, and you also receive it in your data export.
3.15. Pre-sale notification when ticket sales open for an event
On an event page, before ticket sales open, you can sign up to be told when sales start. If the event has a pre-sale, you also receive a pre-sale link when it opens, which lets you buy before public sales. No account is needed.
Purpose: confirming the sign-up, notifying you when ticket sales or the pre-sale open, sending the pre-sale link, and at most three reminders: 24 hours before opening, at opening, and 2 hours before the pre-sale closes. This is not marketing: we do not write to this address about other events or offers. If you also tick the newsletter box when signing up, section 3.7 applies to that.
Legal basis: your consent (GDPR Art. 6(1)(a)). You complete the sign-up with the link in the confirmation e-mail. You can withdraw consent at any time with the unsubscribe link in the e-mails; after that we send no further notifications.
Data: name, e-mail address, language, the event, the time of confirmation and of each notification, the time of unsubscribing, and proof of consent (which text you agreed to and when).
Who controls the data: the event's organiser. If the organiser is YourDJ, YourDJ acts as an independent controller under this section. If you sign up for another organiser's event, that organiser is the controller; YourDJ stores the data and sends the e-mails on the organiser's behalf as a processor, and the organiser can see subscribers' names and e-mail addresses in its own interface.
Retention: until the 30th day after the event (performance) ends; the sign-up is then deleted automatically. For a postponed event, the sign-up is kept until a new date is set.
Recipients: YourDJ's hosting and transactional e-mail providers needed for this purpose, as listed in C1; for another organiser's event, the organiser.
4. Sources of data and required information
Data come directly from users, their chosen sign-in provider, system actions, Organizer contacts or representatives acting in a case. We do not collect unrestricted background information about third parties named by an Organizer.
Mandatory fields are limited to what the requested function or a legal obligation requires. Accounts and electronic delivery cannot be provided without an email address. Rejecting marketing or optional measurement does not prevent purchase. For data obtained from someone else, unless an applicable exception applies, information is provided within the period in GDPR Article 14: no later than one month, or at first communication or disclosure, as applicable.
5. Access and recipients – Annex C1
Annex C1: v0.15; date: November 2, 2026. This annex forms part of the notice. Providers used on the Organizer’s behalf are listed in the provider annex of the Jegyfutár Data Processing Agreement; the Organizer’s own recipients are listed in the Organizer’s privacy notice.
| Provider | Task, data and role for YourDJ’s own purposes | Location, safeguards and retention |
|---|---|---|
| Tárhely.Eu Szolgáltató Kft., 1144 Budapest, Ormánság u. 4. X. em. 241.; gdpr@tarhely.eu | VPS/database; account, support and operational data hosted there; processor | Hungarian data center. VPS: Tárhely.Eu KVM Force VPS (vps1.jegyfutar.hu), Ubuntu 24.04, running in Docker containers: application, PostgreSQL database, Redis, scheduler and queue worker; the test and production environments run on the same machine in separate directories and databases. Remote access: SSH with a key-based deploy user; the test environment is deployed automatically from GitHub Actions. Backups: daily, age-encrypted to Cloudflare R2 (daily 30, monthly 90 days). Physical location, provider access countries and chain: Tárhely.Eu Szolgáltató Kft. (H-1144 Budapest, Ormánság utca 4, 10th floor 241; company reg. no. 01-09-909968; tax no. 14571332-2-42). The VPS runs in Budapest, Hungary; the provider's data centres are at Váci út 188, Victor Hugo u. 18–20 and Asztalos Sándor út 13, Budapest. The VPS IP address is in the Tárhely.Eu network (AS43359); the address block is registered to Freemium Kft. Further processors may be engaged only under a general authorisation with prior written notice (Terms 3.7, 5-day objection right). The provider's terms contain no provision on access from outside the EEA. The VPS is held in the customer account of Globaldogshop International Kft.; Globaldogshop International Kft. is a member (owner) of YourDJ Ügynökség Kft. Hungarian storage alone does not prove EEA-only access. |
| Cloudflare, Inc., 101 Townsend St., San Francisco, CA 94107, USA; dpo@cloudflare.com | CDN/proxy, DNS, R2, Turnstile, Email Routing, Access and Workers; traffic, objects, technical signals and messages depending on product; generally processor | EU-jurisdiction R2 objects in the EU; other routes may be global. DPF for transfers within certification scope; appropriate SCCs where needed. Products used: DNS and proxy/CDN (all requests; Cloudflare protects the site and processes IP addresses and security cookies for this purpose); R2 (media, data-subject exports, backups, map tiles); Turnstile (3 forms); Email Routing and a Worker (email to support@); Access (admin interface); Stream (Organizers’ own videos). Product-specific periods/countries: DNS and proxy/CDN: Cloudflare global network; no request log export (Logpush). R2: EU-jurisdiction buckets (*.eu.r2.cloudflarestorage.com); deletion per lifecycle rule (daily backups 30 days, monthly 90 days). Turnstile: global; Cloudflare publishes no specific retention period. Email Routing and Worker: global edge, no storage. Access: access logs 24 hours (Free) / 30 days (Standard) / 180 days (Enterprise); only the Data Localization Suite restricts location, which we do not use. Stream: Cloudflare global network, no EU-only restriction. |
| Cloudflare’s own Turnstile purpose | Development of bot detection for its own purposes; independent controller under its notice | Cloudflare’s own-purpose processing, separate from the necessary bot protection carried out for YourDJ. Its legal basis and device access: Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) acts as an independent controller of Turnstile signals (IP address, TLS fingerprint, browser user agent, site key and associated origin) to improve Turnstile's bot detection. Legal basis (EU/UK): Cloudflare's legitimate interests. The notice describes the signals as strictly necessary for bot detection and refers to Cloudflare's Cookie Policy for device storage. |
| Plus Five Five, Inc. (Resend), 2261 Market St #5039, San Francisco, CA 94114, USA; privacy@resend.com | Transactional emails and YourDJ newsletters: recipient, content, link, attachment and delivery log; processor | Sending from an Irish (EU) region; email content, logs and webhooks are stored in the US. DPF/SCC for the route used. Plan: Resend Pro; delivery via the Resend API, with the sending domain authenticated in Cloudflare DNS. In our own mail log the recipient appears only as a keyed hash, which is blanked after 24 months. Content, log and webhook retention at Resend: Resend, Inc. (USA): data retention for stored email data (content, logs, webhook events) is 30 days on the Free, Pro and Scale plans; account data is kept until the account is closed. |
| Functional Software, Inc. d/b/a Sentry, 45 Fremont St., 8th Floor, San Francisco, CA 94105, USA; compliance@sentry.io | Filtered technical error data, as processor where personal data remain | EU-region event storage (Frankfurt, Germany); account and support data also in the US. DPF/SCC. The application starts only with an EU-region (*.de.sentry.io) endpoint. Before sending, request bodies, cookies, query parameters and token-like URL segments are removed; users appear only as a keyed pseudonymous ID, and no IP address or email is sent; performance tracing and profiling are off. Our own diagnostic log is kept for 30 days. Account/support data route and retention at Sentry: the Sentry organisation (yourdj-ugynokseg-kft) uses the EU data storage region (Frankfurt, ingest.de.sentry.io); error events and their backups are stored in Frankfurt, while user accounts, organisation settings, access tokens, detailed usage data and data shared with support are stored in the US. Plan: free Developer plan, error monitoring only; sending of personal data is disabled (send_default_pii = false). Sentry retains error events for 30 days on the Developer plan (C1.1). |
| Anthropic Ireland, Limited, South Bank House, 6th Floor, Barrow St., Dublin 4, D04 TR29, Ireland; dpo@anthropic.com | Necessary text, context, response and technical data for requested AI features and Claude support; YourDJ’s processor for its own customer service; further processor authorized by the Organizer for case handling on the Organizer’s instructions | US storage (workspace region: US), model execution in the EU; actual chain and SCCs. No presumed DPF certification. Actual model and endpoint: the Anthropic API row of Annex C1.1. |
| KBOSS.hu Kereskedelmi és Szolgáltató Kft., 1031 Budapest, Záhony u. 7.; dpo@kboss.hu | YourDJ invoicing, partner billing details and items; processor | Számlázz.hu, AWS Frankfurt. Additional functions and chain: Processors of KBOSS.hu Kft. (H-1031 Budapest, Záhony utca 7; reg. no. 01-09-303201; tax no. 13421739-2-41): Amazon Web Services EMEA SARL (Luxembourg; AWS Frankfurt region – hosting and AI assistant), Hibridlevél Kft. (printing, enveloping and posting invoices), Visma Software International AS (Norway; invoice-image OCR), HubSpot Ireland Ltd. (newsletters, complaints, support tickets), Userflow Inc. and Joincube, Inc. (Beamer) (USA; in-app messaging), Nevogate Payment Services Kft. (IT support for electronic payments), CookieFirst (Digital Data Solutions B.V., Netherlands; cookie consent), Orca Security Ltd. (cloud security monitoring, Frankfurt), GIRO Zrt. (payment requests), Riport Applications Kft. (Riport Quick cost tracking). The provider keeps an up-to-date record of subcontractors and processing locations; its infrastructure operates in the EU/EEA. Before deletion three months after service termination, YourDJ secures its mandatory accounting archive in its own storage. |
| Google/Apple sign-in; Google Places | Selected authentication data; Organizer search text and necessary technical details for Places | Google sign-in: OpenID Connect, scope openid email profile; Google provides the chosen account’s identifier, email address and name. Apple sign-in: identifier, email address (may be a relay address) and name. Google Places (venue autocomplete, organiser interface only): the server sends the Organizer’s search text, the language, the region and a session token to Google; the browser does not connect to Google and no buyer data is passed. Legal entity, country, safeguards and retention: Google: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland). Processing may also take place in Google's global systems, including the USA; safeguard: Google LLC is certified under the EU–US Data Privacy Framework, plus Standard Contractual Clauses. Retention per Google's terms; for Places searches the session token lives until the search ends; Apple: Apple Distribution International Limited (Hollyhill Industrial Estate, Hollyhill, Cork, Ireland) – Sign in with Apple; Apple Inc. (USA) may also process the data; safeguards: EU–US Data Privacy Framework and Standard Contractual Clauses; retention per Apple's terms. YourDJ passwords are not shared. |
| Meta, Google Analytics / Google Tag Manager, Google Ads | Measurement used only on YourDJ pages and enabled by consent. YourDJ and the provider are joint controllers (GDPR Article 26) for collection and transmission; the provider is an independent controller for its own use of the transmitted data. Essence of the joint arrangement: Cookie and Tracking Notice, section 7. | Active measurement tags: Google Analytics 4, Google Tag Manager, Google Ads, Meta pixel (based on consent, as set out in the Cookie and Tracking Notice). Local retention: raw event records 30 days, aggregates 25 months, matching data 7 days. Provider retention: Google Analytics 4: per the GA4 property's data retention setting (2 or 14 months; YourDJ's setting: 14 months). Meta and Google Ads: per the providers' own terms; they publish no fixed retention period. |
| YouTube, Vimeo | No external video is embedded on YourDJ’s own pages (home page, event and organiser lists, search). YouTube and Vimeo videos appear only on an Organizer’s event or organiser page, as chosen by the Organizer, after separate permission for the video | Described in the Organizer’s privacy notice and in section 9 of the Cookie and Tracking Notice. |
| Accountant and external operator where they have access | Own invoices, administration and necessary operational data | Legal entity, role, country, contract and retention: Accounting: Acounto Magyarország Kft., 7630 Pécs, Koksz utca 13; tel. +36 72 884 096; hello@acounto.com; https://acounto.com/ – role: processor (accounting), country: Hungary. External operator: none. |
| Google (Google Wallet) | Only if you save your ticket with the “Add to Google Wallet” button: the ticket data (the Organizer's name, the event name and start time, the venue name and address, the ticket QR code and code, the order number and, where applicable, the ticket type, the name on the ticket and the seat) go to Google and are stored in your Google account. An Apple Wallet ticket is downloaded to your device as a file. The QR code of a saved ticket is the same as that of the PDF ticket. | In Google Wallet, the ticket issuer is YourDJ Ügynökség Kft. (Google Pay & Wallet Console); the ticket is added to your Google account through the Google Wallet API when you choose the “Add to Google Wallet” button. Legal entity: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland); processing may take place in Google’s global systems, including the USA; safeguards: Google LLC is certified under the EU–US Data Privacy Framework, together with standard contractual clauses. Retention: the ticket stays in your Google account until you delete it there; otherwise under Google’s terms. |
| The AI provider you choose (3.13) | Your own account data read by the AI assistant connected to your account, within the scope listed on the approval screen; the provider is an independent controller under its own terms | Under the provider’s own notice. |
Better Stack uptime monitoring only checks service availability; it receives no personal identifier in requests, addresses, headers or logs.
Exceptions to Anthropic’s standard API 30-day deletion can include legal retention, a different feature or contract; content flagged for policy violations may remain up to two years, security classifications seven years and data linked to specific feedback five years. Applicable model terms are in the Anthropic API row of Annex C1.1. Deletion within 30 days is therefore not unconditional. We do not send feedback or persistently stored files to Anthropic without justification.
Staff access only what their duties require and are bound by confidentiality. Necessary data are disclosed to authorities, courts or legal representatives only on an appropriate basis. We do not sell personal data.
Additional C1 record – backup Zoho Mail SMTP: Zoho Corporation B.V., Beneluxlaan 4B, 3527 HT Utrecht, Netherlands; privacy@zohocorp.com. The backup route sends transactional emails only (tickets, confirmations, sign-in links, customer-service replies and resale), through the EU endpoint smtppro.zoho.eu, with a daily limit. It is neither a newsletter module nor an AI provider. The fallback is used only if Resend is temporarily unavailable (throttling, server error, network error), not on a permanent rejection. Daily limit: at most 300 emails in the last 24 hours, adjustable within the Zoho plan. Mail over the limit stays queued and is retried: for 6 hours from the first attempt, and for 45 minutes for sign-in, activation, password-reset and order-lookup links, after which it fails (a new link can be requested). On switching over and when the limit is reached, at most one alert per hour goes to the operator. Each email is sent once, via one provider. The sending route prevents incorrect and duplicate delivery. Data: recipient email, necessary name, subject, content, attachment, secure link, delivery and technical logs. We use an EU data center and smtppro.zoho.eu. Zoho Mail EU account with two mailboxes: noreply@jegyfutar.hu is used only for the transactional SMTP fallback (smtppro.zoho.eu:465, SSL); support@jegyfutar.hu forwards incoming support email to ticket.jegyfutar.hu. Provider storage, retention, subprocessors and access countries: Contracting party (EEA customers): Zoho Corporation B.V. (Beneluxlaan 4B, 3527 HT Utrecht, the Netherlands; governing law: Dutch, courts: Utrecht) – Zoho Mail EU (zoho.eu). Zoho Corporation B.V. operates the EU data centres (Amsterdam, Dublin); service data of customers on the EU data centre is stored in the EU and is not physically transferred out of the EU. For technical support, Zoho group staff in India (Zoho Corporation Pvt. Ltd., Chengalpattu, India) may access it remotely under Standard Contractual Clauses. Sub-processor list: https://www.zoho.com/privacy/sub-processors.html. EU storage does not exclude third-country support or subprocessor access; Zoho’s public group list also names an Indian subprocessor. For YourDJ account, waiting-list and platform-support transactional emails, Zoho is YourDJ’s processor. Enabling backup does not mean sending every email simultaneously through both providers.
Users decide separately, by controller, on statistical and marketing purposes for YourDJ and the named Organizer. Choices are applied separately under the Cookie and Tracking Notice.
C1.1. Product-specific data routes and retention
This table sets out, in one place, the data routes and retention of Jegyfutár’s infrastructure providers; the Organizer’s privacy notice and the Cookie and Tracking Notice refer to it. The table distinguishes each product's data route and retention. EU sending, EU hosting and exclusively EU access are different. The contracting entity, region and settings for the actual account are as specified in the indicated fields. For international transfers, the DPF applies only to the entity and data route covered by certification; SCCs apply in the module appropriate to the actual role. A provider contract does not replace the purpose and legal basis for processing.
| Provider / product | Data route and retention | DPA, chain and transfer safeguard |
|---|---|---|
| Zoho Mail EU – support mailbox and transactional SMTP backup | EU centers: Netherlands and Ireland; smtppro.zoho.eu. Actual account: Zoho Mail EU with two mailboxes (noreply@ – SMTP fallback; support@ – receives incoming support email and forwards it to ticket.jegyfutar.hu, so these emails are also stored in the Zoho mailbox); access countries and storage: Contracting party (EEA customers): Zoho Corporation B.V. (Beneluxlaan 4B, 3527 HT Utrecht, the Netherlands; governing law: Dutch, courts: Utrecht) – Zoho Mail EU (zoho.eu). Zoho Corporation B.V. operates the EU data centres (Amsterdam, Dublin); service data of customers on the EU data centre is stored in the EU and is not physically transferred out of the EU. For technical support, Zoho group staff in India (Zoho Corporation Pvt. Ltd., Chengalpattu, India) may access it remotely under Standard Contractual Clauses. Sub-processor list: https://www.zoho.com/privacy/sub-processors.html. SMTP logs, sent folder, trash and backups: Deleted messages stay in Trash for the mailbox's junk clean-up interval (5–180 days), then for a further 30 days on Zoho's servers, after which they are permanently deleted. A deleted user account's data can be recovered for 30 days; when the organisation is deleted, all data is permanently deleted after 30 days. After termination, Zoho deletes data from the active database at the next clean-up (every six months) and from backups 3 months later. Tickets, confirmations, sign-in links, customer-service replies and resale only; daily allowance, without duplicate sending. |
Data centers, DPA access, subprocessors, group list. Safeguard: service data are stored in the EU data centre; for third-country (Indian) support access, the European Commission’s Standard Contractual Clauses (SCCs) apply under Zoho’s Data Processing Addendum (DPA); EU storage can still involve third-country access. |
| Resend | Transactional emails and newsletters. Sending takes place from the Irish (eu-west-1) region, which does not mean EU storage: content, logs, webhooks and account data are stored in the US. Plan: Resend Pro, sending region: EU (Ireland, eu-west-1). In our own mail log the recipient appears only as a keyed hash, which is blanked after 24 months. Retention at Resend: Resend, Inc. (USA): data retention for stored email data (content, logs, webhook events) is 30 days on the Free, Pro and Scale plans; account data is kept until the account is closed. On the general (Free, Pro, Scale) plans, content and log retention is 30 days; after termination, residual data remain for up to 90 days and backups for 7 days; custom-plan differences appear in the account record. | Retention, DPA, chain. SCCs with the module appropriate to the role (II or III); DPF only where its scope is verified. |
| Cloudflare R2 | Applies to objects in the EU-jurisdiction storage bucket; a location hint is not the same safeguard. R2 buckets: media library (images, invoice PDFs), data-subject exports (private, encrypted), database backups (age-encrypted), map tiles (public map data). Deletion: when a media item is deleted, the object with all size variants; a data-subject export on download, at the latest after 7 days; an organiser exit export after 30 days; daily backups after 30 and monthly backups after 90 days under the bucket lifecycle rule. Deletion of versions, cache and residual copies on Cloudflare’s side: Deleting an object in R2 is permanent and irreversible. The buckets are EU-jurisdiction, with no bucket lock configured. Cloudflare publishes no period for internal replicas after deletion. Account/support and other products have separate routes. | R2 location, Cloudflare DPA, SCC, chain. |
| Cloudflare Access | Authentication and access logs; region: not location-restricted: Cloudflare stores the logs in its own systems (by default in the USA); we do not use the Data Localization Suite; only YourDJ’s administrator appears in these logs (no buyers or Organizers). Access protects the platform admin interface and the test environment; only YourDJ’s designated administrator email address can sign in, with a one-time code and a 24-hour session. We do not use log export (Logpush). Cloudflare retains access logs according to the Zero Trust plan: 24 hours on the Free plan, 30 days on the Standard plan (180 days on Enterprise); after that, log entries are no longer available. R2 EU settings do not automatically restrict these. | Logs; Cloudflare DPA/SCC and chain at the R2 row's links. |
| Cloudflare Turnstile | Device and network signals for bot protection; not an exclusively EU route. Jegyfutár uses the Turnstile token once, in the server-side check, together with the visitor’s IP address, and neither stores nor logs the token or the IP address. Retention on Cloudflare’s side: Cloudflare's Turnstile notice states no specific retention period; signals processed for its own purposes are retained under its general privacy policy. Necessary verification and Cloudflare's own development purpose involve separate roles; the independent purpose is not an Organizer's processing instruction. | Turnstile notice; common Cloudflare DPA/chain for processor operations. Details of own purpose: Cloudflare, Inc. (101 Townsend Street, San Francisco, CA 94107, USA) acts as an independent controller of Turnstile signals (IP address, TLS fingerprint, browser user agent, site key and associated origin) to improve Turnstile's bot detection. Legal basis (EU/UK): Cloudflare's legitimate interests. The notice describes the signals as strictly necessary for bot detection and refers to Cloudflare's Cookie Policy for device storage. |
| Cloudflare Workers | Request execution, outgoing recipients and bound storage by product. General Workers log retention is 3 days on the free plan and 7 days on paid plans; exports and bound storage separately. One Worker runs (jegyfutar-support-mail): it forwards support email received from Email Routing, up to 15 MiB and HMAC-signed, into the Jegyfutár system. It stores no data, has no bound storage, and Workers logging is not enabled. Execution location: Cloudflare’s global edge, in the data centre receiving the message; Smart Placement is not enabled. As Workers logging is not enabled, the plan-specific log retention (Workers Free: 3 days, Workers Paid: 7 days) does not apply to this Worker. |
Workers Logs; common Cloudflare DPA/SCC and chain. |
| Cloudflare Stream | Video, transcoded copies, playback IP and metadata. R2 EU settings do not prove Stream EU storage. Only the Organizer’s own uploaded videos: the upload goes from the browser directly to Stream, and Jegyfutár stores only the video identifier. The preview image loads when the page is opened, from a signed URL valid for at most 6 hours; the player loads on click, via a signed URL. Deletion: when the Organizer deletes the video, on data-subject erasure and when the organiser account ends, also from Stream; uploads left incomplete for over 24 hours are removed by an hourly clean-up. Storage and access countries: 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. | Common Cloudflare DPA and chain; requested playback and optional measurement are separate. |
| Sentry | EU-region event storage (Frankfurt, Germany); account and support data route: Functional Software, Inc. (Sentry, USA); organisation: yourdj-ugynokseg-kft, data storage region: EU (Frankfurt, ingest.de.sentry.io). Error events, releases, logs and their backups are stored in Frankfurt; user accounts, notification settings, 2FA authenticators, organisation settings, teams, access tokens, detailed usage data and data shared with support stay in the US. Plan: free Developer plan; error monitoring only (no performance tracing, profiling or session replay); we send no personal data (send_default_pii = false). YourDJ's personal diagnostic data: up to 30 days; provider retention and deletion: under Sentry’s public data retention table, error events and logs are kept for 30 days on the Developer plan; the retention period is fixed at ingestion according to the plan then in effect (Team and Business plans: 90 days for error events). After the retention period the data can no longer be accessed; deletion and backups are governed by Sentry’s Data Processing Addendum (DPA) and security policy. |
EU option, retention, DPA, chain. SCCs or verified DPF scope; the plan's default period does not extend the committed 30 days. |
| Tárhely.Eu | Budapest infrastructure; actual VPS, backups and remote access: the Tárhely.Eu row of Annex C1. We store no backups of our own at Tárhely.Eu: database backups are kept encrypted on Cloudflare R2. Deletion of VPS data and any provider-side backups on termination: On termination, Tárhely.Eu deletes or returns all personal data at the Subscriber's choice, deletes existing copies (unless EU or Member State law requires storage), and records the deletion in a ticket handed to the Subscriber (Terms 12.6, 5.14). For VPS, the provider only makes free system snapshot images (Terms 7.1.10); deletion covers these too. | Processing provisions in the Terms. Full chain used: The provider does not publish a list of further processors for the VPS service; it gives prior written notice of changes (Terms 3.7). Its own customer-management processors: https://tarhely.eu/dokumentumok/adatvedelmi_szabalyzat.pdf. Access from outside the EEA and its safeguards: Tárhely.Eu Szolgáltató Kft. (H-1144 Budapest, Ormánság utca 4, 10th floor 241; company reg. no. 01-09-909968; tax no. 14571332-2-42). The VPS runs in Budapest, Hungary; the provider's data centres are at Váci út 188, Victor Hugo u. 18–20 and Asztalos Sándor út 13, Budapest. The VPS IP address is in the Tárhely.Eu network (AS43359); the address block is registered to Freemium Kft. Further processors may be engaged only under a general authorisation with prior written notice (Terms 3.7, 5-day objection right). The provider's terms contain no provision on access from outside the EEA. The VPS is held in the customer account of Globaldogshop International Kft.; Globaldogshop International Kft. is a member (owner) of YourDJ Ügynökség Kft. |
| Anthropic API | Contracting party: Anthropic Ireland, Limited. Storage: US (workspace region: US). Model execution (inference): global or US, according to the provider’s settings, not restricted to the EU. Service: Anthropic Messages API (https://api.anthropic.com/v1/messages), model: claude-opus-5-5; if the model refuses, the provider's server-side fallback model may answer. Within the Jegyfutár system four functions call it: the AI planning-room assistant (room state and the member's request), the quick-search text interpretation (the search text entered, max. 300 characters), the AI summary of the Organizer’s Visitors report (aggregate figures only, no personal data), and the Claude AI customer service (section 3.5) in platform matters; the system does not itself send Organizer matters, which only YourDJ’s customer service may pass on, with human review (the text, identifiers and justified attachments needed to resolve the case). We use neither file storage (Files API) nor feedback submission. Standard API input/output deleted within 30 days; file storage, different contracts and legal/security exceptions separately. Where the relevant exception applies, flagged content may remain 2 years, security classifications 7 years and submitted feedback 5 years. |
DPA, chain, data residency, retention. SCCs with the module appropriate to the role (II or III); the Irish contracting entity does not mean an EU-only route. |
| Billingo – Organizer-selected invoicing provider (only for the Organizer’s invoicing, under the Organizer’s privacy notice; not used by YourDJ for its own purposes) | AWS hosting. The system sends invoice data to the Organizer's own Billingo account via Billingo API v3 (api.billingo.hu/v3): buyer name, email, country, postcode, city, address, tax number where applicable, and the line items; it downloads a PDF copy of the issued invoice into Jegyfutár's private media storage. The Organizer's API key is stored encrypted and deleted when the organiser account ends, after which the system no longer accesses the Billingo account. AWS region, subprocessors and their countries: Billingo Technologies Zrt. (H-1133 Budapest, Árbóc utca 6, 1st floor; reg. no. 01-10-140802; tax no. 27926309-2-41; DPO: dr. Zalán Gyetvai, adatvedelem@billingo.com). Billingo acts as processor for invoice data. Hosting: Amazon Web Services; the provider does not publicly state the storage location (region). Further processors (22, section 7.2 of the notice), including providers based outside the EEA or with no stated seat: Freshworks Inc., Sentry, Hotjar, Atlassian, SAP Emarsys, Snowflake Inc., Peaberry Software Inc. (Customer.io), Beamer, CustomerView. The notice names no safeguard for third-country transfers. Information on the AWS region, the data processing agreement (DPA) and the notification procedure for changes to further processors is available to the Organizer from its own invoicing provider, Billingo, as YourDJ has no contractual relationship with Billingo in connection with the Organizer’s invoicing. Retention and exit export of invoices held by Billingo: Billingo keeps images of issued documents for 13 years from issue and releases them on request of a person entitled to see them. Access to documents from before the current year may be tied to certain plans. This storage is not digital archiving under ITM Decree 1/2018 (VI. 29.). On termination of the subscription and deletion of the account, Billingo deletes or archives the stored data and deletes the account. On exit: data and invoice export to supported accounting software. Accounting obligations are different from the provider's archiving commitment. | Privacy, Terms. Not automatically YourDJ's subprocessor; the actual international safeguard is part of the chain used. |
| Számlázz.hu | AWS Frankfurt/Germany; additional functions and chain: Processors of KBOSS.hu Kft. (H-1031 Budapest, Záhony utca 7; reg. no. 01-09-303201; tax no. 13421739-2-41): Amazon Web Services EMEA SARL (Luxembourg; AWS Frankfurt region – hosting and AI assistant), Hibridlevél Kft. (printing, enveloping and posting invoices), Visma Software International AS (Norway; invoice-image OCR), HubSpot Ireland Ltd. (newsletters, complaints, support tickets), Userflow Inc. and Joincube, Inc. (Beamer) (USA; in-app messaging), Nevogate Payment Services Kft. (IT support for electronic payments), CookieFirst (Digital Data Solutions B.V., Netherlands; cookie consent), Orca Security Ltd. (cloud security monitoring, Frankfurt), GIRO Zrt. (payment requests), Riport Applications Kft. (Riport Quick cost tracking). The provider keeps an up-to-date record of subcontractors and processing locations; its infrastructure operates in the EU/EEA; transfers: Számlázz.hu transmits invoice data directly to the NAV Online Invoice system. Transfers to a third country (USA) go to Mailchimp (The Rocket Science Group LLC) and Intercom Inc., based on the European Commission's EU–US adequacy decision; Userflow Inc. and Joincube, Inc. (Beamer) are US-based processors. For other processing outside the EEA, the provider applies the Standard Contractual Clauses adopted by the European Commission. Terms 10.4 describe deletion within 3 months after termination and prior export; Jegyfutár also stores a PDF copy of each issued invoice in its own private media storage; plan and archive: Számlázz.hu keeps issued invoices for up to 13 years from issue, but no longer than until the invoicing account is closed (Terms 4.2.10). The statutory retention of invoices is the issuer's obligation, which Számlázz.hu does not assume. After account deletion, the account can be restored once, within 3 months, to save the invoices. Within 3 months after termination, Számlázz.hu permanently deletes the data transmitted to it and anonymises any data kept for statistics; before deletion it offers the user the chance to save the data (Terms 10.4). YourDJ uses the #profi plan: Számlázz.hu digitally archives issued invoices as authentic electronic records with an unalterable invoice image under ITM Decree 1/2018 (VI. 29.) (Terms 4.4). YourDJ has no contractual relationship with Számlázz.hu in connection with the Organizer’s invoicing: further information on the retention of invoices held in the Organizer’s account and on the notification procedure for changes to further processors is available to the Organizer from its own invoicing provider, Számlázz.hu (KBOSS.hu Kft., a Hungarian provider). | Privacy and recipients, Terms. Organizer-selected provider for Organizer invoicing; YourDJ's commission invoicing is separate processing for its own purposes. |
Provider storage does not replace the obligated party's own accounting archive. Current versions of the processing chain are available on the provider pages above; the providers, data categories and safeguards actually used by YourDJ appear in the tables above. Organizers’ change-notification and objection rights are governed by the Jegyfutár Data Processing Agreement; shorter provider deadlines do not reduce them.
6. International transfers
Hosting in an EU region can still involve support or subprocessor access from outside the EEA. Before transfer we check recipient, country, role, onward chain and safeguards.
An adequacy decision, including the EU–US DPF, covers only the actually certified entity and covered data route. Otherwise, appropriate standard contractual clauses (SCCs), transfer impact assessment and supplementary measures where necessary are required. When YourDJ transfers as controller to a processor, we use the controller-to-processor module of the SCCs (Module Two); when it transfers as processor to a further processor, the processor-to-processor module (Module Three). The onward US transfer by the Irish contracting entity (Anthropic Ireland, Limited) is shown in the Anthropic row of Annex C1. The data route and safeguards for tickets saved to Google Wallet are shown in the Google Wallet row of Annex C1.
The substance of safeguards or an appropriate copy can be requested at adatvedelem@jegyfutar.hu, subject to necessary protection of others’ data and trade secrets. Transfer safeguards do not replace an Article 6 legal basis for the purpose. Consent to an exceptional transfer is not a general solution for routine cloud use.
7. Deletion, backups and genuine anonymization
Deletion periods are tied to purpose and data category. Account deletion must not unlawfully destroy mandatory accounting records or specific legal evidence; these are handled separately with restricted access. The Organizer determines deletion of its order data under its own controller responsibility. On deletion, the buyer account is closed immediately and the account data are deleted. Personal data in orders still existing at deletion are deleted under the 24-month order-retention schedule, without a separate post-event deletion run. The starting points in the Organizer’s privacy notice and mandatory-retention exceptions remain applicable. Purchased tickets remain usable. For an activated account, after the retention period the order remains visible in the account marked “Anonymised”, with its basic data (order number, event, date, status, total); the ticket, PDF and invoice are no longer available for it.
Daily backups remain for at most 30 days and monthly backups for at most 90 days from creation. Expiring backups containing deleted data are used only for protected restoration. Deletions, unsubscribes and permission revocations are reapplied before normal reopening after a restore.
External providers’ own deletion is also governed by the service conditions in C1; YourDJ’s 90-day backup limit does not mean that every provider has the same backup period. Annex C1 shows the differences.
A record may remain linkable to a person if order identifiers, ticket codes, payment references, masked card numbers, invoice references or PDFs remain. This is pseudonymization, not anonymization; we therefore apply a retention limit to such records as well (7.1).
On account closure, its resale listings are withdrawn. If a buyer already holds the ticket in their cart at that moment, the sale may complete: the buyer can buy it and your refund arrives via the original payment method of the order. Data on completed exchanges remain until the general 24-month anonymisation of the order, with price and status kept as financial data. You can submit pending claims (refund, complaint) without an account at support@jegyfutar.hu and via the Help form. The data of a customer-service case open at the time of deletion are kept until closure under section 3.5.
7.1. Consistent retention rules and starting points
The order rows distinguish the Organizer's processing; they do not make YourDJ an independent controller for those purposes.
Retention periods are upper limits: the end of a purpose, a justified erasure request or withdrawal of consent may require earlier deletion. Evidence necessary for a specific legal claim is separated; exceptions are reviewed at least every 90 days. Accounting obligations concern necessary records, not the entire profile or raw campaign data. Encryption, HMAC or deletion of a direct identifier is not, by itself, anonymization.
| Data category | Retention and purpose limitation |
|---|---|
| Platform account | Until account closure or five years of meaningful inactivity; not deleted for inactivity while an Organizer membership lasts (3.1) |
| Inactive guest record without an order link | Up to 24 months from creation (3.2) |
| YourDJ accounting records | At least eight years under statutory retention rules (3.6) |
| Evidence of DPA acceptance and Organizer instructions | During validity and five years after expiry (3.6) |
| Incident register | Five years from investigation closure, minimal content (3.4) |
| Marketing mailing list | Until withdrawal of consent or the end of the purpose; afterwards only evidence and suppression data (3.7) |
| Resale waiting list | Until the 30th day after the event/performance ends; for a postponed event, does not run until a new date is set (3.12) |
| Pre-sale notification | Until the 30th day after the event (performance) ends; for a postponed event, not counted until the new date (3.15) |
| AI assistant connection | Until the connection is ended; call log 90 days (3.13) |
| Interest profile | Until consent is withdrawn, then deleted immediately; events older than 24 months are not counted (3.14) |
| AI planning room local data | 30 days after the last selected event or, without an event, 30 days after last activity; also covers membership, invitations and attachments (3.10) |
| Person-linkable UTM attribution | Up to 7 days from the campaign interaction; then deletion or irreversible disconnection from the person and order |
| UTM campaign aggregates that cannot be linked to a person | 25 months; no raw UTM or order-linking key remains in them |
| Conversion matching data | Up to 7 days from collection; no queued event may be sent after withdrawal |
| HMAC-indexed analytical event series | 30 days from capture; daily expiry management; pseudonymous personal data subject to the statistical-consent rules |
| Hourly and daily analytics aggregates | 25 months; cannot be linked to a person |
| Other genuinely anonymous aggregate figures | Retained where reasonable re-identification and inference from small groups are excluded; the separate 25-month limit for UTM aggregates above remains applicable |
| Completed orders, participants and encrypted Organizer legal-profile snapshots | Up to 24 months from the actual event end, or the last event for a season pass; for cancellation/permanent failure, from its recording; for a postponed event, from the end of the new date, not running during the postponement; restricted to necessary fields |
| Permanently failed, expired and unpaid orders | 30 days from final status; minimal evidence of disputed charges separately |
| Temporary exports | 7 days from generation; availability for 30 calendar days on termination with renewable access is a separate obligation |
| Transactional email content / minimal delivery evidence | Local content up to 30 days from sending; minimal evidence 24 months; provider copies separately in the recipient table |
| Diagnostic / MCP / security logs | 30 days from entry / 90 days from action / 12 months from entry; copying full content to another log does not extend the period |
| General support / case handled as a consumer complaint | Up to 24 months from case closure / 3 years from case closure, also where erasure is requested; complaints classified by the “Complaint” category of the web form or by substance (3.5) |
| Daily / monthly backups | 30 / up to 90 days from creation; segregated, solely for restoration |
On restoration, intervening deletions, restrictions, unsubscribes and permission revocations are reapplied before normal access and sending resume. The minimal change register necessary for this remains until the affected restorable backups expire. YourDJ's storage deadline does not mean every external provider copy is deleted at the same time.
Activation and sign-in tokens are valid for 60 and 15 minutes respectively; tokens are stored only as one-way hashes (SHA-256) and cannot be used once expired or used. They are physically deleted together with the account: on data-subject erasure, account termination, deletion after 5 years of inactivity, or anonymisation of a never-activated guest account after 24 months. The AI planning room's 30-day local period also covers membership, invitations and attachments.
8. Automated decisions and profiling
In the described system, dynamic ticket pricing follows sales and time conditions rather than personal profiles.
If you give marketing consent, advertising providers (Meta, Google) may also use the data transmitted to them for ad targeting and profiling (Cookie and Tracking Notice, section 7). This is not an automated decision producing legal or similarly significant effects for you. Withdrawing consent or objecting ends this purpose.
If you have given separate consent to the interest profile (3.14), we build a profile from the event categories of your own paid orders and checked-in tickets and show personalised recommendations based on it; if you have also consented to marketing messages, we send targeted emails. The order of the event list does not depend on it. When you withdraw consent, the profile is deleted immediately.
Payment authentication, bot screening and abuse prevention may use automated elements. Individuals are informed about relevant automated decisions and rights through the following information sheet.
Applicable logic, significance, expected consequences and human review: the system makes no solely automated decision with legal effect in an individual case and no profiling-based decision. Automatic technical operations: if the bot check (Cloudflare Turnstile) fails, the checkout, login-link and help forms cannot be submitted and the check can be retried; rate limits (e.g. login: 5 attempts per minute per account and IP address; free orders: 5 per hour per IP address); for high-demand events a waiting room in arrival order with a per-minute quota; a cart hold expires after 15 minutes; a dynamic price rule approved by the Organizer applies equally to everyone. You can request human review at support@jegyfutar.hu.
9. Your rights
At adatvedelem@jegyfutar.hu or by post, you can request information, access and a copy of your data; correction of inaccurate data; and deletion or restriction under GDPR conditions. For automated processing based on contract or consent, you can request portability of data you provided.
You may object to legitimate-interest processing on grounds relating to your particular situation. Processing can then continue only with compelling legitimate grounds or for legal claims as provided by the GDPR. After an objection to direct marketing, including related profiling, data are no longer processed for that purpose.
Consent can be withdrawn at any time without affecting the lawfulness of earlier processing. Deletion may not apply to data covered by a legal obligation or necessary legal claim; we explain the reason and period of separate processing.
We respond without undue delay and within one month. Where justified by complexity or number of requests, this may be extended by two further months, with reasons provided within the first month. Handling is generally free. If identity is in doubt, only necessary additional information is requested; identity-document copies are not a general condition.
For Organizer data, we direct the request to the relevant Organizer or forward the necessary information and assist as processor.
You can submit a data-subject request – including data export or deletion – from your account after signing in, or at adatvedelem@jegyfutar.hu. You are identified by signing in or by a confirmation email sent to the email address of your account. If you identify yourself in another way, we do not automatically reject the request for that reason: we assess it individually and ask only for the necessary additional information. Account export/deletion interfaces do not replace individual assessment of statutory exceptions.
You can view your interest profile (3.14) on the “My interests” page of your account, delete it item by item or entirely, and you also receive it in your data export. You can end the connection of an AI assistant linked to your account (3.13) on the “AI connections” page.
10. Complaints, courts and changes
You can complain to Hungary’s National Authority for Data Protection and Freedom of Information (NAIH): 1055 Budapest, Falk Miksa utca 9–11.; postal address: 1363 Budapest, Pf. 9.; email: ugyfelszolgalat@naih.hu; telephone: +36 (1) 391-1400; website: https://www.naih.hu. NAIH’s website explains how to submit a formal complaint. You can also complain to the data protection supervisory authority of another EU Member State, in particular in the Member State of your habitual residence, place of work or place of the alleged infringement (GDPR Article 77).
If your rights are infringed, you can also go to court. Such proceedings fall within the jurisdiction of the regional court (törvényszék); at your choice, you may also bring the action before the regional court for your place of residence or stay (Hungarian Privacy Act, Infotv.). Contacting us first is not a prerequisite for approaching the authority or court.
Changes to this notice are published with a version and effective date; material changes to purposes, recipients or legal bases are appropriately disclosed in advance. An amendment does not retrospectively create consent.
JF-03 v0.15.2 EN – END OF COMPLETE DOCUMENT