Privacy Policy
Last updated
VsiProbihy is a calendar of running events in Ukraine with registration, participant lists and results. This page explains in plain words what data we hold about you, what we do with it and how you can control it.
In short
- We collect only what is needed for your account, race registration, payment and results.
- We do not sell your data. Ad platforms (Meta, Google) receive only hashes of your email and phone — so we can show races to you and to similar runners; you can opt out.
- We never see or store bank card details — payments are processed by the WayForPay or monobank payment service.
- Your name in a participant list and in race results is public; in the start list you can hide behind an alias.
- We may bring one person’s results from different races together on a runner page: the name, gender, year of birth and list of races are public, times and places are visible to registered users only; you can ask us to remove the page. We never show a full date of birth.
- You can correct or delete your data in your account or by emailing [email protected] — we reply within 30 days.
Who is responsible
The data controller is Yurii Kostrytskyi, sole proprietor (FOP) (taxpayer number 3083218214, Kyiv, Ukraine), owner and administrator of vsiprobihy.org (“VsiProbihy”, “we”).
For any question about personal data, email [email protected], call +38 050 441 30 70 or message @kostritsky on Telegram.
This policy follows the Law of Ukraine “On Personal Data Protection”.
What data we collect
Data you give us:
- Account — email, password (we store only its hash), first and last name. If you sign in with Google — your Google account identifier, email and name; we never receive your Google password.
- Profile (optional) — gender, date of birth, country, city, phone, club, T-shirt size, Telegram username.
- Profiles of children and other people you register from your account — the same fields. By adding them you confirm you have the right or consent to do so.
- Race registration — distance, bib number, team, answers to the organizer’s extra questions, selected options, promo code, payment status and amount.
- A result you enter yourself, and your likes (“hearts”) for races.
- Messages to us — the content of emails and messages, organizer requests.
Data created while you use the site:
- Page views: page address, referring page, UTM tags, browser type. These records are not linked to an account.
- First-visit source (landing page, referrer, UTM) — kept in your browser and attached to your account when it is created.
- The days you used the site while signed in, and the number of sign-ins.
- Copies of system emails we sent you — visible in your account.
- IP address — processed in technical logs of the server and delivery network to prevent abuse; we do not record it against your account.
- Actions of organizers and administrators on races and registrations — in an audit log.
If you had an account on the previous version of the site, your profile and registrations were carried over unchanged.
Data from public sources: participant lists and results
VsiProbihy brings together lists of registered runners and race results already published by organizers, registration platforms and timing systems. This is why your name may appear here even if you never registered with us.
From such sources we take only what relates to taking part in the event: first and last name, bib number, distance, time and place, gender, age group, year of birth or age, city, club. We do not collect or publish contact details from third-party sources.
Some result sheets (for example, IKS and the Run Ukraine archive) contain a full date of birth. We keep it only to tell namesakes apart and to group one person’s results correctly. The full date never appears on the site or anywhere outside: at most we show the year of birth or age, as the result sheet itself does.
To keep race dates, venues and entry conditions in the calendar up to date, our bot re-reads organizers’ public pages every night: websites, registration pages, Telegram channels, and public Facebook Pages and Instagram business accounts — the latter only through the official Meta API. From them we take only the text and date of the Page’s own posts about the event; we do not collect comments, likes, followers or any data about people. We do not publish or store the posts themselves: we keep only a checksum of the text (to notice changes) and a short quote in the internal change log of the race listing.
The legal basis is the legitimate interest of the running community in a complete and convenient archive of events; the data had already been published by the organizer under the rules of the race.
If you found yourself and want an entry corrected or removed, email [email protected] with a link to the page. We will do it, no questions asked.
What others can see
- A race participant list is public: first and last name, distance, and city, club, bib number and age group where available. Unpaid registrations are not listed.
- When registering you can choose anonymity: the start list will show a random alias instead of your name. You can change this in your account until results appear.
- Results are public and show real names, including for those who registered anonymously — that is how official race results work.
- The race organizer always sees the real details of their participants — they are needed for timing, insurance, race packs and awards.
- We do not publish your email, phone, full date of birth, Telegram or payment details. Results may show a year of birth or age — when the result sheet contains it.
Participant and results pages are open to search engines.
Runner page
We bring one person’s results from different races and years together on a runner page, so that the whole history can be found in one place.
- Results are matched automatically: by name, gender and year or date of birth from the result sheets, and — if you registered through VsiProbihy — by your registration as well. When a match is ambiguous (say, several namesakes of the same age), the result is left off the page.
- A page appears only when we have confidently found the person in at least two races.
- The page shows the name, gender, year of birth, results (race, date, distance, time, places, age group), city and club from the result sheets. It contains no full date of birth, contacts or account data.
- We do not create runner pages for minors.
The name, gender, year of birth, city, club, number of races and a few recent ones are open to all visitors and search engines. Times, places and personal bests, as well as runner search, are available only to registered users who are logged in.
If you do not want such a page, click “Remove my page” on it or email [email protected]. An administrator reviews the request manually, so that nobody can hide another person’s page. Once approved, we hide the page and never create it again; your results remain only in the race result sheets. If you spot someone else’s result on your page, write to us and we will remove it.
Why and on what basis
- Creating your account, registering you for a race, taking payment, showing you in the list and in results — performing what you asked us to do.
- Sending registration confirmations, start reminders, notices about race changes or password resets — the same: the service does not work without these emails.
- A newsletter with race picks — only with your consent; you can turn it off in your profile at any time.
- Keeping payment records for settlement with organizers and for disputes — a legal obligation and our legitimate interest.
- Measuring traffic, finding bugs, protecting the site from abuse, keeping the results archive — legitimate interest.
- Matching one person’s results across races and showing them on a runner page — the running community’s legitimate interest in a convenient archive; you can object at any time, and once we have checked the request we hide the page.
- Showing ads for running events to you and to people like you on Meta and Google — our legitimate interest; how it works and how to opt out is in “Advertising and newsletters”.
We make no automated decisions with legal effect for you.
Who receives your data
Only those the site cannot work without:
- The organizer of the race you register for — receives your registration data and is then responsible for it under their own rules.
- WayForPay — payment service: first and last name, email, phone, amount and order number. You enter card details on their side.
- monobank — payment service (the organizer decides which races use it and which use WayForPay): amount, order number and payment purpose — the race and distance name. You enter card details on their side.
- Brevo and Resend — email delivery: the address and content of the email.
- Google — Google sign-in (if you use it), Google Analytics (aggregate traffic statistics) and Google Ads audiences (hashes of email and phone).
- Meta (Facebook, Instagram) — Meta Pixel on the site’s pages (technical page-view events only, without your name or email) and ad audiences (hashes of email and phone) — only from accounts with newsletter consent enabled.
- Cloudflare — site protection and acceleration: technical connection data, including IP address.
- Hetzner and Oracle Cloud — the servers that run the site and hold backups.
- Anthropic (Claude) — automated parsing of public race pages and result sheets; your account data is not sent there.
Some of these companies operate outside Ukraine — in the EU and the USA — so data may be processed there; all of them are bound to protect data under their own policies and local law.
We disclose data to public authorities only on a lawful request. We sell it to no one.
Advertising and newsletters
Ad audiences. To show information about running events to you and to people like you, we may upload the email and phone from accounts to the ad tools of Meta (Facebook, Instagram), Google and similar platforms. The data is hashed before upload — the platform receives not your address or number but an irreversible fingerprint of it, which it matches against its own users. Contacts are never passed to the platforms in plain form, and they are not used for anyone else’s advertising. Only contacts from accounts with the newsletter consent box ticked in the profile (unticked by default) go into audiences; guest registrations without an account are never uploaded. Untick the box and your contacts disappear from the audience at its next refresh.
Pixels and remarketing. The site runs Meta Pixel, Google Analytics and our own Umami analytics. They record views of race pages and clicks on the registration button — this shows us which races people are interested in and lets us remind those who viewed a race about it. We do not pass your name, email or other account data to the pixels. Umami runs on our server and shares nothing with anyone.
Banners on the site. Every ad banner has a close button “×”. When you press it, we remember that in your browser so we stop showing you that banner, and we store on our server the fact that it was closed: which banner, when, and a random anonymous number of your browser. That number is not linked to your account, email or phone, and we do not pass this information to Meta, Google or any other third party. We use closings to see which banners annoy visitors and to decide what to show to whom in future. To detach the closings already stored from yourself, clear the site data in your browser — the number will change and old records will no longer point to you.
How to opt out of ads:
- Meta — in the ad settings of your Facebook or Instagram account (“Ad preferences” → “Audiences” and “Activity information from ad partners”).
- Google — on the “My Ad Center” page (myadcenter.google.com), where personalised ads can be turned off.
- Pixels — a browser blocker (uBlock Origin or similar) or blocking third-party cookies.
- Completely — email [email protected]: we will remove your contacts from all our ad audiences and will not add them again.
Newsletters. We send the email newsletter with race picks only to those who ticked the consent box in their profile — it is unticked by default. You can unsubscribe via the link at the bottom of every email or in your account. Reminders about registration opening or results appearing for a specific race are sent only at your explicit request on its page; every such email also has an unsubscribe link.
If you want to be removed from both ad audiences and all newsletters at once, email [email protected] from your account’s address. We will do it within 30 days, usually much sooner.
How long we keep data
- Account and profile — for as long as the account exists. You can delete the account yourself in your account settings (“Security and sign-in”): the profile, family members, emails and likes are anonymized at once and disappear from backups within 30 days.
- Registrations and payment records — at least three years after the race: they are needed for settlement with organizers and for disputes. A record of a paid registration stays in an archive even if the registration is deleted. Guest registrations without an account are anonymized three years after the race — only the payment record remains.
- The email archive in your account — two years.
- Browser reports about violations of the page security policy — 90 days.
- Results and participant lists — indefinitely, as a sports archive; on your request we remove or anonymize an entry.
- A date of birth from a result sheet — as long as the corresponding result is kept; removed together with it.
- A runner page you asked us to remove — is never created again: we keep only a note of your refusal.
- Page views — after 13 months the link to the account and browser number is removed; after that they are statistics only.
- Banner impressions and closings with the × button — only by an anonymous browser number, not linked to a person; kept as long as the banner itself exists and removed together with it.
- Password reset and email verification links — valid for a limited time; expired ones are deleted within a week.
- Backups — rotated; deleted data disappears from them within 30 days at the latest.
Children
Children are registered for races by parents or other legal representatives — from their own account, through a family member profile. They also consent to the processing of the child’s data and to the child’s name appearing in lists and results.
If you learn that a child has left their data without a parent’s knowledge, write to us and we will remove it.
We do not create runner pages for minors. A child’s date of birth from a result sheet is never shown, just like an adult’s.
How we protect data
- The connection to the site is encrypted (HTTPS).
- Passwords are stored only as a hash; two-factor sign-in is available. Changing or resetting the password ends all other sessions of the account.
- Organizers’ payment-service keys, two-factor secrets and social-network tokens are stored in the database encrypted — the encryption key is kept apart from the database and its backups.
- Site pages are served with a Content Security Policy (CSP) that stops the browser from running third-party scripts.
- Only administrators can access the database, and their actions are logged.
- A backup is made daily, with a separate copy kept off the main server.
No protection is absolute. If a breach affecting your data occurs, we will notify you and tell you what to do.
Your rights
By law you may:
- learn what data we hold about you, where it came from and who received it, and get a copy;
- correct inaccurate data — most fields can be changed in your account;
- request deletion of your data or account — the account can be deleted by you in your account settings (“Security and sign-in”);
- object to or restrict processing, including removal from lists and results;
- remove your runner page or someone else’s result from it;
- withdraw consent — for example, unsubscribe from the newsletter in your profile or ask to be removed from ad audiences;
- complain to the Ukrainian Parliament Commissioner for Human Rights or to a court.
To exercise a right, email [email protected] from your account’s address. We reply as soon as possible and no later than 30 calendar days. It is free of charge.
Some data cannot be deleted immediately — payment records we must keep; we will say so in our reply.
Changes to this policy
When the way the site handles data changes, we update this text and the date at the top of the page. We will announce significant changes in advance by email or on the site.