Before you repost a customer's photo: rights basics

A customer posts a photo of your product, your café table, your finished work, and tags the business. It is flattering, it is on-topic, and it is far better than anything the business would have shot itself. The obvious move is to repost it.

The reason this feels like a non-question is that the customer clearly wanted the business to see it. That is true, and it is a different thing from wanting the business to publish it. A tag is an act of pointing, not an act of granting. The photograph remains the work of whoever took it, and the person in it has their own separate interest in where their face appears.

None of this makes reposting wrong. It makes it something to ask about, briefly, before doing. The ask takes under a minute and removes the entire category of problem, which is an unusually good trade for a step most businesses skip on the assumption that nobody would mind.

Two separate interests sit in a single customer photo, and conflating them is where confusion starts.

The first belongs to whoever pressed the shutter. Copyright in a photograph sits with its author from the moment it is made; no registration or notice is needed for that to be true. Reposting it is reproducing and publishing someone else's work, which is normally something you need their permission to do. If the customer was photographed by a friend, the person who can grant that permission may not be the person who posted it.

The second belongs to anyone recognisable in the image. Using a person's likeness to promote a business is a different act from displaying a photograph, and it is the part that carries the most risk when a business turns a repost into an advertisement, a printed banner or a paid promotion.

A platform's own terms let the platform display and distribute what users post. They are not a licence handed to other businesses to republish it elsewhere.

Three things get treated as consent and are not.

A like is acknowledgement. It communicates that the business saw the post and appreciated it, which is precisely as far as it goes. A tag or a mention is the customer directing the post at the business, and again it is about visibility rather than rights. A public account means anyone can view the post — that is what public means — and viewing is not republishing.

The strongest version of the mistaken argument is that the customer would obviously say yes. Often they would. But permission is not a prediction about what someone would agree to; it is the thing they actually agreed to. The cases where the assumption fails are not the ones anyone anticipates: the photo shows someone's child, or a home interior they did not intend to broadcast, or the person has since fallen out with the business, or they are happy to be reposted on a feed and unhappy to be in an advertisement.

Asking removes the need to predict.

The ask works best when it is short, specific, and makes the answer easy.

Send a direct message that says three things: that you loved the post, exactly where you would like to use it, and that you will credit them. Specificity is what turns a vague request into an easy yes, and it is also what makes the permission meaningful — someone agreeing to a feed post has not agreed to a printed poster. If there is any chance the image will be used in paid promotion or offline material, say so in the ask rather than coming back later.

A workable message is roughly: this photo is lovely, may we share it on our Instagram feed with credit to you? Nothing more elaborate is needed for ordinary reposting.

When someone says yes, thank them and honour the scope they agreed to. When someone says no, or does not reply, that is the answer. Silence is not a slow yes, and a request that goes unanswered leaves the business exactly where it started rather than halfway to permission.

Permission you cannot produce is close to permission you do not have. The value of a written ask is that the reply is a record, and the record is what resolves a disagreement months later when everyone's memory of the conversation has diverged.

So keep it. A screenshot of the exchange, saved with the image file or in whatever folder the business keeps its content in, is enough for ordinary use. What matters is that it captures who granted permission, what they granted it for, and when — the three facts that a later dispute turns on. A note in someone's memory that the customer definitely agreed is not that.

This is also where a broader habit helps. Businesses that repost regularly end up with a stream of images whose origins blur together, and the one that causes trouble is always the one nobody can trace. Filing the permission alongside the asset at the moment it is granted costs seconds and is the only version of this that survives staff turnover.

Most of the time, nothing. That is worth stating plainly, because pretending otherwise makes the advice easy to dismiss. The reason to do this is not that a reposted photo usually causes a problem; it is that the occasions when it does are cheap to prevent and expensive to fix.

The realistic outcomes, in rough order of likelihood, are: the customer is pleased and nothing else happens; the customer asks for the post to be taken down and the business does so, with some awkwardness; the photographer issues a complaint to the platform and the post is removed, sometimes with a strike against the account; or, in the cases involving paid promotion and a recognisable person, a demand for compensation for commercial use of their image.

The cost of avoiding all four is one direct message. Publishing tools, Socie among them, can hold a caption and an approval step for a post before it goes out — but the permission has to have been asked for and recorded by a person, because it is a conversation, not a workflow state.