We do not collect your reports
This page is the only way one reaches us, and you are the one who sends it.
mend never transmits a report. Not at the end of a task, not on a schedule, not in the background. There is no telemetry in the product, and the endpoint behind this page cannot fetch a report — it has no handle lookup and no read path into any tenant's store, so the only way it ever holds one is if a person hands it over. That is not a policy we are asking you to believe; it is the shape of the code, and it is pinned by tests.
It matters because of what a report contains. Reports carry workspace file names, verdict digests, and the shape of the work you delegated. The service's own report says plainly that no approval covers customer or external data. Harvesting these quietly would make that sentence false, so it is not done.
Declining costs you nothing. No feature is gated on it, nothing is remembered about a report you looked at and did not send, and there is no prompt that will ask again.
1 · Give this page the report
Paste the JSON, or pick an exported .json file. It is read in your browser. Reading is not sending.
2 · This is what you would be sending
Read from the report itself. This page adds colour and nothing else — no field below was invented here.
Workspace file names
The paths this report names. Tick the box below and every one of them is replaced, in the payload as well as on this screen, before anything is sent.
Checks and timeline
What was appraised, and the recorded events in sequence order.
The limits the report attaches to itself
Carried with it. These travel to us unchanged.
The exact bytes
The payload as it would go over the wire, after redaction if you asked for it.
3 · Your call
Nothing has left this page yet. It will not until you press the button.
- It sends nothing until you press Send. Pasting, picking a file, redacting and re-reading all happen in this tab. No box is pre-ticked and the Send button is not focused for you.
- It keeps no credential and asks for none. Sharing is unauthenticated on purpose: you may be holding a report in a browser that has never seen your API key.
- Redaction is done here, before transmission. We never see the unredacted form, which is the only arrangement in which that sentence can be true.
- Redaction covers the paths this page can identify — the report's own path-shaped fields (workspace_files_observed, scope.paths, a check's path, an outside list). If a file name appears inside some other free-text field, this checkbox will not catch it, and the payload above is the thing to check.
- A redacted report no longer matches its own fact_digest. That is expected and is not tampering: the digest covers the facts as issued, and you changed them on purpose. The record we keep says you declared it redacted.
- It stores nothing locally: no cache, no analytics, no third-party request of any kind. Reload the page and it is empty.