Your inputs stay in this page.

No profile, account or server-side personal lookup.

Surname census comparisons

The 2010–2020 surname comparison downloads the same public Census files for everyone. Your typed surname, comparison and downloaded CSV are handled in your browser; they are not sent to us or stored in a profile.

Names, dates and cards

Your typed names, selected dates, language choices, height measurements, blood-type and eye-color choices, chosen comparison groups and calculated results are processed in this browser. The application does not send them to a personal-lookup API or store them in a profile, cookie, local storage or database. The browser downloads public datasets as needed; a yearly dataset request identifies the selected public cohort, not your typed name. Refreshing or leaving the page clears the application state. Your browser may retain its own form history or downloaded files.

A birthday share link contains a public month-and-day path, such as /r/05-14. Opening that link sends the path to our hosting provider like any other webpage request. It contains no name or birth year. A card image includes the details you chose; saving or sharing it intentionally puts those details into the file. Share adds a short caption with the same result and a link: the birthday’s /r/ page, or the general name, surname or card-maker page, never a name. On a browser without a share sheet, the caption and link are copied to your clipboard instead. Device share sheets and any receiving apps apply their own policies. The site does not automatically post cards anywhere.

Links to name and surname results are optional. Only Copy link with this name or Copy link with this surname makes one, and it carries the name after a # in the address, for example howrareismy.com/name#n=Evelyn&y=2025. Browsers keep the part after # on the device: it is not sent to our server, so it never reaches our hosting logs, our page counts or our Google Analytics setup, which reports only the page path. When the link is opened, the page reads the name, repeats the lookup and removes it from the address bar. Anyone you give the link to can read the name in it. Link previews for these pages stay generic and never show the name.

Website delivery and task counts

Search in All tools filters links already on the page. Search text stays in page memory and is not sent in requests, analytics or browser storage. Following a result opens its ordinary page address.

Cloudflare receives ordinary connection information such as IP addresses, request paths and headers to serve and protect the site. We use aggregate first-party counts of page loads, calculator use, card downloads and share actions, plus limited performance and error categories. Page-visit counts also note the domain of the website that linked to the page (if your browser shares one) and a broad source category taken from it or the link's campaign source tag, such as a named search engine or AI assistant. For the slowest response on a page, speed measurements note how the delay divided between waiting, running and redrawing, whether it followed a tap, click or key press, and the broad kind of control involved, such as a button or link. In browsers that report it, they also note whose script ran longest during that response (this site's, a browser extension's or another site's), how it was started, and how the time divided between scripts, page layout and drawing, never the script's address or name. For page loading, they also note how the wait divided between connecting, the server's reply and fetching and drawing the largest image or text, whether that was text or an image, when the largest layout movement happened, and whether the page was opened fresh, reloaded, returned to or loaded in advance. These events do not include names, entered dates, zodiac signs, type-calculator criteria, language choices, height measurements, blood types, eye colors, selected comparison groups, numerical results, card contents or raw error messages. There are no ad pixels, session recordings or remote fonts.

Hosting diagnostics

Cloudflare keeps sampled request and error logs for up to seven days to help diagnose server failures. These hosting logs can include requested page paths (query strings are removed) and ordinary request metadata. They are separate from the anonymous tool counts described above; application inputs are not added to them.

Google Analytics

We use Google Analytics 4 to understand page visits and whether a visit used a tool: the first lookup on a page sends it one fixed tool_used event with the page path, never what you entered or the result. It may set first-party _ga cookies to recognize repeat visits. Google receives the page path, page title, limited campaign tags, the referrer's origin, and ordinary browser and connection information, including your IP address and the approximate location our hosting provider works out from it (country, region, city and approximate coordinates). Our server passes that location on because these requests reach Google through this website. Automatic enhanced measurement and advertising features are disabled. We do not send tool inputs, file names, sequences, calculations or simulated scene settings to Google Analytics. Event-level data is retained for 14 months; aggregate reports may remain available longer. See Google's Privacy Policy.

Google Analytics does not load for visitors in the EEA, UK, Switzerland or Quebec, when location is unknown, or when the browser sends Global Privacy Control. Automated and synthetic test traffic is excluded. You can remove analytics cookies through your browser's site-data controls.

When a page links to another company's product, the link goes through an address that begins with /go/. When you follow one, our server redirects you to that site and counts the click, the same way as a page view: which link, the page it was on and roughly how long after the page opened, but no identifier for you. Once we join a company's affiliate program, the redirect adds that program's referral code, so the company can credit a purchase or sign-up to us; its own privacy policy then applies.

Questions

For privacy or data questions, contact hello@howrareismy.com. If you email us, your email provider and our mail provider necessarily process that message. Please do not send another person’s private information. Read the methodology for the public datasets and the terms for use of results.

Car make, model, variant and manufacture-year choices also remain in page memory. The annual year lookup downloads one identical public file when needed; no make, model or year appears in its request. Its selected-model CSV is made on your device. Model-group data arrives with the car tool. Loading the optional variant lookup requests the same public file for every visitor; no selected model, registration plate or VIN is sent. Cards and history CSVs are generated on your device.

Washington car model/year choices and dog-name lookup or generator inputs remain in page memory. Their public aggregate data arrives with the tool; typed names, prefixes and car selections do not enter a request URL, analytics event or browser storage. No dog photos, owner details, registration plates or VINs are collected by these tools. Charts and share cards are made locally.

Zodiac sign and birthday choices on the zodiac page, and the criteria you choose in the type calculator (who you are looking for, age range, relationship status, education and income), also stay in page memory. The type calculator downloads the same public survey table for every visitor, and neither tool puts a choice in a request, analytics event or browser storage. A card or shared caption contains only what you choose to save or share.

After a birthday lookup, the page downloads one public list of well-known people born on each date; every visitor receives the same file, so the request does not reveal your date. The optional birth year also stays in page memory: when you add one, the page downloads the same public table of daily U.S. births for 1994–2014 that every visitor gets, and works out your day, weekday and age in the page. The year is never put in a link, request, analytics event or share card. The countdown to your next birthday uses your device's own date and is worked out in the page. A birthday story card can name one well-known person born on the same day; that name comes from the same public list.

The calculators on the ranked answer pages also run in page memory: the birthday paradox group size, the same-birthday calculator’s month, day and number of other people, the number of left-handers in a group, the odds of twins by the mother’s age, the weight percentile (weight, unit, sex and age group), the net worth percentile (amount and age group), the job lookup (job title and optional pay), the penny lookup and the quarter lookup (year, mint mark and design). Their data is part of the page or a public file every visitor receives. No typed value or choice is put in a request, analytics event or browser storage; the anonymous count records only that a calculator was used.

Income amounts, the household or personal choice and age selections also stay in page memory. The income calculator downloads the same public percentile table for every visitor; no amount or choice is part of that request. Dog-name shortlists are held only in page memory, with an optional local text download. Browsing, sorting and downloading matching dog names as CSV also run on the page. Neither tool sends its inputs, selections or list contents in requests or analytics. A downloaded income card contains the amount and age group you chose.

The last-name generator uses the same public 2010 Census surname file for every visitor. Starting and ending letters, length and count filters, generated suggestions and the shortlist stay in page memory. Only choosing Copy names writes the selected names to your clipboard; Save list creates a local text file with the recorded counts and source. Refreshing or leaving clears the shortlist. No filter or selected surname is added to a URL, request, analytics event or browser storage.

The cat-name tool loads the same public aggregate name counts for everyone. Typed names, filters and the shortlist stay on the page and are not sent in requests, events or browser storage. Copying and saving files happen only when you choose those actions. Leaving or refreshing clears the shortlist.

The 2020 Census first-name lookup downloads the same public aggregate file for every visitor. The entered spelling stays in page memory, including when transferred from your birth-year result. It is not sent in requests, analytics, URLs or browser storage. The result CSV is created on your device only when you choose Save.