Privacy

Privacy Policy

This page is compiled automatically from public sources and kept up to date. If you spot an error, please use the report form and we will review it.

These terms apply to music.thepublicpeople.com (the site you are currently on) and the other Public People sites and subdomains.

Last updated: 2026-09-01

This Privacy Policy explains what data we process when you use Public People, why, and what choices you have.

Who is responsible for this data

The data controller is PE Viktor Dudochkin, contactable at [email protected]. The controller's registered jurisdiction is Ukraine.

What data we process

(a) Public-figure data: information about public figures, gathered from openly available sources (see the About page's "Data sources" list for exactly which ones this niche draws on). This is public information about people's professional lives, not private personal data we have collected directly from them.

(b) Account data: if you register an account (e.g. to claim a profile or comment), we store your email address and a session identifier needed to keep you signed in. We do not sell or share this data with third parties for advertising.

Lawful basis for processing public-figure data

We process public-figure data on the basis of legitimate interest (GDPR Art. 6(1)(f)): informing the public about people whose professional activity is already publicly documented. We do not process this category of data on the basis of consent, since the individuals concerned have not created an account with us.

Your rights

If a profile is about you (or you represent its subject), you have the right to access, correct, object to, or request erasure of that data, and to request a copy of what we hold about you. Use the report form to submit any of these requests — no account is required.

We aim to respond to legal requests (opt-out, correction, data access, and similar) within 30 days.

What we keep and why

When someone asks us to remove their profile, our default response is to reduce it, not delete it outright — similar to how open reference catalogues remove personal identifiers while keeping the factual professional record. We remove the personal information: personal identifiers, private-life details, personal images, and AI-generated text.

We keep a basic professional record — the person's professional or stage name, their public professional work, notable achievements, and official links they publish themselves — because this reflects a legitimate public interest in a public figure's professional activity, not their private life.

The profile stays public in this reduced form, with a visible note that it was reduced at the subject's request, alongside an invitation to claim and manage it directly. In some cases — for example a court order, a person who turns out not to be genuinely public, or a cataloguing mistake — full removal (unpublishing) is the appropriate response instead; we decide this case by case, within the 30-day response window.

Special-category data

We do not intentionally process special-category data (health, sexual orientation, religious or political views, ethnicity, and similar) unless it has been manifestly made public by the person themselves. Where such information could plausibly appear in a source (e.g. a biography section), it is not published without additional checks.

Children

Public People is not intended to profile minors. If you believe a profile concerns someone who was a minor at the relevant time, please use the report form so we can review it.

Cookies

We use only strictly necessary cookies — a first-party cookie that keeps you signed in and protects your session. We do not use advertising cookies, and we do not need your consent for strictly necessary cookies under applicable e-privacy rules. See the next section for how we measure traffic without using a cookie at all.

Analytics

We use Umami, a self-hosted, first-party, cookieless analytics tool, to understand how Public People is used (which pages are visited, roughly how many people, from which country/device type, and which sites referred them). Umami does not set a cookie and does not write anything to your device, so it does not trigger the consent requirement under e-privacy rules the way advertising or third-party analytics cookies would.

The data it collects is aggregated and de-identified: page paths, referrers, coarse device/country information, and a rotating, salted hash derived from your IP address — never a raw IP address, and never tied to an account. Because it is self-hosted, this data stays on our own server and is not shared with any third-party analytics or advertising company. The lawful basis for this processing is the same legitimate interest (GDPR Art. 6(1)(f)) that covers the rest of the site: understanding and improving the service.

Third-party content

Some content is embedded from third-party platforms (e.g. YouTube videos, Wikimedia Commons images). Viewing embedded content may be subject to that platform's own privacy policy, which we do not control.

Contact

Privacy questions or requests can be sent to [email protected], or submitted via the report form.