Before You Post a Dream Online: What Personal Details to Leave Out
If you want an online community to respond to a dream, you can usually describe its central scene without giving readers the details that identify you or someone else. Before posting, remove names, exact places and dates, distinctive work or family clues, and identifying material in any image. Keep only the context needed to explain the dream and the question you want answered. A useful check is to ask whether several small clues, taken together, could point to a real person or place.
Start with the purpose of the post
Write down the question you want the community to answer, such as whether a particular image or sequence stood out to other readers. Then keep the dream details that make that question understandable. A scene can often remain clear with broad descriptions: “a relative,” “a former workplace,” or “a town near the coast” may communicate the role a detail played without naming a person or place. These substitutions are practical editing choices, not a guarantee of anonymity.
The Federal Trade Commission (FTC) advises people to think before posting because the audience for online material may be larger than expected, privacy settings cannot fully control who sees it, and someone may save or share a post. That guidance applies to a dream story just as it does to other personal writing. FTC, “Heads Up: Stop. Think. Connect.”
Remove direct identifiers first
Read the draft once looking only for details that directly name or contact someone. Remove or generalize:
Your full name, usernames used elsewhere, email address, phone number, and home or work address.
Other people’s full names, handles, phone numbers, or identifying account details.
Names of small organizations, schools, workplaces, clubs, or local groups when they make a person easy to identify.
Account or profile details that connect the dream post to your other public posts.
A nickname is not automatically anonymous if it is unique or familiar to people in the relevant community. Likewise, replacing a name with a role may not help if the role itself is unusually specific. Re-read the sentence around each removed name and ask whether the remaining description points to the same person.
Generalize dates, locations, and routines
Exact timing and place can narrow down who a story is about. Consider changing a precise date to a broad period, such as “a few years ago,” and replacing a named street, venue, or small town with a wider area or a general setting. Keep the detail only if it is necessary to understand the dream or the question.
Review routine details too: a particular shift, weekly activity, regular route, or event can identify someone when paired with a workplace, school, or location. You do not need to erase every ordinary detail. Instead, look for combinations that could be distinctive. The National Cybersecurity Alliance describes how separate bits of online information can add up to reveal more than a person intended to share. Applying that point here suggests checking the whole story for clues that reinforce one another, not just scanning for a name. National Cybersecurity Alliance, “Tread Lightly Online: How to Check and Manage Your Digital Footprint”
Keep other people’s identities out of the story
A dream may include people you know, but they do not need to be identifiable for readers to understand their role in it. Use a broad relationship or a neutral label—“a family member,” “a friend,” or “a colleague”—and remove details that expose their workplace, schedule, neighborhood, or distinctive personal history. If several people appear, use consistent labels so the story remains readable.
Think about what your descriptions reveal when combined. “My cousin” may be broad; “my only cousin who manages the evening desk at a named local venue” is much narrower. That example is an editorial illustration, not a claim about how any particular forum identifies people. The aim is to preserve the scene’s meaning while avoiding unnecessary details about someone who did not choose to post.
Check screenshots, photos, and copied text
Dream posts sometimes include a notebook page, a screenshot, or a photo to show what the writer means. Inspect the whole image before attaching it. It may show a name, notification, profile picture, distinctive room, workplace badge, or location clue in the background. Text visible at the edge of a screenshot can disclose as much as the main content.
Location data is another item to check. The FTC notes that a phone camera may attach information about where a photo was taken. Google Photos explains that camera-saved location data can be included with shared photos depending on the sharing method and settings, and that landmarks may let viewers guess a location even without embedded coordinates. If the image adds nothing necessary, a text description may be simpler. If you do share one, check both its visible contents and the sharing settings for that specific service. FTC, “Heads Up: Stop. Think. Connect.” and Google Photos Help, “How Google Photos protects your location data”
Review combinations and your public profile
After removing the obvious identifiers, read the post as a stranger might. Could a combination of the setting, date, occupation, relationship, and unusual event point to a particular person? Could the community username or profile link it to a public account where your name, town, or workplace appears? If the answer might be yes, broaden one or more details or remove them.
The FTC recommends limiting who can see posts through privacy settings, while also cautioning that settings cannot guarantee control over every viewer or later copy. Treat a community’s privacy controls as one layer of choice, not as a substitute for editing the post itself. FTC, “Heads Up: Stop. Think. Connect.”
A quick edit before submitting
Use this short sequence for a final pass:
State the question you want readers to respond to.
Keep only dream details needed to understand that question.
Replace names and specific places with broad labels.
Loosen exact dates, schedules, and distinctive background facts.
Remove identifying clues about other people.
Inspect attachments for visible details and location information.
Read the full post alongside your public profile for clues that connect them.
As a final test, imagine the post copied out of the community and read without your intended context. The FTC notes that online material may be saved or shared even after deletion. If a detail would feel too revealing in that situation, remove it before posting. This process cannot promise that nobody will recognize a story, but it can help you share the dream with less identifying context while keeping the parts relevant to your question. FTC, “Heads Up: Stop. Think. Connect.”