Booking confirmations, pay notifications, membership updates. Users receive emails every day that contain the facts you need. Burnt lets them prove specific claims from those emails without revealing the content.
The user connects their email through a standard OAuth flow (like Google). They see exactly what permissions are being requested and grant consent explicitly.
We locate the specific email that contains the fact you need verified, like a booking confirmation from an airline, a pay notification from a payroll provider, or a membership update from a loyalty program.
Using the email's existing DKIM signature, Burnt proves a specific fact from the email content without revealing anything else. You get a verified true or false. We never store, log, or retain the email content.
When a mail server sends an email, it attaches a DKIM signature, a cryptographic proof that the email came from that domain and has not been tampered with. This is a standard spam-prevention mechanism used by virtually every major email provider.
Burnt leverages these existing signatures to let users prove facts about their emails to third parties. The user chooses which fact to reveal. Everything else stays private. The email content is processed in memory only and discarded immediately after the verification result is produced.
A user should not have to show their entire inbox to prove they received a flight confirmation. They should not have to forward a payroll email to prove they got paid. Burnt extracts only the specific, relevant fact and produces a verified signal. Nothing more leaves the user's control.
A claimant received a booking confirmation email from the airline. Burnt verifies the email is authentic (signed by the airline's domain), confirms the booking details, and checks for delay notifications. No screenshot uploads. No PDF forgery risk.
Applicants receive pay notifications from their employer's payroll system. Burnt verifies the email came from the employer's domain and confirms the pay amount meets your income threshold.
A user claims to be a member of a competitor's loyalty program. Burnt verifies they received a membership confirmation or status update email from that provider. You get verified proof of competitor status without any data partnership.
Order confirmations, subscription receipts, account statements, appointment notifications. If a company sent the email and DKIM signed it (virtually all do), Burnt can verify specific facts from it.
Not every source has a user portal. But almost every service sends emails. Booking confirmations, pay notifications, status updates. Email verification reaches sources that portal-based verification cannot.
DKIM signatures are applied by the sending mail server. The email content is mathematically proven to be unaltered. Forwarded, screenshotted, or AI-generated emails fail this check.
Users reveal only the fact being verified. The full email, including personal details, other transactions, and unrelated content, stays completely private. We never store or retain email content.
Email content is processed in memory only and discarded immediately. No raw email data is logged, cached, or transmitted to anyone. The only output is the verified result.
See how Burnt can turn transactional emails into verified, privacy-preserving signals for your business.