Is my resume uploaded to a server?
It stays in this browser: 1 copy in IndexedDB, no account and no server-side database. The only upload is the optional AI improve button, which sends at most 600 characters of the field you are editing.
A private resume builder that never uploads your CV.
Resumake runs entirely in your browser. Your resume, photo and settings are stored locally, there is no account, and there is no server-side resume database to breach. The one exception is the optional AI improve button, which sends only the sentence you selected.
Where does your resume data live?
Short answers first, then the details.
What exactly is stored, and where?
It is 2 things: the resume content in IndexedDB, and the settings — template, language, layout — in the same browser profile for resumake.online.
If you open your browser's developer tools and clear site data, both are removed at once.
Does the PDF leave my device?
It does not: 1 local print engine, 0 uploads. Your browser renders the page you see and saves the PDF straight to your downloads folder.
What happens if I clear my browser data?
It is gone: the draft exists only in this browser, so clearing site data deletes it. Download a backup JSON first and you can restore it in any browser later.
Can I open the same resume on another device?
It is possible with 1 file: Save backup downloads a JSON with the resume and settings, and Import restores it on another device. There is no cloud sync because there is no account.
Why does "local only" matter for a resume?
Why does storing it locally matter?
It is the most personal document you own — name, phone, email, city, employment history, education and often a photo. Uploading it creates 1 more copy you cannot delete.
Breaches happen, databases get misconfigured, and "we may share data with partners" clauses are common. The simplest way to reduce that risk is to never send the file anywhere in the first place.
If your main concern is passing automated screening rather than privacy, the ATS-friendly resume guide covers that side. If you just want to skip registration, see resume builder with no sign-up.
No account also means no password to leak.
There is no sign-up, so there is no password reuse risk, no verification email to intercept and no account profile to scrape.
How is this different from a cloud resume builder?
| Resumake | Typical cloud builder | |
|---|---|---|
| Where your resume is stored | Your browser only | Their servers |
| Account required | No | Usually yes |
| Data breach surface | None on our side — we hold no resume data | Whatever they store |
| Cross-device sync | Manual, via a backup file | Automatic |
| Access from a new device | Restore the backup file | Log in |
How to keep a backup of your resume.
-
Save the backup file
In the editor, choose Save backup. You get a small JSON file containing your resume and settings.
-
Store it somewhere you trust
Your own drive, an encrypted folder — anywhere private. It is plain JSON, so keep it out of public repos.
-
Restore whenever you need
Open the editor in any browser and import the file. The resume reappears exactly as you left it.
Frequently asked questions
Is my resume uploaded to a server?
Not unless you press the optional AI improve button. Resume content, photos and settings stay in your browser's local storage, there is no resume database, and the AI only receives the sentence you selected — never the whole document.
What exactly is stored, and where?
Two things are stored in your browser profile for resumake.online: your resume content in IndexedDB, and your settings such as template, language and layout. Neither is synced to a server.
Does the PDF leave my device?
No. The PDF is produced by your browser's own print engine from the page you see, and saved to your downloads folder. It is never uploaded.
What happens if I clear my browser data?
The draft disappears, because the draft only exists in this browser. Download a backup JSON file first; you can restore it in any browser later.
Can I open the same resume on another device?
Yes, through the backup file. There is no cloud sync because there is no account and no server-side storage.
Do you still collect any analytics?
Yes, two anonymous counters: page views via Cloudflare Web Analytics, and whether the editor was opened or a PDF exported. They contain no cookies, no identifiers and nothing about your resume.