Browser Extension Privacy Policy

Who this covers

This policy describes the Silverpath Connections Chrome extension (the “Extension”), used by licensed insurance agents of Silverpath and affiliated agencies. It is separate from the Silverpath website privacy policy and describes only what the Extension itself does.

What the Extension accesses, and why

The Extension exists to let an agent’s own, already-authenticated third-party sessions do work the agent would otherwise do by hand. Everything it reads belongs to the signed-in agent, and everything it sends goes only to that agent’s own agency workspace on Silverpath. Specifically:

• Your IntegrityCONNECT session token (connect.integrity.com) — read when you click Connect, and refreshed on a schedule while the connection is active so it does not lapse, so you can import the clients that are already in your own IntegrityCONNECT book.
• Your MedicareApp session token (your MedicareApp tenant address) — read when you click Connect, and refreshed on a schedule while the connection is active, so your own MedicareApp clients import with the Medicare details that system holds.
• Your MedicarePRO session cookie (medicareproapp.com) — read when you click Connect, and refreshed on a schedule while the connection is active, so your own MedicarePRO client records import into Silverpath.
• Your ManhattanLife session cookie (direct.manhattanlife.com) — read when you click Connect, and refreshed on a schedule while the connection is active, so the ancillary products you are appointed for — hospital indemnity, dental-vision-hearing, cancer, accident and short-term care — can be quoted inside Silverpath beside the plan you are already selling.
• Your Ethos session cookie (agents.ethoslife.com, partners.ethoslife.com) — read when you click Connect, and refreshed on a schedule while the connection is active, so the life products you are appointed for — term life and final expense — can be quoted inside Silverpath beside the plan you are already selling. Ethos requires this session for every quote, so the Extension refreshes it more often than the other carrier connections.
• Your Bankers Fidelity session cookie (agent.bflic.com) — only if you choose to connect it: Chrome asks your permission for this site the first time you click Connect, and the Extension cannot see it before then. Once allowed, it is read when you click Connect and presented again on a schedule while you remain signed in, so your own pending-application requirements and in-force policy reports appear inside Silverpath. It quotes nothing and submits nothing to Bankers Fidelity.
• Silverpath Enrollment Center helper — the optional side panel reads client details from your authenticated Silverpath workspace so you can copy them beside a carrier e-app. Application progress, Integrity evidence checks, and enrollment writes live in Enrollment Center. The panel does not read a carrier page, fill a carrier form, or submit an application. Older installed versions may continue to use the compatibility route for application status and draft-confirmation writes until they update.
• Older Extension versions could read a legacy rate-portal cookie (insurancetoolsportal.com) and send it to your Silverpath workspace. Source version 2.8.2 removes that host access and no longer sends those session updates. The server route remains temporarily for older installed versions; previously stored credentials remain encrypted and can be disconnected from your profile.
• Carrier-portal downloads (humana.com, and UnitedHealthcare’s Jarvis at uhcjarvis.com) — the Extension notices when you download a report from one of these portals and offers to file it. It never sends a file on its own. When you click File it, it fetches that file again with your own sign-in; for uhcjarvis.com Chrome first asks your permission, and the Extension cannot fetch from that site before you allow it. If the file can’t be fetched again (the portal built it in the page, or you declined), the Extension opens Silverpath’s upload page and asks you to choose the file yourself.
• Its own settings and a queue of captured files awaiting your confirmation — stored locally in the browser.

Where your data goes

Data the Extension reads is sent only to your own agency’s Silverpath workspace, over an authenticated same-origin request — the same place you are already logged in. Session credentials are transmitted directly from the extension’s background worker to your Silverpath workspace and are stored there encrypted, per agent.

What the Extension never does

• It never sells, rents, or shares your data with any third party.
• It never sends data to any destination other than your own Silverpath workspace.
• It contains no advertising, no analytics, and no cross-site tracking.
• It does not read the contents of your web requests. Under Manifest V3 it cannot access request or response bodies at all; where it observes carrier-portal endpoints it records only URL paths with query values stripped.
• It requests no access to arbitrary sites — there is no broad-host permission.

Data retention

Session credentials stored in your Silverpath workspace are retained only as long as needed to keep the connection working and expire on their own; you can disconnect any connection at any time from your Silverpath profile. The Extension’s local settings and capture queue live in your browser and are removed if you uninstall the Extension.

Contact

Questions about the Extension or this policy can be directed to your Silverpath agency administrator.