August 2026 · 6 min read

Where Does My Resume Data Go? A Sober Look at Resume Data Privacy

A resume is the most complete identity document most people ever write. Think about what’s on it: your full name, home address, phone number, email, your entire work history with dates, your education, sometimes a photo and a date of birth. That is, give or take a social security number, an identity-theft starter pack. And yet we paste all of it into websites without a second thought, because the website has a nice template gallery. This post is about where that data actually goes — calmly, without the horror music.

Where it goes at a typical cloud builder

At a conventional online resume builder, your document lives in their database, tied to your account. That’s not a secret — it’s the product. The account model is what lets you log back in next year and find your resume waiting for you. It also means your career history sits on someone else’s server indefinitely, associated with your email address and whatever else they know about you.

On top of the database sits the usual web apparatus: analytics, session recording, advertising trackers. You can often see the edge of this in the cookie banner. We checked resume.io while writing this post (as of August 2026): its cookie settings include a “Do Not Sell/Share personal information” option, and its footer carries a “Do not sell, do not share” link to a dedicated page. That wording comes from US state privacy laws like California’s CCPA/CPRA — it exists because “selling or sharing” personal information is a thing the law anticipates a business might otherwise do. To be clear: the presence of the toggle is not proof of anything untoward, and offering it is legally responsible. But it is a fair prompt for the question — if a company offers a switch for not selling my data, what is the switch for?

Which leads to the business-model question worth asking of any free or cheap cloud builder: servers, designers, and support staff cost money. If you’re not paying much, the revenue has to come from somewhere — subscriptions, upsells, advertising, or the data itself. None of these is scandalous. You just deserve to know which one you’re part of.

What can realistically go wrong

No scare stories — just the boring, documented ways centralized data goes sideways:

• Breaches. Central databases get breached. That is not an accusation aimed at any resume company — it’s a statistical property of holding millions of people’s personal data in one place. A breach of a resume database is unusually rich, though: names, contact details, and employment timelines are exactly what makes phishing convincing.
• Data brokerage. Under several US state privacy laws, “selling” or “sharing” personal data for advertising is legal unless you opt out — hence the toggles described above. Most people never touch them.
• Training-data scraping. Resumes posted publicly online are a plausible target for AI training crawlers — they’re structured, well-written personal data. We can’t point at a specific builder feeding your drafts to a model, and we won’t pretend otherwise. But once a document is on a server you don’t control, the difference between “stored” and “used” is a policy document, not a technical barrier.
• Permanence. The quietest risk: a company simply holds your career history forever — through acquisitions, policy changes, and pivots you never agreed to think about. Companies change hands; databases move with them.

The common thread: every one of these risks exists because a copy of your data exists somewhere you can’t reach. Privacy policies govern what a company promises to do with that copy. They can’t change the fact that it exists.

The local-first alternative

There’s a simpler architecture, and it’s the one this site uses: keep the data on your device. The mechanism is called localStorage — a small storage space your browser provides to websites. The important part is what it physically is: data written by your browser, into a file on your machine. It is never transmitted anywhere. When you type your work history into Another CV Maker, it goes from your keyboard into your browser’s storage and stops there. There is no account, because there is no server-side anything to attach an account to.

This is why “there is no server copy to leak” is a stronger guarantee than any privacy policy ever written. A privacy policy is a promise about the future behavior of an organization you don’t control, which can change with a new owner or a revised terms-of-service email. An architectural fact — we never receive your data, because it never leaves your browser — doesn’t depend on anyone’s good intentions, including ours. You don’t have to trust us. That’s rather the point.

The honest trade-offs, because there are some:

• No sync. Your draft lives in this browser on this device. Start on your laptop, and your phone knows nothing about it.
• Clearing browser data wipes it. If you clear site data — or your browser does it for you — the draft is gone. There’s no “forgot my resume” recovery flow, because there’s nothing on our side to recover.
• Backups are your job. The builder has a JSON export/import feature precisely for this: export the file, keep it somewhere safe, import it on any device to continue where you left off. We wrote a separate post on downloading and backing up your CV that walks through it.

Questions to ask any resume builder

Whether you use this site or not, these four questions will tell you most of what you need to know about a builder’s privacy posture:

• Where is my resume stored? “In your browser” and “in our database” are very different answers, and only one of them is checkable by you (open your browser’s developer tools and look).
• Can I use it without an account? Requiring an email address before you can type your own name is a choice, not a technical necessity.
• Is there a “sell/share my data” consent toggle? If yes, read what’s on the other side of it, and decide whether you’re comfortable being on the default side.
• Can I delete everything, really? Not “deactivate my account” — delete. Ask how, and how long backups retain your data after you do.

FAQ

Is localStorage actually private?
From the website’s side, yes: localStorage data lives in your browser’s files on your device and is not sent back to the site’s server — you can watch the network traffic yourself to confirm. The caveats are local: anyone with physical access to your unlocked device and browser profile could read it, just like any other file on your computer.

Can Another CV Maker see my resume?
No. There is no account system and no resume database on our side. Your data is written by your browser to your device, and the PDF is generated locally. We can’t leak what we never had.

What happens to my resume if I clear my browser data?
It’s deleted — that’s the feature and the risk in one. Export your resume as a JSON backup before clearing site data, or whenever you’ve made edits you care about.

Do I still need to worry about where I send my resume?
Yes. This post is about builders, but the document itself is sensitive wherever it lands. Send it to employers you’ve actually engaged with, be wary of “job” postings that exist mainly to harvest resumes, and consider leaving your full street address off — city and state are enough for most applications.