A few minutes before posting can strongly affect anonymity.
After you post, the content may remain through screenshots, reposts, quotes, and archives. Even if you delete it, you cannot erase records kept by people who saw it.
A pre-posting check does not guarantee perfection.
However, it can reduce obvious mistakes.
Five things to check before posting
First, check the account, content, images, time, and visibility.
Check item
Reason to check
Account
Make sure you are not accidentally posting from a real-name account
Content
Check whether personal information, everyday locations, or proper nouns appear
Image
Check for faces, background details, reflections, and location information
Time
Check whether it connects with your current location or behavior pattern
Visibility
Check who can see it
Check these five items for every post.
A post becomes multiple records
A post does not end with the text shown on the screen.
The service side may retain the posting time, account, connection source, device information, edit history, and deletion history. The reader side may retain notifications, screenshots, quotes, and reposts.
Where it is recorded
What remains
Posting service
Account, time, IP, login state, edit history
Reader's device
Notifications, screenshots, saved images
Search engine
Title, body snippets, URL
Archive
Past versions of posts or pages
External service
Embeds, shares, notifications, analytics logs
A pre-posting check is the work of imagining not only what appears on the service screen, but also the records that remain after posting.
Check the post text
In the post text, watch for information that can identify you even when you have not written your name.
Information in the post text
Risk
Workplace or school
Affiliation or possible identities are narrowed down
Region
Usual places become visible
Date or time
It is compared with behavior history
Stories about people involved
Family, friends, and allies are pulled in
Unique experience
It remains as a story only that person would have
When rereading the post body, look at it not through the eyes of a "stranger," but through the eyes of "someone who knows you."
Check the account
Before posting, always check which account you are posting from.
The easiest anonymity failure to understand is accidentally posting from a real-name account. Even if you delete it quickly, it may remain through notifications, screenshots, and quotes.
Check item
Reason
Posting account
Make sure you are not accidentally posting from a real-name account
Profile image
Check whether it uses an old image or a face photo
Display name
Check whether an old handle or personal information remains
Login state
Check whether a real-name login from another service is mixed in
Connected apps
Check whether the post will flow to an external service
The more you switch between accounts, the more important the pre-posting check becomes.
Check images and links
A post may include images or links.
Images can retain backgrounds and metadata, and links can retain tracking parameters and search terms.
Target
What to check
Photo
Face, background, reflection, GPS
Video
Sound, notifications, movement route
Screenshot
Account name, notifications, time
URL
Search terms, referral IDs, tracking parameters
Shared link
Owner name, viewing permissions, edit history
Even if the post text is safe, attachments can break that safety.
Imagine how it will be read
Before posting, think not only about well-meaning readers, but also about how someone trying to identify you would read it.
Look for clues that remain when it is read with questions such as "Where does this person live?", "Where do they work?", and "Who are they connected to?"
Reader
Information they focus on
Acquaintance
Phrases, everyday locations, past stories
Coworker
Work content, time, technical terms
Local person
Shops, stations, schools, scenery
Attacker
Face, images, past posts, account correlation
Service side
IP, , login state, posting time
A post is not always read only by the readers you expected.
Even when visibility is narrow, it may leave that scope through screenshots or sharing.
Decide to delay posting
Posting from the scene, emotional posting, and replying during backlash are dangerous.
Even a short delay can help avoid revealing your current location or adding emotional information.
Posts that should be delayed
Reason
On-site photo
Current location or participants are visible
Post while going home
Movement route is visible
Angry reply
Extra personal information comes out
Post with files
Missed checks are more likely
Post with items you cannot judge
Unchecked risks remain
Delay posts that do not need to be rushed.
Remove before posting
If a pre-posting check finds risk, remove it.
You do not have to avoid posting everything; sometimes you can remove only the dangerous parts.
What to remove
Example
Place
Station name, shop name, school name, workplace name
Time
Expressions such as today, now, the hour, immediately after
People
Information about family, friends, colleagues, allies
Part of an image
Face, name tag, background, reflection
Extra parts of a URL
Search terms, referral IDs, tracking parameters
A post may still communicate even if it is shorter.
In fact, removing unnecessary information can sometimes make it easier to read.
Do not trust visibility settings too much
Even limited, followers-only, and locked posts can leak outside their intended scope.
Examples include screenshots, quotes, forwarding, sharing, account takeover, and a follower losing their device. Visibility settings matter, but they are not a complete wall.
Visibility setting
Remaining caution
Public
Anyone can save, search, and quote it
Followers only
Saving or forwarding by followers cannot be prevented
Private group
Screenshots and reposts by members can remain
Time-limited post
It may be saved while it is visible
DM
It remains on the other person's device or account
Instead of thinking "it is limited, so it is fine to write," check whether the level of detail would still be acceptable if it left that scope.
Read it aloud at the end
Right before posting, reread the post text slowly.
When you are in a hurry, you may publish information that feels like an assumption inside your own head. Reading aloud makes it easier to notice unnecessary proper nouns, strong emotional wording, and clues about region or time.
Use the following questions when rereading.
Question
Purpose
Would someone who knows me recognize it?
Look for correlation from close contacts
Am I pulling in people involved?
Prevent other people's information from leaking
Do I need to post this now?
Reduce time correlation
Is there information I can remove without losing the meaning?
Reduce unnecessary clues
Is it acceptable even if I cannot delete it?
Assume spread after publication
Summary
Before posting, check the account, post text, images, links, time, and visibility.
Even if you do not write your name, region, workplace, timeline, people involved, and photo backgrounds can bring others closer to your identity.
A post is hard to take back after publication.
If you are unsure, choose to delay the post, remove information, use different wording, or not publish it.
Related tools
Reverse image search
Google Lens
An external resource related to this article. Open it only when it fits your situation and threat model.
Why it is listed: It can help with the article topic, but it is outside Anonymity Sense and should be checked before use.