Privacy Policy

This policy applies to the LinkSense LinkedIn Connector Chrome extension (the “Extension”) and the LinkSense web application and API at linksense.devproduct.site (the “Service”). They are operated by Agenticsense (“LinkSense,” “we,” “us,” or “our”). Contact us at info@agenticsense.co.

For account, security, and Service-operation data, Agenticsense determines how information is processed. For prospect, LinkedIn-member, and customer-uploaded data processed on a workspace’s instructions, the organization controlling that workspace is generally the data controller/business and Agenticsense acts as its processor/service provider. Workspace customers are responsible for their instructions, permissions, notices, and lawful basis.

LinkSense is independent and is not affiliated with, endorsed by, or sponsored by LinkedIn Corporation. “LinkedIn” is a trademark of its owner.

The Extension’s single purpose is to connect a user’s LinkSense workspace to that user’s own LinkedIn browser session so user-configured outreach, inbox, discovery, and engagement tasks can be performed in the browser and their results can be shown and managed in LinkSense.

After you pair the Extension and turn the agent on, it periodically authenticates to the Service, requests at most the queued work made available to it, runs that work on linkedin.com, and reports the result. Depending on your workspace settings and review mode, actions such as connection requests, reactions, comments, or messages may require human approval or may run automatically. Turning the agent off stops periodic task execution.

The Extension contains its executable code in the installed package. It does not download or execute remote JavaScript or WebAssembly. The Service sends task data and request descriptors, not executable code, and the Extension rejects non-LinkedIn task URLs.

3.1 LinkSense account and pairing data

The Extension stores the Service URL, a LinkSense extension bearer token, an HMAC report-signing secret, the paired account email, the agent and optional-capture settings, daily counters, timestamps, backoff state, and recent routing diagnostics in chrome.storage.local. Pairing codes are short-lived, single-use credentials. A new successful pairing revokes prior active Extension tokens for that user.

If you choose “Link from dashboard,” the Extension reads the LinkSense sign-in token and cached user record from the active LinkSense dashboard tab’s local storage after your click. If you use pairing-code setup, the dashboard sends the pairing code to the Extension instead. Tokens and signatures are sent to the Service only to authenticate requests and reports.

3.2 LinkedIn authentication information

• The Extension checks whether the LinkedIn login cookie named li_at exists. The Service receives only a connected/not-connected indicator, not the cookie value.
• It reads JSESSIONID locally and uses its value as LinkedIn’s CSRF request header. That value is sent only back to LinkedIn as part of a LinkedIn request.
• Your browser may attach LinkedIn cookies directly to requests made to LinkedIn. The Extension does not include those cookie values in reports to LinkSense.
• We do not collect your LinkedIn password, password for another service, or one-time authentication code.

3.3 LinkedIn and outreach data sent to the Service

According to the features and tasks you enable, reported results may contain:

• Account identity: the connected LinkedIn member ID/URN, name, profile URL, headline, location, biography/about text, and connection count.
• Profiles and connections: names, identifiers, profile URLs, headlines, roles, employers, locations, and other LinkedIn profile fields returned for people discovered or selected by the workspace.
• Search and discovery: search keywords, search-result identifiers and profile URLs, and result-page content when optional capture is enabled.
• Posts and engagement: post identifiers and text, reactions, comments, timestamps, and whether an instructed reaction or comment succeeded.
• Connections and messages: invitations and notes, conversation identifiers, participants, message content, timestamps, delivery outcomes, and replies.
• Notification state: previous and new LinkedIn messaging-badge counts and related timestamps so LinkSense can check for replies promptly.
• Task records: queued action identifiers, result status, HTTP status, routing method, errors, and limited operational metadata.

LinkedIn response bodies needed for a task are returned to the Service for parsing and workflow updates. They may contain more fields than the final normalized lead record. We use them only for the disclosed LinkSense workflow, security, and reliability purposes.

3.4 Optional people-search page capture

Discovery capture is off by default. If you explicitly enable it, the Extension detects navigation to LinkedIn people-search result pages and sends the page HTML to the Service to extract lead identifiers and profile details. A large embedded data block is removed before transmission. Turning the setting off stops future page captures; it does not automatically delete data already added to the workspace.

3.5 Technical and usage data

Status calls may include task counts, agent state, session-present status, routing method, queue state, and timestamps. Our servers and network providers also process standard request metadata such as IP address, user agent, requested endpoint, response status, and timing for security, rate limiting, troubleshooting, and service reliability.

3.6 What the Extension does not collect

• LinkedIn passwords, other account passwords, or one-time authentication codes.
• LinkedIn cookie values on LinkSense servers.
• Your general browsing history or content from unrelated websites.
• Payment-card or banking details through the Extension.
• Data for advertising, data-broker resale, lending, or creditworthiness decisions.

We process the information described above to:

• pair and authenticate the Extension with the correct LinkSense account;
• confirm whether the user’s LinkedIn session is available;
• perform the tasks and workflows enabled by the user or workspace administrator;
• store leads, conversations, task outcomes, activity, and scheduling context in the correct workspace;
• qualify and prioritize leads, prepare or send configured outreach, detect replies, and update pipeline status;
• provide dashboards, auditability, usage controls, support, security, rate limiting, diagnostics, and reliability;
• comply with legal obligations and enforce applicable agreements.

Where data-protection law requires a legal basis, we generally rely on performance of our contract with the account holder, the user’s requested action or consent for optional features and integrations, our legitimate interests in operating and securing the Service, and compliance with law. A workspace customer must determine the legal basis for its outreach and its processing of LinkedIn-member data.

We do not sell personal data. We do not “share” personal data for cross-context behavioural advertising, and we do not use Extension data for personalized, retargeted, or interest-based advertising.

A workspace administrator can configure an AI provider and models. For enabled features, LinkSense may send that provider the minimum context reasonably needed for the selected task, such as lead profile fields, post text, conversation history, the workspace’s messaging instructions, or an uploaded knowledge-base excerpt. Uses include lead qualification, classification, summarization, structured extraction, embeddings, and drafting comments or messages.

Lead qualification may automatically assign a score, recommendation, status, or queue priority. Generated outreach may wait for review or may be executed automatically depending on workspace configuration and the action type. These features are designed for business outreach workflow decisions, not decisions that produce legal or similarly significant effects about a person. Users can change criteria, review available activity and results, pause the agent or a lead, and request correction or deletion.

Agenticsense does not use customer or Extension data to train an Agenticsense general-purpose AI model. The external provider’s retention and model-training treatment depends on the provider, account type, region, and terms selected by the workspace administrator. Workspace administrators should review the chosen provider’s privacy terms and configure an appropriate business/API plan; we do not promise that every selectable third-party provider has identical retention terms.

We disclose data only as necessary to provide or secure the Service, follow the workspace’s instructions, comply with law, or complete a transaction permitted by the Chrome Web Store User Data Policy. The principal recipients are:

We may disclose information to professional advisers, regulators, courts, law enforcement, or other parties when reasonably necessary to comply with law, respond to valid process, investigate abuse, or protect rights and safety. In a merger, acquisition, financing, reorganization, or sale of assets, data may be transferred subject to applicable law; where the Chrome Web Store Limited Use rules require it, we will obtain explicit prior user consent.

We do not transfer Extension user data to advertising platforms, data brokers, information resellers, or lenders.

We use Extension user data only to provide or improve the Extension’s disclosed single purpose and related security, support, and reliability functions. We do not permit a person to read personal or sensitive Extension data unless the user gives explicit consent for specific support, access is necessary for security or abuse investigation, access is required by law, or the data is aggregated and anonymized for lawful internal operations. Access is limited to personnel who need it and is subject to confidentiality and security controls.

The current Extension requests the following permissions:

Chrome may display its own installation warnings based on these permissions. The Extension’s code and Chrome Web Store privacy disclosures should be read together with this policy.

On your device

Extension settings and credentials remain in Chrome local extension storage until you use “Clear stored data,” uninstall the Extension, Chrome removes its storage, or the data is replaced. Server-issued Extension tokens expire after 90 days. Successfully pairing again revokes the user’s older active Extension tokens.

On the Service

Account and workspace records are retained while the Service is active and as needed for the purposes in this policy. The production Service currently applies the following automated housekeeping windows: processed event/outbox records generally 30 days; completed or failed action records 60 days; activity, audit, and LinkedIn-call records 90 days; stage-transition history 180 days; and stored conversation/DM history 365 days. Knowledge-base history keeps the 50 newest versions per section. Operational safeguards, active processing, legal holds, disputes, security incidents, and backup cycles may delay deletion.

A workspace can also enable a configurable lead-retention policy for selected pipeline stages. It is off by default. When enabled, eligible leads and their dependent records are erased after the configured inactivity period, while a limited erasure/compliance record may remain.

Authorized users can erase an individual lead through the Service. To request account/workspace closure, access, export, correction, or deletion, email info@agenticsense.co from the account address. After verification, we delete or de-identify data that we are not required or permitted to retain. Where residual copies exist in backups, they are isolated from normal use and removed through the backup lifecycle.

• Keep the agent off until you want browser-based tasks to run; turn it off to stop periodic task execution and status heartbeats.
• Keep discovery capture off—it is off by default—or turn it off later to stop future people-search page captures.
• Use “Clear stored data” or uninstall the Extension to remove its local copy of settings and credentials.
• Pair again to revoke the user’s older active Extension tokens, or contact us to request revocation.
• Log out of LinkedIn to make LinkedIn-session tasks unavailable to the Extension.
• Pause the workspace agent or an individual lead, adjust automation and review settings, or remove queued work in the LinkSense dashboard.
• Disconnect optional calendar, meeting, email, or AI integrations in the relevant settings and provider account.

Removing the Extension stops browser access but does not by itself delete data already reported to the Service. Use the Service’s deletion controls or contact us for server-side deletion.

Production communication with the Service uses HTTPS. Extension API requests use a user-specific bearer token; action-result reports also use a per-pairing HMAC signing secret and action lease. Pairing codes are single-use, expire after ten minutes, and are stored server-side only as hashes. AI-provider keys and supported OAuth tokens are encrypted before database storage. The Service applies workspace access controls, rate limits, audit records, and restricted task origins.

No method of electronic transmission, browser storage, or server storage is perfectly secure. You are responsible for securing your browser profile, LinkSense credentials, LinkedIn account, devices, and workspace access. Please report a suspected privacy or security issue to info@agenticsense.co.

We and the providers selected for a workspace may process data in countries other than the country where a user or LinkedIn member lives. Where required, the responsible party uses an applicable transfer mechanism and contractual safeguards.

Depending on your location and our role, you may have rights to access, correct, delete, or obtain a portable copy of personal data; restrict or object to processing; withdraw consent; opt out of a sale or targeted-advertising share; or complain to a data-protection authority. LinkSense does not sell personal data or share it for targeted advertising. We may need to verify your identity and, for workspace-controlled data, forward the request to or coordinate with the workspace customer.

To exercise a right, email info@agenticsense.co with “Privacy Request” in the subject. You may also request human review of an automated qualification result. We will not discriminate against you for exercising an applicable privacy right.

Children

The Extension and Service are business tools not directed to children under 16, and we do not knowingly collect personal data from children through them. Contact us if you believe a child has provided data directly to LinkSense.

Your responsibilities and third-party terms

The Extension acts through your LinkedIn account at your direction. You and your organization are responsible for complying with applicable privacy, electronic-marketing, employment, anti-spam, and platform rules, including LinkedIn’s terms. This policy does not authorize conduct prohibited by LinkedIn or by law.

Changes to this policy

We may update this policy as the Extension, Service, providers, laws, or Chrome Web Store rules change. We will post the revised policy here and change the effective date. If a change materially expands Extension data collection or use, we will provide a prominent in-product or listing disclosure and obtain consent where required before applying the new practice.