Your career data belongs to you. Period.
Most modern resume builders operate as cloud SaaS platforms: your salary history, private contact information, references, and work achievements are uploaded to third-party databases, analyzed for ad metrics, and held behind monthly paywalls. Resumes takes the exact opposite approach.
✓ 1. No User Accounts, No Application Backend
There is no "Log in with Google", no email verification, and no remote user database. The app starts immediately upon launch. There are no servers collecting your session details, IP addresses, or application metadata.
✓ 2. Stored Strictly on Your Local Machine
All your resumes, tailored applications, and supporting documents are stored in a standard folder of your choice (by default, ~/Documents/Resumes). The application uses an embedded SQLite database running locally in WAL mode alongside transparent Markdown files that you can inspect, backup, or version control with Git at any time.
✓ 3. Exactly Zero Telemetry or Analytics
The desktop app contains no analytics SDKs. No Google Analytics, no Mixpanel, no PostHog, no Segment, and no Sentry telemetry. When you click a button or export a PDF, not a single ping is transmitted to any analytics service.
✓ 4. Local AI Processing Without Cloud Transmissions
Our AI assistance and bullet point refinement tools run completely locally using deterministic heuristic engines written in Rust (guaranteed 0 RAM overhead and 0 network usage). If you choose to connect local Ollama models, connections are made exclusively to localhost:11434. We never ask for an OpenAI, Anthropic, or cloud API key.
✓ 5. Safe, Sandboxed Document Parsing
Importing external PDF and DOCX files uses memory-safe Rust libraries. Word documents (.docx) are decompressed into temporary memory buffers and parsed specifically for text nodes (<w:t>), strictly discarding and never executing macros (vbaProject.bin) or external script attachments.
How You Can Verify This
You don't have to take our word for it. You can monitor the desktop application using standard OS network diagnostic tools such as Wireshark, Little Snitch, or macOS nettop. You will observe that the application makes zero outbound connections during your writing, editing, and PDF exporting workflows.