Privacy Policy

Last updated 7 August 2026

linkedinto.cv turns a LinkedIn profile into a PDF CV. The extension does that entirely on your computer: there is no server to send your data to, no account to create, and nothing about your profile is ever transmitted. This website, separately, measures its own traffic. That is described below.

What the extension reads

When you press Extract from LinkedIn Page, the extension reads the LinkedIn profile page you already have open and, if you ask it to complete a section, that section's /details/ page. It reads the text that is visible to you: name, headline, location, roles, education, skills, certifications, languages, projects, courses and awards.

If you import a LinkedIn “Save to PDF” export instead, it reads that file from your computer. The file is parsed in the browser and never uploaded.

The extension never modifies the LinkedIn page and never writes to your profile.

The profile does not have to be yours. Recruiters and hiring managers use this to turn a candidate's profile into a CV, and the extension makes no distinction: it reads whichever profile you have open. Everything above applies unchanged to that person's details. They stay on your machine, they are never sent to us, and there is no server that could receive them. If you build a CV from someone else's profile, what you then do with that file is yours to answer for, and the law where you work may have something to say about it.

Completing a section opens that section's own LinkedIn page in a tab, reads it and closes it again, putting you back where you were. Those tabs open in front of you rather than in the background, so nothing is ever read out of your sight.

What is stored, and where

Everything below lives in your browser's own extension storage. None of it is sent to us, and there is nowhere for us to send it to.

On this device only. Anything with your profile in it:

• Profiles you save. Only when you press “Save profile”. Stored so you can return to a CV without extracting again. Up to 25 are kept; the oldest are dropped.
• Your settings. Which template you chose, its colours and typeface, and which entries and sections you ticked in or out.
• Diagnostics. A local record of what each extraction did, kept so a failure can be explained. It records lengths and counts, not profile text, unless you explicitly switch on “Include profile text”. If you do, the report says so at the top before you share it.

Carried between your own Chrome profiles. Three small values are written to Chrome's synced extension storage, so that buying credits on one computer does not mean re-entering the key on the next:

• Your key and its last known balance, if you have bought credits. The balance that counts is the one held at Stripe.
• Your download count. A number, used to enforce the single free download.

Chrome moves those between your devices through your own Google account if you have Chrome sync switched on, exactly as it does your bookmarks. That is Chrome's mechanism and Google's, not ours, and we cannot read it. Nothing from your profile is ever put there.

What leaves your computer

Your key, and only if you have bought credits. It is sent to www.linkedinto.cv/api/spend to read your balance and to deduct one when a CV is produced, and to www.linkedinto.cv/api/portal if you press Invoices and receipts, which returns a link to your billing page at Stripe. Both requests contain the key and nothing else. No profile data, no identifiers, no information about the CV you made.

The balance is held against your customer record at Stripe, who process the payment. We keep no database of our own.

If you never buy credits, the extension makes no network requests at all.

What those two requests leave behind. Like any server, they write an operational log line: the time, which endpoint, whether it succeeded, how long Stripe took, and your Stripe customer identifier, so that if you write in saying a credit did not work we can find the request instead of guessing. Your key is never written to a log, in whole or in part. Nothing about your profile or your CV can appear there, because none of it is ever sent. These logs are kept for 30 days and then deleted.

Send feedback, in the account menu, is a link rather than a form: it opens your own mail client with the extension's version number filled in, and sends nothing by itself. Whatever you choose to write, and anything you choose to paste in, is what we receive.

Your profile data is never transmitted anywhere. Not to us, not to Stripe, not to anyone. We could not read it if we wanted to, because there is no server that receives it.

What we do not do

• We do not sell or share your data with third parties.
• We do not use it for anything unrelated to producing your CV.
• We do not use it to determine creditworthiness or for lending.
• We do not run any analytics, telemetry or advertising inside the extension. It reports nothing, ever.
• We do not use advertising cookies, and we do not sell or share anything with ad networks.

This website

linkedinto.cv, the site you are reading, uses Umami to count visits. We host it ourselves at analytics.neuklick.com, so the data is not passed to a third-party advertising company. It records the usual page-level facts: which page was viewed, the referrer that sent you, and a coarse device, browser and country. It does not use tracking cookies and does not follow you to other sites.

We also run Umami's session recorder on this site, which replays how a visitor moved through the page so we can see where the layout confuses people. It captures clicks and scrolling. There is nothing to type on this site, and no sign-in, so there are no credentials or personal details for it to capture.

None of this applies to the extension. The extension loads no remote scripts of any kind, which is both a promise and a requirement of the Chrome Web Store. Nothing you extract, edit or download is measured, and the analytics above cannot see any of it. To opt out of the site analytics entirely, any content blocker or a browser "do not track" setting will stop it.

Deleting your data

Removing the extension from chrome://extensions deletes everything it stored. To clear saved profiles without uninstalling, delete them from the saved profiles menu in the side panel. Your licence can be released from the account panel with “Remove key from this browser”.

Permissions, and why each one exists

• storage: to keep the settings, saved profiles and licence described above on your machine.
• scripting: to run the extraction script in your LinkedIn tab when you press the button, once, on demand.
• sidePanel: the interface is a side panel, so nothing is drawn over LinkedIn.
• access to linkedin.com: to read the profile you are viewing.
• access to linkedinto.cv: to check and deduct credits, and to open your Stripe billing page, if you have bought any.

Children

The extension is not directed at children under 13 and collects nothing from them, as it collects nothing from anyone.

Changes

If this policy changes materially, the date above changes and the new version is published here before the change takes effect in a released version.

Contact

Questions about this policy, and feedback about the extension, both go to julian@linkedinto.cv. It is one person's mailbox, not a ticket queue.

linkedinto.cv is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. LinkedIn is a trademark of LinkedIn Corporation.