
A happy customer tags your shop in a great photo. It looks better than anything your designer made, so you want to put it in a Facebook ad tomorrow. Most SME owners assume the tag, the like or a quick “sure!” in the comments is enough. It usually is not.
This guide covers the rules on using customer photos in ads in Malaysia: who owns the photo, who must agree to appear in it, and how to collect permission that holds up. It comes from ZenWeb, a Malaysian Google Partner agency with 500+ clients. We are a marketing agency, not a law firm. Every clause below was checked against the official texts, as at October 2026.
This post is general information, not legal advice. Please confirm your own situation with a licensed lawyer before you rely on it.
Sitting on a folder of great customer photos?
We turn real customer content into Facebook and Instagram ads, with the permission trail set up before anything goes live. See our Meta ads management service →
This short US explainer asks who owns a photo: the person in it, or the person who took it? Malaysian law gives a similar default answer, as section 2 explains.
Source video: Carter Law Firm on YouTube. Published May 2015. It discusses US law, not Malaysian law.
Quick Answer: No. A customer photo carries two kinds of rights. The copyright belongs to whoever took the picture. The face and identity belong to each person shown in it. Using customer photos in ads without written permission from the photographer, and consent from every recognisable person, risks a copyright claim, a PDPA complaint and an ad rejection.
Reposting a tagged photo with credit feels normal on Instagram. A paid ad is different: you are using someone’s work and someone’s face to sell. Three sets of rules apply at once.
| Rule set | What it protects | Who must agree | Key provision |
|---|---|---|---|
| Copyright Act 1987 | The photo as a creative work | The photographer (copyright owner) | s26 ownership; s27(3) licence in writing |
| PDPA 2010 (amended 2024) | An identifiable person’s data, including their image | Each identifiable person (a parent for under-18s) | s6 consent; s7 notice; s38 withdrawal |
| ASA code (print, outdoor) | Privacy of any living person in an ad | Each person portrayed | Clause 12.1 express prior permission |
| Content Code 2022 (online, TV) | Individual privacy, read with the PDPA | Each person shown | Part 2, para 11.1 |
Source: Copyright Act 1987 (Act 332); PDPA 2010 (Act 709) and Act A1727; Malaysian Code of Advertising Practice 6th Ed.; Content Code 2022. Mapping is ZenWeb’s. As at October 2026. Licence.
The Copyright Act 1987 treats a photograph as an “artistic work”, irrespective of artistic quality, so a blurry phone snap is protected too. See our Copyright Act guide for marketers for the basics, and our explainer on what user-generated content is for the definition.
Quick Answer: The person who took it. Section 26(1) of the Copyright Act 1987 vests copyright in the author. If a customer’s friend took the photo, the friend owns it, not the customer in it. Only work you commission, or that staff make in their job, passes to you automatically under section 26(2), unless an agreement says otherwise.
The person who sends you a photo is not always the person who can license it.
| How the photo was made | Default copyright owner | Written licence needed from |
|---|---|---|
| Made by the customer’s side | ||
| Customer’s own selfie or product shot | The customer | The customer |
| Photo of the customer taken by a friend | The friend | The friend (plus consent from the customer shown) |
| Customer’s post you found by hashtag | Whoever took it | That person; a tag is not a licence |
| Made by your side | ||
| Staff photo of customers at your shop or event | You, as employer (s26(2)(b)) | None for copyright; consent still needed from people shown |
| Photographer you hired for the event | You, as commissioner (s26(2)(a)), unless the contract keeps it | Check the contract first |
| Paid UGC creator content | Depends on the contract | The creator, with ad usage named |
Source: ZenWeb mapping of sections 26 and 27 of the Copyright Act 1987, MyIPO updated text. As at October 2026. Licence.
The licence must be in writing. Section 27(3) says no assignment and no licence “shall have effect unless it is in writing”. We could not confirm whether a WhatsApp or DM reply counts as “writing” here, so a short signed form that names ad use is the safer standard.
Moral rights still apply. Under section 25, the author can object to missing credit or to edits that distort the work and harm their reputation, so cover cropping and added text in the release. The same logic applies to stock and Google images; see our guide to image copyright in Malaysia.
Quick Answer: Yes, for anyone who can be identified. The PDPA defines personal data as information about a person who is identified or identifiable from it, and a recognisable face used for a commercial purpose fits. The ASA code goes further: clause 12.1 says an ad should not portray any living person without their express prior permission.
The Personal Data Protection Act 2010 applies to data processed for commercial transactions, and advertising is exactly that. These PDPA points matter most:
The Malaysian Code of Advertising Practice allows one narrow exception in clause 12.2(i): inoffensive crowd background shots, which must be withdrawn if someone reasonably objects. Online, Part 2 paragraph 11.1 of the Content Code 2022 asks for respect for privacy in line with the PDPA. Members’ schemes that collect photos follow the same logic as loyalty programme data under PDPA.
Quick Answer: A signed release that names paid ads, the channels and a time period is the strongest. A tag, a like, a hashtag or a public post gives you no ad rights at all. In between sit DM replies and upload checkboxes, which work better when the wording is specific and you keep a dated record.
Here is ZenWeb’s own rating of how well each common type of permission covers both the copyright and PDPA sides when using customer photos in ads.
| Type of permission | Rating | Coverage |
|---|---|---|
| Customer tagged your brand | 0 | |
| Used your campaign hashtag | 1 | |
| “Sure!” reply in comments | 3 | |
| DM reply to a request naming ads | 5 | |
| Upload form with ad-use checkbox | 7 | |
| Signed release, channels and term named | 9 | |
| Signed release plus parent signature for minors | 10 |
Source: Illustrative rating by ZenWeb, based on Copyright Act 1987 s27(3), PDPA 2010 ss6–7 and ASA code clause 12.1. Not a legal test. As at October 2026. Licence.
A “yes” to reposting on your feed is not a “yes” to paid ads. And scraping photos from Facebook groups has the same flaw as buying lead lists under PDPA: you have the data but not the consent. Once permission is sorted, our guide to UGC ads covers the creative side.
Want customer content ads without the permission headache?
We build the upload form, the consent wording and the ad creative as one workflow. Check our Meta ads packages →
Quick Answer: Use one short written release that covers both the copyright licence and PDPA consent. Name the photo, the channels, paid advertising, any edits, the time period and how to withdraw. Collect it through a web form or signed sheet, store it with the photo, and set a date to review or remove the ad.
If photos arrive on WhatsApp, send the release link in the chat rather than relying on the chat itself; see WhatsApp marketing and PDPA. Keep releases for as long as the ad runs plus a sensible buffer, in line with how long you can keep data under PDPA. A release should contain:
| Clause | Why it matters | Sample wording |
|---|---|---|
| “I took this photo” | Confirms the signer can license it (s26) | “I confirm I took this photo or have the right to license it.” |
| Licence grant | Written licence (s27(3)) | “I allow [Business] to use this photo for…” |
| Channels incl. paid ads | Purpose stated in the notice (PDPA s7) | “…paid ads on Facebook, Instagram and Google, and our website.” |
| Edits | Moral rights (s25) | “…including cropping and adding text.” |
| Consent of people shown | PDPA s6; ASA clause 12.1 | “Everyone in the photo agrees, and I am their parent or guardian where under 18.” |
| Time period | Sets a clear end date | “…for 12 months from today.” |
| Withdrawal route | Right to withdraw (PDPA s38) | “Email or WhatsApp us to stop future use.” |
| BM and English versions | Notice in both languages (PDPA s7(3)) | Same text in Bahasa Malaysia |
Source: ZenWeb release template mapped to the Copyright Act 1987 ss25–27, PDPA 2010 ss6, 7 and 38, and ASA code clause 12.1. Sample wording only; have a lawyer review your final form. As at October 2026. Licence.
An agency or freelancer handling the photos acts as your data processor and must keep them secure. Our guide to appointing a Data Protection Officer explains who owns compliance on your side.
Quick Answer: The usual first result is a takedown request or an ad rejection. If it goes further, the photographer can sue under section 37 of the Copyright Act for statutory damages of up to RM25,000 per photo. A PDPA breach can reach a fine of up to RM1 million, jail of up to three years, or both, since the 2024 amendment.
On Meta, Meta’s third-party infringement policy bars ads that violate anyone’s intellectual property rights, and ads can be removed after a rights holder reports them. The legal ceilings are higher:
| Route | Maximum | Relative size |
|---|---|---|
| Copyright statutory damages, 1 photo | RM25,000 | |
| Copyright statutory damages, 10 photos | RM250,000 | |
| Copyright statutory damages, overall cap | RM500,000 | |
| PDPA fine, s5(2) as amended | RM1,000,000 (and/or up to 3 years’ jail) |
Source: Copyright Act 1987 s37(1)(d); PDPA 2010 s5(2) as amended by Act A1727. Maximums only; actual awards depend on the facts. As at October 2026. Licence.
Photo consent is also narrow. It does not cover uploading that customer’s email to Google Ads Customer Match or sending their data through Meta’s Conversions API. If you collect photos through Facebook lead ads, say “photos for ads” on the form.
Quick Answer: Sort each photo by who took it and who appears in it, then decide: use it, get a release first, or drop it. In a typical SME photo set, most images need only a quick release, while a few should never run because a child or stranger is in the frame.
Illustrative example, not a real client: a Petaling Jaya café wants five tagged customer photos for a Meta ads campaign.
| Photo | Issue | Decision |
|---|---|---|
| Latte art shot, no people, customer’s own photo | Copyright only | Send release link; run after signed |
| Two friends at a table, taken by a third friend | Photographer is not the poster; two faces | Release from photographer plus consent from both |
| Family photo with a toddler | Minor in the frame | Parent signature, or crop the child out |
| Weekend crowd shot by your own staff | You own copyright; strangers recognisable | Background use only; pull it on any objection |
| Influencer’s paid Reel | Contract silent on ads; needs a paid label | Amend contract; run as a partnership ad |
For creator content, Meta’s partnership ads run from the creator’s handle with permission set at post or account level. That permission does not replace your written contract, and paid posts still need a label (see our influencer disclosure guide). A quote beside the photo also brings in the testimonial advertising rules. When a release expires, automated rules or a calendar reminder can pause the ad.
Before using customer photos in ads, check each image against this list:
Real customers make the most believable ads, and the paperwork is lighter than it looks. If you pay Meta to boost them, also check withholding tax on Google and Facebook ads. Our Meta ads team can set up the consent form and run the campaign end to end.
A tag is not a licence. Ask first, and get a written “yes” that names ad use if you might boost the post later. Credit alone is not permission.
It is better than nothing, but section 27(3) of the Copyright Act requires a licence in writing, and the point is untested for chat replies. A short release form that names paid ads is the safer record.
From everyone who can be recognised, yes. ASA code clause 12.1 asks for express prior permission from any living person shown. Crowd background shots are a narrow exception.
Only with a parent or guardian’s written consent, since the PDPA treats them as the person who consents for anyone under 18. If you cannot get it, crop the child out or use another photo.
Yes, on the marketing side: upload forms, bilingual consent wording on your website and the ad workflow. We are not lawyers, so have a licensed lawyer review your final release terms.
Cite this page: ZenWeb (2026). Using Customer Photos in Ads: Consent and Copyright Rules. https://zenweb.my/blog/customer-photos-ads-consent/
You may quote our data with this credit and a link. See our Terms of Use.
Turn real customer photos into ads that sell
Talk to ZenWeb about customer-content campaigns with permission built in from day one. We handle the marketing; your lawyer handles the legal advice.
Get A Free Proposal
Complete the form and our team will contact you to discuss your goals. Let’s grow your business.
Chat with us on WhatsApp
Tell us a little about what you need. We'll open WhatsApp with your message ready to send.