Privacy policy
for the plovdiv.run website and the races organised through it
Earlier edition, effective 5 November 2026. Current edition · English translation · Bulgarian original
The personal data controller is VIVENTA GROUP OOD, company registration number 208948386, with its registered office and business address at 4A Anton Chekhov Square, apartment 34, Plovdiv, correspondence address: 4A Anton Chekhov Square, apartment 34, Plovdiv, email: support@plovdiv.run (the ‘Organiser’).
This policy applies to visitors to the plovdiv.run website (the ‘website’), users with accounts, participants in races organised by the Organiser, parents and other legal representatives of participants under 18, and representatives of legal entities registering teams. Terms have the meanings given in the website’s General Terms and Conditions and Regulation (EU) 2016/679 (‘GDPR’).
The Organiser processes only the data needed for the purposes listed in the table:
Purpose | Data | Legal basis | Retention period |
|---|---|---|---|
Creating and maintaining a user account | Email; names where provided; a record of the user’s declaration that they are aged 14 or over; when Google sign-in is chosen — Google account identifier, names, email and verified-email status | Performance of a contract — Article 6(1)(b) GDPR | Until the account is closed |
Race registration and participation, including checking whether a person already has an active entry in the race | names, email, phone, date of birth, results category, selected distance, country, optional club and expected time, shirt size for individual distances, record of making the declaration of health condition and assumption of risk, emergency contact name and phone; for participants under 18 — details of the parent or other legal representative | Performance of a contract — Article 6(1)(b); for the emergency contact and defence of legal claims — legitimate interests under Article 6(1)(f) GDPR | Up to 5 years after the race for necessary contractual evidence; up to 30 days for other organisational data |
Corporate teams | Details of the legal entity’s representative and the participants’ details provided by that representative | Performance of a contract — Article 6(1)(b); legitimate interests, including defence of legal claims — Article 6(1)(f) GDPR | Up to 5 years after the race for necessary contractual evidence; up to 30 days for other organisational data |
Public participant list | first and last names; for participants under 14 — initials, or first and last names with express consent from a parent or other legal representative; country and club if supplied | legitimate interests — Article 6(1)(f) GDPR; publication of the first and last names of a participant under 14 — consent from a parent or other legal representative — Article 6(1)(a) GDPR | up to 30 days after the race |
Payments and invoicing | payer name and email, billing address, amount, currency and order number sent to the payment service provider; the payment result and technical identifiers received from it; for an invoice — name or company name, address, country, VAT number where applicable, and for an individual — the applicable identifier under Article 84 of the Bulgarian Tax and Social Insurance Procedure Code, including EGN or LNCH where it is a mandatory invoice detail or supplied by the recipient | performance of a contract — Article 6(1)(b) GDPR; for invoices and accounting records — legal obligation — Article 6(1)(c) GDPR | payment data — up to 5 years after the race; invoices and accounting records — the periods required by accounting and tax law |
Participant insurance | names, date of birth, distance | performance of a contract — Article 6(1)(b) GDPR | up to 5 years after the race |
Timing, rankings and publication of results | Names, results category, age group, club, country where provided, race number and recorded time | performance of a contract — Article 6(1)(b) GDPR; for the results archive — legitimate interests — Article 6(1)(f) GDPR; publication of the first and last names of a participant under 14 — consent from a parent or other legal representative — Article 6(1)(a) GDPR | the results archive is retained indefinitely as a history of the race, unless an objection is upheld; only initials are published for participants under 14, unless a parent or other legal representative expressly consents to publication of the first and last names; names are replaced with initials if consent is withdrawn |
Medical assistance following an incident and defence against specific legal claims | Health information learned while providing assistance | Vital interests — Article 6(1)(d) and Article 9(2)(c); for legal claims — Article 6(1)(f) and Article 9(2)(f) GDPR | Until the urgent need ends and the information is handed to the medical team; for specific legal claims — under the rule below |
Photography and video | Images of participants and spectators | Legitimate interests in reporting a public event — Article 6(1)(f); for advertising in which the participant is the main subject — consent under Article 6(1)(a) | Up to 5 years after the race; where based on consent — until withdrawal, but no longer than 5 years after the race |
Informational and advertising messages | Names and email | Consent — Article 6(1)(a) | Until consent is withdrawn |
Website security | IP address, device and browser information, access logs | Legitimate interests — Article 6(1)(f) | Up to 12 months from creation of the record |
Complaints, objections and requests | The information in the complaint or request and related correspondence | Legal obligation and legitimate interests — Article 6(1)(c) and (f) | Up to 5 years after the case is finally closed |
Measuring and improving Facebook and Instagram ads | consent and advertising identifiers, public visits and actions; at checkout and confirmed purchase — pseudonymised purchaser email, IP address, browser information, value, currency and a generic event product identifier | separate optional consent — Article 6(1)(a) GDPR | choice — up to 180 days; _fbp and _fbc — up to 90 days; order matching data — up to 7 days; details and retention by Meta — in the ad measurement section |
A participant who names an emergency contact informs that person that they have been named and about this policy. Emergency contact details are used only to contact that person if the participant has an incident and are deleted within 30 days after the race.
These periods are the maximum retention periods for each purpose. Data is deleted or anonymised sooner if it is no longer needed. The participation and team periods apply to copies for the particular race; data in an active account, accounting documents and the results archive follow their separate periods in the table.
For up to 5 years after a race, only data necessary to prove registration, performance of the contract and the declarations made is retained. Data used solely to organise the race, including emergency contact details and shirt size, is deleted within 30 days after the race.
For a specific dispute, incident or legal claim, only relevant evidence is retained, with restricted access, for the necessary period taking account of the applicable limitation period, its suspension or interruption, and until the proceedings are finally concluded and the decision enforced. This rule also applies to records relating to a specific security incident. The need for retention is reviewed periodically, and data is deleted or anonymised when that need ends.
The Organiser does not maintain medical records. In an emergency, health data is processed to protect vital interests where the person is physically or legally incapable of giving consent. The data is handed to the medical team and erased when the urgent need ends. Retention for legal claims is limited to what is necessary for a specific claim under Article 9(2)(f) GDPR.
The need to retain and publish photographs and videos is reviewed at least annually. Their retention period does not limit the right to object or withdraw consent.
The health and risk declaration is made by selecting a checkbox on the registration form. The Organiser stores only the record that the checkbox was selected and the date of selection as evidence that the declaration was made. The Organiser does not collect information about illnesses or other medical information during registration.
The details marked as required on the registration form are necessary to conclude the participation contract. Registration cannot be made without them.
A person under 14 cannot create an account. Their race registration is made by a parent or other legal representative, who supplies their details. A participant aged 14–17 registers personally through their own account with the consent of a parent or other legal representative.
Public participant list
After registration is complete, the participant’s first and last names, country and club, if supplied, are published in the website’s participant list. This enables participants and the public to check who is registered for each distance, participants to check their own registration, and the Organiser to ensure fairness and equal treatment in the race. The legal basis is legitimate interests under Article 6(1)(f) GDPR. Only initials are published for a participant under 14, unless the parent or other legal representative has expressly consented to publication of the first and last names. This consent may be withdrawn through the account or by emailing support@plovdiv.run without affecting participation. Before registration is completed, the participant, or the parent or other legal representative of a child under 14, is informed about publication. Unpaid, cancelled and incomplete registrations, reserve participants, emails, phone numbers, birth dates and emergency contact details are not published. A participant may object through their account or by emailing support@plovdiv.run; their details are then hidden without affecting participation. The objection for the specific entry remains effective until withdrawn by the participant or a parent or other legal representative acting for them. Details remain in the list until 30 days after the race.
Data supplied by another person
When an entry is bought for another person, the purchaser supplies the recipient’s email. After confirmed payment, the Organiser sends the recipient a personal link to complete registration. These details are processed to fulfil the order and send the invitation, based on legitimate interests under Article 6(1)(f) GDPR. The invitation identifies who supplied the email and links to this policy. The invitation is not an advertising message. The recipient may decline it or object to processing. If they accept the entry, their data is processed to perform the contract; representation rules apply to children. The same applies to invitations to team participants whose emails were supplied by a legal entity.
Data recipients
The Organiser discloses data only where necessary: to processors acting on the Organiser’s behalf and instructions — hosting, email, electronic timing and address suggestion providers, and people providing accounting services; to the payment service provider and, where Google sign-in is chosen, Google, acting as independent controllers; to the insurer providing participant insurance — the insurance data listed in the table, which the insurer processes as an independent controller; to the race medical team and emergency medical services in an incident; to photographers and videographers engaged by the Organiser; and to public authorities where required by law. The registration and invoicing system forms part of the website and is not a separate data recipient. For a company lookup, the company registration number is sent to the Registry Agency’s public portal, and country and VAT number to the European Commission’s VIES system.
Data is shared with sponsors and partners only with the person’s consent.
The insurer and insurance terms are published in the event rules once selected. Only the necessary data from the table is provided to arrange insurance. EGN is not collected for this purpose. For an insurance claim, the injured person provides the necessary health data directly to the insurer; the Organiser does not transmit it on their behalf.
Payments, invoices and lookups
Card payment takes place on BORICA’s payment page. To initiate and authenticate payment, the Organiser sends BORICA the payer’s name and email, billing address, amount, currency and order reference. Participants enter their card details directly on BORICA’s page. The Organiser does not receive or store the full card number, expiry date or security code. BORICA and the acquiring bank process payment data as independent controllers under their own privacy policies. The Organiser receives the payment result and the technical identifiers needed to verify it.
When entering an address, the website may suggest options using Amazon Location Service, provided by Amazon Web Services EMEA SARL as a processor acting on the Organiser’s behalf. Only the selected country, street and building number are sent to the service through the website’s server. Entrance, floor and apartment details, names, email, cookies and the user’s IP address are not sent. Address suggestion requests are processed in the Europe (Frankfurt) region. For personal data transfers outside the European Economic Area, AWS applies the safeguards in its data processing agreement, including standard contractual clauses where required. Suggestions are optional and the address may be entered manually.
Invoice details are collected only when an invoice is required by law or requested. EGN, LNCH or the applicable official identifier is used solely to identify the invoice recipient where it is a necessary invoice detail or supplied by the recipient; it is not required for ordinary participation or a payment confirmation. A foreign recipient is not required to have a Bulgarian EGN. Invoices, adjustment notes, payment and refund documents and accounting reports are stored in the website’s registration and invoicing system. Access is granted to the purchaser for their own documents, the Organiser and those providing its accounting services. Accounting access excludes declarations of health condition and assumption of risk and participation data. The legal basis is compliance with a legal obligation; data is retained for the applicable accounting and tax periods.
For a company lookup, only the company registration number is sent to the Registry Agency’s public portal, or only country and VAT number to the European Commission’s VIES system. EGN and LNCH are not sent. Suggested name and address remain editable. VIES verifies a VAT number and does not determine the tax treatment of the purchase.
Checking monetary gift credit requires the full code. Only monetary amounts, availability, reserved credit and dated anonymous amounts are shown; other people’s names, orders and private data are not disclosed. The code is not put in the page address or analytics events. Limited technical request data and a one-way representation of the code in access counters are used to prevent abuse, based on legitimate interests in protecting the service.
Google sign-in
When Google sign-in is chosen, Google also processes identification data as an independent controller. For users in the European Economic Area, the service is generally provided by Google Ireland Limited; Google LLC and affiliated companies may also be involved in processing. Data may be processed outside the European Economic Area. Google describes the applicable international transfer mechanisms at https://policies.google.com/privacy/frameworks, including Google LLC’s participation in the EU–US Data Privacy Framework and standard contractual clauses where needed. Google’s privacy policy is available at https://policies.google.com/privacy. Where the Organiser transfers data outside the European Economic Area, the applicable adequacy decision or another permitted safeguard under Chapter V GDPR is used.
Rights and contact
Everyone whose data is processed has the right to access their data and obtain a copy, request correction of inaccurate or incomplete data, request erasure where the data is no longer necessary or is processed unlawfully, request restriction of processing and portability of data they have provided, object to processing based on legitimate interests, including publication of their name in the results archive, and withdraw consent at any time without affecting the lawfulness of processing before withdrawal.
Consent to informational and advertising messages may be withdrawn at any time using the unsubscribe link in each message or an email to support@plovdiv.run.
Requests should be sent to support@plovdiv.run. The Organiser responds within one month, which may be extended by a further two months for complex or numerous requests; the person is notified of the extension.
Anyone may complain to the Bulgarian Commission for Personal Data Protection: 2 Professor Tsvetan Lazarov Boulevard, Sofia 1592, www.cpdp.bg.
Cookies and analytics
The website uses essential cookies for its operation and account sign-in. Optional analytics through Amazon Web Services (AWS) and ad measurement through Meta have separate choices, both off by default, in ‘Cookie settings’. AWS analytics uses no analytics cookies and includes no names, emails or personal entry details. Allowing analytics does not allow ad measurement. The choice is stored for up to 180 days, after which it is requested again. Refusal does not prevent use of the website, purchase or participation.
Ad measurement through Meta
Only after separate consent under Article 6(1)(a) GDPR does the website use Meta Pixel and Conversions API to determine which Facebook and Instagram ads lead to interest and paid purchases and to improve ad delivery. Meta may associate the data received with a Facebook or Instagram account. This processing is not anonymous and is not needed to buy an entry.
Meta Pixel loads only on the public home pages, Hill Dash pages and privacy policy. It records a visit, a race selection and an accepted newsletter request. An accepted request does not necessarily mean a new subscriber. Meta may receive the public page and referring website addresses, the time and type of action, a generic identifier for the selected distance, language, IP address, device and browser information and advertising identifiers. Meta’s code does not load on sign-in, account, registration, order or payment pages and does not read their fields. Automatic event collection and automatic advanced matching are disabled.
With the same separate consent, the server sends Conversions API events when checkout starts and when a successful payment with a positive value is confirmed. A purchase is not recorded merely because a confirmation page opens, an order is unpaid, payment is declined or an entry is free. Data includes the event time and type, an opaque technical identifier to avoid duplicate counting, value, currency, a generic event product identifier, a public website address, advertising identifiers and the IP address and browser information captured when checkout starts. For matching, the purchaser’s email is also sent after normalisation and one-way SHA-256 transformation. This is pseudonymisation, not anonymisation: Meta can match the value to one of its users. Names, phone numbers, billing addresses, gift recipients’ details, data from runner registrations, including children’s registrations, birth dates, the health declaration, emergency contacts, payment tokens and card details are not sent.
After consent, the _fbp cookie recognises the browser and _fbc stores an ad-click identifier if one is present in the address. They are stored for up to 90 days. The ad-click identifier is not stored for this purpose before consent. The pr_meta_consent cookie and its corresponding local-storage record retain the advertising choice for up to 180 days. The technical consent record contains its version, time, expiry and any withdrawal; the server stores only a one-way transformation of the permission identifier. Matching data attached to the order is kept for at most 7 days from checkout and cleared earlier after the Purchase event is sent, consent is withdrawn or permission expires. The minimal record of whether the event was sent or suppressed, with its technical identifier, time, value and currency, remains with the order evidence for its retention period, without matching data.
The recipient is Meta Platforms Ireland Limited, Ireland. Meta’s joint-processing addendum applies to collection and transmission of event data: https://www.facebook.com/legal/terms/businesstools_jointprocessing. Subsequent processing by Meta is governed by its policy: https://www.facebook.com/privacy/policy/. Meta may process data outside the European Economic Area, including in the United States. Applicable transfer mechanisms are described in Meta’s policy and at https://www.facebook.com/legal/EU_data_transfer_addendum, including adequacy decisions and standard contractual clauses where applicable. Retention and uses of data already received by Meta are determined by its terms and policy; the 90-day cookie duration is not a retention period for all data held by Meta. More about its cookies: https://www.facebook.com/privacy/policies/cookies/.
Consent may be withdrawn at any time through ‘Cookie settings’ at the bottom of the page. The website stops future browser events and deletes _fbp and _fbc. A withdrawal request is also sent to the server; once received, unsent events for that permission are suppressed and matching data is cleared. If offline, the request is retained for retry when connectivity returns while browser ad measurement stays off. Withdrawal does not automatically erase data Meta has already received and does not affect the lawfulness of processing before withdrawal. Rights may be exercised by emailing support@plovdiv.run or using the contact and data controls described in Meta’s policy.
Security
The Organiser applies technical and organisational measures to protect data, including encrypted connections and restricted access. Participant accounts use one-time email codes or Google sign-in; the Organiser does not create or store passwords for these accounts. Administrative access requires a passkey and a code from an authenticator app. The Organiser does not carry out automated decision-making, including profiling, that produces legal effects concerning individuals.
Policy changes
The Organiser may amend this policy by publishing the new text on the website with the date of the change. Account holders are notified of material changes by email.
This version of the policy (2026-11-05.2) takes effect on 5 November 2026 and replaces version 2026-11-05 of the same date. Previously accepted versions and their evidence are retained.