LinkedBridge Pro — Privacy Policy

1

Overview

SCube LinkedBridge Pro is a Chrome extension that reads publicly visible data from LinkedIn profile pages, company pages, search results, and posts — and lets you save that data as records in the CRM you connect. This policy explains exactly what data is accessed, where it goes, and what we never do with it.

Version 3.0.0 adds support for HubSpot, Zoho CRM (all regions), Microsoft Dynamics 365, and Pipedrive alongside the original Salesforce integration. The privacy model is identical for all CRMs: data flows directly from your browser to the CRM you configure — SCube operates no intermediate server.

2

Supported CRMs — Data Destinations

The following CRMs are fully supported in v3.0.0. Data is only ever sent to the CRM you have connected and authenticated — no data is sent to any CRM you have not configured.

3

Data Read from LinkedIn

The extension reads publicly visible information from LinkedIn pages you navigate to. It does not bypass LinkedIn authentication, access private/restricted content, or read data from pages you have not opened yourself.

Profile Pages (linkedin.com/in/*)

Company Pages (linkedin.com/company/*)

Search Results (linkedin.com/search/results/*)

When you use bulk-queue mode on a search results page, the extension reads the visible result cards: name, headline, company, location, LinkedIn URL, and profile photo for each visible result. No background scraping occurs — only cards visible on screen at the time you trigger extraction.

Posts & Events (linkedin.com/feed/update/*, /posts/*, /events/*)

When you use the post-reactions or event-attendees feature, the extension reads the list of people who reacted to a post or RSVPd to an event: name, headline, LinkedIn URL, and profile photo. Only the data visible in the panel LinkedIn shows you as a logged-in member is read.

4

Data We Do NOT Collect

• We do not collect, transmit, or store any LinkedIn or CRM data on any server we operate
• We do not collect analytics, usage metrics, crash reports, or telemetry of any kind
• We do not collect your CRM credentials, OAuth tokens, or enrichment API keys — they remain on your device only
• We do not share data with any third party except the CRM you configure and any enrichment provider you explicitly connect using your own API key
• We do not use cookies, tracking pixels, or fingerprinting
• We do not operate user accounts, registration, or any server-side infrastructure

5

Optional Email Enrichment (BYOK)

When you click "Enrich" on a profile, the extension can call one of three optional enrichment providers using an API key you supply. These calls are made directly from your browser to the provider — SCube does not proxy, log, or intercept them.

None of the enrichment providers are called unless you have configured that provider's API key in Settings. You can remove any provider key at any time.

6

Chrome Permissions Explained

Host Permissions (Network Access)

7

Data Storage & Retention

All data is stored in chrome.storage.local on your device (or chrome.storage.sync for the numeric extraction counter only). The following keys are stored:

• All credentials and tokens are retained until you click "Disconnect" in Settings or uninstall the extension
• The activity log retains the last 50 entries; older entries are automatically pruned
• You can clear all stored data at any time via Settings → Clear All Data
• Uninstalling the extension removes all locally stored data automatically

Outbound Webhooks (Optional)

If you enable the optional webhook feature, the extension will POST a JSON payload to a URL you specify whenever a record is created or updated. The payload contains the same data that was sent to your CRM. SCube does not see or receive these webhook calls — they go directly from your browser to your configured endpoint.

8

Security

• All communication with CRMs and enrichment providers uses HTTPS/TLS
• OAuth tokens and API keys are stored only in chrome.storage.local, sandboxed to the extension and inaccessible to websites or other extensions
• Dynamics 365 uses PKCE (Proof Key for Code Exchange) for its OAuth flow — no client secret is transmitted in the redirect
• The extension uses Chrome Manifest V3, which enforces strict Content Security Policy and prohibits remote code execution
• Webhook deliveries are signed with HMAC-SHA256 using a secret you configure, so your receiving endpoint can verify authenticity
• No CRM credentials are hardcoded in the extension — you enter your own

To report a security vulnerability, email scubedevelopmentteam@gmail.com.

9

Children's Privacy

The extension is not directed at children under the age of 13 and does not knowingly collect any information from children. It is a professional sales productivity tool intended for use by adults in a business context.

10

Changes to This Policy

When this Privacy Policy is updated — for example when a new CRM integration is added — the revised version will be published at this URL with an updated "Last Updated" date. Continued use of the extension after changes are posted constitutes your acceptance of the updated policy.

11

Contact