Privacy policy
for the plovdiv.run website and the races organised through it
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, guardians and curators 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; dates of the last sign-in and last race registration | Performance of a contract — Article 6(1)(b) GDPR | until the account is closed; an account with no sign-in and no race registration for 3 years is closed after the user receives 30 days’ advance warning by email |
Race registration and participation, including checking whether a person already has an active entry on the same race day | names, email, phone, date of birth, gender, results category, selected distance, country, town or city of residence, 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, guardian or curator | 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 |
Planning the race organisation and advertising by location | the participant’s town or city of residence; the purchaser’s answer to “How did you hear about Plovdiv Run?”, if given | legitimate interests — Article 6(1)(f) GDPR | up to 30 days after the race; afterwards only aggregate counts without personal data are kept |
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 |
Matching bank transfer payments to orders and accounting | the payer’s name and account (IBAN), the amount, date and payment reference of the transfer, received from the Organiser’s bank | legal obligation — Article 6(1)(c) GDPR (Accountancy Act, VAT Act) | 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 |
Evidence of notice and closure of an inactive account | email and account identifier; a copy of the warning, its status and dates of sending, delivery, cancellation or account closure | legitimate interests in demonstrating performance and defending legal claims — Article 6(1)(f) GDPR | up to 5 years after account closure or cancellation of the warning; for a specific legal claim — under the separate rule in this policy |
Referral programme | referrer’s account, link to the referred participant, the referred participant’s paid registration, accumulated rewards | performance of a contract — Article 6(1)(b) GDPR | up to 30 days after the race for programme administration; necessary accounting and contractual evidence and data for specific legal claims follow the separate retention periods in this policy |
Website usage statistics through AWS | the public path of the page visited, action type, selected distance or section, contact or sharing method, social network, percentage of the page viewed, and Hill Dash game or performance measurements; analytics records do not include names, emails, IP address, device or browser type, or cookies | consent — Article 6(1)(a) GDPR | 30 days from creation of the record, after which automatic deletion is triggered |
Visit and purchase statistics through Google Analytics 4 | random browser, session and purchase identifiers and a separate pseudonymous identifier for a consenting user; public actions, registration and payment starts, the payment method chosen, technical payment outcomes, purchases and refunds; source and campaign, entry type and quantity, net value, VAT and currency; no personal participation fields | consent — Article 6(1)(a) GDPR | Google Analytics — 14 months for user-level and event-level data; aggregated reports may be retained longer; cookies, permission and linking context held by the website — up to 365 days, cleared earlier on withdrawal or expiry; campaigns — under the periods in the separate section |
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 |
The Filipa assistant on the phone line, in the website chat and in a voice call from the website: answering questions, preparing a registration, status enquiries and requests about an existing order, connecting the person with a member of the team | the phone number the person calls from; voice and audio recording of the call, including the part with a member of the team; text of the call produced by automatic speech recognition, or what is written in the chat; details the person gives (for example names, date of birth, gender, town, race, order number); digits entered on the keypad; an automatically prepared short summary and the actions taken; for calls and chats on the website — a random conversation marker, the account if the visitor is signed in, and a hash of the IP address | taking steps at the person’s request before entering into a contract and performance of a contract — Article 6(1)(b) GDPR; legitimate interests in quality of service, evidence of requests made on the phone or in the chat and protection against misuse — Article 6(1)(f) GDPR | audio recording — 30 days, including the copy held by the telephone switchboard provider; text, summary and phone number — up to 90 days; where they form part of an order, complaint or request — the periods for those; website conversation marker and IP address hash — up to 30 days |
A registration started on the phone or in the chat | names, date of birth, gender, town, phone number and race of each runner; a six-digit code (only its hash is kept); how far the registration on the website has got | taking steps at the person’s request before entering into a contract — Article 6(1)(b) GDPR | the draft — up to 72 hours, then deleted within 7 days; the code is valid for 30 minutes and opens the draft once |
Identity checks for enquiries and changes through the assistant | the names and date of birth given (only compared, not stored separately); a hash of the phone number and the number of attempts; email confirmation by choosing the number said by the assistant, or a code by text message; for calls and chats on the website — the account the visitor is signed in to | performance of a contract — Article 6(1)(b) GDPR; legitimate interests in protecting the order’s data from third parties — Article 6(1)(f) GDPR | attempts — up to 90 days; a confirmed action — as part of the order’s history |
Text messages during a call | phone number, message text, the mobile operator’s delivery report | taking steps at the person’s request — Article 6(1)(b) GDPR | delivery report — 14 days |
Measuring and personalising Plovdiv Run ads on Facebook, Instagram and Google, including audiences | consent and advertising identifiers (_fbp, _fbc, gclid, wbraid, gbraid), a pseudonymous identifier; visits to public pages, race choice, taps on the phone number or email; at registration, payment and purchase — the purchaser’s email, phone number, names, town and country after SHA-256 transformation (to Google, town and country in plain form), IP address, browser information, value, currency and a generic race product identifier | separate optional consent — Article 6(1)(a) GDPR | consent — up to 365 days; _fbp and _fbc — up to 90 days; matching data — up to 7 days; audiences — up to 180 days at Meta and up to 540 days at Google; details and retention by Meta and Google — in the advertising sections |
Evidence of the choice on analytics and advertising | a one-way transformed (hashed) random identifier of the consent; purpose and version of the consent; the edition of the policy in force at the time of the choice; where it was given (window, bar or ‘Privacy settings’); time, expiry and withdrawal; the account the consent is linked to, while it is valid | legitimate interests in demonstrating consent and that the choice was respected — Article 6(1)(f) and Article 7(1) GDPR | up to 5 years after the consent expires or is withdrawn |
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 curator.
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.
When registering, the town or city where the participant lives is given, and the purchaser may say how they heard about the race. The Organiser uses this information only in aggregate — how many participants come from a given town or region and how many orders come from each source — to plan the organisation and where to advertise. The town is not published in the participant list or in results. Only the purchaser’s town is passed to advertising platforms, and only with consent to advertising, as described in the advertising sections; the answer on how they heard about the race is not passed to them. Anyone may object to this processing at support@plovdiv.run.
Data supplied by another person
When an entry is bought for another person, the purchaser supplies the recipient’s email and, optionally, their entry details: first and last names, date of birth, gender, country, town or city of residence, telephone, shirt size, club, expected finish time and the name and telephone of an emergency contact, and for a participant under 18 the details of a parent, guardian or curator. The purchaser supplies these details with the recipient’s knowledge. After confirmed payment, the Organiser sends the recipient a personal link through which they check, correct or complete their details and confirm registration. Until confirmation, the supplied details are available only to the purchaser, the recipient and the Organiser and are not published. After confirmation, the purchaser sees only the recipient’s names and email and whether the registration is confirmed; the recipient’s other details are not available to them. If the recipient declines the invitation or does not confirm registration in time, the details the purchaser supplied for them are deleted within 30 days, except the email and the order details needed as evidence of the order. 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 details 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 team participants whose emails and details 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, address suggestion and website usage statistics (Amazon Web Services EMEA SARL) providers, Google Ireland Limited for Google Analytics 4 and enhanced conversions, the providers of the Filipa assistant (Anthropic Ireland, Limited, Soniox, Inc., ElevenLabs, Telnyx LLC and the Zadarma telephone switchboard) described below, and people providing accounting services; where consent to advertising is given — to Meta Platforms Ireland Limited, which is a joint controller for the collection and transmission of the data and an independent controller for its subsequent processing, and to Google Ireland Limited, which is an independent controller for personalised ads and audiences in Google Ads; to the payment service provider, the Organiser’s bank (UniCredit Bulbank AD) 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.
When a person calls the phone line or talks or chats with the assistant on the website, data is also provided to the following processors: the telephone switchboard provider Zadarma (IP Telecom Bulgaria LTD, Bulgaria, and its affiliated companies under Zadarma’s data processing agreement) — incoming calls, transfers to a member of the team and the recording of that part of the call; Telnyx LLC (USA) — the phone connection and carrying the audio to the assistant, processed in Frankfurt; Soniox, Inc. (USA) — speech recognition, processed in the European Union; ElevenLabs (Eleven Labs Inc., USA, and ElevenLabs Poland sp. z o.o., Poland), processed in the USA — the assistant’s synthetic voice, for which it receives the text the assistant speaks; Anthropic Ireland, Limited (Ireland), processed in the USA by Anthropic, PBC — the Claude language model that conducts the conversation and prepares the summary; and Amazon Web Services EMEA SARL (Luxembourg) — sending text messages and emails and storing the recordings and text of conversations in the European Union.
The Organiser has concluded data processing agreements with the providers of the phone line and the assistant that prohibit them from using the conversations to train models or for any other purposes of their own. Telnyx, Soniox, ElevenLabs and Anthropic are companies based in the United States of America or process the data there. Data is transferred to Telnyx LLC and Eleven Labs Inc. on the basis of the European Commission’s adequacy decision under the EU–US Data Privacy Framework, under which both companies are certified. Data is transferred to Soniox, Inc. and Anthropic on the basis of standard contractual clauses adopted by the European Commission and included in the data processing agreements.
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 paying by bank transfer, the Organiser receives no card details. From its own bank statement, it sees the payer’s name and account, the amount, date and payment reference of the transfer and uses them only to match the payment to the order and for accounting. If the transfer is made at the office of a payment service provider, such as EasyPay, the Organiser receives the details that the provider passed on with the transfer.
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.
Phone line, chat and voice assistant
Filipa, a voice assistant that uses artificial intelligence, answers the Plovdiv Run phone line (+359 32 509 342), the website chat and voice calls from the website. At the start of every conversation the assistant says that it is an artificial intelligence assistant and that the call is recorded, and confirms that it is artificial intelligence whenever asked; the chat shows this at all times. A person who does not want the call to be recorded may contact the Organiser by email at support@plovdiv.run. The assistant is not intended for children under 14; a child is registered by a parent or other legal representative.
When a person calls the phone line, the Organiser processes the phone number the person calls from, their voice and the audio recording of the call, the text of the call produced by automatic speech recognition, the details the person gives (for example names, date of birth, gender, town, race, order number), the digits entered on the phone’s keypad, and an automatically prepared short summary of the call and the actions taken during it. In the website chat, what is written, the summary and the actions taken are processed; in a voice call from the website, the voice and audio recording of the call, the text, the summary and the actions. The microphone is used only during a call the visitor starts with the call button and is released when it ends. Calls and chats on the website also use a random conversation marker, linked to the visitor’s account if they are signed in, and a hash of the IP address, used only to limit misuse.
The data is processed to answer the person’s question, to prepare a registration that the person completes themselves on the website with a code given by the assistant or with a button in the chat, to carry out a request about an existing order, to connect the person with a member of the team or call them back, and for quality of service and the security of the line.
A phone call is recorded as audio from start to finish, including the part with a member of the team if the assistant connects the person with one; a voice call from the website is also recorded. The recording, text and summary are available in the Organiser’s organiser console only to its staff who need them for their work. They are used to check what was said and done, for call-backs, to handle a complaint or request and to improve the service. They are not used for advertising and are not shared with advertising platforms.
The assistant does not ask about the person’s health. If the person shares such information, it is not included in the summary and is deleted together with the recording and text of the call.
The details the person gives for a registration (names, date of birth, gender, town, phone number, race) are kept as a draft for up to 72 hours. On the phone the assistant gives a six-digit code. Entering it at plovdiv.run/en/code opens the draft in the ordinary registration, where the person checks and, if needed, corrects the details; in the chat the draft opens with a button. The code is valid for 30 minutes and opens the draft once. While the call lasts, the assistant sees only how far the registration on the website has got (page opened, email confirmed, order created, payment method chosen, payment made), not what the person enters. The draft is deleted within 7 days after it expires. The registration is completed under the rules for ordinary registration, including those for participants under 18.
Where the conversation concerns a registration or an order, the data is processed to take steps at the person’s request before entering into a contract and to perform the contract (Article 6(1)(b) GDPR). For quality of service, evidence of requests made on the phone or in the chat and protection against misuse, including keeping the audio recording, the legal basis is the Organiser’s legitimate interests (Article 6(1)(f) GDPR).
No contract is concluded and no payment is taken on the phone or in the chat. Registration takes place only on the website, after the person confirms their email address, reviews and accepts the terms and chooses how to pay. Card numbers are not taken on the phone or in the chat.
The person’s voice is not used to establish their identity (no voice biometrics). Identity checks on the phone have two levels.
When the person calls from a phone number recorded on an order, the assistant asks for the names and date of birth of a runner on the order and compares them with the order. Names are compared by sound, so that speech recognition errors do not get in the way, and both names must match; the date of birth is compared exactly. If they match, the assistant says, for that runner only, whether their entry is paid, which race it is for, whether a bank transfer is awaited and what is missing. Details of the other runners on the order are given only after email confirmation. Nothing is sent for this enquiry. The names and date of birth given are not stored separately; only the fact of the attempt is kept, with a hash of the phone number, for up to 90 days, to limit attempts — up to three in one call and up to five from one number a day. If they do not match, the answer is the same whether or not an order exists. So that difficult names are recognised correctly, the names of the runners on active registrations made with the number the person calls from (at most 20) are given to speech recognition as hints at the start of the call; they are held in memory for the call only, are not passed to the language model, are not stored and are not said to the person.
Before other details are disclosed or a change is made (to a runner’s details, cancelling an unpaid order, an invoice, resending a confirmation, a request to the team), the Organiser emails the address on the order. The email states exactly what is being confirmed and shows three numbers. The assistant says one of them, and the person chooses it in the email. The confirmation is valid for 10 minutes, for the current call and that action only; choosing a different number cancels it. What was confirmed and when is kept as part of the order’s history. If the email does not arrive, the assistant can send a six-digit code by text message to the number on the order or connect the person with a member of the team.
In the chat and in a voice call from the website, the assistant sees and changes only the registrations of the account the visitor has signed in to with an email code. A change of details, cancelling an unpaid order and requesting an invoice are carried out only after the visitor presses ‘Confirm’ in the chat or clearly confirms in the call.
The assistant does not confirm or deny whether a phone number or email address has an account or an order.
If the assistant connects the person with a member of the team, the call is transferred through the Organiser’s telephone switchboard and continues to be recorded. The member of the team sees the text and summary of the conversation with the assistant, so that the person does not have to repeat themselves. If nobody answers, the assistant offers to take a message, which the team receives by email and text message together with the text of the call so far. Calls from the website are not transferred; the assistant can pass on a message and a phone number for a call back.
When a person has started a registration on the website and has not paid for it, and has no paid registration afterwards, the assistant may call them on the phone number the person gave for themselves in the registration – once, and if the person does not answer, once more no earlier than the next day. The purpose is to check that everything is all right, to help with a technical problem or an interrupted payment and, if the person wishes, to email them a link to the registration they started or to connect them with a member of the team. The legal basis is the Organiser’s legitimate interest under Article 6(1)(f) GDPR in not leaving without help the people who started a registration themselves. Calls are made on weekdays between 10:00 and 19:00 and on Saturdays between 10:00 and 14:00, and when the person asks to be called again, at the agreed time between 8:30 and 21:00. At the beginning of the call the assistant introduces itself, says that it is an artificial intelligence and that the call is recorded, and says which registration it is calling about; it gives the amount, the payment method and other details of the registration only after the person answers as the one who started it. The phone number, name and gender from the registration, the race, the amount and the stage the registration reached (no card details) are processed, together with the outcome of the call and its recording under the terms and periods described in this section. The call is made through the Zadarma telephone switchboard and Telnyx LLC, listed under “Recipients of the data”.
The person may object to these calls at any time – in the call itself (for example by saying “do not call me”), by phone or by email to support@plovdiv.run. Their number is then marked and they receive no more such calls; the mark is kept for as long as it is needed to respect the objection. Data about the calls and about agreed call-backs is erased 90 days after the call.
So that the person does not have to repeat themselves, in a new conversation with a phone number the assistant uses the short summaries of the conversations with that number from the last 30 days and the data about a call about an unfinished registration from the last 7 days. These summaries are not disclosed to the caller before the caller is recognised in the way described in this section.
The audio recording is deleted 30 days after the call, including the copy held by the telephone switchboard provider. The text and summary of the call or chat and the phone number the person called from are kept for up to 90 days, unless they form part of an order, complaint or request, for which the periods in the table apply. The website conversation marker and the IP address hash are deleted within 30 days.
The assistant makes no decisions with legal effects for the person. Refunds, cancelling a paid entry and exceptions to the rules are decided by a member of the team.
Text messages
The Organiser sends a text message only at the person’s request during the call or when no other way is possible: a link to complete the registration if the person cannot open the website at that moment, or a verification code if the email confirmation does not arrive. The mobile operator’s delivery report is kept for 14 days so that the Organiser can establish whether the message was delivered. Promotional text messages are not sent without separate consent. Links in the messages lead only to plovdiv.run.
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, object at any time to processing for direct marketing, including profiling related to it, 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.
A person who has called the phone line or spoken with the assistant on the website may request access to the audio recording, text and summary of their conversation, object to their retention for quality of service, or request their erasure — by email to support@plovdiv.run or on the phone, where the assistant passes the request to the team. Before providing a recording or text of a conversation, the Organiser checks that the request comes from the person who had the conversation.
Anyone may complain to the Bulgarian Commission for Personal Data Protection: 2 Professor Tsvetan Lazarov Boulevard, Sofia 1592, www.cpdp.bg.
Cookies, analytics and advertising
If the visitor consents to statistics, the website uses Google Analytics 4 and AWS statistics to measure visits and purchases. If the visitor consents to advertising, the website uses Meta Pixel, the Conversions API and Google’s advertising features to measure Plovdiv Run ads on Facebook, Instagram and Google and to show personalised ads. Without consent, these tools are not loaded and no data is sent to Google or Meta for these purposes. The details are set out below.
The website uses essential cookies for its operation and account sign-in. The chat with the Filipa assistant keeps a random marker of the current conversation in the browser (sessionStorage) until the tab is closed, and a note in localStorage that the assistant’s introduction has already been shown. Both are necessary for a service the visitor chooses to use and need no consent. There are two optional purposes — ‘Analytics’ (Google Analytics 4 and AWS statistics) and ‘Advertising’ (Meta and Google’s advertising features) — and both stay off until the visitor allows them. Until the visitor has chosen, every page of the website shows a question with two identical buttons, ‘Accept’ (allows both purposes) and ‘Decline’ (refuses both purposes), and a ‘Settings’ button in which each purpose can be allowed separately. On the home page and the Hill Dash game pages the question appears in a window over the page; on other pages it appears in a bar at the bottom, so that it does not get in the way of reading or registering. The choice can be changed at any time with the ‘Privacy settings’ button at the bottom of the page. Allowing statistics does not allow advertising. Refusal does not prevent use of the website, purchase or participation and does not change prices.
Google’s and Meta’s code loads only after the corresponding consent and only on these public pages: the home page (plovdiv.run, in Bulgarian and in English), the Hill Dash game pages, the privacy policy, the general terms and conditions and the event rules. It does not load on sign-in, account, registration, order or payment pages, in the participant list or on personal links, and does not read their fields. The addresses that reach Google and Meta are limited to these pages and approved generic campaign labels.
Consent is valid for 365 days, after which the question is shown again. A refusal — including a refusal of only one of the purposes — and a withdrawal are remembered for 183 days; until then the question is not shown again, unless the Organiser materially changes the purposes, the data collected or the recipients, in which case all visitors are asked again. The question is also shown again when the choice has been deleted from the browser or the visitor uses another browser or device. A previous choice covering AWS statistics alone is not used as consent to Google Analytics. Consent given before edition 2026-11-21 of this policy is not used for the new events and data it describes, and the visitor is asked again; events recorded earlier on the basis of such consent are sent only with the data described in the previous edition and only while that consent is valid.
When consent is given, the browser sends the website’s server a random identifier of the consent. The server keeps only its one-way transformation (hash), together with the purpose and version of the consent, the edition of this policy in force at the time of the choice, where it was given (window, bar or ‘Privacy settings’), the time and the expiry. On withdrawal, the record is marked as withdrawn. A refusal without earlier consent is kept only in the browser and counted only in the aggregate counters described below. The record contains no IP address, browser information or email. When a consenting visitor signs in to their account or makes a purchase, the consent is linked to their account, so that the choice is respected at the purchase and consent given by another person on the same browser is not used. The records are kept for up to 5 years after the consent expires or is withdrawn, on the basis of the Organiser’s legitimate interests in demonstrating that it obtained consent and respected the choice (Article 6(1)(f) and Article 7(1) GDPR).
The website counts how many times a day the question is shown and how many times ‘Accept’ or ‘Decline’ is chosen or a choice is saved in ‘Settings’ — separately for the window and the bar and for each language. The counters are totals only: they contain no identifier, IP address or browser information, are not linked to any visitor and nothing is stored in the browser for them. The Organiser uses them to judge whether the question is clear and convenient.
The limited statistics records sent to AWS are stored in AWS Amazon CloudWatch for up to 30 days. Amazon Web Services EMEA SARL acts as a processor on the Organiser’s behalf. The safeguards described in this policy for AWS processing and transfers outside the European Economic Area apply to these records.
The following cookies and browser records are used for analytics and advertising. The record of the choice itself is needed to respect the choice and requires no consent (Article 4a(4) of the Bulgarian Electronic Commerce Act); the others are set and read only after consent, in line with Article 4a(1) of the same Act. When the browser connects to Google and Meta, they may also set and read their own cookies on their own domains (for example google.com and facebook.com) if the browser allows it; these are described in their cookie policies.
Cookie or record | Set by and accessible to | Purpose | Duration |
|---|---|---|---|
Record of the choice in the browser’s local storage (localStorage) | the website; stays in the browser | keeps the choice on analytics and advertising, its random identifier, version and expiry, with consent to advertising also the address, without parameters, of the last page visited among those listed above and, when offline, unsent withdrawal requests until they are sent | with consent — 365 days; after a refusal or withdrawal — 183 days |
pr_meta_consent | the website (the browser and the website’s server) | keeps the consent to advertising and its random identifier, so that advertising events are sent only with consent, and the address, without parameters, of the last page visited among those listed above, which is sent to Meta as the address of the registration and payment events | until consent expires, at most 365 days |
pr_ga4_context | the website (the browser and the website’s server) | links the consent to statistics with the Google Analytics browser and session identifiers, so that the registration, payment and purchase can be reported | until consent expires, at most 365 days |
_ga, _ga_<identifier> | the Google Analytics code on the plovdiv.run domain; the values are sent to Google | random browser and session identifiers for statistics | at most 365 days, not renewed on every visit |
pr_statistics_attribution | the website (the browser and the website’s server) | the first and the most recent campaign the visitor came from: source, channel and generic labels | up to 30 days, not longer than consent |
pr_advertising_attribution | the website (the browser and the website’s server) | the first and the most recent advertising campaign and the Google ad-click identifiers (gclid, wbraid, gbraid) | up to 30 days, not longer than consent |
_fbp | the website, which also renews it from its server; the value is sent to Meta | a random browser identifier for Meta | 90 days from the last renewal, not longer than consent |
_fbc | the website, when the address contains a Meta ad-click identifier (fbclid); also renewed by the website’s server; the value is sent to Meta | the identifier of the ad click | 90 days from the last renewal, not longer than consent |
_gcl_au and other cookies whose name begins with _gcl | Google’s code may set them with consent to advertising; the values are sent to Google | linking clicks on Google ads with visits and purchases | up to 90 days according to Google; deleted when consent is withdrawn or expires |
A note in sessionStorage for a single reload | the website; stays in the browser | reloads the page once without the referring website’s address before Meta’s code loads | until the tab is closed |
Statistics through Google Analytics 4
Only after express consent to statistics under Article 6(1)(a) GDPR does the Organiser use Google Analytics 4 to measure visits, actions on public pages and entry purchases. Google’s code loads only after consent and only on the pages listed in the section ‘Cookies, analytics and advertising’. Browser events cover public page views, race selections, percentage of the page viewed, website actions and technical performance measurements. Addresses are limited to public pages and approved generic campaign labels; private links and form-field contents are not sent.
With the same consent, the server records registration and payment starts, the payment method chosen (card or bank transfer), technical payment failures, confirmed paid purchases and amounts actually refunded. A page opening, unpaid order, declined payment or free entry is not counted as a paid purchase. Data includes random browser, session and purchase identifiers, a separate pseudonymous identifier for a consenting user, action type and time, payment method, distance, quantity, discount, value excluding VAT, VAT and currency. Statistics permission alone does not enable advertising features or send emails, phone numbers, names or their hashes. Billing addresses, card details, date of birth, gender, the declaration of health condition and assumption of risk, the emergency contact and other runners’ data are excluded under every choice. Granular location and device collection remains disabled.
When connecting to Google, the browser sends its IP address and technical device and browser information. According to Google, IP addresses from EU traffic are used to derive approximate location and discarded before data is logged. This does not mean the IP address never reaches Google. The website does not add an IP address to server analytics events. The pseudonymous identifier and optional advertising features are described separately below.
The Google Analytics cookies and their durations are listed in the table in the section ‘Cookies, analytics and advertising’. User-level and event-level data in Google Analytics is retained for 14 months, with monthly automatic deletion after expiry. New activity does not reset this period. Standard aggregated reports are not deleted by this setting and may be retained longer.
In the website’s system, the link between permission, browser, session and payment is retained until permission expires, for no more than 180 days, to report the confirmed purchase and subsequent amounts actually refunded. It is cleared earlier on withdrawal. Minimal technical event records are retained for up to 180 days, and the permission record under the rule on evidence of the choice in the section ‘Cookies, analytics and advertising’; after the linking context is cleared, they contain no browser or session identifiers or complete transmitted message. Financial records and summaries of entry type, quantity and value are retained under separate accounting and contractual periods.
Google Ireland Limited acts as a processor of analytics data on the Organiser’s behalf under https://business.safety.google/adsprocessorterms/. Google may process data outside the European Economic Area, including in the United States. Transfers use the mechanisms in that agreement, including applicable adequacy decisions and standard contractual clauses. More information: https://policies.google.com/privacy.
Consent to Google Analytics may be withdrawn at any time through ‘Privacy settings’. The website stops new browser events and deletes its Google Analytics cookies. The request is also sent to the server; once received, unsent events for that permission are suppressed and associated identifiers are cleared. If offline, the request is retained for retry while browser statistics remain off. Withdrawal does not automatically delete data Google has already received. Rights requests may be sent to support@plovdiv.run.
Advertising on Facebook and Instagram (Meta)
Only after separate consent to advertising under Article 6(1)(a) GDPR does the website use Meta Pixel and the Conversions API to determine which Facebook and Instagram ads lead to interest, registrations and paid purchases, to improve ad delivery and to show personalised Plovdiv Run ads. Meta associates the data received with a Facebook or Instagram account, if there is one. This processing is not anonymous and is not needed to buy an entry.
Meta Pixel loads only on the pages listed in the section ‘Cookies, analytics and advertising’. It records a page being opened (PageView), a race being chosen (ViewContent — with the generic identifier of the race and its price in euro, when known) and a tap on the contact phone number or email (Contact). Meta receives the page address without personal parameters and, if the browser passes it on, the name of the referring website without its specific page or the public plovdiv.run page the visitor came from, the time and type of action, language, IP address, device and browser information, the _fbp and _fbc cookies and, for a visitor signed in to their account, the pseudonymous identifier for Meta described in the section on measurement across devices. Automatic event collection and automatic advanced matching are disabled, and the Pixel does not read the fields on the pages.
The website also sends the same events through its server to Meta’s Conversions API, with the same event identifier, so that Meta counts them only once, including when the browser blocks the Pixel. The website’s server adds the IP address and browser information from the request, the _fbp and _fbc cookies and the pseudonymous identifier and, if the visitor is signed in to their account and the consent is linked to the same account, the matching data of that account described below. In its response the server renews the _fbp and _fbc cookies in the browser, for no longer than 90 days and the duration of consent, because some browsers shorten the life of cookies set by the page’s code.
With the same consent, the server sends Meta an event through the Conversions API when a registration is saved in the account before payment (CompleteRegistration), when payment by card or bank transfer starts (InitiateCheckout) and when a successful payment with a positive value is confirmed (Purchase). 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, the generic product identifier of the race, the public address of the last visited page among those listed in the section ‘Cookies, analytics and advertising’, the IP address and browser information, _fbp and _fbc and the pseudonymous identifier, and at payment and purchase also the number of entries, their prices, the total amount including VAT and the currency.
For matching with Meta’s users, these events also carry the purchaser’s data: email, phone number in international format, first name and last name (in Cyrillic and in Latin script under the Bulgarian Transliteration Act), town (in Latin and in Cyrillic script) and country. They are taken from the purchaser’s own registration as a runner; when the purchaser does not take part in the race, only the name, email and phone number they gave in the order are used, with Bulgaria as the country. If the registration gives no country, Bulgaria is used as well. Before sending, this data is normalised and transformed one way using SHA-256. This is pseudonymisation, not anonymisation: Meta can match the values to one of its users, so they remain personal data.
Date of birth, gender, club, T-shirt size, expected finish time, the declaration of health condition and assumption of risk, the emergency contact, data of other runners on the order and of gift recipients, parent, guardian or curator details from a runner’s registration, the answer to ‘How did you hear about Plovdiv Run?’, free text, the order number, the billing address, payment tokens, card details, conversations and chats with the assistant and personal links are never sent to Meta or Google. When a date of birth on the order or on another order from the purchaser’s account shows that the purchaser is under 18, when a date of birth on the order shows that a runner is under 14, or when a place on the order is registered by a parent or guardian, no events are sent to Meta and no matching data is sent to Google for that order. When such a purchaser under 18 is signed in to their account, the website does not load Meta Pixel, sends no browser events to Meta and does not turn on Google’s advertising features.
The _fbp, _fbc and pr_meta_consent cookies and their durations are listed in the table in the section ‘Cookies, analytics and advertising’. The ad-click identifier is not stored before consent. Matching data attached to the order is kept for at most 7 days from when the registration is saved or payment last starts and cleared earlier after the Purchase event is sent, consent is withdrawn or permission expires. Matching data for other events is kept only until they are sent, for at most 7 days. 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.
With the same consent, the Organiser may create audiences in Meta from these events — for example people who visited the website, started a registration or bought an entry — to show them Plovdiv Run ads or to stop showing them ads once they have bought an entry. From such an audience, Meta may also create a similar audience of other Meta users with similar interests. Membership in an audience lasts at most 180 days from the person’s last event. The Organiser sees only the approximate size of the audience, not the names or emails of the people in it, and does not upload lists of customers’ emails or phone numbers to Meta. Showing personalised ads is profiling for direct marketing; it produces no legal effects for the person.
The recipient is Meta Platforms Ireland Limited, Ireland. For the collection of data through Meta Pixel and the Conversions API and its transmission to Meta, the Organiser and Meta Platforms Ireland Limited are joint controllers under Article 26 GDPR. Under their arrangement, the Organiser is responsible for obtaining consent and providing the information in this policy, and Meta is responsible for the exercise of rights regarding the data it has received. For matching the events and for the Organiser’s ad reports, Meta acts as a processor on the Organiser’s behalf, and for subsequent processing of this data for its own purposes Meta is an independent controller. Individuals may exercise their rights with both the Organiser and Meta. Meta’s Controller Addendum applies to the collection and transmission of event data (https://www.facebook.com/legal/controller_addendum), and information on the joint processing is at 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. According to Meta, transfers to Meta Platforms, Inc. in the United States rely on the European Commission’s adequacy decision for the EU–US Data Privacy Framework (Implementing Decision (EU) 2023/1795), under which Meta Platforms, Inc. is certified, and where necessary on standard contractual clauses; details are in Meta’s policy and at https://www.facebook.com/legal/EU_data_transfer_addendum. 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 as easily as it was given — through ‘Privacy settings’ at the bottom of the page. The website stops future browser events and deletes _fbp, _fbc and the other advertising cookies. 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. The person leaves Meta audiences when their membership in them expires.
Campaigns and measurement across devices
Only with the corresponding permission does the website retain the first and most recently recorded campaign: source, channel, generic labels or technical campaign and advertisement identifiers, and date. Separate statistics and marketing cookies retain these labels for up to 30 days, without outlasting permission. The copy attached to the order is retained until permission expires, for no more than 365 days, and is cleared on withdrawal. Unattributed purchases remain without an advertising source; statistical attribution does not prove that an advertisement caused a purchase.
For signed-in users with the corresponding consent, the website may use one separate random identifier for Google Analytics and another for Meta. These connect permitted actions by the same user across devices, contain no name, email or runner registration details, and are not Facebook profile identifiers. The identifier for Google is sent as user_id, and the identifier for Meta, after SHA-256 transformation, as external_id by the Pixel and by the server. The link held by the website is limited to the duration of permission, at most 365 days, and is cleared when permission is withdrawn or expires; new permission does not restore the previous identifier.
Advertising on Google
Only with consent to advertising are ad-click identifiers (gclid, wbraid, gbraid), advertising measurement and personalised ads on Google used; these features also require consent to statistics. Google Signals may associate permitted visits with information held by Google about signed-in, consenting users, including for aggregated interest and demographic reports. With the same consent, when a purchase is confirmed, the server sends Google, for enhanced conversions, the purchaser’s email, phone number in international format, first name and last name after normalisation and one-way SHA-256 transformation, and the town and country in plain form, as Google requires, together with the pseudonymous identifier. This data is taken in the same way and with the same exclusions as for Meta. This is not anonymisation and does not give the Organiser a list of visitors’ Google profiles. Statistics permission alone does not enable these advertising features. Google sign-in does not grant advertising permission either.
With the same consent, the Organiser may create audiences in Google Analytics from these events — for example people who visited the website, started a registration or bought an entry — and use them in Google Ads to show them Plovdiv Run ads or to stop showing them ads once they have bought an entry; Google may also show the ads to other Google users similar to the people in the audience. Membership in an audience lasts at most 540 days. The Organiser sees the size of the audience, not the names or emails of the people in it, and does not upload lists of customers’ emails or phone numbers to Google.
The recipient is Google Ireland Limited. For Google Analytics and enhanced conversions, Google acts as a processor on the Organiser’s behalf (https://business.safety.google/adsprocessorterms/), and for personalised ads and audiences in Google Ads as an independent controller under its terms (https://business.safety.google/adscontrollerterms/) and policy (https://policies.google.com/privacy). How Google uses data from sites that use its services: https://business.safety.google/privacy/. According to Google, transfers to Google LLC in the United States rely on the European Commission’s adequacy decision for the EU–US Data Privacy Framework (Implementing Decision (EU) 2023/1795), under which Google LLC is certified, and where necessary on standard contractual clauses; details are at https://policies.google.com/privacy/frameworks. The Organiser may link analytics reports to advertising accounts and import aggregated costs, impressions and clicks from Meta; this does not give Meta access to personal orders or all Google Analytics records. Google may combine first-party analytics and advertising identifiers with Google advertising cookies and identifiers. Permission for these features may be withdrawn through ‘Privacy settings’; the website stops future advertising events and clears its advertising cookies and stored identifiers, and the person leaves Google audiences when their membership in them expires. Additional controls are available at https://myadcenter.google.com/ and https://tools.google.com/dlpage/gaoptout.
When daily export to Google BigQuery is enabled, a copy of permitted analytics events is stored in the Organiser’s project in the European Union for detailed reporting, with restricted administrative access and automatic deletion of raw tables within 60 days. No separate user-profile export is used. Withdrawal stops future transmission; data already transferred is not automatically erased, and rights requests may be sent to support@plovdiv.run.
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 (version 2026-11-21) takes effect on 21 November 2026 and replaces version 2026-11-19.