How CV Maker handles your personal data

Resumes, folders, drafts, applications, and uploaded photos are stored locally using IndexedDB. There is no CV Maker account and no application backend that receives this information. Clearing site data can permanently remove it, so export important resumes as JSON backups.

AI features remain off until you choose a provider and supply your own API key. When you request a rewrite or generation, the relevant resume or cover-letter text and, when applicable, the job description are sent directly from your browser to that provider. This can be OpenAI, Anthropic, Google, Groq, or a custom OpenAI-compatible endpoint you configure. The request does not pass through a CV Maker server. The provider's own privacy and data retention terms apply.

By default the provider, model, endpoint, and API key are kept in sessionStorage and disappear when the browser session ends. You can explicitly choose to remember them on the device, which stores them in localStorage. Browser storage cannot make a key truly secret: use restricted keys, review usage, and rotate them when no longer needed.

• The ATS keyword check runs locally and does not use an AI service.
• PDF output is generated inside your browser; CV Maker does not generate it remotely and your CV is never sent anywhere to be rendered.
• JSON import and export happen locally in the browser.
• The application contains no advertising, analytics, or telemetry integration.

Local-first storage does not automatically follow you to another browser or device. Before clearing browser data, replacing a device, or switching browsers, export important resumes as JSON backups. You can import those files later without sending them to a CV Maker server.

You can export individual resumes as JSON, delete resumes and folders from the dashboard, and delete all local application data from Document settings. Browser settings can also clear stored site data. Because there is no server copy, deleted local data cannot be recovered by CV Maker.