Publishing Principles
Reporting built for adversarial environments and scrutiny
Dossiers, evidence files, and a record that can stand up in hard rooms
Our public work is usually a long investigation, not a quick update. A typical dossier runs about 15,000 to 40,000+ words and it is supported by reporting files, exhibits, interview notes, and verification logs kept inside our internal records.
The version you read on the site may be shorter than the full record because we sometimes remove details that could expose a source, hurt a victim, invade privacy, or damage an ongoing inquiry that is still active.
Our media network includes more than 1,000 investigative outlets and more than 25,000 media properties. When our work is distributed, it happens through paid licensing and custom terms so the reporting stays intact and people stay safe.
Network Brands — Slow Rotation
Hover pauses
Why we do this
Public-interest reporting that targets hidden control
We publish investigations that bring daylight to quiet abuse of power, corruption, market cheating, criminal enterprise, broken oversight, and organized wrongdoing when the public deserves to know and the record is strong.
We are not built like a fast newsroom that races a clock. We are built like a file room that keeps proof straight and keeps our words careful.
We publish only when the evidence can be defended as fair, ethical, and lawful across more than one country, because our work is read in many places at once.
How we are structured
What we choose over speed
- Evidentiary depth comes first, even if it takes longer to publish.
- Repeatable checking matters more than dramatic storytelling tricks.
- Right-of-reply is a discipline, not a headline accessory.
- We build durable records that stay useful after the first news cycle ends.
Reader test
What happened
A dossier states the event pattern in plain words, with dates and names when it is safe and lawful to do so.
Reader test
How we know
We show the path to proof through documents, interviews, data, and cross-checks so a serious reader can follow the trail.
Reader test
Confirmed vs guessed
We separate facts from reasoned conclusions, and we mark what we could not prove instead of dressing it up as certainty.
Reader test
Who was asked
We document who was contacted, what questions were sent, and how the subject responded, including silence when there is no reply.
Reader test
Limits
Every dossier tells you what we do not know, what we cannot confirm, and what we left out for safety or legal reasons.
Record rule
One canonical file
The canonical version is the master record, and other copies must point back to it so the public can see corrections and updates.
Executive Findings
A short top section that states what we found and why the finding matters to the public.
Targets and Scope
A clean list of the people or entities involved, the time window, and the places covered.
Methodology Summary
A plain description of how the reporting was done so the process is not a mystery.
Core Narrative Findings
The fact pattern, arranged so the reader can see sequence, motive claims, and consequence without confusion.
Evidence Summary
A map of what exists in the record, how it was checked, and why some material is withheld.
Right of Reply
Questions sent, answers received, and notes about non-response placed where readers can see them.
Public-Interest & Harm Check
A section that explains why publication serves the public, plus what we did to reduce avoidable harm.
Limits & Uncertainties
A clear boundary line that tells the reader what we cannot claim and where gaps remain.
Appendices
Definitions, technical notes, and reference material that make the main story easier to verify.
Changelog / Versioning
A dated list of changes so readers can see what was updated and why it changed.
Exhibits Index
A catalog of exhibits we rely on, described carefully to avoid exposing sensitive details.
Jurisdiction Notes
A section that flags legal differences that affect what can be shown in public versions.
Why we often describe instead of dumping files
We work in many places, including hostile environments, so public dossiers often explain what evidence shows instead of posting raw material that could expose sources or victims.
When we hold back material, we try to state the reason in simple words, such as source safety, privacy, active proceedings, or local restrictions.
We may publish redacted excerpts when it helps
- It increases accountability by showing a meaningful slice of proof.
- It does not expose a source, a victim, or an innocent bystander.
- It avoids needless harm that would outweigh the public benefit.
- It fits within the law and does not create a new safety risk.
Independence from funders and partners
Licensing money never buys control of what we investigate, what we conclude, or when we publish.
No advertiser, donor, political actor, or distribution partner can dictate corrections or block them.
Conflicts of interest
Staff and contributors must disclose financial, personal, professional, and political conflicts so readers are not misled.
If a conflict exists, we may move the work to another reporter, add oversight, or decline publication entirely.
Accountability inside the process
- Reporting lead review checks the reporting plan and the record quality.
- Evidence review checks key documents, data, and exhibit handling.
- Editorial review checks clarity, fairness, and the line between fact and inference.
- Legal and risk review checks exposure, wording precision, and jurisdiction issues when needed.
- Security review checks source risk, travel risk, and data handling where relevant.
Public-interest gravity
We focus on cases tied to public money, safety, rights, governance, and market integrity.
Magnitude and scale
We prioritize systemic harm over private disputes that do not affect the wider public.
Accountability gap
We lean in when oversight is weak, captured, or silent even when warning signs are clear.
Evidence feasibility
We start only when claims can be checked to our standard, not just repeated as rumors.
Originality
We publish when we add new reporting, new proof, or a clearer verified timeline.
Risk proportionality
We proceed when harm can be reduced responsibly while still serving the public interest.
No paid influence
We do not pursue targets due to popularity, vendettas, or money, and we do not publish to punish.
Timing rule
We publish when the record is strong enough to stand up under hostile review, not when it feels loud.
Methods we use
- Primary documents and records that can be checked.
- Public filings, court materials, and official releases when relevant.
- Datasets, forensic work, and pattern analysis where the story needs it.
- Interviews on-record, background, off-record, or confidential based on risk and law.
- Open-source research and archives that preserve old proof.
- Field reporting when distance would hide what is real.
- Experts for hard topics like finance, cyber, medicine, and engineering.
Interview clarity
We explain terms like on-record and off-record so people know what will be published and what will not.
We follow recording-consent rules that apply in the place where the recording happens.
We do not misrepresent identity or purpose except in rare cases with a very high threshold.
Undercover / deception (rare)
- The public interest must be substantial, not trivial.
- The information cannot be obtained by reasonable alternatives.
- Senior editorial review must approve the method before it begins.
- Safeguards must exist for legality, ethics, and minimizing harm.
How we label what we know
Verified facts are treated as facts only after we check them with reliable proof.
Supported inference is a reasoned conclusion from evidence, and we say it is an inference.
Unverified claims are not written as truth, even when they sound convincing.
Corroboration rule
For serious allegations, we aim to have at least one strong support path, and often more than one.
- More than one independent source when possible.
- Documents that match the claim and survive checks.
- Technical or forensic support for digital and financial matters.
- Contemporaneous records like messages, logs, filings, images, and trace data.
Document authentication (when central)
- We assess provenance and chain-of-custody where it matters.
- We check internal consistency and metadata when available.
- We cross-check with independent records that should match.
- We seek expert validation when the item is technical.
Precision in language
We avoid words that pretend we are sure when we are not.
We write in a way that matches our confidence level, using careful phrases like “records show” or “we could not confirm.”
If something is unknown, we say it is unknown instead of turning it into a claim.
Evidence handling (internal)
We keep internal reporting files such as interview notes, exhibit catalogs, verification checklists, and security notes when lawful.
Public versions may not show these files because safety and legal rules can require restraint.
When we do not publish a file, we aim to explain the reason without giving away sensitive details.
Right of reply is standard
If a dossier contains adverse findings about identifiable people or entities, we make reasonable efforts to contact them before publication.
We summarize what concerns them and offer a real chance to respond, not a token message.
Deadlines vary by risk and urgency, and we may continue outreach after publication when time is tight.
How responses are published
We publish responses accurately, in context, and with clear attribution so readers know who said what.
We do not edit replies in a way that changes meaning, even when the reply is hostile.
If a response contains a claim we can disprove, we may add a note with verified counter-evidence.
No “ambush-by-excerpt”
Because dossiers are long, selective quoting can easily mislead, so syndication must not distort findings by chopping out key context.
Fairness is not a decoration; it is part of the record, and it must stay visible.
If a partner republishes our work, they must preserve meaning instead of squeezing it into a false shape.
When we grant confidentiality
We may grant confidentiality when a source faces real risk and the information can be checked.
We do not grant anonymity to help personal attacks or to avoid verification steps.
When a source is protected, the work still must stand on proof, not on mystery.
Protective measures
- We may remove or generalize identifying details.
- We may delay publication of sensitive specifics until risk is lower.
- We may redact or paraphrase documents when the raw copy is dangerous.
- We may compartmentalize access inside the team to reduce exposure.
Secure communications
Use these channels for tips and sensitive contact, and please keep your own safety in mind.
Safety reminder
If you are in immediate danger, do not take risks to contact a newsroom; choose safety first.
If you share documents, remove details that could identify you unless you have a safe plan.
If you are unsure, start with a short message and wait for guidance.
Confidential tips are not a promise
A tip is the start of a check, not a guarantee of publication.
We may ask follow-up questions to verify details before we rely on information.
If the record cannot be verified safely, we may choose not to publish.
Personal data and doxxing
We avoid publishing home addresses, personal phone numbers, private emails, IDs, banking details, and other private identifiers unless there is an overriding public-interest reason and legal clearance.
We do not publish private details just because they exist in a file.
When names must appear, we use restraint and focus on what is necessary.
Minors and vulnerable persons
We use extra caution with minors and we usually avoid identifying them.
We also take care with victims and survivors of violence, and with non-public figures pulled into a story by accident.
We do not treat human pain as content.
Graphic or traumatic material
We publish only what is needed to establish truth and accountability, and we use warnings when content may be distressing.
We avoid shock for shock’s sake.
We keep the focus on facts, causes, and responsibility.
One record, many legal systems
We publish across the US, UK, EU, India, and other jurisdictions where defamation, privacy, contempt, data protection, and court restrictions can differ.
High-risk dossiers may receive jurisdiction-aware review before publication, especially when claims could trigger cross-border legal action.
This page is a statement of editorial principles and it is not legal advice.
What we do because of that
- We use precise attribution and careful evidentiary framing.
- We apply privacy-by-design with minimization and redactions when needed.
- In rare cases, we may adapt presentation to comply with lawful orders while keeping version history visible.
- We avoid silent rewriting that changes meaning without a public note.
Security is part of quality
If security fails, sources can get hurt and the record can get polluted, so we treat security as a core part of the work.
We do not publish sensitive details that would expose staff or sources.
We plan risk and reduce it before we chase a story.
Examples of safeguards
- Encryption in transit and at rest where appropriate.
- Access controls with least-privilege permissions.
- Separated workspaces for sensitive investigations.
- Secure evidence repositories with audit trails when feasible.
- Risk checks for fieldwork and sensitive travel.
Operational restraint
We share enough to be accountable without handing a playbook to hostile actors.
We keep source paths narrow when exposure would create danger.
We aim to protect the work so it can keep going.
No plagiarism
We do not steal text, reporting, data, images, or other people’s work.
When we rely on prior reporting, we credit it clearly.
When we summarize third-party materials, we do it accurately and in good faith.
Clear separation
We separate what we discovered from what we cite.
We do not dress up citations as original reporting.
We avoid shortcut language that hides where information came from.
Image and data care
We avoid misleading cropping, edits, or captions that distort what a photo or chart really shows.
If a visual is illustrative and not evidence, we label it that way.
If we correct a data error, we note it in the version log.
Permitted assistive uses
We may use tools that help with speed on mechanical tasks, but humans stay responsible for what is published.
- Transcription, with a human checking accuracy.
- Translation, with editor review when the stakes are high.
- Document sorting and deduplication to reduce time waste.
- Entity and timeline assistance, validated against primary material.
- Code assistance for analysis, reviewed and tested before use.
Prohibited uses
We do not treat tools as authorities, and we do not publish machine-made claims as facts.
- No generating “facts” that are not grounded in evidence.
- No fabricated quotes, sources, documents, events, or exhibits.
- No synthetic media presented as real.
- No using tools to decide guilt, intent, or wrongdoing.
Human accountability
Every claim in a dossier remains the responsibility of human editors and reporters.
For critical passages, the underlying evidence must remain reviewable in our internal record.
If a tool affects method in a meaningful way, we may disclose that use in the methodology section.
No shortcut verification
Speed does not excuse weak checking.
If we cannot verify a claim, we label it as unverified or we do not use it.
We keep our proof standards the same even when the topic is popular.
Reader trust rule
We would rather be slower than wrong.
We would rather be plain than confusing.
We would rather say “we don’t know” than pretend we do.
Corrections (material factual errors)
If we publish a material error, we correct it promptly and add a note that says what changed and why.
We timestamp corrections so the record is honest about its own history.
We avoid quiet edits that alter meaning without telling readers.
Updates (new facts or new responses)
New information is added as an update with a date and a clear explanation.
We do not backdate changes.
We keep the changelog visible so readers can track evolution.
Retractions (rare)
A retraction happens only when core findings cannot be supported or a serious process failure invalidates the work.
A retraction notice remains visible and explains the reason as fully as safety and law allow.
We preserve the public record of the retraction so it cannot be hidden later.
How to request a correction
Email corrections@hansajekalavya.com and include the dossier URL, the exact passage, and any supporting evidence.
If you are a subject and want right of reply, include the question you are answering and the best contact details for follow-up.
If you claim a document is fake, tell us why and show proof that can be checked.
Why versioning is strict
A dossier is a long-lived public record, so change tracking is not optional.
Readers must be able to see what was changed without guessing.
Licensees must respect the canonical record so corrections do not disappear.
Canonical version
Each dossier has a canonical URL on our mastersite, and that page is the reference record for wording, updates, and corrections.
Partners must link to the canonical page so readers can verify the latest version.
Republished copies must not pretend to be the original record if they are edited.
No distortion by editing or excerpting
- Do not remove qualifiers that explain uncertainty.
- Do not omit right-of-reply material in a way that changes fairness.
- Do not cherry-pick passages that invert the meaning.
- Do not use misleading headlines, thumbnails, or captions.
- Do not remove correction notes or changelog entries.
Permitted adaptations (contract-based)
- Formatting changes that do not change meaning.
- House-style punctuation that keeps the claim intact.
- Translation with quality control and meaning preserved.
- Excerpting within agreed limits, with a prominent canonical link.
Embargoes and coordinated release
When an embargo applies, licensees must follow release timing and handle advance materials with care.
If approved assets are required, partners must use those assets rather than swapping in misleading ones.
If a partner breaks an embargo, access can be restricted under contract.
Correction propagation across the network
When we issue a material correction, we notify licensees through designated channels.
Republished versions must be updated within the contract SLA.
Correction notes must remain visible or must link prominently to the canonical correction.
Licensing scope (what contracts define)
- Territory and language rights.
- Exclusivity windows when applicable.
- Excerpt limits and format rights (web, print, broadcast, newsletters).
- Archival duration and takedown or update duties.
- Monetization rules and paywall boundaries.
- Branding and attribution requirements.
Syndication contact: syndications@hansajekalavya.com
We separate critique from intimidation
We take credible challenges seriously, especially when backed by documents or checkable facts.
We do not remove accurate reporting simply because a powerful party demands silence.
We keep a record of serious allegations of error and respond through the corrections process.
Evidence-first review
If a claim is disputed, we ask for evidence and we re-check the disputed point against our record.
If the dispute is unsupported, we may note that the subject disagrees without changing verified facts.
If we find a mistake, we correct it and state the change openly.
Response statements
When a subject publicly misrepresents our reporting, we may publish a short response that points readers back to the record.
We avoid personal mud fights and we keep the focus on what can be proven.
We do not trade safety for online arguments.
What we welcome
We welcome counterevidence, expert critique, and reasoned disagreement that helps the public get closer to the truth.
We take corrections seriously when they are specific and supported.
We prefer clear receipts over loud insults.
What we do not host
- Harassment, threats, or doxxing of any person.
- Incitement or targeted hate against protected groups.
- Coordinated disinformation campaigns in our channels.
- Calls for violence or instructions to harm others.
Why moderation exists
If we allow abuse, honest sources stop speaking and the public loses information.
If we allow doxxing, people get hurt and reporting becomes harder.
If we allow hate, truth becomes background noise.
Editorial contact
Editorial: editorial@hansajekalavya.com
Editors: editorials@HansajEkalavya.com
Legal: legal@hansajekalavya.com
Corrections and disputes
Corrections: corrections@hansajekalavya.com
If you dispute a claim, include the dossier title and URL, the exact lines, and evidence supporting your position.
If you want right of reply, include the best contact details for a follow-up call.
Licensing and syndication
Licensing: licensing@hansajekalavya.com
Syndication: syndications@hansajekalavya.com
Secure tips and secure drop links are listed above in the source protection section.
Publishing Principles – Version: v11.0
Last updated: June 22, 2026 4:34 AM
These principles exist so readers, sources, and subjects can understand how our dossiers are built and how changes are handled.
If you have evidence, questions, or a reply to a dossier
Use one email thread so nothing gets lost, and include links and documents when you can do so safely.