The RTS Recruiter Bridge is an internal tool built for the recruiters of
Roy Talman & Associates (“the firm”). It connects the LinkedIn profile a recruiter
has open to the firm’s own recruiting application (“RTS”), and pre-fills prepared
InMail drafts into the LinkedIn composer for the recruiter to review. This policy explains exactly
what the extension does and does not do with data.
The short version: The extension only acts when a recruiter clicks. It reads the
LinkedIn profile the recruiter deliberately has open and sends it to the firm’s own RTS
application. It never sends messages on its own, never stores data by itself, and never shares data
with any third party.
What the extension accesses
Only in response to a recruiter action, and only for the candidate the recruiter currently has open,
the extension may read:
Profile information visible on the open LinkedIn (Recruiter or public) profile —
name, headline/title, and work history.
Contact details — only if the recruiter opens the candidate’s
“Contact info” panel and captures it.
Message/InMail history with that candidate — only if the recruiter uses the
“capture messages” action.
The active tab’s identity — enough to detect that a LinkedIn candidate
profile is open and which candidate it is, so the right profile is captured.
How that information is used
It is transmitted only to the firm’s own RTS application — the production
instance at roytalman.ai, the firm’s hosted test instances on
*.up.railway.app, or a developer’s local machine during development — where it is
stored as a candidate record.
It is used to pre-fill InMail drafts into the LinkedIn composer for the recruiter
to review and send themselves.
What the extension does not do
It never sends any message, connection request, or InMail — every send is done by
the recruiter.
It stores no data of its own; captured information lives in the firm’s RTS
application, governed by the firm’s own data practices.
It does not sell or transfer data to third parties, and does not use data for
advertising, profiling for unrelated purposes, or to determine creditworthiness or lending.
Permissions, and why they are needed
tabs — to identify the LinkedIn tab the recruiter has open so the correct candidate is captured.
scripting — to read that LinkedIn profile page and to fill the message composer on it.
Host access to linkedin.com — the profile and composer pages being read and filled.
Host access to roytalman.ai, *.up.railway.app, and localhost
— the firm’s RTS application instances (production, hosted test, and developer machines) that receive the captured data.
The extension contains no remote code — all of its code ships inside the published package.
Data retention
The extension retains nothing after an action completes. Candidate records created in RTS are retained
and managed by Roy Talman & Associates under the firm’s internal data-retention practices.
Who can use it
The extension is distributed privately to Roy Talman & Associates staff and is not intended for the
general public.