We open it
Nothing here is leaked. Every document in every film was already public — printed in a gazette, filed with a regulator, published as a whitepaper, handed to you on a factsheet. It was public, and nobody read it.
Investigations into finance, technology and government in India — and the places where the three meet. Machines do the reading: we go through filings, tenders and policy diffs at a volume no one person could get through. Every film says exactly where the machine was used, and every tool we build to do it gets released — the pipeline, the croppers, the skills. None of it is published yet. It goes out with the first film.
Seven in ten rupees of individual money sits in the version of the fund that pays a commission. The identical cheaper one is one click away — and the person who sold you the first is forbidden by rule from selling you the second.
The narration is the narrator's own voice, cloned from his recordings. No platform requires that to be disclosed. We disclose it anyway, because the voice reading an investigation is the person vouching for it, and you should know how it was made. It is never used to imitate anybody else.
The statute citations are unverified. Our text is the Bill as introduced; the enacted Act came into force 1 April 2026 and section numbers may have moved.
| Id | Document | State |
|---|---|---|
| C-01 | SEBI (Mutual Funds) Regulations, 2026
sebi.gov.in · last amended 10 Oct 2026 ·
the register it sits in The clause text loads over AJAX, so we hold the register entry, not the provisions. |
Listing only |
| C-06 | AMFI — Code of Conduct for Mutual Fund Distributors (PDF) Revised April 2022 · § II.1 Fiduciary Duty · § f cites SEBI letter SEBI/IMD1/DoF-1/SK/2021/25517/1, 6 Sep 2021 | Complete |
| C-07 | The Income-tax Bill, 2025 — full text (PDF)
via PRS Legislative Research
· ss. 76, 123, 196, 198, 202 and Schedule XV incometaxindia.gov.in serves 403 to automated clients, so the enacted text needs a manual check. |
Verifying |
| C-08 | AMFI Monthly Report, October 2026 (PDF) Industry AUM ₹83,38,858.06 cr · equity ₹37,14,550.45 cr · ELSS ₹2,28,711.73 cr · every month since 1999 | Complete |
| C-09 | Direct vs regular cost gap — our own arithmetic
₹10,000/month · 25 years · 12% gross · 1.14% against 2.21%
→ ₹1,42,18,525 vs ₹1,20,33,015 · gap ₹21,85,510 The chart computes this at render time, so film and dossier cannot diverge. |
Reproducible |
| C-04 | SPIVA India Scorecard S&P Dow Jones Indices · returns HTTP 403 to every non-browser client. We did not forge one, so no SPIVA claim appears anywhere in the film. | Blocked |
| C-10 | Total distributor commission, industry-wide AMFI's site carries a notice that publication of disclosures is delayed. | Not published |
WhatsApp's encryption is real, current, and has no off switch. Its own whitepaper proves it. The argument is about the definition — a “third party” is anyone not in the conversation, Meta holds the private keys for business chats, and Indian law wants to know who said a thing first.
SS-001 has been re-cut with the narrator's own voice and a new score. This one has not. What you are hearing is the crude system voice used to time the edit, and the old music under it. It is the older film in every respect except the research.
We came to this file to prove the encryption was a lie. It is not, so the film says so. Dropped: that it claims to be peer-to-peer (it never has — the whitepaper prints the relay diagram on p.36), and that Meta can read your messages (alleged in a 2025 US filing, denied, no court finding).
The discarded version of a story tells you more about a newsroom than the published one.
| Id | Document | State |
|---|---|---|
| C-01 | WhatsApp Encryption Overview — technical whitepaper (PDF)
“A third party in this context means any organization that is not the sender or recipient user directly participating in the conversation.” “WhatsApp does not consider communications with Meta services, or communications with businesses using Cloud API, to be end-to-end encrypted.”Version 10 · 30 Oct 2026 · archived in the dossier p.35 on the Cloud API: “Meta will have access to their private keys.” Transport security “encrypts metadata to hide it from unauthorized network observers”. p.39 heading: “Encryption Has No Off Switch.” |
Primary |
| C-02 | Security of End-To-End Encrypted Backups (PDF)
“We recommend that users who opt in to end-to-end encrypted backups also deselect WhatsApp from the apps that are included in their device-level backups.”Version 3 · 8 Oct 2026 · archived The engineering is strong. The finding is that it is opt-in, and that the phone's own cloud backup runs against it by default. |
Primary |
| C-03 | Private Processing for WhatsApp — technical whitepaper (PDF)
“… use cases where end-to-end encryption is not possible … backed by different technology which requires different security guarantees.”Meta · V3 · 20 Oct 2026 · archived |
Primary |
| C-04 | IT (Intermediary Guidelines and Digital Media Ethics Code) Rules, 2021 — Rule 4(2)
“… shall enable the identification of the first originator of the information on its computer resource …”25 Feb 2021, as amended by G.S.R. 275(E) of 6 Apr 2023 · gazette text archived Third proviso: no intermediary “shall be required to disclose the contents of any electronic message”. Fourth proviso deems a first originator outside India to be the first person in India to have sent it. The film states both. |
Primary |
| C-05 | WhatsApp LLC v. Union of India — challenge to Rule 4(2), Delhi High Court We do not hold the petition, an order or a transcript. The film says only that a challenge is pending and that no court has ruled — no hearing date, no quotation of the widely reported “we will leave India” line, no prediction. The filing year is press-sourced, so the film says “pending since 2021”, never “pending for five years”. | Secondary |
| C-06 | WhatsApp Privacy Policy Fetched, not archived locally. To be captured with a timestamp before record; until then nothing load-bearing rests on it. | Secondary |
| C-07 | WhatsApp law-enforcement FAQ faq.whatsapp.com serves a JavaScript application that returns “Page not found” to a plain fetch. We did not dress a request up as a browser to get round it, so the page is not quoted and nothing in the film depends on it. | Blocked |
Each of these has a dossier before it has a script. The state below is the honest one: how many of its claims we actually hold the document for. No line is written until the document behind it is archived.
The regulator has published, three times, that around nine in ten individual derivatives traders lose money. The product is still licensed, the exchanges still earn on every lot, and the advertising still runs.
Holding: 0 of 5 documents. The SEBI studies are press-reported only and the figures conflict — 87.7, 88 and 89 per cent all appear. Nothing is spoken until the PDF settles it.
India has a data protection law, and its duties fall due in May 2027. The question is narrower than whether the law is good: it is who the law applies to, and what it did to the Right to Information Act on its way through.
Holding: 0 of 4. The government's own press release returned 403 to us and was not worked around.
A rule says no single app may carry more than 30% of UPI volume. Two apps carry roughly four fifths of it. The deadline has moved three times. Nobody has broken a rule, which is the point.
Holding: 0 of 4 — but NPCI publishes app-wise volume every month, so the chart that is the whole argument is public and waiting.
The law that lets the state read a message, stop a message, or switch off a network is four subsections long. Its safeguard is that somebody writes down why.
Holding: 2 of 4 in paraphrase. One set of rules may still be a draft — that is settled before a word is said about it.
India's transparency law is good. Its front door is a web form. This is what the form does to a request — the wrong-government trap, the character limit, the appeal that only works if you started online.
Holding: 1 of 4, and it is the spine — the portal's own FAQ. Ships with the RTI tool.
Because they are drafts, and a draft that claims more than it holds is how a newsroom ends up correcting itself in public. Each file lists what must be fetched, from where, and which reported figures contradict each other.
Every dossier also carries a what this film does not say list before it carries a script.
One claim, under a minute, and the document it rests on.
Shorts are cut from the master timeline of a film rather than shot separately, so they inherit the same claim ids and the same corrections. A short that cannot cite is not published.
What the whitepaper says happens to a business chat on the Cloud API.
SS-002 · C-01 · 00:34
The message is sealed. Everything written on the outside of it is not.
SS-002 · C-01 · 00:28
The proviso that makes the first person in India to forward a thing its originator.
SS-002 · C-04 · 00:32
An investigation you cannot reproduce is an assertion. So the machinery goes out with the films — the scripts that crop a clause out of a gazette, the gate that refuses an unlicensed image, the renderer that draws a chart straight from the claim file, and the investigation skills as we write them. Each one ships with the thing most tool lists leave out: what it cannot establish — and, where there is one, the case where it failed.
Word-level bounding boxes out of a PDF, matched on the whole run of words, cropped across the full text column. Gives you a legible clause on screen instead of an unreadable A4 page.
Cannot establish: that the PDF is the operative version of the document. That is still a human reading the masthead and the date.
Refuses any image whose licence field is not PD, CC0, CC BY, CC BY-SA or GODL, and requires the subject in the file title.
Cannot establish: that the caption is true. Ours caught a demonetised note sold as current money only because the title was checked too.
Dossier, script and timeline are text files in one repository; the film is rendered from them. A correction is a commit and the film cannot drift from its evidence.
Cannot establish: anything about the claims. It only guarantees the film and the dossier say the same thing.
A machine-readable row per production stage — who did it, model or person, and what the person checked. Generated by the pipeline, not written afterwards, so it cannot go stale.
Cannot establish: good faith. It records what happened; it does not prove the record is complete.
Your SIP, your years, the two expense ratios off your own factsheet — and the gap between them, compounded. Same arithmetic as the film, so the numbers agree. Use it →
Cannot establish: your actual return. The gap is made of fees, which are the one input that is certain.
Shows what is hidden inside a photograph of a document — the phone, the account, the coordinates — and hands back a clean copy. Never uploaded. Use it →
Cannot establish: that you are safe. It does not touch what is visible, does not handle PDFs, and cannot defuse a per-recipient watermark. It says so on the page.
You have not clicked anything or logged into anything. This is what a website learned about your machine anyway, in the time it took to load — and roughly how many bits of you that is. Open it →
Cannot establish: how rare your particular values are. That would need a database of everyone else's, which is the thing we are not building.
The link somebody sent you often carries their name in it. Strips the tracking parameters and says what each one was doing there. Use it →
Cannot establish: where a shortener goes. Resolving one needs a request to its server, and this page makes none.
Five written: proving a PDF is the operative version, the claim schema and its states, the fourteen-day right-of-reply letter, what to do when a source blocks machines, and the per-film AI disclosure record. Drop them into an agent and it loads the one that fits.
Cannot establish: a finding. A skill returns a lead. Confirmation is a person and a primary document, every time.
Routes you to the right government, turns your question into a request for a record, drafts the application inside the portal's 3,000-character limit, and diaries every deadline including the day your appeal opens. Use it →
Cannot establish: whether you will get an answer. It runs entirely in your browser — no server, so we never see what you asked.
One sentence on screen, one document, one state: primary, secondary, blocked, not published. It is what makes the receipts tables on this page generate themselves.
Cannot establish: that a document says what the claim says it says. Only a reader does that.
Not a tool we reach for occasionally — it is how the work gets done. Watching tender portals, filings and policy diffs for the lead. Pulling documents apart. Transcribing and translating. Drafting structure. Rendering every chart from the dossier, so a figure on screen is the figure in the claim file. One person, reading at the volume of a newsroom.
The narration is the narrator's own voice, cloned from his own recordings so a film can be cut without a recording session. No platform requires that to be disclosed. We disclose it on every film anyway, because the person reading an investigation is the person vouching for it.
It is never used to speak as anybody else, and no machine wrote the words. Where an older cut still carries the stand-in voice, its production record says so.
Every tool used to make a film gets released: the document croppers, the licence gate, the claim-to-chart renderer, the whole edit-as-code pipeline, and the investigation skills. A method you cannot inspect is a method you have to take on trust, and this is not an outlet that asks for trust.
As of today none of it is public. Five skills and four tools are written and sitting in a repository nobody else can see. They go out with the first film, and this paragraph gets replaced with the link. If it is still here when a film is published, we did not keep our word.
The documents we could not get, and why. SPIVA blocks automated access. The commission total is not published. A law-enforcement FAQ hides behind a script we refused to impersonate a browser to defeat. All of them are in the tables above, because a gap you can see is worth more than one you cannot.
Every body named in a film gets the findings in writing with fourteen days to answer, before publication. The letter is published with the film, answered or not. Neither letter has gone out yet.
Each film is a repository. A fact changes, the claim file changes, the film re-renders at the same address with a card on screen at the moment it applies.
No correction has ever been issued, because nothing has been published. The log exists from the first day rather than being added after the first mistake. The open verifications listed on the films above are not corrections — they are things we have not finished checking.
No analytics, no cookies, no ad network, no embedded player, no tracking pixel, and no third-party request of any kind. The typefaces used to load from Google Fonts, which handed Google your address every time this page opened; they are now served from this server, which is why they are fatter TTF files rather than WOFF2 — Google serves the smaller format only to requests that look like a browser, and we do not disguise requests.
Two things this page does reach for, both to this server and nowhere else. The newsletter form posts your address here when you submit it, and nothing before that. A link to YouTube, where the films are also published, is a link and not an embedded player — nothing loads from Google until you click it, and then you have left.
A page that lectures you about fingerprinting should say what it leaks.
We publish the document, never the person who sent it. Nothing identifying a source is kept longer than verification takes, and nothing identifying a source is published at all.
One thing that changed this week in a gazette, a circular, a filing or a tender, and that nobody reported. Four hundred words. Tuesday morning. It always links the document itself, so you never have to take our word for the quote.
Where the list lives. On this server, in a file. Not on Substack, not on Mailchimp, not on anything with a pixel in it. An outlet that asks people to send it documents should not hand the list of everyone who reads it to a third party. The cost of that choice is ours: no recommendation network, so every reader has to arrive some other way.
We keep your address and the date you gave it. Nothing else — no name, no opens, no clicks, no tracking pixel in the email. One click unsubscribes and the row is deleted, not flagged.
Tenders, replies to requests, internal circulars, policy diffs. We publish the document, not the person who sent it. There is no secure drop address yet, and we are not going to print an ordinary email here and call it one — a channel that looks safer than it is does more harm than no channel. Until it exists, the honest answer is to wait, or to use the metadata stripper and send from an account and a device that are not yours.
open@sealedsecrets.org is an ordinary mailbox, and we are naming it as exactly that. Corrections, right-of-reply letters, press questions, legal notices. It is read by one person and it is hosted by a company that can be served a warrant, so treat anything you send to it as a letter rather than a secret.