Privacy policy

What we collect

Nothing. Resume Canvas has no accounts, no sign-up and no back end that receives your resume as you write. We do not run analytics, advertising or third-party tracking scripts.

There are only two ways anything leaves your device, and each happens only when you ask for it: creating a share link, and using the AI import or quick-add tools. Both are described in full below.

Where your resume is stored

Everything you type is saved to your browser’s local storage on your own machine. It stays there until you clear it, either with the “Start over” action in the builder or by clearing your browser data. Because it is stored per-browser, your resume will not appear on another device or in a private window.

Sharing a resume

If you choose to create a share link, your resume is encrypted in your browser first. What is uploaded is the encrypted file and the random value needed to decrypt it in combination with the key — nothing else. We do not store your name, your IP address, your browser or the page you came from alongside it.

The decryption key is generated on your device and placed in the part of the link after the #. Browsers never transmit that part in a request, so the key never reaches our server. The practical consequence is that we hold a file we are unable to read, and that anyone who has the complete link can read it — so treat a share link as you would the resume itself.

You choose how long a link lasts, up to one year. When it lapses the encrypted file is deleted automatically and the link stops working. Shared pages are marked noindex and excluded in robots.txt so that search engines do not list them.

AI import and quick add

Where a deployment has AI enabled, you can import an existing resume (a PDF or text file, or pasted text) and draft entries from a short description. These are the one case where your content is sent unencrypted, because a model has to read it: the text goes to our server and from there to an AI model through OpenRouter, whose policies and those of the model provider then apply. For a PDF, only the text extracted from it is sent on — never the file.

Our server does not store or log that text; it passes the answer back to your browser and keeps nothing. Nothing changes in your resume until you review the result and confirm it. If you would rather not send your content anywhere, simply don’t use these tools — everything else works without them.

Photos and files

A photo you add is resized in your browser and stored in that same local storage. It is not uploaded unless you create a share link, in which case it is encrypted along with the rest of the resume.

Exporting

PDF export uses your browser’s own print engine, and the plain-text export is generated in the page. Neither sends your content anywhere.

Fonts

Typefaces are served from this site rather than a third-party font CDN, so loading a page does not disclose your visit to another company.

Hosting logs

The site is served by a hosting provider that, like any web server, may record standard request logs such as IP address and user agent. Those logs are not linked to any resume content, which the server receives only encrypted (for a share link) or in passing (for an AI request it does not keep). To limit abuse of the share and AI endpoints we count recent requests against a one-way hash of the caller’s address, held for an hour and never stored with a share.

Your control

• Clear your data at any time from within the builder.
• Choose whether to share at all — nothing is uploaded until you create a link, and every link expires.
• Choose whether to use AI at all — nothing is sent to a model unless you start an import or a quick add.
• Inspect exactly what is stored — the code is open source and runs in your browser.
• Use the site without providing any personal detail to us.

Questions

Open an issue on GitHub.