Privacy Notice
Pursuant to Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016 on the protection of natural persons with regard to the processing of personal data and on the free movement of such data, and repealing Directive 95/46/EC (General Data Protection Regulation; hereinafter: “GDPR”), we hereby provide the following information.
This Privacy Notice applies to the The Path event application (mobile application and Organiser interface; hereinafter: the “Application”).
The Data Controller and its contact details
Name: HPB Sportmanagement Kft.
Registered office: 1013 Budapest, Lánchíd u. 15–17, ground floor, unit 1 Company registration number: 01 09 281053
Tax number: 25539448241 Represented by: Hunor Dudás Email: office@thepathsm.com Telephone: +36202769276
The Application and the categories of data subjects
The Application is the companion mobile application and Organiser interface of professional sports events (conferences). We process the personal data of three categories of persons:
- Participant: a person who has purchased a ticket to the event and registers in the Application. The Participant views the programme, marks favourites, exchanges messages and arranges meetings with other Participants, and builds contacts.
- Speaker: a person featured in the programme of the event. The Speaker’s data are entered by the Organiser; the Speaker may, but is not required to, have his or her own account.
- Organiser: the administrator of the event, who manages the programme, the tickets, the broadcast messages and the notifications on the Organiser interface.
Personal data originate from three sources: (1) the Participant provides them upon registration and when editing his or her profile; (2) the Organiser enters them on the Organiser interface (programme, Speakers, partners, broadcast messages); (3) ticket data imported from the Cooltix ticketing system. The Application does not sell tickets; it mirrors the tickets purchased from the ticket seller so that the registration can be linked to the ticket.
The data are stored in a database (PostgreSQL) and in a separate file storage (images, attachments, presentation materials).
Definitions
- ‘personal data’ means any information relating to an identified or identifiable natural person (‘data subject’); an identifiable natural person is one who can be identified, directly or indirectly, in particular by reference to an identifier such as a name, an identification number, location data, an online identifier or to one or more factors specific to the physical, physiological, genetic, mental, economic, cultural or social identity of that natural person;
- ‘processing’ means any operation or set of operations which is performed on personal data or on sets of personal data, whether or not by automated means, such as collection, recording, organisation, structuring, storage, adaptation or alteration, retrieval, consultation, use, disclosure by transmission, dissemination or otherwise making available, alignment or combination, restriction, erasure or destruction;
- ‘data controller’ means the natural or legal person, public authority, agency or any other body which, alone or jointly with others, determines the purposes and means of the processing of personal data; where the purposes and means of processing are determined by Union or Member State law, Union or Member State law may also determine the controller or specific criteria for the designation of the controller;
- ‘data processor’ means a natural or legal person, public authority, agency or any other body which processes personal data on behalf of the data controller;
- ‘recipient’ means a natural or legal person, public authority, agency or any other body to which personal data are disclosed, whether a third party or not. Public authorities which, in the framework of a particular inquiry, have access to personal data in accordance with Union or Member State law shall not be regarded as recipients; the processing of such data by those public authorities must comply with the applicable data protection rules in accordance with the purposes of the processing;
- ‘consent’ of the data subject means any freely given, specific, informed and unambiguous indication of the data subject’s wishes, by which the data subject, by a statement or by a clear affirmative action, signifies agreement to the processing of personal data relating to him or her;
- ‘personal data breach’ means a breach of security leading to the accidental or unlawful destruction, loss, alteration, unauthorised disclosure of, or unauthorised access to, personal data transmitted, stored or otherwise processed.
Principles governing the processing of personal data
Personal data shall be:
- processed lawfully, fairly and in a transparent manner in relation to the data subject (‘lawfulness, fairness and transparency’);
- collected for specified, explicit and legitimate purposes and not further processed in a manner that is incompatible with those purposes; further processing for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes shall, in accordance with Article 89(1) GDPR, not be considered to be incompatible with the initial purposes (‘purpose limitation’);
- adequate, relevant and limited to what is necessary in relation to the purposes for which they are processed (‘data minimisation’);
- accurate and, where necessary, kept up to date; every reasonable step must be taken to ensure that personal data that are inaccurate, having regard to the purposes for which they are processed, are erased or rectified without delay (‘accuracy’);
- kept in a form which permits identification of data subjects for no longer than is necessary for the purposes for which the personal data are processed; personal data may be stored for longer periods insofar as the personal data will be processed solely for archiving purposes in the public interest, scientific or historical research purposes or statistical purposes in accordance with Article 89(1) GDPR, subject to implementation of the appropriate technical and organisational measures required by the GDPR in order to safeguard the rights and freedoms of the data subject (‘storage limitation’);
- processed in a manner that ensures appropriate security of the personal data, including protection against unauthorised or unlawful processing and against accidental loss, destruction or damage, using appropriate technical or organisational measures (‘integrity and confidentiality’).
The Data Controller shall be responsible for, and be able to demonstrate, compliance with the foregoing (‘accountability’).
The Data Controller declares that its processing is carried out in accordance with the principles set out in this section.
Individual processing operations
Below, for each purpose, we set out the data processed, the purpose of the processing and its legal basis. Where the legal basis is the data subject’s consent, the giving of consent is voluntary and may be withdrawn at any time, and the withdrawal does not affect the lawfulness of processing based on consent before its withdrawal. The Data Controller records the giving and withdrawal of consent per purpose, together with the time and the version of the notice displayed.
Registration, account and login
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Email address | Login ID, notification address, linking of account and ticket | Article 6(1)(b) GDPR |
| Password (irreversible hash only) | Authentication | Article 6(1)(b) GDPR |
| Name, role (Participant / Speaker / Organiser), language setting | Account identification; use of the Application in the appropriate language and with the appropriate permissions | Article 6(1)(b) GDPR |
| Date and time of email address confirmation, of registration and of the last modification | Verification of the email address; keeping a record of the account | Article 6(1)(b) GDPR |
| Hashes of login and one-time codes (email confirmation, maintaining login, Speaker invitation, QR business card exchange), and the time of their validity and redemption | Maintaining login, secure creation of the account and business card exchange | Article 6(1)(b) GDPR |
| Telephone number (may be provided voluntarily) | Contacting the Participant; not displayed to other Participants in the Application | Article 6(1)(a) GDPR |
Data subjects: all users registered in the Application.
Duration of processing: until deletion of the account, but no later than 1 year after the closing of the event; expired or redeemed login codes are deleted within [7] days.
The Application does not require the provision of any data other than that necessary to create an account (email address, password, name).
Ticket verification, admission, import of ticket data
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| The ticket seller’s ticket code (in a QR code) | To verify the validity of the ticket and grant entry to the event | Article 6(1)(b) GDPR |
| Email address | Linking the ticket to the account | Article 6(1)(b) GDPR |
| The Participant’s name on the ticket | Identification of the ticket holder upon admission and in the participant directory | Article 6(1)(b) GDPR |
| Name of the ticket type, ticket status (valid / refunded / invalid), the ticket seller’s internal identifier, time of import | To determine eligibility, to recognise an existing ticket during a repeat import, and to provide information specific to the ticket type | Article 6(1)(b) GDPR; Article 6(1)(f) GDPR |
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Telephone number (if provided at the time of ticket purchase) | To contact the ticket holder in urgent matters relating to the event | Article 6(1)(f) GDPR |
| Ticket import log (source, file name, number of rows, warnings, which may also contain data originating from the row) | Verifiability of the data import; correction of errors | Article 6(1)(f) GDPR |
Data subjects: all persons purchasing a ticket for the event, even if they do not register with the Application.
Source of the data: the system of the ticket seller (Cooltix); the data subject provided the data upon ticket purchase. The Data Controller receives the data by uploading or importing a file exported from the ticket seller’s system.
Legitimate interest: the Data Controller’s legitimate interest lies in the orderly conduct of the event, the verification of tickets and admission, and the prevention of abuse. The data subject has the right to object to processing based on legitimate interest.
Duration of processing: for 1 year after the closing of the event (handling of complaints and refunds), after which the data are deleted or anonymised. Ticket handling does not cease upon deletion of the registration, because the data are linked to the email address and not to the account; the deletion of a registered user’s account does not affect the ticket data, the deletion of which the data subject may request separately.
Networking profile and participant directory (data visible to other Participants)
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Name | Identification of the user in the participant directory, in messages and on his or her profile | Article 6(1)(a) GDPR |
| Position, organisation/club, sport, capacity of attendance (athlete, manager, coach, professional, sponsor, other) | Networking and filterability of the participant directory | Article 6(1)(a) GDPR |
| Introduction (free text), profile photo | Facilitating networking | Article 6(1)(a) GDPR |
| ‘Looking for / Offering’ free text and selected tags | Recommending matching Participants; use of the participant directory | Article 6(1)(a) GDPR |
| Fact and time of exclusion from networking | Implementation of the Organiser’s decision; the excluded person does not appear in the participant directory | See point 9 |
Data subjects: Participants who have created a networking profile in the Application. Who can see it: the details of a profile entered in the participant directory (name, position,
organisation, sport, introduction, photo, ‘looking for / offering’ texts and tags) are visible to all Participants of the event. The telephone number and email address are not visible to other Participants on the profile.
Use of the networking function is voluntary. The programme, favourites and notifications may be used without consent as well; giving consent is not a condition for using the service. Consent may be withdrawn at any time when editing the profile, whereupon the profile disappears from the participant directory.
Recommendation: the Application recommends matching Participants on the basis of the tags and texts selected. This does not involve automated decision-making producing legal effects concerning the data subject or similarly significantly affecting him or her (Article 22 GDPR).
Duration of processing: until consent is withdrawn or the account is deleted, but no later than 1 year after the closing of the event.
Warning: data visible to other Participants may be used by recipients for networking within the Application; their use for mass marketing or other purposes is prohibited.
Contact requests, contact list, blocking
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Contact request (who made it, to whom, at which event, its status, relevant dates and times) | Operation of the ‘Connect’ function; retention of a declined request to prevent immediate re-requests | Article 6(1)(b) GDPR |
| Contact list (with whom, where and in what way – message, QR exchange, recommendation, meeting, accepted request – the user became acquainted) | The user’s own contact list, the post-event summary | Article 6(1)(b) GDPR |
| The user’s private note about the other person | The user’s own reminder; visible only to the owner of the note | Article 6(1)(b) GDPR |
| Blocking (who blocked whom, and when) | Protection of the user, prevention of unwanted contact; the blocked user is not notified | Article 6(1)(b) GDPR; Article 6(1)(f) GDPR |
Data subjects: Participants using the features and persons who come into contact with them.
Duration of processing: until the account is deleted (upon deletion of the account of either data subject concerned, the related entry is also deleted), but no later than 1 year after the closing of the event.
Messaging and attachments
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| The full text of the message, the sender, the conversation, and the dates and times of sending and reading | Private messaging between two Participants | Article 6(1)(b) GDPR |
| Attachment (PDF, Word, image), file name, file type, size | Sharing of documents within the message exchange | Article 6(1)(b) GDPR |
Data subjects: the Participants sending and receiving the message.
Who can see it: only the two Participants in the conversation; the Organiser cannot view the messages on the Organiser interface. There are no group conversations.
Duration of processing: until the account is deleted, but no later than 1 year after the closing of the event. When the sender’s account is deleted, the messages and attachments sent – together with the files in the file storage – are deleted, and therefore also disappear from the other party’s history.
Scheduling meetings
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| The parties to the meeting, its time and venue (free text), the initiator’s message, its status, the time the reminder was sent | Scheduling between two Participants for the duration of the event (acceptance, counter-proposal, rejection, cancellation) | Article 6(1)(b) GDPR |
| The event log for the meeting (who took what action and when, time of the counter-proposal) | Traceability of status changes, as the counter-proposal overrides the time | Article 6(1)(b) GDPR |
Data subjects: the person initiating the meeting and the invited Participants.
Who can see it: the two parties; the Organiser sees only the number of meetings in the statistics.
Duration of processing: until the account is deleted (upon deletion of either party’s account, the meeting and its log are also deleted), but no later than 1 year after the closing of the event.
Use of the programme: favourites, following, interests, ratings
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Sessions and side programmes marked as favourites | Sending reminders and programme-specific information | Article 6(1)(b) GDPR |
| Followed Speakers | Notification before the Speaker takes the stage | Article 6(1)(b) GDPR |
| Selected topics (areas of interest) | Filtering the programme, targeting broadcast messages | Article 6(1)(b) GDPR |
| Ratings of sessions and of the event (1–5 stars) | Measuring and improving the quality of the event | Article 6(1)(a) GDPR |
Data subjects: Participants using the features.
Who can see it: the user can see their own data; the Organiser can only see aggregate figures and averages, not individual ratings or individual favourites lists.
There are no written reviews. Duration of processing: until the account is deleted, but no later than 1 year after the closing of the event; thereafter, ratings may only be retained in anonymised, aggregated form.
Notifications, push notifications and broadcast messages
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Push notification device identifier (token), device platform (iOS / Android), time of registration | Sending push notifications to the user’s device | Article 6(1)(a) GDPR |
| A copy of the notifications (type, title, text, linked content, time of reading and of sending); for new messages, the message text; for a meeting, the time and the other person’s name | The in-app notification centre, providing information about related events (messages, meetings, contact requests, reminders) | Article 6(1)(b) GDPR |
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Notification settings (types of notifications that have been disabled) | Enforcing the user’s notification preferences | Article 6(1)(b) GDPR |
| The Organiser’s broadcast messages and targeting criteria (everyone / topic / favourite session / ticket type); time of dispatch, number of recipients | Information relating to the event; critical messages (e.g. changes, safety information) also sent by email | Critical message: Article 6(1)(f) GDPR. Other broadcast messages: Article 6(1)(a) GDPR |
Data subjects: Participants and Speakers using the Application.
Duration of processing: the push token is retained until the account is deleted or consent is withdrawn (upon revocation of push permission on the device); notifications are retained until the account is deleted, but no later than 1 year after the closing of the event. Names appearing in other users’ notifications are anonymised when the account is deleted.
The Application does not send messages for marketing purposes. Should the Data Controller introduce a newsletter or direct marketing communications, these will be sent solely on the basis of the data subject’s prior, explicit consent (Article 6(1)(a) GDPR, Section 6 of Act XLVIII of 2008 on the Essential Conditions of and Certain Limitations to Business Advertising Activity), and this Privacy Notice will be amended accordingly. Consent may be withdrawn at any time, free of charge and without restriction or justification, via the link provided in the messages or in the Application’s settings.
Reports and exclusion from networking
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Identification details of the person making the report and the person reported, and the date of the report | To manage abuse and harassment, and to protect Participants | Article 6(1)(f) GDPR |
| Free-text explanation provided by the reporter | Assessment of the report | Article 6(1)(f) GDPR |
| Fact and time of exclusion | Implementation of the Organiser’s decision; the excluded person does not appear in the participant directory | Article 6(1)(f) GDPR |
Data subjects: the person making the report and the Participants reported.
Legitimate interest: the legitimate interest of the Data Controller and the Participants lies in the safe, harassment-free operation of the networking space.
Who can see it: the person making the report and the Organiser; the person reported cannot see that a report has been made within the Application.
The person reported may exercise their right of access in accordance with Article 15 GDPR; the Data Controller may restrict access in order to protect the identity of the person making the report and the rights and freedoms of the other party (Article 15(4) GDPR).
Duration of processing: for 1 year after the closing of the report; in the case of exclusion, the timestamp of the exclusion for 1 year after the closing of the event; where a legal claim is brought, until its conclusion.
Speakers’ details
| Personal data | Purpose of processing | Legal basis |
|---|---|---|
| Name, title/position (in Hungarian and English), introductory text, photograph, social media and website links (LinkedIn, X/Twitter, Instagram, Facebook, website) | To list the Speaker in the event programme and to provide Participants with information about the Speaker | Performance of a contract: Article 6(1)(b) GDPR; and, in the case of photographs and social media links, Article 6(1)(a) GDPR |
| Email address | Sending an invitation to create a Speaker account, maintaining contact; not visible to Participants | Article 6(1)(b) GDPR |
Data subjects: Speakers at the event, even if they do not have their own account.
Source of the data: the Organiser enters them on the Organiser interface, based on the data provided by the Speaker.
Duration of processing: for 1 year after the closing of the event; upon deletion of the account, the Speaker’s personal data will be deleted or anonymised; an archived, anonymised copy of the event programme may be retained.
Persons entitled to access the data, recipients of personal data
Personal data may be processed by the Data Controller’s authorised staff and by users with the ‘Organiser’ role, within the scope of their authorisation. The Organiser can view networking profiles, ticket details, reports, the targeting of broadcast messages and aggregate statistics; it cannot view private messages, contact lists, notes, individual favourites or ratings.
Other recipients: the details of profiles entered in the participant directory are made available to the other Participants of the event (see point 3); Data Processors (see below). Data may otherwise only be disclosed on the basis of a legal obligation or in response to a request from a public authority.
Data Processors and other controllers engaged
| Service provider | Activity and data processed | Comment |
|---|---|---|
| Rackforest Informatikai Kereskedelmi Szolgáltató és Tanácsadó Zrt. (1132 Budapest, Victor Hugo utca 11, 5th floor, B05001; info@rackforest.hu) | Operation of the Application, the database and the file storage; all personal data provided by the data subject | Data processor. Duration: until the termination of the agreement between the Data Controller and the service provider. Legal basis: Article 6(1)(c) and Article 6(1)(f) GDPR. |
| [Name and registered office of the email (SMTP) service provider] | Sending emails (confirmation emails, Speaker invitations, critical broadcast messages); the email address and the content of the message | Data processor. |
| COOLTIX Kereskedelmi és Szolgáltató Kft. (1126 Budapest, Kiss János Altábornagy utca 33b, 2nd floor, door 3) | Ticket sales; source of ticket purchaser data. The Application imports ticket data. | The Data Controller does not transfer any data to Cooltix. |
Data Processors act in accordance with the Data Controller’s instructions, on the basis of a written agreement in accordance with Article 28 GDPR.
Data retention, erasure and the effect of account deletion
The Data Controller automatically deletes data when the purpose of processing has ceased to apply, the retention period has expired, or the data subject has exercised their right to erasure. The Participant may delete their account within the Application or submit a request for deletion to the Data Controller’s contact details.
| Category of data | Retention period | Upon account deletion |
|---|---|---|
| Account and profile data, contact list, blocks, favourites, ratings | Until the account is deleted, but no later than 1 year after the closing of the event | Deleted |
| Messages and attachments | Until the account is deleted, but no later than 1 year after the closing of the event | The sender’s messages and attachments are deleted (including from the file storage), and also from the other party’s message history |
| Notifications, push token | See point 8 | These will be deleted; the name appearing in other users’ notifications will be anonymised |
| Meetings and their event logs | Until the account is deleted, but no later than 1 year after the closing of the event | Deleted |
| Reports, exclusion | For 1 year after the closing of the report | Deleted along with the account of the person who reported the incident or the person reported, unless required for the establishment, exercise or defence of legal claims |
| Login codes | Until their expiry date; expired codes are deleted within 7 days | Deleted |
| Ticket data, ticket import log | For 1 year after the closing of the event | They are not deleted, as they are linked to the email address rather than the account; they can be deleted separately at the request of the data subject |
| Speaker details | For 1 year after the closing of the event | Upon deletion of the Speaker account, personal data are deleted or anonymised |
| Photos and attachments stored in the file storage | For the same period as the data containing them | Deleted |
The Data Controller shall retain data necessary for the fulfilment of a legal obligation or for the establishment, exercise or defence of legal claims for as long as necessary.
Rights of data subjects
The data subject may:
- request access to the personal data concerning him or her (Article 15 GDPR) and a copy thereof;
- request rectification (Article 16 GDPR) – the user may also modify his or her profile data in the Application;
- request erasure (‘right to be forgotten’, Article 17 GDPR);
- request restriction of processing (Article 18 GDPR);
- request data portability (Article 20 GDPR) in the case of automated processing based on consent or contract;
- object to processing based on legitimate interests (Article 21 GDPR), in which case the Data Controller may no longer process the data, unless compelling legitimate grounds justify the processing;
- withdraw his or her consent at any time (Article 7(3) GDPR), in the settings of the Application or via the Data Controller’s contact details.
The Data Controller shall inform the data subject of the action taken on the request without undue delay and in any event within one month of receipt of the request. The request may be submitted by post or by email. The Data Controller is entitled to verify the identity of the data subject. The Data Controller shall inform the data subject by electronic means of the erasure of any personal data provided by the data subject, pursuant to Article 19 GDPR.
The Application does not use automated decision-making that produces legal effects concerning the data subject.
Security of processing
The Data Controller and the Data Processor shall take appropriate technical and organisational measures, taking into account the state of the art, the costs of implementation, as well as the nature, scope, context and purposes of the data processing, and the risk of varying likelihood and severity to the rights and freedoms of natural persons, in order to ensure a level of data security appropriate to the risk.
IT security
- The Data Controller does not store the password, only its irreversible hash; the same applies to login and one-time codes.
- Access to data is governed by roles (Participant, Speaker, Organiser); the Organiser can only view the data necessary for their tasks.
- The Application’s data are protected by backups and archiving.
- Systems containing personal data can only be accessed using a username and password.
Informing the data subject of a personal data breach
Where a personal data breach is likely to result in a high risk to the rights and freedoms of natural persons, the Data Controller shall inform the data subject without undue delay. The Data Controller shall document the breach and, where necessary, notify the supervisory authority within 72 hours.
Right to lodge a complaint and legal remedies
Complaints in respect of any infringement by the Data Controller may be lodged with the Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság; “NAIH”); in addition, the data subject may bring the matter before the
courts, and the action may also be brought before the regional court (törvényszék) of his or her place of residence or place of stay:
Hungarian National Authority for Data Protection and Freedom of Information (Nemzeti Adatvédelmi és Információszabadság Hatóság)
1055 Budapest, Falk Miksa utca 9–11. Postal address: 1363 Budapest, P.O. Box 9 Telephone: +36-1-391-1400
Fax: +36-1-391-1410
Email: ugyfelszolgalat@naih.hu
Date of creation and validity of this document: [… 2026]