Scout extension privacy policy
Version 1.2 · last updated 27 October 2026
Who this is for
The Scout extension is used by recruiters at firms that use Scout. It is not a consumer product and there is nothing in it for someone without an account.
What it reads
Only LinkedIn pages, and only for work the recruiter started: a run (the search results pages it opens, and the profiles it was asked to collect), a profile they chose to add from the popup, or a message run (the message window of each person it was asked to write to, and the recruiter’s own list of newest connections, to find who has just connected). It reads the page the same way a screen reader does: the accessibility tree and the visible text.
It does not read any other site. It has no access to any other tab, to browsing history, to bookmarks, or to anything the recruiter types outside Scout. It sends a message only in a message run the recruiter started, only to the people on that run’s list, and only the text written from the recruiter’s template for that run.
The text of the profile pages you add from the popup is sent to Scout and turned into the candidate’s record. The page text is deleted when that is done, and also when the read ends without a record (it was incomplete, it failed, or it was cancelled). Scout keeps the record, not the page text.
In a message run, a person’s message window is read only to check whether the conversation already has text in it. The text of a conversation stays in the browser; Scout is told whether it was empty and whether a message went.
Where it goes
To the recruiter’s own Scout workspace, over their signed-in session, and nowhere else. Profiles arrive as candidates on the role the session belongs to. They are the same records the recruiter would create by pasting the same profiles in themselves.
The extension has no server of its own, no analytics, and no third-party services. It talks to LinkedIn, from the recruiter’s browser, and to their Scout workspace. Scout’s own servers never contact LinkedIn.
What is kept
- The profiles the run reported (name, headline, location, public profile URL, experience and skills as the profile shows them), stored as candidates on that role.
- A log of the run: which step it was on, which page it was looking at, what it did and what came back. The contents of the pages are not kept; an entry records the URL, the page title, any warning LinkedIn showed, and the first part of what was there.
- Counters for the run (profiles collected, connection requests sent, tokens used), so the recruiter can see what it did.
- Messages a run sent: the text, who it went to and when.
Locally, in the browser, the extension keeps only what it needs to carry on after a restart: which run is going, which tab it is on, and a short log of recent actions, which are cleared when the run ends. For profiles you add from the popup it also keeps the read that is waiting (its address and first name), whether reading is paused, the name and the progress of the last person you added, and the last roles you picked. The read and the last add go when the read ends; the roles go when you remove the extension.
What is never done with it
Nothing collected is sold, rented, or shared with anyone outside the recruiter’s own workspace. It is not used to train models, not combined with data from other firms, and not passed to any advertising or analytics service.
Who can see it
The recruiter and the teammates in their Scout organisation who have access to candidates. Members limited to their own candidates see only the people assigned to them. Nobody at another firm can see any of it; access is enforced by the database rather than by the application.
Deleting it
An owner can delete a closed role, and that deletes its sessions, runs and candidates with it, CV files included. Deleting a run can also remove the candidates it found that nobody has moved past Reviewed, if the recruiter chooses that. An owner can also find one person and erase everything held about them, in Organisation, Data and privacy. Removing the extension stops any run immediately and clears everything it kept in the browser.
Permissions, and why
- Access to www.linkedin.com: to read the pages of a run, in the recruiter’s own signed-in session.
- Access to the Scout application: to ask what to do next and to report what was found.
- Debugger: to observe the page and to click and type as a person does, in the tab a run is using or in the one background tab Scout opens to read a profile you added. The browser shows a bar for as long as this is in use, and dismissing it stops the run or the read.
- Tab groups: to keep the background tab that reads a profile in a collapsed group named Scout, and to mark the tab a run is using with a group of its own.
- Scripting, storage, alarms: to read the name and headline of the profile you choose to add, and to show Scout’s progress on it, to remember the run’s state across a browser restart, and to notice when it has been quiet too long.
Changes to this policy
If what the extension reads, keeps or does changes, this page changes with it and the version number above moves. There is no separate notice beyond that. This page is the record.
Contact
Questions about this policy, or about data collected through the extension: contact@scoutnext.io.