The Ozigi for LinkedIn extension performs LinkedIn actions on your behalf inside your own browser, using your own logged-in LinkedIn session. It exists because LinkedIn does not serve its interface reliably to server-side automation.
This policy covers the extension only. Our main policy is at ozigi.app/privacy-policy. Questions: hello@ozigi.app.
What it accesses
The extension runs only on linkedin.com and only reads two kinds of page:
- LinkedIn people-search results. It reads the public profile URL, name and headline shown on each result card, for people matching the ideal-customer profile you defined in Ozigi.
- A lead’s profile page. It locates the Connect button, sends the connection request with the note Ozigi wrote, and reads back whether LinkedIn now shows the invitation as pending.
What it sends to Ozigi
- Profile URL, name and headline of people found in your searches, saved as leads in your account.
- The outcome of each connection request — sent, already connected, or failed — plus an error description when one fails.
Everything is sent over HTTPS to ozigi.app, authenticated with a token you generate in your Ozigi settings and paste into the extension. That token identifies your account and nothing else; it is not your LinkedIn password and grants no access to your LinkedIn account.
What it never does
- It never reads, collects or transmits your LinkedIn credentials.
- It never reads your LinkedIn inbox, messages or notifications.
- It never sends LinkedIn messages or DMs. The connection request is the only thing it sends.
- It never runs on any site other than
linkedin.com. - It never sells, rents or shares your data with third parties, and it is not used for advertising.
- It never acts while you have it switched off, or while your browser is closed.
Why it needs the permissions it asks for
- debugger
- LinkedIn ignores clicks that did not come from a real person — its own handlers check whether an event was browser-generated before opening the invite dialog. The Chrome DevTools Protocol input API is the only way to produce a click LinkedIn will accept. It is used solely to dispatch mouse and key input at coordinates on LinkedIn pages, and only while an action is running. Chrome displays its standard banner whenever it is attached.
- tabs & scripting
- To open the lead’s LinkedIn profile in a tab and read that page in order to find the Connect button.
- storage
- To keep your connection token, your on/off preference and today’s counters on your own machine.
- alarms
- To check for due work on a timer, and to pace actions so they occur at a human rate.
- Host access to linkedin.com and ozigi.app
- LinkedIn is where the work happens; ozigi.app is where instructions come from and results go.
Retention and control
Leads and outreach records live in your Ozigi account and are deleted when you delete the campaign or your account. Removing the extension stops all activity immediately; revoking the token in your Ozigi settings does the same, from the other end.