Local workflow record
Local file workflow evidence without uploading a source file
A local browser workflow can produce useful evidence about what it did with a selected file without sending that file to an Aftermath processing service. The record should describe observed local facts and remain honest about what no local tool can see.
On this page
A local receipt is a record of the operation, not a chain of custody
A receipt can state that a selected source produced a separately named output, list chosen settings, and report observable output facts such as dimensions, bytes, page count, duration, or warnings. It is useful for repeating a workflow or explaining a technical decision.
It does not establish who created the source, who possessed it at every moment, its legal status, originality, or what happened after the downloaded copy left the browser. Those claims need a different evidence process.
Worked example: an image prepared for a form
A receipt might say: a separate JPG copy was created locally at 600 × 600 pixels and 72 KB after a selected crop method; the original remains outside the tool; the output was visually reviewed for clipping. This is specific and reproducible without collecting the image itself in the receipt.
The note should not say that the form accepted the image, that it proves identity, or that it is appropriate for every recipient. Those things happen outside the local preparation step.
| Record item | Example | Boundary |
|---|---|---|
| Input relationship | A user-selected source was read in the current browser session. | Does not identify or authenticate the source owner. |
| Output fact | New copy measured at 72 KB. | Does not prove server acceptance. |
| Warning | Visible crop requires human review. | Does not make the editorial judgment automatically. |
Privacy claims need careful language
Browser-local processing describes the intended location of the file operation. It should not be expanded into claims that no information exists anywhere in a person’s device, browser history, downloaded files, extensions, operating system, backups, or future sharing channel.
Read the privacy boundary and use a trusted environment. Sensitive material still deserves minimum disclosure, careful filenames, and a thoughtful download and sharing path.
Keep receipts useful by keeping them narrow
The best receipt records just enough to reproduce and review a technical transformation. Avoid copying sensitive content, secret values, or unnecessary personal data into a note designed for operational facts.
If a recipient needs formal evidence or proof of submission, use its official system and follow its documented record process. A browser result receipt is neither a notarization nor a third-party confirmation.
Use a local tool