Job seekers

How ApplyCandid Fills LinkedIn Easy Apply Without Storing Your Password

The first question most people ask before installing a job-application extension is a fair one: does this thing need my LinkedIn password? It's a reasonable worry — handing a browser extension your login credentials for a site where your professional identity lives is a real ask. The short answer for ApplyCandid is no, it never asks, and it never stores one. Here's what actually happens instead.

The extension doesn't log in — you already are

ApplyCandid is a browser extension, not a separate service that connects to LinkedIn on your behalf. When you click "Start Run" on a LinkedIn Easy Apply page, the extension's content script runs inside that tab, in the same authenticated session your browser already has open. It reads the Easy Apply modal's form fields the same way any other page script can read the DOM of the page it's injected into — it doesn't make a separate authenticated request to LinkedIn's servers, and it has no mechanism to.

That's a deliberate architectural choice, not an incidental one. There's no login form anywhere in the extension's UI, no field labeled "LinkedIn password," and no OAuth flow that hands the extension a long-lived access token to your account. If you're not logged into LinkedIn in that tab, the extension has nothing to act on — it can't log you in, because it was never built to.

What actually fills, and where it comes from

Once a run starts, fields split into two categories:

Notice what's missing from both lists: your LinkedIn credentials never appear in either path, because the extension was never handed them in the first place.

What's stored, and where

Your resume text lives in Chrome's local storage on your device and on the AI server you've connected. Your job preferences and AI server connection details live in Chrome's synced storage. Your application history stays local to your device and is never sent anywhere. None of that storage has a slot for a LinkedIn password, because none of the extension's logic needs one to function.

Why this matters beyond privacy

There's a practical safety benefit here too, not just a privacy one. An extension that stored your portal password would be a much bigger target if it were ever compromised, and would need its own separate authentication flow to LinkedIn — a flow LinkedIn would have every reason to treat as suspicious automated access. Acting inside a session you're already logged into, instead, means the extension inherits exactly the access you already granted yourself by logging in — nothing more.

That doesn't mean automated form-filling carries zero platform risk — LinkedIn can still restrict accounts for unattended, scripted-looking activity, and that risk is real regardless of how credentials are handled. Auto-Submit is off by default for exactly that reason, and even when you turn it on, it's capped per day to avoid a bursty pattern. You can read the fuller answer on that in the FAQ.

What you actually see happen

Click "Start Run," and the extension works through the Easy Apply modal: deterministic fields fill in almost instantly, AI-drafted fields take a moment longer while the draft comes back from the server, and then everything sits there for you to review. Nothing submits until you click Submit yourself — unless you've explicitly opted into Auto-Submit, and even then, the daily cap still applies. The whole point of not needing your password is that the extension never needed more access than "read and fill the form you're already looking at" in the first place.

Try it on your next Easy Apply.

Free to start. No portal passwords, no unattended submitting, no invented answers.