Evidence ops guide13 min read

Post-order evidence operations

Living injunctions and the fresh-URL evidence log

Personality-rights orders increasingly let rightsholders submit newly discovered infringing URLs directly to named platforms under time-boxed acknowledge-and-act duties. This evidence-operations guide explains how the fresh-URL log behind such an order works: discovery, capture, supporting particulars, submission tracking, acknowledgment records, outcome logging, and escalation of gaps. It is workflow preparation, not legal advice, and the order mechanics discussed are jurisdiction-specific.

Updated September 2026By Henryk Wexel

Key takeaways

A living injunction keeps working after judgment: the order gives the rightsholder a route to submit newly discovered infringing URLs directly to the platforms named in it. The Delhi High Court decree of August 24, 2026 in Rajat Sharma v. Tamara Doc (CS(COMM) 1147/2024) requires acknowledgment within 24 hours and action within 36 hours after the platform's own examination.
The order is only as strong as the log behind it. Each submission needs the URL, observation and capture timestamps, account context, supporting particulars tying the material to the order's scope, a submission record, the platform acknowledgment, and the outcome.
Capture before submitting. A submitted URL can be deleted or altered within minutes; a preserved full capture with a hash and timestamp keeps the record verifiable afterward.
Scope calls stay with counsel. The evidence log documents observable facts; whether a new URL falls inside the order, and whether to submit it, is the instructed law firm's judgment. Finium structures the record and does not make legal calls.

What a living injunction is

Living injunction

A court order that continues to operate after judgment by letting the rightsholder submit newly discovered infringing URLs directly to the platforms named in the order, under time-boxed acknowledge-and-act duties. The order's mechanics are jurisdiction-specific.

Why the order is only as strong as the log

A fresh-URL mechanism shifts work from the courtroom into an operations loop: someone has to notice new material, preserve it, document why it falls within the order's subject matter, submit it through the right channel, and track what happened. That is a monitoring and record-keeping problem before it is a legal one. Without a disciplined log, submissions become inconsistent, outcomes become unverifiable, and gaps stay invisible: a platform that never acknowledged, a URL altered after submission, an account that reappears under a new handle. The log is what turns a standing order into an enforceable operating rhythm.

Discovery: where new material surfaced (search, monitoring, tip, platform suggestion) and when
Preservation: a full capture of the URL and account context before the material can change
Particulars: the neutral facts tying this URL to the order's scope, prepared for counsel review
Submission: which channel received it, when, and with which attachments
Acknowledgment: whether and when the platform acknowledged the request
Outcome: action taken, declined, or no response, with the platform's own reference numbers
Escalation: which gaps were reported to counsel for a decision on next steps

The fresh-URL log: fields per submission

Minimum fields for each fresh-URL submission record

Field	What to record	Why it matters
URL and platform	Exact URL as observed, platform, and the posting account or channel	Identifies the target and lets counsel check it against the order's scope
Observation timestamp	When and how the material was first seen, with timezone and discovery path	Establishes that the material appeared after the order and shows monitoring cadence
Capture record	Full-page capture, original media files where obtainable, capture timestamp, file hash	Preserves what existed at submission time in case the URL is later deleted or altered
Account context	Handle, display name, profile URL, visible subscriber or follower state at capture	Connects repeat material to the same actor or pattern without asserting identity
Supporting particulars	Neutral facts showing how the material uses the protected name, likeness, image, voice, or marks	Supplies the particulars counsel needs for an affidavit and the platform needs for its examination
Submission record	Channel, date and time, recipient if known, attachment list	Starts the acknowledgment clock and proves what was sent
Acknowledgment and outcome	Platform acknowledgment time, action taken or declined, platform reference numbers	Completes the chain; missing acknowledgments become visible escalation items

Capture before submitting

Material can disappear within minutes of a submission triggering platform review. The capture has to exist first. That means a full-page capture of the URL, the account or channel page as it looked at capture time, the surrounding context (titles, descriptions, visible engagement), and the original media files where the platform allows them. Each capture gets a timestamp with timezone and a SHA-256 hash recorded at capture time. A custody note records who captured the item, where the file lives, and every later step that touched it. This is the same discipline described in the chain-of-custody workflow, applied at submission cadence rather than once at intake.

Capture the exact URL as observed, not a share-shortened variant
Capture the posting account or channel page in the same session
Record observation time, capture time, and the time source separately
Hash each capture at creation and store originals in restricted storage
Log the discovery path so a later reviewer can explain how the item surfaced

Privacy minimization for sensitive material

Fresh-URL work in personality-rights matters regularly touches intimate or degrading material. The log has to stay operable without spreading that material through the firm or the submission chain. The evidence layer minimizes: sensitive originals are captured once into restricted storage, referenced by evidence ID in working documents, and never duplicated into logs or spreadsheets. Every access to an original is recorded. What actually gets attached to a submission is counsel's decision, scoped to what the order and the platform process require.

Sensitive originals stay in restricted storage; working copies are redacted or referenced by ID
The log records that material exists and where it lives, not the material itself
Access events (who opened an original, when) are logged alongside the capture record
Submission attachments are scoped to what counsel approves, not everything captured
Where an order provides for confidential handling of intimate material, that handling is counsel's decision; the evidence layer's job is to make minimization practical

Who does what

The pattern only works with clear roles. The evidence layer observes, captures, and logs. Counsel decides scope and strategy. The rightsholder or their agency approves submissions and owns the platform relationship. The platform examines and acts under its own policies and the order.

Evidence operations: discovery logging, full capture, hashing, timestamps, log maintenance, gap reports
Instructed counsel: whether a URL falls inside the order, what particulars to submit, when to return to court, privilege and confidentiality handling
Rightsholder, agency, or comms team: authorization, submission approval, brand and communications context
Platform: independent examination under its own policies, acknowledgment, action, and any disclosure directed by the order

What the log is not

The fresh-URL log is an operational record, not a legal filing and not a prediction. It does not establish that any URL infringes anything: characterization belongs to counsel and, where the order says so, to the platform's own examination. It does not identify anonymous actors; it documents observable patterns such as handles, profile URLs, and posting cadence, while identification stays with courts, platforms, and lawyers through the mechanisms the order provides. And it is not a removal guarantee: platforms act under their own policies, and an acknowledgment clock is a duty to respond, not a promise of any particular outcome.

Disclaimers and operating boundary

This guide is an evidence-operations reference, not legal advice. The Delhi High Court decree discussed here is jurisdiction-specific; nothing in this guide states or implies that similar mechanisms exist or would apply in any other court, jurisdiction, or matter, and the case remains subject to its own procedural posture. Finium does not contact platforms, submit URLs on a rightsholder's behalf, decide whether material falls inside an order, or promise platform-action outcomes. Finium structures discovery logs, captures, timestamps, hashes, custody notes, and submission tracking so the instructed law firm remains the legal actor and makes every scope, submission, and escalation decision itself.

Frequently asked questions

What is a living injunction?

A court order that keeps operating after judgment by giving the rightsholder a route to submit newly discovered infringing URLs directly to the platforms named in the order, usually with time-boxed duties to acknowledge and act. The Delhi High Court decree of August 2026 in Rajat Sharma v. Tamara Doc is a current example, with a 24-hour acknowledgment window and a 36-hour action window after the platform's own examination.

Do these orders apply everywhere?

No. The 24-hour and 36-hour duties discussed here are specific to that Indian order and the platforms named in it. Other courts and jurisdictions use different mechanisms, and nothing in this guide generalizes those mechanics to other orders, platforms, or countries.

What is a fresh-URL log?

An operational record of every newly discovered URL relevant to an order: observation time and discovery path, full capture with hash, account context, supporting particulars, submission channel and time, platform acknowledgment, outcome, and any gaps escalated to counsel.

Does Finium submit URLs to platforms?

No. Finium structures the evidence layer: discovery logging, capture, timestamps, hashes, custody notes, and submission tracking. Submission decisions, scope calls, and any platform contact belong to the rightsholder and their instructed counsel.

Does the log identify anonymous accounts?

No. It documents observable patterns such as handles, profile URLs, and posting cadence. Identification of actors stays with courts, platforms, and lawyers through whatever mechanisms the order provides.

How does this relate to monitoring alerts?

Monitoring produces candidate URLs. The log turns each candidate into a preserved, timestamped record that counsel can assess against the order's scope, so alerts become submissions with a verifiable trail instead of scattered screenshots.

References