India's synthetic media rules: label it, and take it down on the right clock
In force since 20 February 2026. Four takedown windows run from two hours to
seven days, and which one applies depends on how the notice is classified. Nobody is fined here
— the intermediary simply stops being immune.
20 Feb 2026G.S.R. 120(E), notified 10 February 2026.
Fastest clock
2 hoursFrom an individual's complaint about intimate imagery or impersonation.
Penalty
NoneNo fine, no offence. Rule 7 removes the section 79 safe harbour instead.
Text
ExcludedAudio, visual and audio-visual only. MeitY's FAQ says so expressly.
01The clock
India did not pass an AI act. It amended the intermediary rules that already governed platforms,
which is why the duties here attach to hosting and distribution rather than to model development
— and why the sanction is the loss of an immunity rather than a fine.
The draft is published
It proposed a label covering at least ten per cent of the display area, and for audio the
initial ten per cent of its duration. Neither figure survived.
A separate amendment takes effect
G.S.R. 775(E) rewrote rule 3(1)(d) with a 36-hour window. This is a different instrument, and
it is frequently conflated with the synthetic-media rules that followed.
G.S.R. 120(E) is notified
The Information Technology (Intermediary Guidelines and Digital Media Ethics Code) Amendment
Rules, 2026, published in the Gazette of India, Extraordinary. Some alerts date this to
16 February; the Gazette says the tenth.
The rules commence
Labelling, embedded provenance, user declarations, verification for significant social media
intermediaries, and the shortened takedown windows all begin.
02What counts as synthetically generated information
Audio, visual or audio-visual information which is artificially or algorithmically created,
generated, modified or altered using a computer resource, in a manner that such information appears
to be real, authentic or true and depicts or portrays any individual or event in a
manner that is, or is likely to be perceived as, indistinguishable from a natural person or
real-world event.
IT Rules 2021, rule 2(1)(wa), as inserted by G.S.R. 120(E)
The test is cumulative. Content must both appear real and be indistinguishable —
or likely perceived as indistinguishable — from a real person or event. Obviously stylised output
that nobody would take for reality does not meet the second limb.
Text is not covered. The definition reaches audio, visual and audio-visual
information only, and the ministry's own published questions and answers state that pure text and
written outputs are not, by themselves, synthetically generated information. A number of law-firm
alerts and news pieces say otherwise. They are wrong, and the point is not marginal — it removes
every large language model's text output from the regime.
A proviso further excludes routine, good-faith work: editing, formatting, enhancement, technical
correction, colour adjustment, noise reduction, transcription or compression that does not materially
alter substance, context or meaning; the ordinary creation of documents, presentations, educational
materials and research outputs, provided no false record results; and use of a computer resource
solely for accessibility, clarity, quality, translation, description or searchability without
manipulating any material part.
03The labelling duties
The visible label — and the number that is not there
Rule 3(3)(a)(ii)
Synthetically generated information must be prominently labelled in a manner that ensures
prominent visibility in the visual display, easily noticeable and adequately
perceivable — or, in the case of audio content, through a prominently
prefixed audio disclosure.
IT Rules 2021, rule 3(3)(a)(ii), as inserted by G.S.R. 120(E)
The draft's ten-per-cent-of-display-area requirement did not survive into the notified
text. Nor did the audio equivalent. The notified rules contain no percentage anywhere, and
the audio duty is positional rather than durational — the disclosure goes at the front, with no
minimum length. Several explainers still in circulation assert the ten per cent rule is live; they
contradict the Gazette.
That absence creates the real compliance problem. With a percentage, compliance is measurable.
Without one, "easily noticeable and adequately perceivable" is a judgement your team makes, per
surface, per format — and the only defensible record is one that captures the basis on which
prominence was claimed at the time, not a screenshot produced afterwards.
Embedded provenance
Rule 3(3)(a)(ii), second limb, and rule 3(3)(b)
Such information shall be embedded with permanent metadata or other appropriate technical
provenance mechanisms, to the extent technically feasible, including a unique
identifier, to identify the computer resource of the intermediary used to create, generate,
modify or alter it. The intermediary shall not enable the modification, suppression or removal of
that label or metadata.
IT Rules 2021, rule 3(3), as inserted by G.S.R. 120(E)
Read the qualifier carefully: "to the extent technically feasible" attaches to the
metadata limb only. The visible label carries no such softening. Several published alerts
apply the qualifier to the whole sub-clause, which would make the visible label optional whenever
it is inconvenient. The text does not support that.
Note also who the non-removal duty binds. It obliges the intermediary not to enable
stripping. It is not a prohibition on users, and it creates no offence — a contrast worth
drawing with China, which prohibits malicious removal by anyone and bans supplying tools to do
it.
04Declarations and verification
The rules push part of the classification problem onto users, and then require the larger
platforms to check the answer.
An intermediary must require a user uploading content to declare whether it is
synthetically generated, and significant social media intermediaries must additionally deploy
reasonable and appropriate technical measures — including automated tools — to
verify that declaration. Where the check indicates the content is synthetic, it must
be displayed with the required label.
Two consequences follow. First, a declaration is an event with a timestamp and an author, and the
platform's own verification is a second event with a method and a result — two facts that
together decide whether the platform behaved reasonably, and that exist nowhere unless recorded.
Second, the rules protect platforms that act: removal or disabling done in compliance with the rules,
including through automated tools, does not itself break the conditions of the safe harbour. Acting
on a positive detection is safe; the risk sits in not acting, and in not being able to show what the
check returned.
05Takedown runs on more than one clock
This is the part that most coverage reports backwards. There is no single takedown window. There
are four, they run from different starting events, and the spread between the fastest and the slowest
is eighteen-fold.
Window
Rule
Clock runs from
What it covers
2 hours
3(2)(b)
Receipt of a complaint by the individual, or someone on their behalf
Content exposing a private area, showing full or partial nudity, depicting a sexual act — or impersonation in electronic form, including artificially morphed images
3 hours
3(1)(d)
Receipt of actual knowledge
Unlawful-act content: sovereignty and integrity, security of the State, friendly foreign relations, public order, decency or morality, contempt of court, defamation, incitement. Actual knowledge arises only from a court order or a conforming reasoned written intimation
36 hours
3(2)(a)(i) proviso
Such reporting
Removal requests under rule 3(1)(b) — except sub-clauses (i), (iv) and (xi)
7 days
3(2)(a)(i)
Date of receipt
All other grievances. Acknowledgement within 24 hours is unchanged
Three corrections worth making, because each one is widely published the other way round:
36 hours is not the court-order window. It used to be. This amendment cut the
court-and-government route to three hours, and the 36-hour figure now belongs to a grievance window
that was itself cut from 72 hours. Anyone still treating 36 hours as their response time for a
court order is operating on a clock that expired twelve times over.
The 36-hour window excludes intellectual property. The carve-out for sub-clauses
(i), (iv) and (xi) takes third-party rights, patent and trademark and copyright infringement, and
general unlawfulness out of the fast window — so copyright takedowns fall back to seven days.
The two-hour duty is softer in kind than the three-hour one. Rule 3(2)(b) asks for
all reasonable and practicable measures to remove or disable access. Rule 3(1)(d) is an absolute
removal obligation. A shorter clock is not automatically a stricter duty.
Across an eighteen-fold
spread, a guessed window is a manufactured finding. The classification of the notice is the whole
question — which is why the record has to capture the class that was assigned, when the notice
arrived, and when removal completed, rather than computing a verdict against a window nobody
agreed on.
06What failure actually costs
Do not budget for fines. These Rules impose no penalty and create no offence.
This is the single most misreported point about the regime.
Where an intermediary fails to observe these rules, the provisions of sub-section (1) of section
79 of the Act shall not be applicable to it, and the intermediary shall be liable for punishment
under any law for the time being in force.
IT Rules 2021, rule 7
Mechanically: section 79 conditions an intermediary's immunity on observing due diligence and such
other guidelines as the Central Government prescribes. These Rules are those guidelines. So
"due diligence" for safe-harbour purposes simply is compliance with them, and breach means the
immunity ceases to be available — leaving the intermediary exposed to primary liability for
content posted by other people.
That is a different risk shape from every other regime on this site, and it changes what evidence
is for. There is no regulator order, no hearing, and no appeal against "losing safe
harbour." It is a defence that falls away, and it is adjudicated after the fact, in whatever
proceeding somebody else brings, possibly years later. You will not be told you have lost it. You
will discover it when you try to rely on it.
A defence you cannot evidence at the moment you need it is not a defence. That is the whole
argument for contemporaneous records here — not a fine to avoid, but an immunity to be able to
demonstrate you were entitled to.
One amplifier for larger platforms: a significant social media intermediary is
deemed to have failed due diligence where it knowingly permitted or promoted
non-compliant synthetic content, or failed to act on it.
07Duty → receipt
This is where Planisphere enters, and not before. One event per act — and, uniquely among the
regimes here, a pair of events that are bound together by a statutory clock.
Note prominence_basis. Because the notified rules dropped the
percentage, prominence is a judgement rather than a measurement — so the field records the basis
on which it was claimed, at the time it was claimed.
The takedown pair is the part built specifically for this regime. The notice record carries a
notice_class, and the completion record points back to it with
starts_from_action_key. The elapsed interval is then
computed from two sealed records and measured against the window that class carries
— two hours, three hours or thirty-six — rather than asserted afterwards by whoever is
writing the response.
And where the class is not one the pack recognises, it records the interval and returns
no verdict. That restraint is deliberate: across an eighteen-fold spread, guessing
which window applied would manufacture a finding rather than report one.
08The integration
Two calls, bound together. First the notice, which starts the statutory clock:
# A complaint arrives about morphed imagery. Two-hour class.
curl -X POST https://api.planisphere.ooo/v1/record \
-H "Authorization: Bearer $PLANISPHERE_API_KEY" \
-d '{
"pack": "in-it-rules",
"event_type": "takedown_notice_received",
"occurred_at": "2026-08-01T06:12:00Z",
"source_payload": { "notice_sha256": "3d7e…" },
"metadata": {
"notice_class": "intimate_or_impersonation",
"received_at": "2026-08-01T06:11:48Z"
}
}'
# → returns an action_key. That key is the start of the clock.
Then the completion, pointing back at it:
curl -X POST https://api.planisphere.ooo/v1/record \
-H "Authorization: Bearer $PLANISPHERE_API_KEY" \
-d '{
"pack": "in-it-rules",
"event_type": "takedown_completed",
"occurred_at": "2026-08-01T07:38:19Z",
"starts_from_action_key": "<the notice key>",
"source_payload": { "content_sha256": "b204…" },
"metadata": { "removed_at": "2026-08-01T07:38:02Z" }
}'
# → elapsed 1h26m against a 2h window, computed from the sealed pair.
The full API reference covers authentication, idempotency, batching
and rate limits; pricing is per record with a monthly free allowance.
09What Planisphere does not do
Stated plainly, because a vendor who is vague here will be vague in front of a court.
Planisphere is an evidence layer. It sits beside your systems, never inside the act.
It does not label content, embed provenance metadata, host content, or remove
it.
It does not observe when a removal actually took effect. A notice record
paired with a completion record evidences your own account of the interval between them;
it is not independent observation of the removal.
It does not classify a notice for you, and where the class is not one it
recognises it records the interval and gives no verdict.
It does not verify user declarations or detect synthetic media.
It is not a grievance-officer filing, and not a safe-harbour
determination. No vendor can make one. A record is evidence a third party can check; it is not a
finding that you complied.
It does seal the notice and the completion as they happen, so the
interval between them is arithmetic on sealed records rather than a claim made later by the party
with the most to lose.
10Questions
Is the ten per cent label rule real?
Not any more. It was in the October 2025 draft and did not make it into the notified rules,
which contain no percentage at all. Explainers still asserting it are quoting a draft. The notified
standard is prominence — easily noticeable and adequately perceivable — and for audio, a
prominently prefixed disclosure with no minimum duration.
Are we covered if we only generate text?
No. The definition reaches audio, visual and audio-visual information, and the ministry's
published questions and answers state that pure text outputs are not synthetically generated
information by themselves. Note this is a narrower position than the EU takes, where the marking
duty covers text on the face of the provision.
We are not based in India. Does this reach us?
The rules bind intermediaries, and the intermediary regime has long applied to services offered
to users in India regardless of where the company sits. The practical question is usually whether
you are an intermediary at all, and whether you are a significant social media intermediary, which
carries the additional verification duty.
Is there any enforcement to look at?
None that is public. We found no rule 7 proceeding, no safe-harbour revocation and no reported
challenge to the amendment. Treat that as an absence of public record rather than proof of
inactivity — enforcement here is characteristically not announced, and the sanction surfaces inside
private litigation rather than in a regulator's press release.
Is anything else coming?
A second amendment was published in draft in March 2026 and revised in April, with consultation
closed in May. As of this writing it has not been notified. We will not describe a draft as law;
check the Gazette before relying on it.
11Sources
Every rule number, window and quotation on this page was read from the signed Gazette notification
rather than a summary of it.
PrimaryMeitY — the consolidated IT Rules and the ministry's questions and answersThe confirmation that pure text outputs are not synthetically generated information. Note the consolidated text still prints words in rule 3(1)(b)(v) that were struck down by the Bombay High Court in 2024, without annotation.
The console opens on the India pack with each labelling and takedown act listed, showing the exact
call that seals it and how the notice and the completion bind together. Sealing a record takes about
a minute, and the first thousand each month are free.