Permissions - Introd

Browser permissions

Permission	Current use
storage	Stores extension auth state, settings, sync checkpoints, status, and browser-local caches
alarms	Runs signal sync, cache cleanup, session heartbeat, automatic connection-import resume, and queued profile-image work
tabs	Checks LinkedIn pages, opens sign-in pages, and creates or reuses an inactive connections tab for import
scripting	Runs page-aware identity capture and path-context logic on permitted LinkedIn surfaces

Host access

Host	Current use
`https://www.linkedin.com/*`	Detects the LinkedIn session; processes connections; and inspects visible identity containers on profiles, feeds, comments, messaging surfaces, hover cards, organization people pages, events, discovery results, and lists
`https://linkedin.com/*`	Covers LinkedIn host variations
`media.licdn.com` over HTTPS (all paths)	Retrieves LinkedIn-hosted profile images used during supported profile processing
`https://getintrod.ai/*`	Handles Introd pages used by sign-in and extension bridging
`https://.getintrod.ai/`	Handles the Introd app and API subdomains used by the extension

The manifest also permits Introd website and app pages to connect to the extension for supported bridge behavior.

What Chrome permission does not mean

Host access allows the content script to run on a matching page. It does not mean every field on that site is imported, but it does allow the script to inspect rendered page content. With the default capture settings on, derived identity and relationship fields can be recorded locally and submitted to Introd for enrichment when authenticated.

Current selectors include LinkedIn messaging containers, and relationship parsing can fall back to their rendered text. Pausing a connection sync does not stop this page processing. Disable the extension in Chrome before opening a sensitive page if you do not want its code to run there.

Review before approving

Confirm the extension name is Introd for LinkedIn.

Confirm the version matches the build information supplied by Introd.

Compare Chrome’s permission prompt with this page.

Stop and contact [email protected] if the build asks for access outside these hosts or permissions.

See Integration Data Usage for the fields used after permission is granted.

​Browser permissions

​Host access

​Permissions not requested

​What Chrome permission does not mean

​Review before approving

Browser permissions

Host access

Permissions not requested

What Chrome permission does not mean

Review before approving