Privacy Policy

Without an account, your CV stays on your device

You can use write.cv without signing in. Then all of your content is stored locally in your browser (using local storage). It is not uploaded to, or saved on, our servers.

If you clear your browser data or use another device, your CV will not be there unless you exported a backup file yourself.

Optional account: Sign in with Google

Signing in is optional. If you sign in with Google, Google shares your name, email address, profile picture and a Google account ID with us. We store these only to identify your account. We never see your Google password and get no access to anything else in your Google account.

A cookie keeps you signed in for up to 30 days. It is used only for that.

Your CV in your account

While you are signed in, your CV is saved to our servers so you can open it on any device. Only you can access it while signed in.

When you sign out, the browser goes back to the CV it had before you signed in; your account's CV stays safe in your account.

Public CV pages (only if you publish)

Nothing is public unless you choose “Publish”. When you do, anyone with the link write.cv/@your-username can see your full CV — including any email, phone number or other contact details you put in it. Only publish what you are comfortable sharing.

Public pages are hidden from search engines unless you turn that on. You can unpublish at any time and the page disappears immediately, though people or services may have already kept a copy.

We are notified when a CV is published and may review public pages. Visitors can report a page; we review reports and may remove pages that break our Terms.

A public page can also be shown as a profile page, with the photo, cover image, links, social accounts, music, videos and portfolio you add. Images you upload are stored with your account (on Cloudflare) and deleted when you remove them or delete your account. If you haven't uploaded a photo, your Google account picture is used — you can turn that off in the profile settings.

Music and video on a profile come from YouTube, Vimeo, Spotify, SoundCloud or Apple Music. The player only loads when a visitor taps it; from then on that service may set its own cookies under its own privacy policy.

Deleting your account

You can delete your account at any time from the account menu. This permanently deletes your account details, your saved CV, your username and your public page, straight away. It cannot be undone.

Reports

If you report a public CV, we receive the page link, the reason, your note and your approximate country (from your connection). We don't store the report; it is emailed to us for review.

Cookies and analytics

Essential storage is always on, because the site can't work without it: the sign-in cookies that keep you logged in (only if you sign in), and your browser's local storage, which holds your CV and settings.

Only if you agree in the cookie banner, we also use Google Analytics (through Google Tag Manager) and PostHog (product analytics and session replay — see the next section) to understand how the site is used — pages visited, device and browser type, approximate location, and actions such as exporting a PDF — and Google Ads cookies to measure how our ads perform. Until you agree, these tools set no cookies and receive no identifiers, and PostHog isn't loaded at all. Your CV's content is never sent to them.

You can change or withdraw your choice at any time with the “Cookie settings” link in the site footer or the editor's menu.

Product analytics and session replay (PostHog)

Only if you allow analytics in the cookie banner, we use PostHog — a product analytics service run by PostHog, Inc., with data hosted in the United States — to understand how people use write.cv so we can improve it. Requests go through write.cv's own address and on to PostHog.

What it collects: the pages you visit; clicks and other interactions with the site's buttons and menus; your device, browser and screen size; your approximate location (country and city, worked out from your IP address); how you arrived (for example from a search engine or a link with campaign tags); and a random, anonymous ID kept in a cookie and in your browser's local storage. If you're signed in, this is linked to an internal account number — never to your name or email address.

Session replay: PostHog may also record how pages are used — mouse movements, clicks, scrolling and page layout — so we can find the parts that confuse people. Everything you type is always hidden. In the editor, on CV pages and in your account, all text is masked as well, photos in your CV are blocked, and the content of network requests is never recorded. Masking happens in your browser, before anything is sent.

Your CV's content — your name, contact details, experience, and anything you write to the AI assistant — is never recorded or sent to PostHog. The events we send ourselves contain only things like which template you picked, counts, and your ATS score.

Retention: session recordings are kept for up to 30 days and analytics events for up to 12 months, then deleted.

You can withdraw your consent at any time with “Cookie settings” in the site footer or the editor's menu. PostHog then stops straight away, and its cookies and stored data are removed from your browser.

Who else handles data

We do not sell, rent, or share personal data. To run the service we rely on: Cloudflare (hosting and storage of accounts and saved CVs), Google (sign-in, and — only with your consent — Analytics and Ads measurement), PostHog, Inc. (product analytics and session replay, hosted in the US — only with your consent), and Resend (delivering notification emails to us, and a one-time thank-you email to you when you publish a public page).

Usage counters

write.cv shows how many CVs have been created with it. This is a simple anonymous counter: each time a CV is exported to PDF, your browser sends a bare “+1” signal.

That signal contains no identifier, no personal information, and nothing from your CV. We store only the running total — nothing about you.

AI suggestions

If you use the optional AI feature, the specific text you choose to improve is sent to an AI provider solely to generate suggestions and return them to you. It is not used to identify you.

PDF export

Exporting your CV to PDF happens entirely in your browser using the browser's print engine. The file is generated on your device.

The write.cv Chrome extension

The extension only runs on a page when you open it there (Chrome's “activeTab” permission). It does not read, record or send the sites you visit, and it never submits a form for you.

What it stores, on your computer only: your CV (a copy of the one saved in your browser, or read from your account) an access token if you connect your account, and the CV PDF you add on My space → Autofill, which it attaches only to the upload field of a form you choose to fill. The PDF is never sent to write.cv. Disconnect any time from the extension or My space; revoke the token in Account → Connect AI agent.

What it sends, only when you press a button: “Fill this form” sends the form's questions (labels and choices, not what you typed), a short piece of the job text and your CV to write.cv, which asks our AI provider (Google Gemini) for answers. “Save job” sends the job's title, company, location and link to your Applications. These requests are used solely to produce the answers and return them to you; write.cv stores nothing from them except the job you save.

Questions about salary, visa, nationality, gender, disability, age, religion and agreements are never answered for you. The extension is not used for advertising, and its data is never sold or shared for any other purpose.

Contact

Questions about privacy, or a request about your data? Email support@write.cv.