Networkwide policy page
Networkwide editorial ethics and binding policies
Plain rules for how our investigations are built, checked, corrected, and shared
Ekalavya Hansaj publishes investigations as long dossiers. A typical dossier is 15,000+ words, and many run past 40,000 words, backed by exhibits like documents, data tables, interview notes, timelines, and clear method notes.
This page tells you what we care about (truth, independence, fairness, public value, and reducing harm), what we do before publishing (verify, source, offer a real chance to respond, review, and protect people), and what we do after publishing (fix mistakes with visible corrections and keep a clear record of changes).
These standards cover every editorial format under Ekalavya Hansaj: full dossiers, shorter investigative briefs, explainers that depend on our reporting, newsletters, podcasts, and social posts that summarize our work.
Network Brands — Slow Rotation
Hover = pause
What we publish
Long dossiers, not quick headlines
Our main work is the investigative dossier. It is long, detailed, and built to be checked. It usually starts around 15,000 words and can grow far beyond that when the proof requires it.
What this page explains
Values, methods, and accountability
You can use this page to understand what we protect, how we verify, how we treat people mentioned in our work, and how we correct mistakes without hiding the history.
Where it applies
Every editorial channel
These rules apply to dossiers, shorter investigative briefs, explainers that rely on our findings, newsletters, podcasts, and any social distribution that summarizes our reporting.
Evidence-led
Proof comes first
We do not ask you to “trust us” as a shortcut. We show our work with documents, data, and clear sourcing so you can see why a claim is safe to publish.
Independent
Money does not pick the truth
Sponsors and advertisers do not decide what we investigate, when we publish, or what we conclude. Editorial calls are made by editors and reporters, not by payers.
Not breaking news
Depth over speed
We are not built for quick updates every hour. We aim for careful work that survives scrutiny later, even when the subject fights back.
Fair
A real chance to answer
If a person or group faces serious criticism, we try to reach them, ask clear questions, and include their response in context instead of clipping it for drama.
Proportionate
Harm is weighed, not ignored
Some facts can hurt innocent people. We plan what to publish, what to redact, and what to delay so the public still learns what matters without reckless damage.
Transparent
Methods are visible
We explain where information came from, what we could not confirm, and what changed after publication, so readers are not left guessing.
3.1 Accuracy
Accuracy is the rule that never bends
If we cannot back a claim with evidence, we do not publish it as fact. When certainty is not possible, we label the uncertainty in plain words and explain why it remains.
3.2 Independence
Pressure does not rewrite findings
We guard decisions against donor wishes, sponsor expectations, advertiser influence, legal intimidation, and internal business pressure that tries to soften public‑interest reporting.
3.3 Fairness
We separate fact, claim, and allegation
Readers deserve clean labels. We mark what is verified, what is alleged, and what is analysis, and we avoid language that quietly turns an allegation into a “known” truth.
3.4 Public interest
We publish to serve the public, not to entertain
Sensitive material is used when it helps the public understand real power, real harm, real public spending, real corruption, or real safety risks.
3.5 Harm minimization
We protect victims and bystanders
We consider the impact on victims, minors, whistleblowers, and vulnerable people. We do not drop private details just because we can.
3.6 Accountability
We correct loudly, not quietly
When we get something wrong, we fix it fast and visibly. We keep a record of meaningful changes so the public can see the trail.
4.1 Architecture
What a dossier normally contains
A dossier is built like a case file: an executive summary, clear findings, the proof story, a timeline when useful, method notes, right‑of‑reply coverage, limits, and exhibits with safe redactions.
4.2 Claim discipline
How we label statements
We use simple labels: verified fact, corroborated account, attribution, analysis, inference, and allegation. That way a reader can tell what is solid and what is still being tested.
4.3 Canonical version
One source of truth
Every dossier has a main URL on Ekalavya Hansaj that acts as the authoritative version. Corrections and updates start there and must be carried into licensed republications.
5.1 Source evaluation
How we judge a source
We look at how close the source is to the events, whether details stay consistent over time, what the person gains or loses by speaking, and how easy it is to confirm their story independently.
5.2 On the record
Names are preferred
Named sources are stronger for readers. We use anonymity only when there is a real public‑interest need and a believable risk to the person who is speaking.
5.3 Anonymous controls
Extra rules when a name is hidden
When anonymity is granted, the reporting team knows who the person is, we write an internal note explaining why, and we do not use a single anonymous voice as the only support for a major allegation unless senior editors approve.
5.4 Paying sources
We do not buy testimony
We do not pay for information. In rare cases, we may reimburse basic costs to make an interview possible, but only with approval and clear documentation.
5.5 Experts
Expert help is vetted, not assumed
An expert must match the topic, show clean methods, and disclose conflicts. If a conflict matters for a reader’s judgment, we disclose it in the dossier.
6.1 Authentication
Documents are checked, not worshipped
A file is not “true” just because it looks official. We check how it was obtained, examine details and metadata when available, cross‑match it with other records, and use deeper checks when manipulation is a risk.
6.2 Redaction
We hide details to protect people
We redact to protect confidential sources, victims, minors, private individuals who are not central, personal identifiers, and security details that could enable harm.
6.2 Boundary
Power is not protected by redaction
We do not redact just to shield powerful interests from scrutiny. If a fact is public‑interest critical, we work to publish it safely rather than hide it for comfort.
6.3 Leaked material
Context matters as much as the leak
We weigh authenticity, selective leaking risks, and whether the point can be made without exposing harmful details. Sometimes we summarize key parts instead of posting raw files.
7.1 Threshold
Serious claims need serious support
For major claims, we try to secure at least two independent supports when possible: documents, separate corroboration, data records, direct observation, or qualified technical review.
7.2 Workflow
Layered review for high-risk work
Dossiers go through a claim grid, editor review for fairness and clarity, an independent check of names, numbers, dates, and quotes, and a final audit to keep titles and summaries consistent with the evidence.
7.3 Media integrity
No edits that change meaning
We do not alter photos, audio, or video in a way that changes what happened. Cropping and basic correction are fine; protective blurring is allowed; reconstructions are labeled.
8.1 Who receives it
Serious criticism triggers outreach
People and organizations facing serious allegations are offered a reasonable chance to respond before publication, so the dossier reflects the full dispute honestly.
8.2 What we send
Clear questions, fair time
We share a summary of the claims, ask specific questions, set a deadline that matches the complexity, and provide secure channels when the situation is sensitive.
8.3 Rare limits
Safety can change timing
Outreach may be delayed only when it could cause immediate harm, such as evidence destruction or retaliation, and only with senior approval and a documented reason.
8.4 Publishing responses
Responses are shown in context
If someone replies, we include it fairly. If they decline, we say so. If there is no reply, we state we requested comment and record our attempts.
9.1 Private individuals
Higher bar for naming
Naming a private person can cause lasting harm. We consider role, proof strength, necessity, and foreseeable danger such as harassment, job loss, or physical risk.
9.2 Minors
Children are protected by default
We usually do not identify minors in sensitive situations. Any exception requires a strong public reason and approval by senior editorial leadership.
9.3 Victims and survivors
Trauma-aware reporting
We avoid graphic detail for shock. We avoid blame language. We prioritize consent and safety, and we anonymize when needed to protect the person from further harm.
9.4 Sensitive data
Extra care for intimate information
Health details, sexuality, and similar private data require unusually strong justification. We do not publish intimate content for spectacle, and we redact aggressively when protection is required.
When allowed
Only for exceptional public importance
Undercover reporting is used only when the issue is serious, open reporting cannot obtain the facts, the method is proportionate, and senior leadership approves the plan after risk review.
What is forbidden
No entrapment and no staged wrongdoing
We do not trick someone into committing a harm just to record it. We do not fabricate events. The goal is to reveal hidden truth, not to manufacture a scene.
11.1 Disclosures
Conflicts must be declared
Staff and contributors disclose financial interests, paid roles connected to a coverage area, close personal ties relevant to an investigation, and political roles tied to subjects in the reporting.
Mitigation
We reduce risk, not hide it
When a conflict exists, we may reassign the work, require recusal, or include a clear disclosure so readers can judge the reporting with full context.
11.2 Gifts
No gifts meant to influence
We do not accept benefits offered to sway coverage. Rare access-related support must be approved and may be disclosed when it matters for trust.
Firewall
Commercial money stays out of editorial calls
We accept funding from donors, sponsors, and advertising (not grants), and we keep a strict separation so business relationships do not control story selection or conclusions.
12.1 No funder control
No previews, no vetoes, no “kill rights”
Donors, sponsors, and advertisers do not approve framing, timing, or language. They do not get suppression rights. Legal and security review stays an internal process.
12.2 Major funders
Supporter disclosure is public
A list of major institutional supporters is available at:
https://app23513.cloudwayssites.com/institutional-supporters/
12.3 Sponsored content
If paid, it is labeled
Sponsor-funded material is clearly marked as Sponsored / Advertisement / Partner Content, produced under separate processes, and never presented as independent investigative reporting.
Role
An internal check on high-risk calls
The Standards Editor maintains this policy, reviews high‑risk decisions, audits corrections and serious complaints, and advises on sourcing thresholds, fairness language, and right‑of‑reply sufficiency.
Authority
Can require more verification
When the risk is high, the Standards Editor can require added checks, clearer labeling, or an editor’s note before or after publication to keep the dossier honest and safe.
What we disclose
Data work is explained in plain steps
When analysis matters to a finding, we describe where data came from, how it was collected, what definitions were used, what was changed during cleaning, and what the known gaps are.
Limits
Correlation is not magic
We separate correlation, inference, and proven causation. When the data cannot prove a claim on its own, the dossier says so clearly and shows what else supports the finding.
Supporting material
We share what we safely can
When lawful and safe, we publish supporting datasets or redacted samples and method appendices so a careful reader can judge the work without needing special access.
15.1 Secure channels
How to reach us safely
Secure Tips: https://app23513.cloudwayssites.com/tips/
SecureDrop: https://app23513.cloudwayssites.com/securedrop/
Signal: @hansaj.02
Email: editors@hansajekalavya.com
15.2 Access control
Sensitive details stay limited
Access to source identities and raw materials is restricted to people who need it for editorial work. When risk is high, information is compartmentalized to reduce exposure.
15.3 Safety planning
We plan for retaliation risk
Before outreach and publication, we consider harassment, doxxing, legal threat, and physical risk, then choose steps that protect reporters and sources without burying public‑interest facts.
Allowed use
Tools can assist, people stay responsible
We may use AI-assisted tools for transcription and translation with human checking, document triage and summarization as a lead aid, coding help for data work with testing, and finding inconsistencies that still require manual confirmation.
Not allowed
No fake proof and no fake people
We do not use such tools to invent quotes, invent sources, invent evidence, generate unverified “facts,” create deceptive media, or replace human accountability in editorial decisions.
Disclosure
Material tool use is stated
If a tool meaningfully shapes a published output, we disclose that use and explain the checks performed so readers understand what was assisted and what was verified by humans.
17.1 Commitment
No silent rewrites of big claims
Errors are corrected promptly and clearly. Substantive changes are not hidden. Readers deserve to see what was wrong and what is now correct.
17.2 Categories
Four clear labels
Correction: factual error. Clarification: wording that could mislead. Update: new verified information. Editor’s Note: important context about disputes, process, or strong limitations.
17.3 Change log
Each dossier should list meaningful changes
A change log notes what changed, when it changed, why it changed, and whether the update affects core findings. Older versions are kept internally for accountability.
17.4 Request a correction
How to contact the newsroom
Email editors@hansajekalavya.com with the canonical URL, the exact quote or section, what you believe is wrong, and supporting documentation. Sensitive submissions can use SecureDrop or Signal (see Section 15).
Terms
Republishing requires signed terms
Only partners with signed syndication or licensing arrangements may republish our work. Terms:
https://app23513.cloudwayssites.com/republishing-terms/
https://app23513.cloudwayssites.com/licensing-terms/
18.1 Canonical rule
The original URL stays the anchor
Partners must keep the canonical URL reference and must not present a modified copy as the authoritative original. The main page remains the place where corrections begin.
18.2 No distortion
No cherry-picking that flips meaning
Partners may not remove key context, add fresh unverified allegations, change headlines to claim more than the dossier supports, or delete right‑of‑reply statements and editor’s notes that affect fairness.
18.3 Propagation
Corrections must travel with the story
Partners must carry corrections, clarifications, editor’s notes, and significant updates within the timeframes stated in the terms or promptly upon notice, whichever is stricter.
18.4 Translation
Meaning cannot be softened into errors
Translations must preserve meaning and legal or technical precision. When a term has no exact match, a short note is required rather than a misleading simplification.
19.1 Submit
What to include in a complaint
Email editors@hansajekalavya.com with the canonical URL, the exact statements you contest, the reason (inaccuracy, unfairness, missing context, privacy harm), supporting evidence, and the remedy you want.
19.2 Review
How disputes are evaluated
Complaints can be reviewed by the assigning editor, senior editorial leadership, and the Standards Editor when stakes are high. We may request documents and may publish an editor’s note when the dispute is meaningful.
Rule
Embarrassment is not a reason to delete
We do not remove content simply because it is controversial or because a powerful subject dislikes scrutiny. Pressure is expected; it does not rewrite public record.
When considered
Only extreme cases
Removal is considered only when core claims are demonstrably false and cannot be corrected responsibly, when there is a credible imminent safety risk that cannot be reduced by redaction, or when a valid legal requirement compels it.
Tombstone
We usually leave a notice
If content is removed, we generally publish a short notice stating that removal occurred and why, unless law forbids us from explaining.
Global readership
Different laws, same discipline
Our work is read across jurisdictions, including the United States and India. Defamation rules, privacy rules, court restrictions, and intermediary liability can differ, so our process includes careful wording, attribution, and documented outreach.
Balance
Safety and due process matter
Legal risk does not replace truth. At the same time, safety planning, fairness, and proof standards are treated as essential, not optional, especially in high-stakes reporting.
Separation
Community work is not editorial control
We may run events, programs, or other community initiatives. These activities are separated from editorial decisions so participation does not become a backdoor for influence.
No special rights
Participation does not buy coverage
Community involvement does not grant editorial influence, early access to findings, preferential coverage, or suppression rights. Investigations remain evidence-led and independent.
Maintenance
This policy is kept current
Editorial leadership maintains this policy with input from the Standards Editor. We review it as investigative methods, security risks, and legal environments shift.
Change visibility
Updates are dated
When the policy changes in a meaningful way, the “Last updated” date changes and a short note may be added so readers understand what moved and why.
Editorial email
editors@hansajekalavya.com
Use this for editorial questions, correction requests, and right‑of‑reply responses when secure channels are not required.
Secure tips
Multiple protected paths
Secure Tips: https://app23513.cloudwayssites.com/tips/
SecureDrop: https://app23513.cloudwayssites.com/securedrop/
Signal: @hansaj.02
Disclosures and terms
Public reference links
Major supporters: https://app23513.cloudwayssites.com/institutional-supporters/
Republishing: https://app23513.cloudwayssites.com/republishing-terms/
Licensing: https://app23513.cloudwayssites.com/licensing-terms/
Effective date
June 22, 2026, 4:34 am GMT+0000
This is the time the current wording takes effect for readers across the network.
Last updated
June 15, 2026, 4:34 am GMT+0000
This is the timestamp for the prior policy state shown for reference.
Publisher and rights holder
Ekalavya Hansaj, Inc
Owner: Ekalavya Hansaj
Address: 180 Sansome ST STE 200 San Francisco CA 94104 United States
Mastersite
https://app23513.cloudwayssites.com
Rights and permissions portal: https://app23513.cloudwayssites.com/licensing/
Owned outlets list: https://app23513.cloudwayssites.com/sister-news-brands/
Licensing and permissions
licensing@hansajekalavya.com
Use this when you need permission to reuse, quote at scale, or license material for redistribution.
Syndication and network
syndication@hansajekalavya.com
Use this for partner republication requests and network distribution questions.
Legal
legal@hansajekalavya.com
Use this for formal legal notices, court orders, or jurisdiction-specific issues.
Rights enforcement
rights@hansajekalavya.com
Use this to report unlicensed copying, stripping of canonical links, or removal of correction notes in republished copies.
Corrections
corrections@hansajekalavya.com
Use this when you have proof of an error and want a fast, visible correction path.
Editorial
editors@hansajekalavya.com
Use this for questions about sourcing, right‑of‑reply replies, and dossier methodology notes.
If you want to ask a question, email the editors
Use this button to open your email app and write to the editors. Keep your message simple, include the page link, and point to the exact line you mean so we can respond quickly.