Originality verification

Someone shared a document made in Minidocs and you scanned its verification QR code. This page checks the QR's signature and shows what the QR says about how the document was created — the document name, when it was exported, the macOS account that wrote it, and how those words got into the editor.

Nothing is uploaded. The data lives entirely inside the URL you scanned, and the check runs in your browser.

No verification record in URL. Scan a Minidocs Originality QR code to view a record here.
What the signature does — and doesn't — prove

What it proves: the QR code was produced by something that knew Minidocs's signing secret. If the badge above says Signature verified, no one tampered with the URL after Minidocs generated it. Edit a single character in the QR's URL and the badge flips to Signature mismatch.

What it does not prove:

Treat a verified record as evidence the author is willing to attach their name to. It raises the cost of forgery from "anyone with a text editor" to "anyone willing to read the app binary." For most academic and professional contexts, that's where the friction lands. It is not, and cannot be, cryptographic proof.

What this means in practice

Self-attested. Minidocs runs locally on the author's Mac. The "typed", "pasted", "inserted", and "imported" character counters are recorded by the editor as the document is written, and embedded in the QR code at export time. Minidocs does not send these to a server.

Counters are per-machine: a document opened on a different Mac will start fresh counters on that Mac. The install ID identifies the Minidocs install, not the human author.

Questions

If something here is unclear, or a record looks wrong, write to support@getminidocs.app. The full data-handling policy, including everything contained in the QR payload, is in the privacy policy.