In this article
Every stage of the staff cycle already has an article on this site: finding people, onboarding them, training them, keeping them. None of them cover the phone everyone already carries in their apron — and what happens the moment it starts filming mid-shift.
A staff member films a busy pass, a colleague making a mistake, or — without thinking twice — a guest at a table. It is online within the minute, with your venue's name attached, and nobody asked you because nobody thought there was anything to ask about.
Most owners have no policy for this, for two opposite reasons. Half assume the problem solves itself — a bad clip fades on its own. The other half bans anything involving a phone, which kills off the cheapest, most genuine marketing a small team can produce.
Neither is right, and this article is about why. Not a list of bans — five numbers that explain what you actually control once something is posted, what it can really cost, and the one moment a policy still reads as neutral rather than as a reaction.
This is not about your own restaurant's marketing on social media — that piece already exists on this site. This is about the posts your staff make themselves, on their own phone, on their own account, about your venue — the ones you never approved because you never saw them.
Why this catches most owners off guard
It does not feel like a business risk because it does not feel like work. It is a staff member filming something funny between two orders, not a decision that calls for a policy. Which is exactly why nobody thinks about it until it becomes one.
And by the time it is a problem — a colleague embarrassed by a clip, a guest complaining, a new dish online three weeks before launch — it is too late to say anything neutral about it. Whatever you do next reads as a reaction to one specific person, never as a rule that was already there.
5 numbers that separate a policy from a reaction
None of these come from a market survey — they are structural mechanisms: how platforms work, how GDPR applies the moment somebody is identifiable, and what actually makes a restriction hold up. That is exactly why they are worth naming: obvious once said out loud, and almost never said before the fact.
1. Zero — the number of accounts you actually control
The video is not on your account. It is on your staff member's own personal account, and that account belongs to them, not to you. You can ask for something to come down; you cannot force it, and a platform answers to the account holder, never to the venue the clip is about.
That is why "we'll just get it taken down" is not a plan. By the time a colleague has asked, the platform has replied and the clip is finally gone, others have already saved it, forwarded it, or reposted it elsewhere. Prevention is the only lever that is actually yours to pull.
No survey, no external study — structural mechanisms that apply to any venue in Europe, whatever its size or location.
These are mechanisms, not statistics with a source underneath — how platforms, data protection and working relationships actually function. For the exact legal limits in your own country, see the FAQ below.
2. One — the identifiable face that turns a fun clip into a GDPR question
The moment one colleague or guest is recognisable on screen, that clip stops being a fun moment and becomes the processing of personal data — a photo or video of an identifiable person falls under the same rules as a name or an address. That applies to whoever is filming, not only to the venue: a staff member filming a colleague without asking is, in principle, doing the same thing the venue itself would be doing without consent.
For guests it cuts a little sharper, because they never chose to work at your venue: photographing or filming somebody purely for content, without asking, is exactly the territory the related article on photographing guests for Instagram covers in more depth.
3. One — the number of moments a policy still reads as neutral
Before anything has happened. That is the only one. A rule introduced right after one specific staff member posts the wrong thing does not read as policy — it reads as a measure against that one person, and the rest of the team reads it exactly that way too.
A rule that is already on the table at onboarding, signed alongside the rest of the agreements, is the opposite: a standard that applied to everyone equally before anything was ever at stake. That is also why it belongs in the same document as the rest of the onboarding plan, not in a one-off e-mail after an incident.
4. Three — the only things a rule can actually stand on
A blanket "don't post about work, full stop" rarely holds up in practice and is rarely followed — it is too broad to still have a reason behind it. What does hold up always traces back to one of three things: a trade secret (a dish, a price, a supplier before launch), a colleague's or guest's privacy, or the venue's own brand and image rights.
Write every rule back to one of those three. "No photos of guests without their consent" is a privacy rule with a reason. "No photos, period" is a mood, not a rule — and that difference is exactly what decides whether anyone actually follows it.
5. What a damaging post actually costs, in bookings
The number most owners have never worked out is not legal — it is commercial. A clip that lands badly does not cost a fine; it costs a few weeks of lower turnout, exactly when nobody planned for it. Work out below what that would mean for your own venue, with your own numbers.
An editorial judgement, not a measured figure: where a bar stops speaks to how much could go wrong, not how often it happens.
Low does not mean risk-free, and high does not mean forbidden — it speaks to how hard it is to undo once it is posted.
What would a dip in bookings actually cost you?
No restaurant tracks exactly what a bad week costs — which is why it is the number most owners have never worked out. Type your own figures; everything runs in your own browser and nothing is saved or sent anywhere.
The cost of a temporary dip
Default: a 12% dip over two weeks — replace both with what you would expect at your own venue.
—
Default: 220 guests a week, €32 average spend, a 12% dip, 2 weeks — an average 50-seat bistro.
Illustrative, not a forecast. How long and how deep a real dip runs depends on how visible the incident was and how quickly and honestly it was addressed.
How to be ready before you need this
Write three rules, not thirty — and tie each one back to one of the three things that actually hold up: trade secrets, colleague and guest privacy, and the brand. A list of thirty bans gets read by nobody; three rules with a reason attached get followed.
Put those three rules in the same document as the rest of onboarding — the staff handbook every new hire already signs alongside the other house rules. That is the moment it still reads as a standard, not as a reaction.
Say just as clearly what IS welcome and even wanted — a proud moment, a full room, a new dish once it is already on the menu. A team that knows what is fine rarely posts, by accident, what isn't.
The short answer
You cannot undo a clip once it is posted — which is exactly why prevention is the only lever that matters. A written rule, signed at onboarding, that limits itself to trade secrets, privacy and the brand holds up in practice. A blanket ban does not.
The calculator above puts a number on it: usually a bigger number than the time it takes to write three sentences and talk them through on the first shift.