In this article
Your chef flambés something, someone films it for Instagram, and in the background sits a table that never chose to be there. That shot isn't a marketing question — it's a legal one, and most venues never answer it.
Every restaurant now films itself: the opening shift, the new menu, the buzz on a busy Friday. That's exactly what works on Instagram and TikTok — but a room is never empty while you're filming, and every clip carries guests nobody asked whether they wanted to be in it.
Two other articles on this blog already touch related ground: how to collect customer data (name, email, booking history) in a GDPR-compliant way, and how to run CCTV cameras at the till within the rules. Both are about data YOU record for YOUR own operation. This article is about something else: a guest's image, captured to be shared with the outside world.
That image is protected twice over. Under GDPR, a recognisable face is personal data, full stop — whether you have five followers or five thousand. And separately, almost every EU country has its own "right to one's own image": France's droit à l'image, Germany's Recht am eigenen Bild with its own statute (the Kunsturhebergesetz), and a case-law-built variant of the same principle in Belgium and the Netherlands.
The good news: the rules are predictable once you walk them in the right order. This article lays them out as a ladder — from "no problem" to "don't post" — plus a test that tells you in ten seconds where a specific photo sits on that ladder.
Why this is more than a theoretical question
In Spain, the AEPD — the national data protection authority — fined a gym €21,000 for filming classes and posting them on social media without valid consent, and a second gym chain up to €36,000 (reduced to €15,000 for early settlement) for the same practice. The regulator ruled explicitly that "film along or leave" is not freely given consent — exactly the mechanism a restaurant reproduces when it tells a table "we're shooting content tonight, just act natural."
That's the core of the problem: a restaurant shooting content repeats the same mistake, only with guests instead of gym members. And the damage is rarely the fine itself — it's the guest complaining publicly, the time a complaint costs, and the fact that one ignored takedown request escalates into a complaint to the regulator, while a request resolved within a day costs nothing.
So this isn't a question of "what if there's ever an inspection" — it's a question of what an ordinary Thursday night already produces the moment a camera is involved. Six rules decide whether that's trouble-free.
The ultimate guide Restaurant Technology: 6 Steps from 7 Tools to 1 System From customer data to cameras to content policy: everything your systems need to handle for you, in one guide. Open the guideThe six rules, in the order the law actually applies them
Each rule builds on the last. The moment an answer is "no", you don't need to climb the rest of the ladder — you already know enough.
1. Recognisable is enough — a face in a photo is personal data
GDPR defines personal data as any information that can identify a person, directly or indirectly (Art. 4(1)). A face is the most obvious example there is. The moment someone is recognisable in a photo — not centred, not sharp, just recognisable — you're processing personal data as soon as you publish it. That applies to your own Instagram account just as much as to a customer database.
This has nothing to do with how many followers you have or how "small" the post is. GDPR draws no line between a business account with twelve followers and an influencer with a million. The question is never "is this big enough to matter" — it's "is this person recognisable".
What does count: unrecognisable is unrecognisable. A back, a blurred background, a face out of frame — that's not personal data, and this whole article stops applying. The simplest way to remove a risk is still turning the camera a few centimetres.
2. Incidental often needs no consent — the main subject always does
Not every recognisable guest is a problem. Germany writes this into law explicitly: the Kunsturhebergesetz (KUG) requires consent in principle (§22), but carves out an exception for people who are merely incidental to a place or scene (§23(1) No. 2) — the so-called Beiwerk rule. Think of a table that happens to sit in the background while you film the interior, not a guest who is the actual subject of the shot.
That exception is narrower than it sounds, and it doesn't apply the same way everywhere. Even in Germany it falls away the moment publication harms a legitimate interest of the person shown (§23(2) KUG) — a guest caught in a compromising moment is never "incidental", however briefly they're in frame. And countries like France apply a stricter starting point, where even an incidental recognisable presence is treated as a problem sooner.
The practical rule of thumb, everywhere: the more central and sharp a person is in the shot, the stronger the duty to ask. A test almost every country applies is simple: would an average viewer say the photo is about that person, or about the place? When in doubt, ask.
Every photo sits somewhere on this ladder. The higher up, the more you need to sort out before publishing.
The ladder follows rules 1 through 3 above: recognisability, the incidental/main-subject line, and the type of consent.
3. Consent for the table photo isn't consent to post it
Say you do ask — "can I get a quick shot of your table?" — and the guests nod. That's consent for the photo itself, not for what you do with it afterwards. France's data protection authority, the CNIL, is explicit here: consent has to be specific to the intended use, and an agreement to a photo you share privately with the table itself doesn't automatically count as agreement to publish that same photo on the restaurant's public Instagram.
That's also exactly what GDPR means by "freely given, specific and informed consent" (Art. 4(11), Art. 7). "Specific" is the word most venues skip: you have to say WHERE the photo will end up — your Instagram account, your website, a flyer — for the consent to be valid for that use.
In practice this costs one extra sentence most venues currently don't say: not "can I take a photo", but "can I take a photo for our Instagram?" That costs nothing, and it's the difference between valid consent and a photo standing on shaky ground.
4. Staff on camera is a different file from guests
A staff member who appears in content sits under a different legal basis than a guest: the employment relationship. That doesn't make consent unnecessary — an employee still has to be able to refuse freely, without consequences for the job, and "freely" is exactly where it usually goes wrong, because an employee who feels pressured by the boss isn't giving free consent in the GDPR sense.
What is practical: a staff member can settle this once, through an internal policy or an employment-contract clause, instead of asking again every shift. That route doesn't exist for a guest — they're there for one evening, so consent has to be asked fresh every time.
In short: handle the staff piece separately — a clear, written policy every employee signs on joining, with a genuine right to refuse — and treat every guest as a new case. Two files, two processes.
5. What your country adds — from "just ask" to written proof
GDPR applies the same way across the EU, but the portrait right layered on top of it differs per country, and that decides how much weight to put on your evidence. Germany has the Beiwerk exception above, with a statute to point to. France runs on droit à l'image, where the CNIL explicitly recommends asking for written consent before publication — a verbal "yes" is weaker evidence in front of a French court than it is elsewhere.
Belgium and the Netherlands build on the same underlying principle — the portrait right, partly rooted in copyright law — but without Germany's explicit Beiwerk carve-out: the balancing act happens more case by case, through case law rather than a fixed statute.
Operating in several countries, or posting content that can be viewed across several (which, on Instagram, is true by definition)? Assume the strictest regime that could apply to you, not the most lenient one. That's usually France: ask specifically, ask in writing where you can, and you're covered everywhere.
6. A refusal must never be a lost post — build the workflow
The real problem is rarely the first ask — it's what happens when someone refuses, or asks afterwards to have a photo taken down. GDPR gives a guest a concrete, enforceable right to this (Art. 17, the right to erasure) and a concrete deadline to respond: in principle within one month of the request (Art. 12(3)), extendable by a further two months for complex or numerous requests — provided you tell the guest within that first month.
Build that in as a standing process, not an exception: who on the team may edit or remove a post, how fast (the fastest answer costs literally nothing — cropping or blurring takes a minute), and where you log it so you can show you responded within the deadline.
A refusal then "costs" you at most one shot out of ten. An ignored request costs you the complaint, the response time and, in the worst case, as the Spanish cases above show, a fine wildly out of proportion to what it would have cost to simply ask.
The same guest request, two very different paths.
The one-month deadline comes from GDPR Art. 12(3) — see rule 6.
Test: is this photo safe to post?
The six rules above translate into one decision per photo: post it, adjust it, or ask first. The test below does that translation for you — four questions, an instant answer.
Already received a takedown request? The counter below works out how much time is left on the statutory GDPR Art. 12(3) deadline.
Four questions, one answer
Answer the four questions for the photo you want to post.
—
—
Based on GDPR Art. 12(3): in principle one month (treated here as 30 days), extendable by a further two months for complex or numerous requests — provided you tell the guest within the first month.
No test replaces a lawyer for a genuinely borderline case — this gives you the direction, not the final word. If in doubt about a specific, sensitive situation (a minor, a medical moment, a family argument that happened to be in frame): always ask, whatever the test says.
What the test does do: answer the nine ordinary evenings out of ten — a busy room, a good mood, a happy table — in a few seconds, so the team doesn't have to guess every time.
What you do this week, this month and this quarter
Rolling out six rules at once doesn't work for anyone. This order does, because each step makes the next one easier.
This week — put the process on paper
- Write down one line the team says before every content shoot: "we're grabbing some shots for Instagram in a bit, is that okay?"
- Assign one person to handle a takedown request, and agree a response time — not "whenever I get to it".
- Bookmark the test from this article on the phone the team uses to shoot content.
This month — sort out the staff piece
- Have every employee sign a short policy: appear on camera or not, and how they flag it.
- Check your last ten Instagram posts: is there a recognisable guest in one where you can't recall whether you asked?
- Set up a fixed folder or chat where the team can log a "take this down" request straight away — not a stray DM that gets lost.
This quarter — build the evidence
- Start asking for written consent (a short confirming message is enough) for every shoot with a clear main subject.
- Review your content calendar: schedule fixed "content moments" rather than filming guests at random — that makes it easier to ask in advance.
- Line these six rules up against your customer-data and camera policies, so you end up with one coherent privacy policy instead of three separate ones.
One photo, six questions, no more guessing
Shooting content for Instagram is part of the job now, and it doesn't have to be a risk. The risk isn't in the filming — it's in the guessing.
Recognisable or not. Main subject or incidental. Consent, and for exactly what. Private or public. Four questions, in that order, and most evenings are answered within ten seconds.
And when it does go wrong: respond fast to a takedown request. That's the difference between a photo you simply adjust, and a complaint that costs weeks.