# A social wall where nothing leaves the room.

Canonical human page: https://guestwalls.com/private-social-wall
Category: Work & conferences

A private social wall for events: only people with your code can post, a moderator approves what reaches the screen, and nothing is published anywhere public.

## What this solves

Most social walls are public by default: anyone can post to them, and everything posted lands on a social network first. A private wall works the other way round—only your room can contribute, and what they write exists nowhere else.

Attendees join with a short event code, and an optional event password closes the wall to everyone else. A moderator can hold every post until it is approved, so the screen in front of the room is always the version you chose. When the event is closed the whole wall—messages, photographs, and all—is deleted automatically after its retention window.

## Why GuestWalls fits this event

- **Closed to everyone else:** There is no public hashtag and no open feed. Guests need the event code, and an optional password shuts the wall to anyone who was not given one.
- **Nothing is published outward:** Posts go to your screen and nowhere else—no attendee's followers, no company page, no permanent record on a platform you do not control.
- **Deleted when you are done:** Close the event and guest posting stops immediately. After the retention window the wall and its photographs are permanently removed.

## Setup

1. **Create the wall and lock it.** Name the event, switch on approval, and set an event password if the room is sensitive.
2. **Give the code to the room only.** Put it on the agenda, the badge, or a slide—somewhere your attendees see it and nobody else does.
3. **Moderate and then close.** One person clears the queue during the event. Closing the wall afterwards stops new posts and starts the deletion clock.

## Prompts for guests

Private rooms answer differently. These prompts get real responses when people know the screen is not public:

- “One thing that went better than expected this quarter.”
- “A question you would ask if this were anonymous.”
- “Who on another team made your job easier this year?”
- “The moment from today you will still remember on Monday.”
- “One word for how the last six months felt.”

## Frequently asked questions

### What makes a social wall private?

Three things: only people with the event code can post, a moderator can approve everything before it reaches the screen, and nothing is published to any social network or public page.

### Can we add a password as well as the code?

Yes. The host can set an event password, and guests need both it and the code to reach the wall.

### Is anything posted to social media?

No. GuestWalls does not read from or post to social platforms. Posts travel from the attendee's phone to your event and stay there.

### What happens to the messages after the event?

The host keeps access to the wall and its playback while the event stays open. Once it is closed, guest access ends immediately and everything is deleted automatically after a 30-day retention window—or sooner if the host deletes it.

### Can we use it for confidential or internal-only sessions?

Yes. Approval mode plus an event password is the usual setup for town halls, offsites, and any room where the content should not travel. It is worth telling attendees how posts will be used before you open the wall.

### Do attendees need an account?

No. Guests post from a normal phone browser with no sign-up, so nothing about them is stored beyond the post they choose to send.

## Product boundaries

GuestWalls accepts posts directly through an event link or code; it does not aggregate public hashtag posts. Guests use a browser and do not create accounts. The venue display needs an internet-connected computer and screen. For product-wide privacy, retention, availability, and recommendation details, read https://guestwalls.com/index.md.