Facebook's Restricted list is not the same as blocking a date

What the Restricted list actually does

The documented purpose of Facebook's Restricted list is to limit what a specific person sees of your content. The eSafety Guide explains that a person placed on your Restricted list can still see your public posts and any posts you tag them in, and that they are not notified of the restriction. In other words, restricting someone is a partial visibility control, not a complete separation. It can be useful when you want to reduce what someone sees without making a visible break, but it does not change the underlying connection or the person's ability to view public material. [eSafety Guide: Facebook]

• Check which of your existing posts are public before relying on restriction to limit someone's view.
• Assume a restricted person may still see posts you tag them in, and tag deliberately.

Restricted is not blocking

Blocking and removing contact are distinct from individual-post audience controls. The eSafety Guide treats these as separate mechanisms, which matters when you are deciding how firm a boundary you need. Restriction leaves the connection in place and relies on content visibility. Blocking or removing contact changes the relationship more directly. Neither choice is a judgment about someone else's character, and neither should be read as proof of anything about another person. The decision belongs to you and should reflect what you want to share. [eSafety Guide: Facebook]

• Decide first whether you want less visibility or no contact, then pick the matching tool.
• Do not assume restriction prevents all contact or all viewing.

Public posts and tagged posts are the gaps

The most common surprise with restriction is the public post. Because public posts can still be seen by a restricted person, restricting someone does not make your public material private. Tagged posts are the second gap: if you tag a restricted person, they can still see that post. The practical takeaway is that restriction works best alongside deliberate posting choices. Before you rely on it, review your default audience and think about when you tag people. [eSafety Guide: Facebook]

• Review your default audience setting and change it if you want fewer public posts.
• Pause before tagging someone you have restricted.

Separate observation from conclusion

Visibility settings describe your content, not another person. If someone on your Restricted list can still see a public post, that tells you about the post's audience setting, not about the person's intent, location or safety. The eSafety Guide describes controls over who can see posts and profile information; it does not establish anything about another person's conduct. Treating a badge, a status, a matching photo or a silence as proof of identity or intent is a mistake. Keep what you know about platform mechanics separate from conclusions about people. [eSafety Guide: Facebook]

• Write down what you actually observed versus what you inferred.
• Avoid confronting someone based only on a visibility signal.

Set your own sharing boundary

A sharing boundary you choose is more reliable than a signal you interpret. The documented controls let you decide who can see individual posts and profile information. Use that to decide what you post, who you tag and what stays public. If your goal is less contact, consider blocking or removing contact instead of relying on restriction. If your goal is less visibility, restriction plus tighter audience settings may fit. No approach guarantees that someone cannot see or infer something, so choose based on your own comfort rather than on assumptions about another person. [eSafety Guide: Facebook]

• State your goal in one sentence: less visibility or less contact.
• Adjust post audience and tagging habits to match that goal.

A short worksheet for your own decision

Use a brief written check before you change settings. Name what you want to protect, what you are willing to keep public, and which tool matches. This keeps the decision anchored in your own choices rather than in what another person appears to see. It also helps you avoid treating a restriction as a stronger measure than it is. The rows below are hypothetical examples, not platform tests.

Take one step at a time

You do not have to resolve everything at once. Review one audience setting, one tagged post and one public post, then decide whether restriction is the right level. Small, deliberate changes are easier to keep consistent than a single dramatic move based on a guess. If limiting contact matters more than limiting visibility, choose the tool that matches that goal rather than trying to interpret platform signals. [eSafety Guide: Facebook]

A couple more questions