AKD
Every claim on this site, with the measurement behind it.
AKD VaultPDF runs entirely inside your browser tab. Nothing you drop into it is uploaded, and nothing here is a number we made up — each one below came from a real file run through the live site, checked with tools that aren't ours.
Open the tools See passes — $2.22 a day
Watch it happen — nothing staged
A real resume, a real job posting, and the score moving from 43 to 62 as each gap is answered in the applicant's own words.
What was measured, and on what
A number without its scope isn't evidence. Each row names the file it was measured on.
| Claim | Measured | On what |
|---|---|---|
| Redaction covers what it says it covers | 99.9% | of the sensitive ink on a 6-page contract — checked against the file's own word coordinates using poppler, not our own tool's report |
| The text is gone, not covered | 0 | occurrences of 412-88-7391 in the output's raw bytes; pdftotext
returns nothing at all |
| It searches the whole document | 1.0 s | 6 pages, 28 matches boxed — you type the name once instead of hunting page by page |
| The resume loop raises the score | 43 → 62 | one resume against one Senior Platform Engineer posting; the exported PDF re-scores at 62 when uploaded back in as a fresh file |
| Page extraction is exact | 4 of 131 | pages 1-3 and 5 pulled from a 131-page document; extracted text identical to source |
| Merge preserves everything | 133 | pages out of 2 + 131 in, order kept |
| Column maths is exact | 2,413,791.56 | 500-row invoice CSV — matches Python on the same file to the cent |
| It refuses rather than guessing | "Not a number column" | pointed at a date column it declines, instead of reading the year and handing back a confident 1,013,000 |
The part most tools can't do
Left: type a name once and every occurrence on every page is boxed — then the page is flattened so the text is genuinely gone. Right: the reader declining a column it can't honestly total.
Why on-device is the whole point
Most document tools require you to transmit the file before you can protect it. That transmission may well be lawful — a data-processing agreement usually makes it so — but lawful and low-risk are not the same sentence. Every upload creates a copy you then have to reason about: where it lives, who can reach it, how long it persists, what happens in a breach.
Running on your machine removes the question instead of answering it. There's no copy to govern, because the file never moved. You can verify that yourself: open your browser's network tab and use any tool on this site.