← Back home

Privacy Policy

Last updated: November 11, 2026

Summary

It’s your personal LinkedIn account, so you stay in control of your data. The connections Outscore tracks are stored in your own browser and are never sold or shared with your employer. They leave your machine only when you choose, to a CSV file you download or to your own CRM that you connect. The extension sends us only anonymous, non-content usage data, plus the email address you use at checkout if you buy Outscore Pro, and anything you choose to type into the short form we show if you uninstall (including an email address, only if you want us to reply about it).

What the extension accesses

When you are logged into LinkedIn and trigger a sync, the extension reads publicly-visible information from three pages in your own LinkedIn account:

  • Sent invitations page (linkedin.com/mynetwork/invitation-manager/sent/): names, profile URLs, and the date you sent each connection request.
  • Connections page (linkedin.com/mynetwork/invite-connect/connections/): names, profile URLs, headlines, and the date each connection was made.
  • Received invitations page (linkedin.com/mynetwork/invitation-manager/received/): names, profile URLs, headlines, and the date of each person-to-person invitation you have received, plus your Accept or Ignore action when you take it. Invitations to follow companies, newsletters, pages, or other non-person entities are excluded; only person-to-person invitations are tracked.

The extension only reads data you can already see yourself when logged in. It does not read your posts, private details, or any data outside these pages. Messages are handled by the pipeline view described in Your messages below: conversation previews already on your screen, and conversations you explicitly choose to add. Nothing else.

Your messages: the pipeline view

When you save a conversation to Outscore, or browse LinkedIn messaging with Outscore installed, Outscore derives your outreach timeline for contacts you track: when you sent the first message, when they first replied, and the date and direction of the latest message. Outscore stores these timestamps and one short preview of the latest message per contact, on your device only. A full conversation is kept only when you click Save conversation on it (after a one-time consent), and then only on your device, so you can read it later in the dashboard; you can copy it, delete it with the person, or clear all saved conversations in Settings. This data appears in your dashboard and in exports you choose to create, and clearing Outscore’s data removes it. It is never sent to Outscore’s servers.

Two reads make this work, both limited to what is already on your screen: the list of conversation previews LinkedIn shows you (read passively; Outscore never opens a conversation), and the full text of a conversation you opened yourself and explicitly saved. Outscore never navigates to messaging on its own and never opens a thread in the background.

If you connect a CRM, saving a conversation can also copy its messages into your CRM as activities. The messages travel from your browser to your own CRM. They are never sent to us, never stored on our servers, and never shared with anyone else.

Where your data is stored

  • Locally, on your device. Your tracked connections are stored in your browser’s IndexedDB and chrome.storage.local.
  • Your tracked LinkedIn connection data is never sent to the developer’s servers. Names, companies, notes, and connection history stay on your device unless you choose to send them (see “When your data leaves your browser” below).
  • No tracking of your browsing. The extension reports home only an anonymous health ping and anonymous usage counts, both described below, and never your LinkedIn content.

When your data leaves your browser (only when you choose)

  • CSV export (Pro): clicking Export saves a CSV to your computer via Chrome’s download manager. It is not transmitted to us.
  • CRM sync (Pro): if you connect a CRM (HubSpot), you choose exactly which connections and fields to send, and those contacts are written directly from your browser to your own CRM account, not through our servers. If a connection you track shared contact details in their LinkedIn Contact info (email address, phone number, birthday, or the date you connected), Outscore can read them (they are visible to you because your connection chose to share them with you) and include them when you push that contact. They are never looked up or guessed from outside databases, and like every pushed field they travel only from your browser to your CRM, never to us. With HubSpot connected, Outscore can also check whether the person or company you are viewing on LinkedIn is already in your HubSpot, and show what your HubSpot says about them, such as their owner and lifecycle stage. When you click Edit, Outscore reads the record’s title, company, email, phone, mobile, city, state and country to fill the form, and Save writes only the fields you changed. That check also runs only between your browser and HubSpot, and you can turn it off in Settings. From version 3.0.0 you connect HubSpot with a service key you create in your own HubSpot account: the key is stored only in your browser and sent only to HubSpot’s API, never to us, and disconnecting deletes it. Connections made before 3.0.0 used OAuth: for those our backend stores your CRM’s authorization (an encrypted refresh token) and issues your browser short-lived access tokens, and disconnecting revokes it and deletes the stored tokens. Either way we never see or store your CRM password. From version 3.2.0, if you cannot create a key yourself, your HubSpot admin can create it for you through Ask my admin: the key is encrypted in the admin’s browser so that only your browser (or, for a team, whoever holds the team link) can open it, and our server holds only that encrypted copy, which it cannot read, until your browser picks it up (at most 7 days; a team key until the admin deletes it). You can also connect read only with your own HubSpot personal key, which stays in your browser and is sent only to HubSpot’s API.
  • CRM dashboard summaries (Pro): when a CRM is connected, the extension also sends anonymous summaries of your outreach (counts and rates such as total requests sent, acceptance rate, and how many are still pending) to our backend, so they can appear on your dashboard inside your CRM. These summaries contain no names and no contact details. Your contacts stay in your browser and reach your CRM only when you choose to push them.

Anonymous health ping and usage counts

The extension sends a small diagnostic ping to our backend when it is installed or updated, and after each sync. The ping contains only counts and status labels: the random per-install identifier (a UUID generated in your browser, not derived from you or your accounts), the extension version, whether each LinkedIn page could be read and how the sync ended, how many list entries each page showed versus how many were read, how long the sync took, a coarse score band, and aggregate outreach tallies (how many of your invitations are currently accepted, pending, or declined). Counts only, never who: the ping carries no names, no profile URLs, and no message content.

The extension also sends anonymous product-usage events, feature counts such as “connected a CRM” or “pushed N contacts,” tied to the same anonymous install identifier. These contain no contact data and nothing you typed; we use them only to understand which features are used.

We use this to know when a LinkedIn interface change has broken syncing so we can ship a fix quickly, and the outreach tallies let us spot a tracking bug (for example, statuses flipping when they should not) across all installs the same day it ships. The ping never includes LinkedIn data, names, profile information, your email, browsing history, or anything you typed, and the identifier is not linked to your identity. To have your install record deleted, use the contact form.

Website analytics

This website (connectiontracker.org) sets no analytics cookies and loads no third-party analytics scripts. The live chat (Crisp, see Third parties) loads only after you click “Chat with us”; until then the page loads nothing from Crisp and Crisp sets no cookie. When you click an install link, our own server counts the click as an anonymous total (which page it came from, when, and whether the request looked like a crawler) before sending you on to the Chrome Web Store. Our own server also counts page views: which page was opened, the name of the site you came from (for example google.com, never the full address) or the source label on the link you followed, whether you were on a phone, a tablet or a computer, and, if you arrived from one of our ads, which ad platform. We keep no IP address and no identifier with these counts, so they cannot tell two visits apart or recognize you when you come back. No cookies, no personal data, nothing that follows you between sites. The extension itself contains no analytics SDKs and no tracking of any kind beyond the health ping described above.

One exception, for visitors who arrive by clicking one of our paid ads (for example in ChatGPT, Google or Bing). The ad link carries a click reference created by the ad platform, and this site keeps it in one first-party cookie for up to 30 days. Right after you install, the extension asks our server whether your browser came from an ad, which lets our server match the click reference to the extension’s anonymous install identifier. We then tell the ad platform that this click led to an install, a HubSpot connection or a purchase. The platform receives only its own click reference and the name of that step, never your email, your name, your LinkedIn data or your CRM data. If you did not arrive from an ad, there is no cookie and nothing is matched.

Visitors who arrive from a ChatGPT ad also get OpenAI’s measurement script on this site, so OpenAI can count the visit for that ad. It sets OpenAI’s own cookies (an ad click reference and a random browser reference). We also keep a small cookie that says only which ad platform you came from, so the script loads on later pages too. Visitors who did not come from a ChatGPT ad never load it.

Visitors who arrive through a partner’s referral link also load Lemon Squeezy’s referral script, which tells Lemon Squeezy about that visit (the page, the site you came from and a browser identifier the script computes) and keeps a referral reference in a cookie on this site for up to 30 days, so the partner is credited if you buy Pro here or in the extension; visitors without a partner link never load it, and nothing else is shared.

Email me the install link

On a phone, this site can email you the install link so you can open it on your computer. We use your address once, to send you the install link. Nothing else. We do not save the address in our database, we do not add it to any list, and we do not write to you again. To send that one email, the address passes through our email provider (Resend), which keeps its own delivery record for a limited time under its own privacy policy. We count how many links were sent, without the address.

Data export

You may export your tracked data as a CSV file at any time from the extension’s side panel or dashboard. The CSV is saved directly to your computer by Chrome’s download manager. It is not transmitted anywhere.

Data deletion

To delete all local data, uninstall the extension or clear the extension’s site data via chrome://extensions→ Details → “Extension options” / site data controls. All local data will be removed.

To delete your license or anonymous install record from our backend, use the contact form and we’ll remove your email and associated records from our database. If you hold a paid license, this also revokes the license. Request a refund first if you want your money back.

Your privacy rights

You can ask us what personal data we hold about you, ask for a copy, or ask us to delete it. Because of how Outscore is built, the answer is usually short: the only personal data we hold is the email address you gave at checkout (if you bought Pro), an anonymous per-install identifier with feature-usage counts, and anything you sent us through the contact or feedback form.

Your tracked LinkedIn data is not ours to hand over or delete. It lives in your own browser, and in your own CRM if you chose to push it there. We never receive a copy. You can export it yourself to CSV from the extension at any time, and remove it entirely by uninstalling the extension.

To make a request, use the contact form. We accept requests sent any other way too. We will verify your request against the email address on file before acting, so that nobody can use a request to reach someone else’s data. We acknowledge within 5 business days and complete within 30 days, usually much sooner. If deleting your records would revoke a paid license, we will tell you before we do it so you can request a refund first.

If you are a person whose details were added to someone else’s CRM using Outscore, that CRM account holder controls that data, not us, and the request needs to go to them. We hold no copy of it and cannot delete it on their behalf, though we are happy to help them action it.

License data

Outscore is free to use. If you buy Outscore Pro, checkout is handled by Lemon Squeezy and the email you provide there is stored together with a per-install identifier (a random UUID generated in your browser) so we can deliver and validate your license key and reply to support requests you initiate.

We do not send newsletters, marketing email, or any other communication to this address, and your connection data and LinkedIn activity are never sent to us.

Permissions explained

  • storage: Save your tracked connections locally in your browser.
  • downloads: Save CSV exports to your computer when you click Export.
  • alarms: Schedule automatic background syncs at your chosen interval.
  • tabs: Open LinkedIn’s sent-invitations, connections, and received-invitations pages during a sync, then close them when done.
  • identity: Used only for HubSpot connections made before 3.0.0, which run the OAuth flow on HubSpot’s official consent screen. New connections use your own service key and do not use it. The extension never sees your CRM password.
  • Access to linkedin.com: Required so the extension can read the sent-invitations, connections, and received-invitations pages on your behalf, and, only when you press Withdraw on a person, to withdraw that one invitation (on LinkedIn’s Sent page or their profile, or by opening LinkedIn’s own withdraw box for your click).
  • Access to api.hubapi.com: When you connect HubSpot and choose to sync, write the connections you selected into your own HubSpot account, from your browser.

Third parties

The extension does not use any analytics SDKs, advertising networks, or tracking pixels. Your tracked LinkedIn connection data is never sent to the developer’s servers; it only goes to a destination you choose (a CSV file, or your own CRM).

The following third-party services are used for operational purposes only, and receive only the data described below:

  • Lemon Squeezy: processes your payment and issues license keys. Lemon Squeezy is the merchant of record and has its own privacy policy. Receives your email and payment details at checkout.
  • HubSpot: the CRM you optionally connect. When you sync, the connections you selected are written from your browser into your own HubSpot account, using a key you create in your HubSpot (or, for connections made before 3.0.0, OAuth on HubSpot’s own consent screen). You can disconnect at any time.
  • Neon: hosts the PostgreSQL database that stores license records, anonymous install/usage records, for connections made before 3.0.0 the encrypted CRM authorization, and the encrypted keys in transit from Ask my admin, which we cannot read. Data is held in the United States.
  • Vercel: hosts the website and the backend API routes that activate license keys, record anonymous usage events, receive Lemon Squeezy payment webhooks, and broker CRM OAuth connections made before 3.0.0. Receives the same request payloads that Neon stores.
  • OpenAI (ChatGPT Ads): only for installs that came from one of our ads in ChatGPT. Receives the click reference it created for that ad and which step followed it (install, HubSpot connected or purchase, with the amount paid). Nothing else.
  • Web3Forms: delivers messages submitted through the extension’s in-app feedback form and the website’s access-request, contact and partner application forms to the developer’s inbox. Receives only what you type into those forms (the message text and, optionally, the name/email you enter). We do not submit any form data on your behalf. It only fires when you click Send.
  • Resend: sends the install-link email when you ask for one on a phone. Receives the address you typed and that one email. Nothing else.
  • Crisp: runs the live chat on this website, in the extension’s chat window, and on the chat page the extension’s “Chat with support” buttons open. It loads only when you open the chat, and then sets its own cookie to keep your conversation. Receives what you write in the chat, the email you give it (if you do), the page you chatted from, and, when you come from the extension, its version, your plan and which button you clicked. Never your LinkedIn data. Crisp has its own privacy policy.

Children

The extension is not directed at children under 13 and does not knowingly collect data from anyone.

Changes

If this policy changes, the updated version will be published at the same URL with a new “Last updated” date.

Contact

Questions? Use the contact form and we’ll reply by email.