Use this tab to create a permanent, verifiable proof that a specific person sent you an email on a given date — before a deadline, before a decision, before a dispute. The stamp is stored on Arweave and cannot be altered or deleted. Anyone can verify it independently.

Enter your email address and an app password, then specify the sender and a date range. Click Fetch emails to retrieve matching messages, select one, and stamp it. Or switch to Upload .eml file to stamp a message you've already exported or received as an attachment — DKIM is checked directly against the original file's bytes, and if it contains a forwarded message you can pick the inner message to analyze separately. You get the strongest origin check by uploading the original message as a .eml file, or by having it forwarded to you as an attachment.

What you can prove

The stamp records the sender's address, the date, and a cryptographic hash of the message. It proves that a specific sender sent this exact message before the moment of stamping. It does not prove the content is true — only that it exists and was sent.

Gmail: create an app password

Gmail requires an app-specific password for IMAP — your regular Gmail password will not work here.

1. Make sure 2-Step Verification is enabled on your Google account.
2. Go to myaccount.google.com → Security → App passwords.
3. Choose Mail as the app and give it any name.
4. Copy the 16-character password shown and paste it into the Password field above.

The app password gives read-only access to your email via IMAP. You can revoke it any time from the same page.

Finding the sender and date in Gmail

1. Open the message in Gmail.
2. The sender's address is shown next to the name in the From line — hover over the name to reveal the full address.
3. The date is displayed at the top right of the message. For the exact timestamp, click the three-dot menu → Show original.
4. Enter the sender address and a date range that covers that date, then click Fetch emails.

Use this tab to draw a new conclusion from two or more existing Leima stamps. For each stamp, upload the Leima package (.zip) you downloaded when the stamp was created. The system validates each package's integrity and Arweave anchor, reads the full verdict content, and lets the AI reason across all of them to evaluate your new combined claim.

For example: three reference letters stamped separately each prove one thing. A bundle can then prove "this person has three verified references."

What you can prove

The bundle verdict is itself a new permanent stamp. It proves that on this date, a set of independently sealed verdicts was examined and found to support your combined claim. The original stamps remain unchanged on Arweave — the bundle is an additional layer of reasoning on top of them.

Where to find the package file

After any stamp is created, a download button appears below the verdict: ⬇ Download Leima package (.zip). Save it and upload it here — one package per stamp, 2–10 packages total.

Writing a good claim

Describe what the documents together prove — a timeline, an agreement, or a sequence of events across multiple sources.

Upload a photo or paste an image URL, then write a claim about what it shows. The AI analyses the visual content and stamps the result permanently on Arweave. If the image contains C2PA provenance data, the stamp also records whether the image is authentic and unmodified.

What you can prove

The stamp records a hash of the image and the AI's verdict on your claim. If the image has valid C2PA data, the stamp additionally confirms that it has not been altered since it was captured.

What is C2PA?

C2PA is a standard that embeds a cryptographically signed certificate inside an image at the moment of capture. If modified after capture, the signature becomes invalid.

Use this tab when you want to stamp a factual claim without attaching any source document. The AI evaluates the claim using its own knowledge and records the verdict permanently on Arweave.

What you can prove

The stamp records the claim text and the AI's verdict. It proves that on this date, the claim was evaluated and found to be supported or not supported by AI knowledge available at that moment.

Use this tab to stamp any document you have in hand. Use the sub-menu to choose how to bring it in: upload a PDF, paste text directly, or fetch a PDF from a URL.

Due diligence example

A company shares confidential financial projections during due diligence. The buyer stamps the document with a claim such as "this document shows projected revenue above €10M for 2026" — the verdict characterises the content without reproducing the sensitive figures in full.

Paste a public URL and write a claim about what the page says. The AI fetches the page content at the moment you click Analyse and evaluates your claim against it.

What you can prove

The stamp proves that at this specific moment, the page at this URL contained the content that supports or contradicts your claim.

Enter a GitHub repository and optionally a commit hash, branch, or tag. The AI fetches the specified files and evaluates your claim about the code.

What you can prove

The stamp records the repository, the commit reference, and the AI's verdict. It proves that specific code existed in a public repository at a given commit.