Last updated June 2026. Plain English, because that's the whole point.
By default, everything you type stays in your own browser — no account, and nothing saved on our side. There's exactly one exception, and it's opt-in: if you click ✨ Polished PDF, your resume's content is sent to our server only to render the file, then discarded. The normal ⬇ Download PDF and Save backup never leave your device.
As you type, everything is saved only in your own web browser, on your device (in local storage). Simply using the builder never uploads anything — the whole thing runs inside your browser.
⬇ Download PDF uses your browser's built-in print-to-PDF — the file is made on your device and saved by you. We never receive it.
Save backup writes a JSON file to your device that you control. We never receive it.
✨ Polished PDF (optional) is the one feature that sends data off your device: your resume's HTML is sent to our server, rendered into a clean PDF by headless Chromium in memory, and the PDF is sent straight back to you. We do not store it, log its contents, or keep a copy — it exists only for the few seconds it takes to render, then it's gone. If you'd rather nothing ever leave your device, use ⬇ Download PDF instead — it does the same job, locally.
Using “Clear,” or clearing your browser data, permanently removes the resume saved in your browser. We never keep a copy on our end — including from Polished PDF — so there's nothing on our side to delete.
We use Google Analytics to count visits and see which pages get used — the same simple measurement across all of our sites. It tells us things like "300 people opened the builder today," and never sees the contents of your resume. (Analytics is about page visits; it's entirely separate from the Polished PDF render, which also never feeds it.) You'll see a cookie banner the first time you visit; you can decline and the builder still works fully.
Part of AI-Ministries.com. Free tools, no paywalls, no selling your data.