Last updated 29 August 2026

Privacy at EntOS.

This policy explains how EntOS handles information across the EntOS service, including workspace collaboration, relationship intelligence, enrichment, introduction workflows, and the EntOS browser extension.

Information you and your workspace provide

• Account and profile information such as your name, email address, authentication identifiers, preferences, and workspace membership.
• Workspace information, including the operating company, workspace address book, company network, target accounts, target contacts, notes, ownership, and assignments.
• Introduction workflow information such as desired asks, enablement packs, messages, selected introduction paths, introducers, activation history, and outcomes.

Relationship and enrichment information

EntOS builds a relationship graph of people, companies, employment roles, and sourced relationships. This information may come from workspace members, authorised integrations, the browser extension, enrichment providers, public professional and company sources, or information supplied directly to EntOS. We retain source and provenance information so observations can be evaluated, reconciled, and audited.

Browser extension

The extension has one purpose: to help account executives work with EntOS while browsing LinkedIn by securely syncing the professional profile, company, search, and connection data needed to maintain relationship intelligence and find warm introduction paths to target accounts. It handles:

• LinkedIn profile, connection, company, and people-search information visible to the signed-in LinkedIn account, together with relevant LinkedIn URLs and capture times.
• EntOS and LinkedIn account identifiers needed to connect a capture to the correct EntOS user and workspace. For supported same-origin LinkedIn requests, the extension uses the LinkedIn session cookie and CSRF token already present in the browser. LinkedIn passwords, session cookies, and CSRF tokens are never sent to EntOS.
• For each supported workflow, a bounded, sanitised, route-scoped representation of the page's main professional content and relevant responses from LinkedIn's same-origin APIs. Scripts, forms, styles, event handlers, embedded documents, credentials, and off-origin links are excluded from the page representation.
• Extension settings, sync state, build version, and limited operational diagnostics.

Optional LinkedIn data exports

If you choose to upload a LinkedIn member data export through the extension, EntOS uses selected information to bootstrap and improve your relationship graph. This can include connections and connection dates; endorsement and recommendation direction and dates; message counterparties, direction, and timestamps; email addresses supplied in the export; and references to your reactions (including likes) and comments.

Personal-communications metadata is used narrowly: message counterparties, direction, and timestamps, plus recommendation direction and dates, are used only to derive relationship evidence. EntOS does not retain message subjects or bodies, recommendation text, or comment text. For reactions and comments, EntOS retains only the LinkedIn activity URL, timestamp, interaction type, reaction type where available, and import provenance. These references are currently held as pending work for future relationship analysis and do not yet affect relationship rankings.

The uploaded ZIP and raw CSV contents are transient processing inputs and are not written to durable storage. They are discarded as soon as processing finishes. Derived relationships, identifiers, the sanitised import audit summary, and pending interaction references remain subject to the retention and deletion terms below. You may instead upload selected CSV files, or remove files and rows from an export before uploading it.

Technical and usage information

We handle device, browser, request, feature-usage, performance, error, and security information needed to operate EntOS reliably, diagnose problems, protect accounts, and understand how the product is used. EntOS authentication and essential product features may also use cookies or similar local storage.

How we use information

We use information to provide and improve EntOS: to authenticate EntOS users; operate workspaces; resolve people and companies; build the workspace address book and company network; enrich sourced records; find and rank introduction paths; prepare enablement packs; record activated path outcomes; support collaboration; provide support; monitor reliability; prevent abuse; and meet legal obligations. We do not sell personal or extension data or use it for personalised advertising.

When information is shared

Workspace-owned information is available to EntOS users according to workspace membership and product permissions. Information included in an introduction or intelligence request may be shared by a workspace member with the selected introducer or recipient as part of that workflow. We may use contracted hosting, database, authentication, enrichment, research, observability, and security providers to operate EntOS. Those providers may process information only to deliver their services to us. We may also disclose information where required by law, to protect EntOS and its users, or as part of a corporate transaction subject to appropriate safeguards.

Storage, security, and retention

We use access controls and technical and organisational safeguards appropriate to the information we handle. Data sent to EntOS is transmitted over HTTPS. The extension stores configuration, connection state, and a short local activity history in Chrome storage. We retain workspace, relationship, workflow, and operational data while needed to provide the service and for legitimate security, provenance, audit, and legal obligations. Pending LinkedIn interaction references are retained until they are processed or deleted under an applicable data request. We then delete or de-identify retained information in line with the workspace relationship and applicable law.

Your choices

Workspace owners and EntOS users may request access, correction, export, or deletion where applicable. You can stop browser collection by disabling or uninstalling the extension. Some information may need to be retained for security, provenance, audit, or legal reasons. Reach out to your EntOS account manager or visit the EntOS support page for help with an account or data request.

Changes

We may update this policy as EntOS evolves. If extension data practices change, we will update this policy and prominently disclose the change before the new collection or use begins where required.