Outscore and HubSpot: shared data

What Outscore is

Outscore is a Chrome extension that tracks the status of your own LinkedIn connection requests (accepted, pending, declined) and lets you push the connections you choose into your own HubSpot account. You decide what reaches the CRM. It sends no connection requests and reads only pages you could see yourself.

Permissions the app requests, and why

The app requests the minimum scopes needed to write the contacts you select. It never requests schema or property-settings permissions, so any rep with ordinary contact access can install it.

• oauth: baseline for the OAuth connection.
• crm.objects.contacts.read: find whether a LinkedIn contact already exists (dedup by LinkedIn URL) and read the current values of the fields you are about to write, so we can fill only what is empty.
• crm.objects.contacts.write: create or update the contacts you choose, and log a timeline note.
• crm.objects.companies.read: find an existing company by name before creating a duplicate.
• crm.objects.companies.write: create the contact’s company and associate it.
• crm.objects.owners.read: resolve your HubSpot user so pushed contacts are assigned to you as owner.

Data the app reads from HubSpot

• Contact records matching the LinkedIn URLs you are pushing (to dedupe and to fill empty fields only).
• Company records by name (to avoid duplicate companies).
• Your owner record (to set contact ownership).

The app does not read your wider contact database, deals, tickets, conversations, or any records you are not actively pushing.

Data the app writes to HubSpot

Only for the connections you explicitly select, and only the fields you enable:

• Contact: first and last name, job title, company, LinkedIn profile URL (hs_linkedin_url), and owner.
• Company: found or created by name, and associated to the contact.
• A one-time timeline note recording the connection (for example the connection request and any invite note).

Nothing is pushed automatically. There is no background writing and no bulk import of your LinkedIn network.

Data stored on Outscore's servers

• The encrypted HubSpot authorization (a refresh token), so the extension can obtain short-lived access tokens. Encrypted at rest; deleted when you disconnect.
• A random per-install identifier and anonymous usage counts (for example “connected a CRM”, “pushed N contacts”).
• Aggregate outreach summaries (counts and rates such as total requests sent, acceptance rate, and how many are still pending) so they can render on your dashboard inside HubSpot. These contain no names and no contact details.

What is never stored on our servers: your LinkedIn contact data. The contacts you push travel directly from your browser to your own HubSpot account. Our backend brokers the connection; your contact data does not pass through it.

How data flows

• Your tracked LinkedIn data lives in your browser’s local database.
• When you push, contacts go browser to HubSpot directly, using a short-lived token.
• Only the aggregate outreach summaries (counts and rates, no contact data) are sent to our backend, and only so the in-HubSpot dashboard can display them.

Sub-processors

• Neon (managed PostgreSQL): stores the encrypted authorization, install and usage records, and aggregate summaries.
• Vercel: hosts the backend that brokers the connection.
• Lemon Squeezy: processes the optional one-time Pro payment (email only, no CRM data).

Your controls

• You choose every contact and every field that syncs.
• Disconnecting in the extension revokes the HubSpot authorization and deletes the stored tokens.
• To delete your install and usage records, use the contact form.

Full privacy policy: connectiontracker.org/privacy.