Local-First Resume Privacy: What Stays on Your Device
A local-first resume workflow keeps more drafting control on your device, but you should still review what you paste, export, share, and delete.
Direct answer: Local-first resume editing is useful because your draft stays closer to your own device while you write. In a true local-first builder, all drafting data, styling parameters, and PDF generation processes stay exclusively within your browser's local sandbox (IndexedDB and LocalStorage). The only external network communication occurs when you explicitly configure and invoke an external AI API with your own key.
Know what local-first changes
A local-first workflow changes the default posture: start with your browser and your draft, not with an account record. That is helpful because resumes often include sensitive details such as phone numbers, locations, work history, and private project context.
A robust local-first privacy model divides document lifecycles into three distinct containment boundaries:
- Storage Isolation (Client-Side Persistence): Resume drafts, past versions, and layout configurations reside inside your browser's private database. No background daemon syncs your keystrokes to a remote cloud server.
- Execution Isolation (Local PDF Compilation): The PDF engine renders fonts, vectors, and page layouts directly inside the browser using client-side JavaScript, ensuring no rendered documents pass through external processing queues.
- Telemetry Isolation (Zero Content Logging): The web application serves static assets without logging form inputs or inspecting user inputs.
Data flow map: what stays vs what travels
Understanding the precise flow of your resume information helps you make informed privacy decisions:
| Operation / Event | Where Processing Occurs | Leaves Your Device? | Data Destination |
|---|---|---|---|
| Typing & Formatting | Browser DOM / React State | No | Local device memory only |
| Saving Drafts | IndexedDB / LocalStorage | No | Local browser sandbox |
| PDF Generation | Client-side Print / Vector Engine | No | Local downloads folder |
| Importing JSON Data | Local file reader API | No | Browser memory only |
| AI Bullet Polish (BYOK) | Direct HTTPS fetch call | Yes (Opt-in only) | Official AI provider API (e.g., DeepSeek/OpenAI) |
| Submitting to Employer | Manual file upload / Email | Yes (User-driven) | Target employer / ATS portal |
Separate drafting from sharing
Writing locally is not the same as applying for a job. Before you share, create a deliberate handoff:
- finish the draft in the local editor,
- export the clean PDF file,
- open the exported file in a PDF reader,
- remove private notes, placeholders, or proprietary details,
- then send only the intended version to recruiters.
Direct AI API calls without middleware logging
When you choose to utilize AI features within Iris Resume, the connection architecture maintains maximum privacy:
[Browser Sandbox] ──(Direct HTTPS / Zero Middleware)──> [LLM Provider API Endpoint]
- Client-Side Key Storage: Your personal API key is stored only in your browser's local storage and is never transmitted to Iris Resume servers.
- Direct Pay-As-You-Go: You pay the model provider directly for exact token usage, avoiding subscription markups.
- Enterprise Privacy Controls: Modern LLM providers (including OpenAI and DeepSeek via API) offer zero-retention policies where API inputs are not used to train foundation models.
Review sensitive fields
Give extra attention to the following areas before submitting your resume:
- Street Address: Replace full street addresses with city and state/country only.
- Phone Number: Ensure you provide a direct personal mobile line rather than a corporate extension.
- NDA Compliance: Verify that all referenced projects, systems, and clients comply with non-disclosure agreements.
- Client Names: Generalize confidential enterprise partners (e.g., "a Fortune 50 healthcare company").
- Internal Tools & Codename: Replace internal project codenames with descriptive industry terminology.
Privacy is not one switch. It is a series of small checkpoints.
Ready to build a clean, secure resume? Try the Iris Resume Builder or compare workflows in our Local-First vs Cloud Guide.
FAQ
Does local-first mean nothing ever leaves my device?
Not automatically. It means the drafting workflow keeps all state in local memory and storage, but external AI requests, manual exports, and links you share still travel over the network.
Does a local-first resume builder send any data to your servers by default?
No. In Iris Resume, 100% of resume text, contact details, layout configurations, and PDF renders remain strictly inside your browser's private local memory.
What happens when I use AI features in Iris Resume?
AI requests only occur when you explicitly trigger them. When activated, your browser sends the selected prompt text directly to the model provider (e.g., DeepSeek or OpenAI) using your configured API key.
Which resume fields deserve extra attention before exporting?
Review street address, phone number, personal links, employer names under confidentiality limits, client names, internal tools, and any security-sensitive projects.