LinkedIntel Privacy Policy

Where the extension can run

Chrome only lets an extension touch the sites listed in its manifest. LinkedIntel lists three: LinkedIn profile pages, LinkedIn company pages, and our own API.

• https://*.linkedin.com/in/* — profile pages
• https://*.linkedin.com/company/* — company pages
• https://api.linkedintel.ai/* — our own API

Anything outside those three patterns is out of reach: your LinkedIn inbox, your connections, your feed, your saved searches, your notifications, and every other website you visit. This is enforced by Chrome, not by our good intentions, and you can verify it in the extension's Chrome Web Store listing under "Site access".

What leaves your browser

When you run an analysis, the extension sends a short set of identifying fields to our API so our servers know what to research. The page itself is never uploaded — no HTML, no screenshot, no full-text scrape.

We do not collect your LinkedIn password or session cookie, and signing into LinkedIntel is done through Google, not LinkedIn. The Google sign-in requests two scopes only: your email address and your basic profile.

What is stored in your browser

The extension uses Chrome's own storage on your machine. Nothing here is readable by us directly; it is state the extension needs to work.

• Your sign-in token, if you signed in
• Your usage counters — analyses used this month, your allowance, and your plan
• The random analytics identifier described above, plus a short queue of analytics events waiting to be sent if you were offline
• The LinkedIn page currently in context and any analysis in flight, held in session storage and cleared when you close Chrome

Removing the extension from chrome://extensions deletes all of it.

What is stored on our servers

Our database is hosted with Supabase. Four kinds of record exist:

• Your account. The email address and profile name from your Google sign-in. Anonymous trial analyses have no account record at all.
• Usage logs. One row per analysis: whether it was a person or company, the company name, the person's name and title, the LinkedIn URL analysed, whether the result came from cache, how many credits it used, which data sources were involved, and the timestamp. This row is linked to your account when you are signed in.
• Cached analyses. The finished research result, keyed by the company or person analysed rather than by user. See "Caching" below, because this one has a consequence worth understanding.
• Billing records. Your plan, credit balance, and a record of each payment: the amount, currency, status, and the payment and customer identifiers issued by Dodo Payments. Card numbers are entered on Dodo's hosted checkout and never reach our servers.

Caching, and what it means for you

Analysis results are cached against the entity analysed — a key like company:acme — not against your account. That is why re-analysing a company you have already looked at is instant and does not cost you a credit.

The consequence: if another user analyses the same company or person, they may be served the result our system generated earlier, including one generated for you. The analysis itself is built from publicly available information, and the cache holds no reference to who requested it. What stays private is the link between you and what you looked up — your usage log is visible only on your own account.

Who else processes your data

We use third-party services to run the product. Each one receives only what it needs, and each is governed by its own privacy policy.

We do not sell personal information, and we do not share it with advertisers or data brokers. The services above are processors we pay to run the product, not partners we sell to.

How long we keep it

Being straight about this: usage logs and cached analyses are currently retained indefinitely. We do not run a scheduled deletion job against them today. Account and subscription records last for the life of the account, and payment records are kept beyond that where accounting and tax rules require it.

If you want your records removed sooner, ask us and we will delete them. That is a real option, not a formality.

Your choices and how to exercise them

• Stop all collection. Remove the extension at chrome://extensions. This takes effect immediately and clears everything stored in your browser.
• Use it without an account. The first three analyses need no sign-in and create no account record.
• Access, correction, deletion, or a copy of your data. Email contact@linkedintel.ai from the address on your account. There is no self-service delete or export button in the dashboard yet, so these are handled manually. Say what you want and we will action it.
• Someone else's data. If you are a LinkedIn member who believes LinkedIntel holds an analysis about you and you want it removed, email us with the profile URL and we will purge the cached record.

Security

All traffic between the extension, our API, and every service listed above runs over HTTPS. Access to the database is restricted to the application and our operators. Payment card data is handled entirely by Dodo Payments and is never transmitted to or stored on our systems. No service can promise it will never be breached; if a breach affects your data, we will tell you.

Children

LinkedIntel is a business tool and is not directed at anyone under 18. We do not knowingly collect data from children. If you believe a child has used the product, contact us and we will delete the records.

Changes to this policy

When what we collect or who processes it changes, this page changes with it and the "last updated" date above moves. Material changes will also be noted in the extension's release notes.