inkline
/ verify
inkline
/ verify
Paste the email to confirm a human approved exactly these words with Touch ID. Runs entirely in your browser — nothing leaves this page.
The text above is the canonical action exactly as it was shown on the signer's Mac and signed. Companies compose it in their backend; Inkline never rewrites it.
Only text is signed. Images and attachments are not covered by the receipt — leave them out. A Google Drive attachment shows up as its file name in the text, so include that.
A valid receipt proves the enrolled key signed exactly this content — an email, or an action a company asked a person to approve — after a Touch ID check on the signer's Mac, or, for passkey receipts, after the enrolled user's passkey verified them in their browser. The result names the tier: hardware-attested stamps carry Apple's App Attest certification that the key was created in a genuine Secure Enclave; passkey receipts carry no hardware attestation; receipts from before 17 September 2026 predate attestation and say so. It does not prove who composed the words. Email fields are canonicalized before hashing, so transport rewrites don't break verification — any change to the words does. BCC is never part of the signed content: it would reveal hidden recipients. Action receipts carry the canonical action text itself; edit one character and the hash check fails. source