Most tools that put guest posts on a big screen are public by default. Anyone can contribute, everything contributed lives on somebody’s public profile first, and the screen shows whatever arrives. For a music festival, that is the point. For a company town hall, a hospital study day, or a school prize evening, it is the reason the idea gets rejected in the first planning meeting.
So people search for a private social wall. The trouble is that “private” is doing at least three different jobs in that phrase, and most product pages do not say which ones they mean. Here is how to tell them apart, and what to check before you put anything on a screen in front of a room.
Private means three separate things
Ask three questions in this order. A wall can pass one and fail the others.
Who can post? On a public wall, the answer is anyone who finds it. On a private wall, only people you handed the way in — a code, a link, a password, or some combination. This is the difference between a screen your room fills and a screen the internet can fill.
Who decides what appears? Even a closed room produces a post you would rather not project. A private wall lets a moderator hold everything in a queue and release it deliberately. Without that step, “private” only narrows who can embarrass you.
Where does it live afterwards? This is the one people forget, and it is usually the one the legal team asks about. If posts are published to a social network, they persist there on that network’s terms, long after your event. If they live only in the event, someone has to be able to tell you when they are deleted.
A wall that closes the door but publishes everything outward is not private. Neither is one that keeps posts internal but shows them unfiltered to four hundred people. You want all three.
Why public walls fail in certain rooms
The obvious risk is the troll: someone outside your event posting something ugly onto a screen you paid to rent. It happens, and it is why a lot of organisers who ran open walls a few years ago stopped.
But the more common failure is quieter and costs you more. On a public wall, contributing means broadcasting. An employee who would happily say this quarter was brutal but we got there to a room of colleagues will not say it under their own name on a feed their manager, their clients, and a recruiter can all read. So they say nothing, and you get eleven posts from the same four extroverts and a wall that looks like a failure.
Privacy is not only a defensive feature. It is the thing that makes the quiet 80% of the room willing to speak at all.
The four things to check before you commit
Whatever tool you are looking at, including this one, these are the questions worth making someone answer plainly.
1. How does somebody get in — and how do they get kept out? Look for a specific mechanism, not a reassurance. A short event code is the baseline. A code plus a password you set is stronger, because a code on a slide can be photographed and a password rarely is. If the answer is “the link is unlisted,” that is not access control, that is hoping.
2. Can every post be held before it reaches the screen? Approval-first should be a setting you can switch on before the doors open, not something you negotiate with support. Also ask who can moderate: if only one account can clear the queue, you have created a single point of failure on the one night it matters.
3. Is anything published outside the event? Ask directly whether posts are copied to any social network, public gallery, or shared page. Ask whether the guest’s post appears anywhere their own followers can see it. If contributing to your wall also posts to someone’s profile, your wall is not private and your attendees will work that out before you do.
4. When is it deleted, and who decides? You want a real answer with a real number in it. Ours is that closing an event stops guest access immediately, the host keeps the wall and its playback through a thirty-day retention window, and everything — messages, photographs, all of it — is then deleted automatically. A host who wants it gone sooner can delete it outright. The privacy page says the same thing in more detail, which is the point: you should be able to send your compliance team a link rather than a paraphrase.
How GuestWalls handles it
Worth being concrete, since this is our site. Guests reach a wall with a short event code, and hosts who need a tighter room can add an event password on top of it. There is no public directory of walls and no way to browse to one you were not given.
Approval mode holds every post in a host queue until someone releases it, so the screen in front of the room is always a version a human chose. Guests post from a normal phone browser with no account, which means there is nothing about them stored beyond the message they decided to send.
And nothing is published outward. GuestWalls does not read from social platforms and does not post to them. A message travels from an attendee’s phone to your event and stops there. That is a real trade — you give up the marketing reach a public hashtag campaign can generate — and the comparison is worth making deliberately rather than by accident.
When you do not need this
A private wall is the wrong default for some events, and it is worth saying so.
If the whole point is reach — a product launch where you want attendees amplifying to their own followers, a conference building public buzz, a fundraiser trying to be seen — then a closed wall is working against your goal. You may still want moderation, but the privacy layer is costing you the outcome you are paying for.
If the room is small and entirely trusted — a team of twelve, a family event — approval mode can make the wall feel sluggish and over-administered. Turn it off. Contributions land instantly, the screen feels alive, and twelve people who know each other will self-moderate better than any queue.
The setup that needs all three layers is the middle case: a room large enough that you do not know everyone, sensitive enough that the content should not travel, and public-facing enough that a bad post on screen would be a genuine problem. Town halls, internal all-hands, medical and legal conferences, school events, and anything where minors are in the room.
Tell people what the wall is
The last step is not technical. Before you open a wall in a room where privacy is the reason you chose it, say so out loud — one line on the slide next to the code.
Posts go to this screen only. They are not shared anywhere else, and the wall is deleted after the event.
Two things happen. People who were never going to post because they assumed it was going on the internet now post. And you have set an expectation you can be held to, which is a healthier position than letting everyone guess.
That sentence does more for participation than any feature on the list above. It is also the one nobody remembers to write.
A short pre-event checklist
- Event password set, if the room warrants one.
- Approval mode on, with a named moderator and a named backup.
- One line on the slide telling attendees the wall is private and when it is deleted.
- Agreement with whoever owns the room about how long the wall stays open afterwards.
- A prompt specific enough to answer — a vague wall gets a vague wall.
Get those five right and the wall does the thing you actually wanted, which was never the screen. It was hearing from the people who do not put their hand up.