NGO Website Development in India: How to Publish Beneficiary Stories and Photos Without Breaking Trust or the Law

NGO Website Development in India: How to Publish Beneficiary Stories and Photos Without Breaking Trust or the Law

An NGO can publish beneficiary stories and photos safely if it gets informed, specific and withdrawable consent from the person (or from a parent or guardian for a child), tells the story with the person's dignity and agency intact, and builds the website so that a photo or story can be changed or removed quickly and does not leak hidden data such as GPS location. In NGO website development in India, the legal duty is only part of the job. The larger part is practical: who is allowed to publish, what goes into a file name and alt text, whether a page can be indexed, and what happens when someone later says "please take me down". This guide is for communications leads and founders who publish stories and want a workable process, not a lecture.

Nothing here is legal advice. The laws below are described from their published text and from commentary, and how they apply to your facts is a question for a qualified lawyer. Where a point depends on rules that are still being phased in, we say so.

Why stories work for donors, and where the risk sits

A specific account of one person, why she needed help and what changed gives a visitor something to understand, which is why most NGO sites lead with stories. The same property makes them risky: they contain names, faces, health conditions and locations of people who are often poor, young, ill or at risk. Once published, the material can be copied, scraped, indexed by search engines, run through face search tools and shared on WhatsApp long after your campaign ends.

The risks are harm to the person (a neighbour recognises a woman from a shelter story), legal exposure, loss of trust when beneficiaries feel used, and operational failure: a consent nobody can find, or a volunteer who posts without approval.

The legal frame in plain language

DPDP Act 2023 and a person's photo

India's Digital Personal Data Protection Act 2023 covers digital personal data, and a photo, video or story that identifies a living person is personal data. The organisation that decides why and how the data is used, usually your NGO, is called a Data Fiduciary. The general model is consent that is free, specific, informed, unconditional and unambiguous, given by a clear affirmative action, and as easy to withdraw as to give. The Act also lists "legitimate uses" that do not need consent, but a promotional story on your website is not an obvious fit, so plan for consent and confirm your case with counsel.

The Act and the DPDP Rules 2025 are published on the Ministry of Electronics and Information Technology (MeitY) website. We cover donor records in our article on NGO donor data protection under the DPDP Act and sites in general in DPDP Act website compliance in India.

Phasing: check the current status

The Rules were notified in November 2025 with staggered commencement. Commentary on them (for example SCC Online's summary) reports that most operational rules, including the one on children's data, take effect eighteen months after publication, which points to around the middle of 2027. Today is October 2026, so verify the current position on the MeitY site before relying on any date.

Children under 18

Section 9 of the Act deals with children, defined as anyone under eighteen. As published, it requires verifiable consent of the parent or lawful guardian before a child's personal data is processed. It says a Data Fiduciary shall not undertake tracking or behavioural monitoring of children or targeted advertising directed at children, and shall not process data in a way likely to harm a child's well-being. Exemptions for certain classes and purposes can be prescribed. Rule 10 of the 2025 Rules describes how verifiable parental consent is to be obtained; read it directly.

Two practical points. First, treat everyone under eighteen as a child, so a sixteen-year-old's story needs a parent or guardian's consent plus the young person's own recorded assent. Second, the tracking restriction means a page featuring a child should not load advertising pixels, remarketing tags or behavioural analytics.

Identity protection for children in legal proceedings

Two other laws are stricter than consent and apply to a narrower group of children. They restrict identification whatever a parent signs.

• Juvenile Justice (Care and Protection of Children) Act 2015, section 74. As published, no report in any newspaper, audio-visual media or other form of communication about an inquiry, investigation or judicial procedure may disclose the name, address, school or any particular that could identify a child in conflict with law, a child in need of care and protection, or a child victim or witness of a crime, and no picture of such a child may be published. The Board or Committee may permit disclosure, for reasons recorded in writing, in the child's best interest. The penalty is up to six months' imprisonment, or a fine up to two lakh rupees, or both.
• POCSO Act 2012, section 23. As published, no media report may disclose a child's identity, including name, address, photograph, family details, school or neighbourhood, unless a Special Court permits it in the child's interest. The publisher or owner is jointly liable for employees' acts, and the penalty is six months to one year of imprisonment, or a fine, or both.

The Ministry of Information and Broadcasting issued an advisory on these provisions in October 2018. Whether an NGO website counts as "media" under them is a question for counsel, and a cautious NGO assumes it does. The working rule: a child in conflict with the law, in the care system, or a victim or witness of a crime is never identifiable on your website, by face, name, school, village or a combination of details, and not even with a parent's signature.

Consent that holds up

Consent has five qualities. If one is missing, treat the story as unpublished.

1. Informed. The person knows where the material will appear (website, social media, printed report, donor emails, press), that anyone can copy it, and that it may stay online for years.
2. Specific. Separate choices for story text, photo, video, name, location and each channel. One "I agree to everything" box is weak.
3. Voluntary. Help is not conditional on agreeing. Where possible, someone other than the service provider explains the choice and says that no changes nothing.
4. In a language the person understands. For people who cannot read, record how the explanation was given, with a witness.
5. Withdrawable. The person knows how to withdraw and that you will remove the material from your channels within a stated time.

Consent form outline (not legal text)

Have counsel finalise the wording. A useful form covers: who we are and a named contact; tick boxes for what we may share (story text, photographs, video, first or full name, age, location, sensitive details); where it may appear (website, newsletter, social media, annual report, press); identity options (full identification, first name only, pseudonym with a non-facial image, no image); how long it stays online and when we review it; your rights to say no, change your mind and request removal; what we cannot control (existing copies, slow search caches); signature or thumb impression with date, language and who explained it; and for a child, the parent or guardian's details, how identity was verified, and the child's own assent in age-appropriate words.

Consent register template

Keep the register securely, separate from the public CMS, with limited access.

The "where published" column is the one most NGOs omit, and it is what turns a takedown from weeks into hours.

Dignity-first storytelling

Consent answers "may we". Editorial standards answer "should we". A short code for the wall of the communications office:

• Agency over pity. Show the person as the one who acted: the woman who started the tailoring unit, not the woman "rescued" from poverty. Use her words and let her choose what to include.
• No before-and-after exploitation. Do not use a child's worst moment, a wound, a hospital bed or a hungry face as a headline image. A "dirty before, clean after" pair invites shame.
• Accuracy. Do not merge several people into one composite and call it real; label composites and illustrations.
• Review by the person. Show them the final draft and photo in their language before it goes live.
• Do no harm by detail. Ask whether a neighbour, an abuser, a creditor or an employer could identify the person from age, village, occupation and a distinctive background object.

Our articles on transparency and impact reporting for NGO websites and NGO impact report metrics cover how stories sit alongside evidence.

Pseudonyms and testimonials

If you use a pseudonym, say so once: "Names in these stories have been changed." A pseudonym protects no one whose face, village and job remain, so pair it with a non-facial image such as hands at work or an illustration, and keep the real name only in the register. A testimonial that cannot be traced to a consent record should not be on the site.

AI-generated images

Generated images can avoid photographing vulnerable people, but an image of a "beneficiary" who never existed misleads donors if shown as documentary. Label it ("illustration, generated with AI, not a real person"), never use it as evidence of impact, and never imitate real beneficiaries.

Technical handling on the website

1. Strip hidden data from images

Phone photos usually carry EXIF metadata, which can include date, time, device model and GPS coordinates. A picture of a shelter posted as the original file can reveal where it is. Strip metadata on upload, ideally automatically in the CMS or image pipeline, and verify by opening a published image in a metadata viewer. Keep originals in a private store. Many optimisation tools strip metadata by default, but check.

2. File names and alt text

Use neutral file names such as tailoring-unit-pune-2026-03.jpg, never sunita-sharma-hiv-patient.jpg. File names appear in URLs and in image search.

Alt text exists for people who use screen readers, and Google's image guidance recommends useful, descriptive alt text. Descriptive does not mean identifying. Write "A woman stitching at a sewing machine in a small workshop", not a name plus a condition or location. Keep sensitive categories ("rape survivor", "HIV positive child") out of alt text, captions, page titles and meta descriptions whenever a face or name is present, because titles and descriptions appear in search results.

3. Indexing controls for sensitive pages

For pages you do not want in search results, use a noindex directive (robots meta tag or X-Robots-Tag header). Do not rely on robots.txt alone: it stops crawling but does not guarantee a URL stays out of the index, and if a page is blocked Google cannot see a noindex on it, as Google's documentation on blocking indexing explains. Keep sensitive pages out of the XML sitemap. A story meant only for partners or donors can sit behind a login.

4. Galleries and face search

Public galleries of identifiable children are what scrapers and face search tools prefer. For minors, avoid galleries pairing faces with names, schools or locations; prefer hands, backs and distant group scenes, and never tag children by name. Blocking right-click gives little protection; not publishing the face does.

5. Embedded video and social widgets

An embedded YouTube, Instagram or Facebook player usually loads third-party scripts and cookies when the page opens, and the platform may track the viewer. On a page featuring a child, that collides with the DPDP Act's restriction on tracking and targeted advertising directed at children. Safer options:

• Use a privacy-enhanced embed mode where offered, or a click-to-load placeholder so nothing loads until the visitor presses play.
• Host the video yourself or on a service without advertising, then check the browser developer tools for third-party requests.
• Remove marketing pixels and remarketing tags from story pages involving children. Our article on remarketing audiences and consent explains how tag consent works in practice.

6. CMS roles and permissions

Many leaks come from a well-meaning volunteer with admin access. Set up at least these roles:

Add a required "consent ID" field on every story and image upload and block publishing without it. Turn on two-factor authentication for publishers and keep an audit log.

7. Retention and archiving

Set a review period, for example yearly, and at review renew consent, archive the page or delete it. Write the periods into your privacy notice, delete original photos you no longer need, and keep consent records while the story is public plus a period your counsel advises.

Takedown and withdrawal workflow

Withdrawing must be easy, and you must be able to act. The target times below are examples to adapt, not legal requirements.

On search: once the page is removed or changed, Google's outdated-content tools and help pages let you ask it to refresh, and people can use Google's own form for removing personal content from Search when it meets its personal-content policies. Google cannot delete content from the web itself; only the site owner can, so your own removal comes first.

Put a visible line on every story page: "If you appear in this story and want it changed or removed, contact [name, email, phone]". It signals respect and makes withdrawal as easy as giving consent.

Decision tree in text

Answer in order and stop when you reach an action.

1. A child in conflict with the law, in the care or protection system, or a victim or witness of a crime? Do not publish anything identifying; use general text or an illustration and ask counsel. Any other child, go to 2; an adult, go to 3.
2. Verifiable parent or guardian consent, the child's assent and a form in their language? If not, do not publish. If yes, go to 4.
3. Informed, specific, recorded consent collected independently of service delivery? If not, do not publish. If yes, go to 4.
4. Could face, name, location, condition and background together identify or harm the person? If yes, lower the identity level (pseudonym, no face, general location) and ask again.
5. Has the person seen the final draft and image in their language? If not, show them.
6. Metadata stripped, alt text and file names checked, consent ID entered, no third-party trackers? Then an authorised publisher approves, and the review date goes into the register.

Story-publishing checklist

Copy this into your CMS workflow.

• Consent form completed in the person's language, explained by someone independent of service delivery
• Parent or guardian consent and the child's assent recorded for anyone under 18
• Safeguarding check: not a child covered by juvenile justice or POCSO identity rules
• Uses and identity level ticked in the register
• Person shown with agency, in their words; no pity imagery; composites and AI images labelled
• Person has reviewed the final draft and image
• EXIF and GPS removed; neutral file names; alt text, title and description free of identifying detail
• Noindex or login protection where needed; not in the XML sitemap
• No ad pixels or behavioural tracking on pages with children; embedded video loads on click
• Removal request line on the page; register updated with URLs and review date

Common mistakes

• One blanket consent signed years ago, reused for later uses such as a fundraising video.
• Consent collected by the person who controls services, so nobody feels free to refuse.
• Hidden location data or a sign board in the background that names the shelter.
• Names and conditions in alt text or file names, which are indexed even when the page looks anonymous.
• Face visible, name changed, and volunteers with publish rights.
• No list of where a story was used, so a withdrawal cannot be completed.
• Treating a parent's signature as enough for a child in care or legal proceedings.

Working with Govindani Infotech

Govindani Infotech Pvt. Ltd. is a web design and development company in Pune, and we have built more than 500 NGO websites. If you want your site set up with a story-submission form that requires a consent ID, image metadata stripping, role-based publishing, click-to-load video and a removal-request workflow, we can review your current site and tell you what is needed. See how we approach NGO sites on our NGO website page, and what a build includes on our website creation service page. For other essentials, see our guide to must-have NGO website features.

To talk it through, message us on WhatsApp or use the contact page. The legal wording of your consent forms should come from your own counsel; we build the website and workflow around it.

To publish such stories on an ongoing basis, see our guide to building an NGO news and updates section.

Frequently Asked Questions

Do we need consent to publish a beneficiary's photo on our NGO website?

In practice, yes. A photo that identifies a person is personal data under the DPDP Act 2023, and a promotional story is not an obvious fit for the uses that skip consent. Get informed, specific consent the person can withdraw, record it, and confirm the current commencement status of the Rules with your counsel.

Can we publish photos of children if a parent signs the form?

Not always. For children generally, the DPDP Act asks for verifiable consent of a parent or guardian and restricts tracking and targeted advertising aimed at children. For a child in conflict with the law, in need of care and protection, or a victim or witness of a crime, the Juvenile Justice Act and POCSO restrict identification regardless of a parent's signature. Ask counsel before publishing.

How do we remove a beneficiary story if someone withdraws consent?

Hide the page quickly, delete the media files, remove it from newsletters and social posts you control, clear caches, and use Google's refresh or removal tools if the old version still appears in search. Then confirm in writing and update your register. Set target times in advance and keep to them.

Should alt text include the beneficiary's name?

No. Alt text should describe what is visible so screen reader users understand the image, without names, diagnoses or locations that identify a vulnerable person. Use the same care in file names, captions and page titles.

Is it acceptable to use AI-generated images instead of real beneficiary photos?

It can be, if you label them clearly, do not present them as evidence of real impact, and do not imitate real beneficiaries. Many NGOs find an illustration or licensed stock image simpler and more honest.