1. Overview
resume-as-code is a paid product. We do not have a free tier, do not sell advertising, and do not have a business interest in your attention beyond providing the product you pay for. This policy describes what data we collect and what we do with it.
The product has three data surfaces: the Cloud hosted service, the Local downloadable application, and the Chrome extension paired with a per-account cloud queue. Each is described below.
2. Hosted services data
Your resume-as-code account stores your email, billing information (handled by our payments processor), and the metadata needed to verify your license. If you have a Cloud or Teams subscription, we additionally store your resume repository, tailored variants, saved jobs, application status, and activity logs needed to run the service.
If you use the Chrome extension, we store the jobs you've captured in a per-account queue until your local machine pulls them or 90 days pass, whichever comes first. You can export a complete copy of any data we hold at any time and delete your account from settings.
3. Local product data
Local runs on your machine. Your resume, your variants, and your jobs (once pulled from the queue) live on your computer's filesystem. We do not have access to that data. We do not transmit it to our servers, and we have no way to recover it if you lose it. Back it up the same way you'd back up any other important file.
Local communicates with our infrastructure only to verify your license, pull your extension queue, and check for updates. None of those calls transmit your resume content.
4. Chrome extension
The Chrome extension only transmits data when you click its Save button. It does not read pages in the background, track which sites you visit, or send analytics about your browsing behavior. When you save a job, the extension transmits the page URL, the detected company and role, the job description text, and the time of capture to your account's queue. Nothing else.
Authentication uses standard token-based sign-in scoped to your account; the extension cannot access any other data on your behalf. The extension's source code can be audited via the Chrome Web Store listing's reviewer documentation.
5. AI and training
The AI that writes resume prose for you operates on your data per request. We do not use your profile, your variants, your saved jobs, or any other content you create to train any model — ours or anyone else's. We do not sell or share your data with third parties for training purposes.
On Cloud, the AI runs in our infrastructure with the same per-request scope. On Local, the AI is whichever agent you have installed (Claude Code, Cursor, Codex, OpenCode, or equivalent); that agent's data-handling policies apply to anything it processes on your machine. We don't see, store, or train on those interactions.
8. Exports and deletion
You can export a complete copy of your data — profile, variants, saved jobs, edit history — at any time from your account settings. The export is in standard, portable formats. There is no "Pro export" tier; this is included with every subscription and with the free account.
You can delete your account at any time from settings. Deletion removes your hosted data within 30 days; the only retention beyond that is what tax and accounting law require us to keep (billing records, primarily). Local product data on your own machine is yours to delete or keep as you wish.
9. Changes to this policy
We update this policy when the product changes in a way that affects how we handle data. Material changes get a notice in-product and an email to your account address. The "last updated" date at the top of the page reflects the most recent revision.
If a change you don't agree with affects you, the export and deletion paths above apply.
10. Contact
Questions about this policy, requests for specific data we hold about you, deletion requests, or anything else privacy-related: email hello@resume-as-code.dev with subject "Privacy". A real person reads every one.