Ask for a proof. Never hold the statement.
Stop collecting full bank statements you then have to store and protect. Send a request link; the applicant proves exactly what you asked — income, levies paid, address — and reveals nothing else. You verify it in your browser, and their private data never touches your systems.
Create a request
You'll need an account to save requests and collect returned proofs in your verified inbox. The applicant who completes the request, and anyone who opens a proof to verify it, need no account — those run entirely in the browser.
You ask, they reveal
The applicant chooses which figures to show. You get proof of what you need without their whole financial life.
No data to protect
You never receive or store the full statement — only a verified, redacted proof. Nothing to breach, nothing to comply over.
Verify it yourself
Every proof checks in your browser against the sender's own signature (or is clearly labelled self-attested). No trust in the applicant required.
Honest about what's verified
A proof arrives as one of two clearly-different certificates. Source-verifiedmeans the document is proven to genuinely come from a named institution (the sender's DKIM signature, a signed PDF, or a verified session). Self-attestedmeans it's sealed and unaltered since the applicant shared it, but the source isn't cryptographically proven — treat those with the same care as any document. For anything fraud-sensitive, require source-verified.
Integrate proofs into your own product
Request and verify proofs programmatically with an API key — create a source-verified proof of a figure from a DKIM-signed email in one call, and the recipient verifies the returned proof in their browser (no account). Bulk request links and webhook delivery of returned proofs are included.
# Create a source-verified proof — reveals only the chosen figure
curl -X POST https://tinyfiles.io/api/prove-income \
-H "Authorization: Bearer $AT1_API_KEY" \
-H "content-type: application/json" \
-d '{"rawEmail":"<base64 of the .eml>","figure":"77000.00"}'
# -> { "proof": { ... }, "publicSignals": [ ... ] }
# The recipient verifies it in-browser at https://tinyfiles.io/verify — no account.Keys are issued from your dashboard. Source-verified proving needs the figure to sit in the signed email body (invoices, payslips, levy/rates or utility notices); larger documents use the self-attested tier. Talk to us for onboarding, SLA and volume rates.