Privacy-safe family profiles compared with the default of publishing everything

What to take away

Privacy-safe family profiles compared with the default of publishing everything come down to one test: does this detail need to be here? A page can be accurate and still send someone to a school gate.

The working standard covers what to leave out, which named services hold a record, and how to handle requests. The evidence question comes first in the guide to what a public role licenses.

The two defaults, named

The publishing default runs in most newsrooms and fan sites: gather what exists, publish it, remove on complaint. The privacy-safe default starts with an empty page. It adds a detail only when you can name the reader's use for it.

The comparison criteria are starting point, privacy control, who it suits and cost.

The second default is not hypothetical. Ancestry and MyHeritage hold family trees behind an account and let living people be marked private.

Geni and FamilySearch do the same for collaborative trees. FamilySearch restricts living-person data to the contributor. Findmypast applies comparable living-person rules.

Each is a place to keep a lineage record without it becoming a search result.

For a public-facing profile, the choice is between a CMS that publishes by default and one that holds drafts until approval. WordPress, Squarespace and Ghost all publish on save unless you change the setting. A staged workflow is the privacy-safe configuration.

Start from nothing and justify each addition

Applied honestly, the empty-page rule removes most of what profiles habitually carry. A child's age is rarely load-bearing. A neighborhood almost never is. "Readers are interested" is not a use; it is a description of traffic.

The test is whether you can finish the sentence "the reader needs this because." If you cannot, the detail does not go on the page.

Individually harmless, collectively not

Each fact can be publicly available and defensible on its own while the page as a whole is something none of the sources are. That is the mechanism documented under data re-identification.

A complete profile carries children's full names, birth years, the city, and a school. It also includes a regular activity, recognizable photographs, and the family relationships. Together they are a route to a specific person on a specific afternoon. A structure makes assembly easier, as the guide to privacy in a family diagram describes.

They are also uncomfortably close to shared secrets used in knowledge-based authentication. These secrets include:

So judge the page, not the sentence.

The default exclusions

Leave these out unless a specific reason survives an editor's challenge:

Named tools for holding and removing a record

The tools split by job. Registries hold a record privately; removal services clear what is already indexed.

Pricing varies by country, plan and number of people. Treat the table figures as typical ranges as of 2026, not quotes.

Google's own removal request process handles the rest: personal information removal requests, and removal of images of minors on request by a parent or guardian. Those are free and are the first stop before any paid service.

None of these tools decide what belongs on your page. They change what is reachable, not what is appropriate. For which relationships are being asserted in the first place, see the guide to three questions habitually collapsed.

Children get the strictest rule

A child has not chosen a public role, and what you publish now will still be there when they are an adult with a searchable name. The Convention on the Rights of the Child frames identity and privacy that way. The working standard is in the guide to claims about children.

The default for a minor is the relationship and nothing else, where the parents have made even that public. Not the name unless the parents released it. Not the age, school, appearance or interests. Not current photographs.

This holds even when the material is available. Availability is a fact about the internet, not a decision about your page. Measure against the child's later view of it, not this year's traffic.

Consent does not transfer

A parent posting a photograph has decided to share it with their audience, on their terms, revocably. That is not permission for a publication to reproduce it, keep it, and rank for it indefinitely.

Three distinctions worth holding. Sharing something is not licensing it. A subject who has spoken about one aspect of their family has not opened the whole subject. A deletion is a withdrawal: republishing after a takedown overrides the person who removed it.

What actually makes something public

"They're a public figure" is doing too much work. Narrow it.

Family members who hold no public role are covered by no row here except the first, and only for what they themselves have said.

Requests, and how to handle them

Requests arrive from subjects, families and representatives. Sorting them makes them manageable. Have a route that reaches a person; a form that goes nowhere converts a solvable problem into a formal complaint.

The profile record

The omissions row is the one that saves you. Without it, every future editor sees an incomplete profile and helpfully completes it.

Common questions

It is already on the first page of search results. What harm does one more page do?

It adds reach, durability and a new claim to rank for the person's name. Harm here is cumulative. Every publisher making this argument is what produces the aggregate.

The subject discussed their family in an interview. Is the subject open now?

What they said is on the record. Everything they did not say is not. An interview is not a waiver, and it is certainly not a waiver on behalf of relatives who were not in the room.

A photograph was taken in a public place. Can we run it?

Legality and appropriateness are separate questions, and the rules differ by jurisdiction. Before either, ask what the image adds. Pictures of children going about ordinary life almost never add anything a sentence could not.

How do we cover a family matter that is genuinely newsworthy?

Cover the matter at the narrowest scope that makes it comprehensible. Name the adults involved in it, keep uninvolved relatives out, and do not use the story as an occasion to publish a general family inventory alongside it.