Back to blog
Guide

The Photograph You Posted On Sunday

The picture is good, the room looks full, and it goes up on Sunday afternoon. On Tuesday somebody messages asking you to take it down, and nobody in the venue has ever decided what happens next.

The picture is genuinely good. The room looks full, the light is right, and it goes up on Sunday afternoon because Sunday afternoon is when people look.

On Tuesday a message arrives. Somebody in the background wants it taken down. They are not angry, but they are serious, and the person who reads the message is whoever happens to have the login. What happens in the next hour has never been decided by anybody.

⚠️ What this page cannot tell you

What you may photograph, what you may publish, what consent you need, how long you may keep images and what you must do when somebody asks for removal are legal questions. They involve image rights, data protection and — where a photograph identifies somebody — rules that can carry real penalties. They differ by country.

This page is not that and cannot substitute for it.Ask your solicitor what applies to your premises and to your posting, get it in writing, and put the answer where whoever holds the login can read it.

⭕ What follows is the operational half only: the arrangements that make Tuesday manageable, whatever the law says.

The Licence Conditions Nobody Reads

Why a venue is different from a restaurant

Three things make this harder here than almost anywhere else.

People are not where they said they were

⚠️ ⛔ This is the whole subject in one line. A photograph places a specific person in a specific room at a specific hour, and for some guests that is the single most sensitive fact about their evening.

⭕ The request to remove it is very rarely about vanity, and treating it that way is the mistake that turns a message into a complaint.

The background is full of people who did not agree to anything

⇒ The subject of the photo posed. ⚠️ The eleven people behind them did not, and one of them is the one who messages on Tuesday.

And everybody has a camera

⭕ Staff, guests, promoters, performers. Your own posting is a small fraction of the images of your room that exist, but it is the only one you control and the only one you will be asked about.

The Staff Account That Is Also Your Marketing

What actually goes wrong

None of these involve anybody behaving badly.

Nobody decided who can post

⚠️ ⭕ The login is shared, and shared logins mean nobody is responsible. A photo goes up because somebody had it and thought it was good, which is exactly how it should feel — but only if somebody owns the decision.

The request arrives where nobody is looking

⇒ A comment, a direct message, a message to a personal account, a word to a door supervisor. ⭕ The single most common failure is that the request is never seen, and silence reads as refusal.

The Complaint That Never Reached You

The person who can take it down is asleep

⚠️ These messages arrive on Sunday evening and Monday morning. If removal requires one specific person who works Thursday to Saturday, the delay is built in.

And the reply makes it worse

⭕ "It's a public place" is often true and is almost always the wrong sentence. ⚠️ A defensive first reply converts a removal request into a formal complaint more reliably than anything else on this page.

What to settle before the next photograph

Everything else follows from these, and none of them costs anything.

One: who can post, by name

⇒ ⭕ Not a role, a person, with a named second. Shared access with nobody accountable is the arrangement that produces the Sunday photo nobody would have approved.

Two: where removal requests are supposed to arrive

⚠️ ⭕ One place, and everybody who might be told is told where it is. Door staff, bar staff and the person on the account all need the same answer.

Three: what the answer is, and how fast

⭕ Deciding in advance that requests are actioned without argument, within a stated time, removes the entire negotiation. ⚠️ The speed matters more than the wording — most people who ask are anxious, and a fast, plain reply ends it.

The Review You Never Replied To

What makes the request easy to action

The decision is only half of it. Removal has to actually be possible.

You know where else it went

⚠️ ⭕ A photo posted once is usually posted three times — the main account, a story, a repost by a promoter. Taking down one of three is worse than useless, because it looks like compliance and is not.

Somebody can reach the account today

⇒ Not "the person who runs the socials". ⭕ Two people, both able to act, one of whom is around on a Monday.

The Keys You Cannot Account For

The original is findable

⚠️ If a version is cropped or reused later, the venue needs to know which images relate to which night — otherwise the same picture reappears in six months in a montage.

And somebody notes that it happened

⇒ ⭕ One line: what was asked, when, what was done. Not for bureaucracy — because a second request from the same person, handled as if it were the first, is what escalates.

The Incident Log You Do Not Keep

Reducing how often it happens

Prevention here is cheap and almost nobody does it.

Shoot the room, not the faces

Wide, from behind, at an angle, in motion. A room that looks full does not require identifiable people, and the photographs that work commercially usually do not need them anyway.

Post the room and the detail, not the crowd

⇒ The bar, the light, the glass, the queue from behind. ⚠️ These perform comparably and generate no requests at all.

The Photo Everyone Sees First

Tell people when a camera is working

⛔ ⚠️ Whether notice is required, and what it must say, is a legal question in most places — ask. ⭕ Operationally, a visible sign and a word at the door removes most surprises, and surprise is what produces Tuesday's message.

Ask the subject, on the night

⇒ ⭕ Thirty seconds and it removes the entire question for that photograph. It also produces better pictures, because people who agreed are looking at the camera.

And be careful with private hire

⚠️ ⭕ A birthday, a work party, a private booking — the expectation is completely different, and posting from one of those without asking the organiser is the version that damages a relationship rather than generating a message.

The Birthday Booking

The situations that need extra care

Four cases where the ordinary approach is not enough.

Somebody who is visibly drunk

⚠️ ⛔ Posting an identifiable person in that state is the version most likely to produce something more serious than a removal request. ⭕ The operational rule is simple: do not.

Somebody who is working

⇒ Staff and performers are in your photographs constantly. ⭕ They are also in a position where saying no is harder, which is why asking has to be genuinely optional and asked away from a manager.

The Shift Where Everyone Is New

Somebody who has asked before

Keep a note. A person who asked to be removed in March and appears again in September has a much stronger grievance, and a venue with no record cannot avoid it.

And guests who did not follow what was asked

The Guests Who Do Not Speak Your Language

What good looks like

The login test

Ask who can take a photo down within an hour on a Monday morning. ⇒ Two names means this works. One name, or a pause, means it does not.

The three-places test

⚠️ Take a photo you posted last month and find every place it went. If you cannot list them, removal is not something you can actually deliver.

The reply test

Working     — a removal request is actioned without argument, same day
Not working — the first reply explains why the venue was entitled to post it

Three to hold

1  A photograph places a person somewhere at a time — that is the whole sensitivity
2  A photo posted once is usually posted three times; taking down one is not removal
3  Speed of reply matters more than wording — most people asking are anxious, not angry

Where the record has to sit

Who posted what, on which night, to which places, and every request that arrived with what was done about it — with the other operating records rather than in the memory of whoever holds the login. Kept there, Tuesday takes ten minutes and ends. Kept nowhere, a reasonable request meets silence for two days and then a defensive reply, and a person who only wanted a picture taken down becomes somebody with a complaint about how the venue handled it.

The Report You Open Every Monday

Read next

Free, no signup, ~5 minutes

Map out your operations in 5 minutes

Eight questions cover reservations, customer management, shifts, and settlement. Results shown instantly with industry benchmark. Sales emails only if you request them.

Your answers are not stored. The assessment runs entirely in your browser.

Try tasteck free for 30 days

No credit card required. Full access to reservations, cast shifts, dispatch, and analytics.

  • No card required
  • Free data migration support
  • All features unlocked for 30 days