docs/use-cases/privacy-focused-resume-builder.mdx
Reactive Resume is a privacy-focused resume builder: the code is open source, you can self-host it, editing is private by default, and both sharing and AI are choices you make yourself.
You edit resumes inside your account. When you want someone else to read one, turn on a public URL and send them the link. Public resume URLs are not search-indexed by default. You can turn public access off again, and a public resume can require a password.
For the sharing workflow, see Sharing your resume publicly. For account security, see Setting up two-factor authentication and Setting up passkeys.
Use this path when you want to understand the tradeoffs before choosing hosted use, self-hosting, public sharing, API automation, or AI features. It matters most if your resume holds sensitive job-search information, or if you plan to share links with only a few people.
Do not treat public sharing as access control. Use password protection, or keep the resume private, if only specific people should open the link. Do not turn on AI features unless you are comfortable sending the prompts and resume content to the provider you configure.
The source code is on GitHub, so you can read how the application works. If you need direct control over infrastructure, storage, auth providers, and deployment policy, run your own instance.
Start with:
AI is optional. Reactive Resume does not need it to create, edit, export, or share a resume. If you do want AI help, you configure the provider and the key yourself.
For setup details, see Using artificial intelligence, Using AI in the builder, and Using the AI Agent workspace.
<Info> Review the privacy policy for the instance you use. If you self-host, you are responsible for the deployment's data handling, storage, email, and third-party provider configuration. </Info>Read the Privacy Policy, then go to Sharing your resume publicly for link controls or Self-hosting with Docker for infrastructure control.