Privacy

Baby Name Score has two different kinds of pages, and they carry different privacy properties. This page explains both plainly.

Public name pages (/name/…, /compare/…, /names)

These pages cover a first name on its own — meaning, origin, pronunciation, international usability, and popularity. They are not personal to you: they are the same page for every visitor, indexed by search engines, and never contain a surname or any information you enter.

Private reports (/report/…)

When you generate a report for a full name (first name plus, optionally, a middle name and surname), you get a private link with an unguessable, randomly-generated address — it does not contain your name. That page is marked so search engines do not index it (“noindex”), and it is never listed in our sitemap or linked from any public page.

Important: “Not indexed” is not the same as “access controlled.” Anyone who has the exact link can open it — the same as most unlisted links across the web (an unlisted video, an unlisted document). Treat the link itself as something you control who you share it with.

What we don't currently offer

We do not currently have a self-service tool to delete a report or expire a link on a schedule. If you want a report link retired, contact us at whitelandstudios@proton.me. We do not claim reports expire automatically, because they don't today.

Analytics

We use privacy-focused, aggregate analytics to understand which features get used. Analytics events never include your first name, middle name, surname, full name, a report's address/token, or the contents of a report. Automatic page-view tracking is specifically filtered so that any private report URL is redacted before it ever leaves your browser.

What we don't collect

We don't require an account or login. We don't sell personal data. We don't run cross-site advertising trackers.

If a private link is ever accidentally indexed

If you find a private report link appearing in search results, please email whitelandstudios@proton.me with the URL — we treat this as a priority issue and will request removal from the search engine's index in addition to any fix on our side.