Your choice of tools
Use an assistant that can open ZIP files and execute cryptographic checks. The bundle contains the instructions, signatures and public verification material.
Download the message bundle. Drop it into your AI. Ask it to verify. See how easy it is to check the cryptographic evidence independently of We Secure Data.
Open the message’s verification section and download the message and verification evidence. The ZIP brings the message, attachments and available cryptographic evidence together.
One download. Everything needed for the included checks.
Attach the original ZIP to an AI assistant with file access and code execution. Ask “Verify these files”, or use the ready-to-copy prompt below. The bundle includes precise independent verification instructions.
No coding or manual hash comparison required from you.
In this real example, the assistant reports matching file hashes, two valid digital signatures and a Merkle inclusion proof that reaches the recorded audit-anchor root.
The assistant executes the checks against the original evidence.
The report breaks down the provenance signature, audit-anchor signature and Merkle proof. You can see which operations ran and what each result establishes.
Repeatable checks using published algorithms, outside We Secure Data.
The evidence travels with your message. Your AI can run the mathematics using its own tools, without calling a We Secure Data verification service.
Use an assistant that can open ZIP files and execute cryptographic checks. The bundle contains the instructions, signatures and public verification material.
No We Secure Data account or live service is needed to perform the included offline mathematical checks. Keep the bundle and repeat them later.
File hashes detect changed bytes. Digital signatures authenticate the signed record against its key. Available Merkle evidence links an audit event to a signed anchor. These checks can be reproduced by third-party tools using the downloaded evidence.
Attach the original evidence ZIP, then paste this prompt. Choose an assistant with binary file access and code execution so it can run the checks.
A completed mathematical check is distinct from establishing who owns a signing key. The example report shows that distinction explicitly. Public key records can be checked separately; unavailable or pending evidence should be identified clearly in the report.
Guided walkthrough using real product and AI-session screenshots. ChatGPT is shown as an example; file access and execution capabilities vary by assistant. Verification results relate to the supplied evidence and executed checks.
All demonstrations →