Contact, editorial corrections, and disclosure channels
Three named channels for readers, advertisers, and editorial corrections: a dedicated email for corrections, a dedicated email for privacy requests, and a 72-hour response window.
Three channels, three response windows
The editorial gateway routes reader contact through three named channels. The first channel is for editorial corrections: a typo, an outdated number, a misattributed quote. The second channel is for privacy requests under the DPDP Act 2023. The third channel is for takedown notices under 17 U.S.C. § 512(c)(3). Each channel has a published response window and a named owner.
What the editorial gateway treats as a correction
A correction is any factual error in an article: a misstated limit, a wrong date, a wrong attribution, a misspelled name. The editorial team records the correction request in the editorial log, verifies the correction against a second source, and updates the article within 72 hours. The correction note carries the date of the correction and links back to the original sentence.
Corrections channel, in detail
The corrections channel accepts typo reports, outdated numbers, misattributed quotes, and inaccurate summaries. The channel is published in the byline of every page and on the Contact page. The corrections channel is monitored during Indian business hours. A correction that arrives after hours is acknowledged the next business day.
How the corrections channel works
When a correction arrives, the editorial team first verifies the claim against a second source. The verification step is the binding rule; a claim that cannot be verified is escalated to the editor in chief and either verified through a third source or declined with a published reason. The corrections log records the verdict on every correction, whether approved or declined.
A 72-hour response window for corrections, a 7-day window for privacy requests, and a 24-hour window for takedown notices.
The editorial gateway routes reader contact through three named channels. The first channel is for editorial corrections: a typo, an outdated number, a misattributed quote. The second channel is for privacy requests. The third channel is for takedown notices.
Privacy channel, in detail
The privacy channel accepts DPDP Act 2023 rights requests, including the right of access, the right of correction, the right of erasure, and the right to nominate. The privacy channel is monitored during Indian business hours. The privacy desk responds within 7 days for cookie-specific requests and within 30 days for full data requests. The privacy desk publishes the response format on the privacy channel page.
How the privacy channel works
A privacy request triggers a data lookup job that scans the editorial gateway's account tables, contact tables, analytics tables, and support inbox. The job compiles a single export that the privacy desk reviews for redaction before delivery. A reader who requests erasure triggers the same lookup job followed by a purge job across the same tables. The purge job is auditable.
Takedown channel, in detail
The takedown channel accepts DMCA notices, trademark complaints, and court orders. The takedown channel is monitored 24 hours a day, 7 days a week. The takedown desk responds within 24 hours of receipt. The takedown desk publishes the formal notice format the editorial gateway accepts under 17 U.S.C. § 512(c)(3) on the DMCA page.
How the takedown channel works
A takedown notice that meets the published format triggers a content-removal job within 24 hours. The job records the URL of the removed content, the date of removal, and the case reference. If the alleged infringer submits a counter-notice, the content-removal job is reversed after the 10-14 day waiting period unless a lawsuit is filed.
Published values, in one table
Contact channels published by the editorial gateway
| Channel | Use for | Response window | Owner | Corrections | Editorial typo, outdated number, misattributed quote | 72 hours | Editorial team | Privacy | DPDP rights, data access, deletion | 7 days | Data desk | Takedown | Copyright, trademark, court order | 24 hours | Legal desk | Press | Citations, interviews, attribution | 5 days | Editorial team | Advertising | Affiliate disclosure, sponsored content | 5 days | Commercial desk | General | Everything else | 7 days | Front desk |
|---|
What the editorial gateway does not accept
The editorial gateway does not accept promotional pitches through the contact channels. The editorial gateway does not accept requests to publish content in exchange for compensation. The editorial gateway does not accept requests to remove legitimate editorial coverage. The editorial gateway does not accept requests to add backlinks to unrelated content. The editorial gateway does not entertain requests to alter coverage of the operator based on affiliate economics.
What the desk declines
The editorial team declines requests to publish promotional content, requests to alter coverage based on affiliate economics, requests to add backlinks to unrelated content, and requests to remove legitimate editorial coverage. The team declines by publishing the response in the editorial log and pointing the writer to the editorial charter.
How the editorial team handles a disagreement
Where a reader disagrees with the editorial coverage, the disagreement is recorded in the editorial log and answered in a reply. The editorial team does not edit coverage because a reader disagrees; the team edits coverage only when the factual record is wrong. The reply is published alongside the original coverage so a future reader sees the disagreement and the answer.
How disagreements are logged
A disagreement with editorial coverage is logged as a reply alongside the original coverage. The reply appears on the same URL after the editorial body, dates from the disagreement date, and carries the editor's answer. A future reader who visits the URL sees the original coverage, the disagreement, and the editor's answer in chronological order.
Editorial accountability and the response window
The contact channels are monitored by named owners, and the response window is published for each channel. The accountability is logged on the editorial log: every message, the date, the assigned owner, and the date of the response. The editorial log is published quarterly on the editorial responsibility page. A reader who wants to verify the accountability can navigate to the log, find the case reference, and read the response.
How the editorial gateway runs the contact-channel audit
The editorial gateway runs the contact-channel audit on a monthly cadence. The audit checks every channel, every response window, and every named owner. The audit produces a published report that lists every channel, every response window, and every owner. The audit report is published on the editorial responsibility page; the report carries the date of the audit and the date of the next audit. The audit report is the binding rule. A discrepancy between the audit report and the contact channel triggers an update on the next refresh; the update is logged in the editorial log. A reader who wants to verify the contact channel against the audit report can navigate to the editorial responsibility page.
Frequently asked
How do I report an editorial error?
Use the corrections channel. Include the article URL, the paragraph, the error, and the corrected version with a verifiable source.
Will my correction be published with my name?
Yes, unless you ask for anonymous publication. The correction note links to the article that was corrected; the date of the correction is the publication timestamp.
How do I exercise my DPDP rights?
Use the privacy channel. State which right you are exercising (access, correction, erasure, nomination) and the email associated with any account you may have.
Do you accept anonymous tips?
Yes. The editorial gateway reads anonymous tips and protects the source by default.
Is there a phone number?
No. The editorial gateway publishes channels that produce an audit trail.
Where is the editorial team based?
The team is based in Bengaluru, India. The editorial gateway publishes content for readers across India.
What if I disagree with a published correction?
You can use the contact channel to add a follow-up note. The follow-up note is published alongside the correction; the editor's response is appended.
How long until my message is acknowledged?
All three channels acknowledge within 1 business day. The corrections channel responds within 72 hours; the privacy channel within 7 days; the takedown channel within 24 hours.
Can I send a tip anonymously?
Yes. The contact channels accept anonymous messages; the editorial team protects sources by default.
Is the editorial team reachable on weekends?
The takedown channel is reachable 24x7. The corrections and privacy channels respond during Indian business hours.
How does the Contact page sit within the wider editorial network?
The contact page is one of the published stops in the editorial network. The wider network covers the editorial method (About), the privacy notice (Privacy), the cookie policy (Cookies), the contact channels (Contact), the DMCA procedure (DMCA), the legal framework (Legal), the editorial responsibility page, and the corrections log. Every stop in the network links to the others through the footer.
Where can I read the underlying source document?
The underlying source document is linked from the editorial log on the editorial responsibility page. The source document is the binding rule; the Contact page is the editorial reading. A reader who wants to verify what is written here can navigate to the editorial log and read the source document at first hand.
What if the source document changes?
A source-document change triggers an editorial-log refresh on the next editorial pass. The contact page is updated to reflect the change; the editorial log records the date of the change and the date of the refresh. The quarterly audit cycle picks up the change on the next pass.
Looking for the editorial correction log?