Private input
Autocomplete and search submissions use POST requests. A successful lookup stays on the canonical homepage and displays a transient result below the search. The surname is not copied into a query string or permanent result URL.
Privacy
Your surname search is not a profile
No account or email is required. The free search uses public aggregate Census files. Raw form and autocomplete input is not sent to product analytics, placed in query-string URLs, written by application logging code, or shared with advertising technology.
Current practices
No identity inference
A surname does not reliably determine a person's ancestry, race, ethnicity, nationality, religion, or culture. This product makes none of those claims.
Coarse pageview analytics
Vercel Web Analytics measures pageviews. The lookup remains at /, and no custom surname event or search-history store is used. Query strings and fragments are removed before any approved analytics event is sent.
About the data and routes
The Census surname files contain national aggregate publications, not personal records. This site does not ask who a search concerns and does not connect a surname result to a person.
Former surname-profile, directory, comparison, and sharing routes are permanently retired. They return a minimal HTTP 410 response with a noindex crawler directive and do not load analytics or advertising code.
Advertising and cookies
Current status
The site publishes an AdSense seller declaration and a production-only account-verification meta tag. It does not currently load an AdSense script, request an ad, display an ad, or set an advertising cookie.
If ads are enabled
Third-party vendors, including Google, may use cookies or similar identifiers to serve ads based on a visitor's prior visits to this site or other websites. Other authorized advertising vendors would be named here before use.
Consent before ad requests
Advertising code will not be enabled until the required consent controls are configured. Personalized ads in the EEA, UK, or Switzerland require a Google-certified consent management platform integrated with the IAB Transparency and Consent Framework.
If ads are enabled, visitors will be able to manage personalized advertising through Google Ads Settings. Google explains how it uses information from partner sites in How Google uses information from sites or apps that use its services.
Raw surname input will remain excluded from advertising requests and custom advertising events. Any future ad implementation requires a separate documented privacy review, consent decision, owner authorization, and release validation.
Changes to this notice
This notice describes the product as implemented on August 27, 2026. Storage, email subscriptions, live advertising, payments, a new analytics vendor, or new telemetry fields require a documented product and privacy review before release.