A resume builder with nowhere to send your data
Your resume names your current employer, your phone number, where you live, and the fact that you are looking. Most resume sites hold all of that on a server. This one has no server to hold it on.
Why a resume is sensitive
It is one of the densest personal documents most people ever produce: full legal name, contact details, home city, complete employment history with dates, education, and — implicitly — your current employer plus clear evidence you are looking to leave.
The consequences of that leaking are not abstract. It is a precision-targeted phishing kit, a data point for identity verification questions, and, if it reaches the wrong inbox, a conversation with your current manager you did not plan to have.
What actually happens to your data here
- It is never transmitted. The editor, preview, PDF writer and DOCX writer are all JavaScript running on your machine.
- It is stored in one place you control — this browser’s
localStorage— plus any file you download. - There is no account, so there is nothing linking a document to an identity.
- There is no content analytics. Nothing reads your resume text.
- There is no recruiter marketplace, no partner network, and nothing to sell.
- "Start over" is real deletion. It clears local storage. The data is gone, not soft-deleted in a table somewhere.
Verify it yourself
This is a claim you should not take on trust — and unlike most privacy policies, you can check it in about thirty seconds.
Open your browser’s developer tools, go to the Network tab, and use the app: type, switch themes, export a PDF. You will see the initial page load and the webfonts, and nothing carrying your content. Then disconnect from the network entirely and export again — it still works, because there was never a round trip.
The source is public, too, so the claim is auditable rather than merely assertable.
The trade-off
No server means no sync. Your work lives in the browser you used, so a different machine starts empty, and clearing site data clears the resume with it.
The mitigation is built in: export a JSON or PDF and keep it. Because every export embeds its own source data, that downloaded file is a complete save — re-import it anywhere and you are exactly where you left off, theme and all. You are your own backend, which is the point.
Frequently asked questions
Is my resume uploaded to a server?
No. There is no server component. Editing, preview, and PDF and DOCX generation all run locally in your browser, and your content is never transmitted.
How can I verify nothing is being sent?
Open your browser’s Network tab and use the app — you will see only the page and font loads. Or disconnect from the network entirely: everything still works, because there is no round trip.
Does ez-resume sell my data to recruiters?
No. There is no account system, no database, and no recruiter partnership. Your content never reaches anywhere it could be sold from.
Where is my resume saved?
In your browser’s localStorage on your own device, plus any file you export. Clearing your browser data removes it, so keep an exported copy as your backup.
Can I use it completely offline?
Yes. Once the page is loaded, editing and exporting need no network connection.