5 points worth checking on former couples privacy

Prominence fades. A person who was widely written about ten years ago may be doing something else entirely now, with no public role and no interest in one. The entry about them does not fade. It stays indexed, loads instantly, and is often the first thing a search returns.

That gap between a person's current position and their archive's position is the privacy problem specific to former couples. This article sets out five checks for deciding what a celebrity relationship timeline should retain about a former couple, from the dated public event to private details that do not belong in the entry. Two illustrative request cases below show possible remedies. They are composites, not real requests.

Five privacy checks for former-couple timeline entries

Date the public interest and set a review point

Publishing about a person's private arrangements is defended on the basis of a public role. That defense has a date on it, and it is not permanent.

The legal framing is useful here, though the editorial question is separate. In the EU, Article 17 of Regulation (EU) 2016/679 (the General Data Protection Regulation, or GDPR) provides a right to erasure, subject to conditions. In California, the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), includes a right to delete personal information under California Civil Code section 1798.105. The California Privacy Protection Agency and the California Attorney General have enforcement roles under the California law.

A public figure analysis turns on what a person did to enter public debate. That is an act at a time, not permanent status.

Someone who held a public role in one period may hold none now. Material defensible then is republished today because the page still exists.

The question to ask about an old entry is not whether it was right to publish, but whether you would publish it today, about this person, as they are now.

For example, Brad Pitt and Jennifer Aniston's joint separation statement, issued through their representatives, is dated January 7, 2005. Ben Affleck and Jennifer Garner's joint separation announcement, posted publicly by the couple, is dated June 30, 2015. In a relationship timeline, those dates support entries about the public announcements, not claims about when a private relationship ended or why.

To add either entry, pull the statement from its first publication and record the outlet or account, the URL, the date it carries and the date you retrieved it. Keep that record with the entry as its supporting source, and do not add private reasons or details the statement does not establish.

Whether an entry should stay once it exists is a different question, and it frequently gets a different answer. The reasoning about what makes an entry publishable in the first place is in the main guide to former couples. For what a court shields from the record, see divorces privacy.

Four remedies and their editorial tradeoffs

Here, “cost” means an editorial tradeoff, not a quoted fee. The table compares what each remedy changes or leaves in place rather than assigning dollar amounts.

Most requests are answered with a refusal on the grounds that the material was accurate. A page can be accurate in every line and still be a disproportionate thing to keep publishing about someone whose connection to public life ended a decade ago.

The narrower doctrine of false light is a reminder that harm from publicity is not limited to falsity, and the editorial version of that point is broader still.

Narrowing is the underused option. An entry reduced to the documented act, with the characterizations and the surrounding detail stripped out, usually keeps whatever value it had and sheds most of what made it intrusive.

De-indexing has a separate request path: Google offers its “Results about you” tool and a personal-information removal request process, while Microsoft provides the Bing Content Removal Tool. These requests affect search results; they do not remove the publisher's page.

Two illustrative cases, invented to show the range, are described here. In the first, a former partner of a state legislator asked that a 2013 engagement page be de-indexed; the publisher narrowed the entry and added a dated note. In the second, a person named only in a photograph caption asked for removal; the publisher cut the caption and kept the article.

The person who was never the subject

Every entry in this category touches someone whose only connection to public life was the connection itself. A partner with no public role. Family. People who appeared in a photograph once.

None of the arguments that make writing about a public figure legitimate apply to them, because none of those arguments were ever about them. They have no representation, no route to respond, and no reason to expect any of it.

The general form of that boundary, and why aggregation is a new act rather than a repetition of old ones, is set out in the notes on what a record should hold.

Write a retention rule before any request arrives

Two things move in opposite directions as an entry ages, and both matter.

The public interest declines, because the role that supported it recedes. The exposure rises, because the entry accumulates links, gets copied, and outlives the coverage around it. An old page is often more findable than the reporting it was built from, precisely because it is maintained and the reporting is not.

That combination argues for a retention rule written in advance. Before any request arrives, decide how long an entry of this kind is carried, what triggers a review, and which remedy is the default at that point. A workable example: review at five years, and make removal the default at ten unless a current public role is documented.

A rule written in advance is applied evenly; a rule written during a request is a negotiation. The maintenance cost of carrying entries indefinitely is worked through in the notes on maintenance load.

Handling a request without publishing the requester

A request is a dated fact and belongs in your log. It does not belong on the page.

Record who asked, when, what they asked for, what you checked, what you decided, and why. Publish none of it. A note saying an entry was narrowed on a date is appropriate; dated status lines show how to word it.

A note identifying who asked for it is a new disclosure about the person who was trying to reduce one. Where the change touches something already published, it is a change to the record and takes a dated note on the lines set out in the guide to corrections.

Common questions

Does an old entry become safer because the material is widely available elsewhere?

No. Your page is a separate publication making its own decision, and availability elsewhere is a fact about other publishers rather than a standard.

If the entry is accurate, is there any obligation to change it?

Legal obligation varies and is not what this is about. Editorially, accuracy answers whether an entry is wrong, not whether it should still be published, and those questions come apart as time passes.

Should the page keep a record of what was removed?

Internally, yes, with the reason and the date. Publicly, a note that an entry was withdrawn and when is enough. A public log of what used to be there republishes the thing you removed.

Is de-indexing enough on its own?

Rarely. It reduces one route to the page and leaves the page. Where the material genuinely should not be published any more, narrowing or removal is the remedy that matches the decision.