Coming Soon
Encrypted before upload

Understand any
document in seconds.

Document Explainer analyses legal, official, and financial documents and gives you a plain-language summary, flags the risks, and tells you exactly what to do next.

See how it works

Works with all kinds of documents

๐Ÿ“œ Contracts & NDAs๐Ÿฆ Bank documents๐Ÿ›๏ธ Government letters๐Ÿ  Tenancy agreementsโš–๏ธ Legal notices๐Ÿ’ผ Employment contracts๐Ÿ’Š Insurance policies๐Ÿ“‹ Terms & conditions
How it works

Three steps to clarity.

01

Upload your document

Your file is encrypted in your browser using AES-256-GCM before a single byte leaves your device. Only the encrypted version is uploaded โ€” we never receive your document in readable form.

02

Queued for secure processing

Your encrypted document enters a processing queue (BullMQ). When your turn comes, it is decrypted in server memory only โ€” never written to disk โ€” sent to an AI model for analysis, and the result is immediately re-encrypted under your key.

03

Only you can read the result

Your encrypted analysis is delivered back to your browser and decrypted locally using your key. The server deletes all processing credentials after the job completes.

Features

Everything you need.

Plain-language explanations

Any legal, official, or financial document translated into clear, jargon-free language you can actually understand.

Risk identification

Automatically flags clauses, obligations, deadlines, and terms that could put you at a disadvantage.

What to do next

Actionable recommendations after every analysis โ€” know exactly what your next step should be.

Full history dashboard

Every document you've ever uploaded, with its analysis, stored securely in your personal dashboard.

Offline-resilient queue

Submit a document and go offline. BullMQ queues your job and processes it when ready. Your encrypted result waits securely until you return.

In-memory processing only

Documents are decrypted and analysed in server RAM. No plaintext is written to disk at any stage โ€” not even temporarily.

Supported formats
PDF
Word (.docx)
Plain text
Scanned docs (OCR)
Privacy & Security

Encrypted before it leaves your device.

Your document is encrypted in your browser using AES-256-GCM โ€” derived from your password via PBKDF2 โ€” before upload begins. Our servers process your document in memory only, then permanently delete all processing credentials. What we store is ciphertext. Only you hold the key to read it.

Browser-side encryption

AES-256-GCM encryption runs entirely in your browser via the Web Crypto API. Your key is derived from your password using PBKDF2 (310,000 iterations). The raw key is non-extractable โ€” the browser itself prevents it from being exported.

In-memory processing

For queued jobs, your session key is temporarily wrapped with our RSA-OAEP public key. The server decrypts your document in RAM, runs analysis, re-encrypts the result, then permanently deletes the wrapped key. No plaintext touches disk.

Encrypted storage on AWS S3

Encrypted blobs are stored temporarily on AWS S3 (eu-central-1) and are subject to AWS data retention policies. We store your ciphertext, IV, and job metadata โ€” never plaintext. Every decryption event is logged with timestamp and document hash.

Transparency

What we store โ€” and what we don't.

We believe vague "bank-level security" claims help no one. Here is exactly what lives on our servers.

We store
  • Encrypted document ciphertext (AES-256-GCM)
  • Encrypted analysis result
  • Initialisation vector (IV) โ€” not secret
  • Job metadata (timestamps, status)
  • SHA-256 hash of document (for audit log)
We never store
  • Your document in readable form
  • Your encryption key or password
  • Plaintext analysis results
  • Processing credentials after job completes
  • Any data in localStorage or long-lived cookies

Be the first to know when it launches.

Join the waitlist and get early access free of charge.