Privacy Policy (Zero Database)

Our Core Privacy Commitment

Most online resume builders treat candidate data as a commodity: they store your name, phone number, salary history, and career details in remote databases, and some sell aggregated resumes to recruiters or data brokers.

CVMake was founded on the fundamental principle that your career history belongs to you alone. We designed our entire platform from day one to operate with zero persistent application database.

1. How the Browser-Based System Works

When you enter your details into CVMake, the data is held in in-memory React state on your local device. If you enable autosave, it is synchronized to your local browser storage (window.localStorage).

No Remote Database: We do not run PostgreSQL, MongoDB, Firebase, Supabase, Redis, or any server-side database storing user resumes.

No Mandatory Accounts: You are not forced to register an email, create a password, or authenticate with Google or Facebook.

Client-Side PDF Generation: Resumes and cover letters are rendered using client-side vector print formatting. No documents are uploaded to third-party PDF rendering microservices.

2. Data We Do NOT Permanently Store

Our servers never permanently store or record:

❌ Full Name

❌ Email Address

❌ Phone Number

❌ Home Address / Location

❌ Employment History

❌ Education Records

❌ Generated Cover Letters

❌ Uploaded Documents

❌ Recruiter Search Logs

3. How AI Features Operate

The majority of AI features in CVMake (including action verb scoring, Google XYZ bullet formulation, ATS diagnostics, and skill recommendations) run completely offline inside your browser using deterministic algorithms.

When optional serverless AI completion endpoints are invoked to rewrite text, requests are processed statelessly in memory with zero logging of candidate resume content. We never train public AI models on your submitted text.

4. Cookie & Client-Side Storage Policy

CVMake complies fully with GDPR, the EU ePrivacy Directive, and California privacy standards through a simple approach: we do not use non-essential or tracking cookies.

Summary of Client-Side Storage:

cvmake_resume_draft_v1: Essential local storage key used strictly to preserve your in-progress resume text across page reloads. Kept only on your device.
cvmake_cover_letter_draft_v1: Essential local storage key used to preserve your drafted cover letter on your device.
cvmake_cookie_consent_v1: Remembers your acknowledgment of this notice so you aren’t shown redundant prompts.

Because we use zero tracking, marketing, or behavioral profiling cookies, you will never see intrusive third-party cookie walls or pay-for-privacy mechanisms on CVMake.

5. Privacy-First Analytics & No Advertising Trackers

We use Google Analytics 4 (GA4) with IP anonymization to monitor aggregate website traffic, popular template usage, and Core Web Vitals performance. We do not transmit your resume text, work experience, personal contact details, or documents to Google Analytics or any third party.

We do not install invasive session replay tools (such as Hotjar or FullStory), ad remarketing pixels (Meta Pixel, Google Ads), or data broker SDKs. We do not sell, rent, or monetize your resume data under any circumstance.

6. How to Clear Locally Stored Data

Because your resume drafts reside in your browser’s local storage, you have total control over them at all times. You can delete your saved resume with one click inside the builder toolbar, or by clearing your browser cache and cookies for cvmake.dev.

Open Builder to Manage Local Data →