Safety controls

Start with the risk

LinkedIn's User Agreement does not allow software that automates activity on its site, and LinkedIn can restrict accounts that use it. OutreachGenie cannot change that. The controls below lower the pace and stop work quickly when something looks wrong; they do not make automation risk-free. Read LinkedIn's User Agreement and decide what you are comfortable running from your own account.

Where the actions run

Every LinkedIn step runs in your own Chrome browser, through the OutreachGenie extension, while you are signed in to LinkedIn. There are no shared cloud browsers, proxies or second logins.

The extension lets Chrome attach your LinkedIn cookies to requests it sends to LinkedIn. Your LinkedIn session cookie (li_at) is never sent to OutreachGenie servers, and we never ask for your LinkedIn password. The privacy policy lists what is stored and for how long.

Pace: daily and weekly caps

Each workspace picks a pace. Every pace sets a daily cap, a weekly cap counted over the last seven days, an hourly limit, a cooldown after each action and a minimum gap between any two actions. When a cap is reached, work waits; it is never squeezed in later. Workspace owners can tune the numbers in Settings, Execution.

Connection requests are also spaced at least 10 to 20 minutes apart depending on the pace, and no two LinkedIn actions run closer than 45 to 180 seconds.

When it runs

A campaign can run immediately or on a schedule: the days of the week, a daily start time and a daily end time, in the campaign's own time zone. Nothing is sent outside that window. A step that becomes due after the end time waits for the next active day.

Stopping

• Pause or stop a campaign. It takes effect before the next step. A step the extension has already started may still finish, because LinkedIn may already have received it.
• Pause everything. Any workspace member can stop every campaign step and automatic lookup in the workspace with one button in Settings, Execution. Only an owner or admin can resume.
• Stop after a reply. Before each follow-up message in a sequence, OutreachGenie checks the conversation. Once the person has replied, no more follow-ups from that sequence are sent.

When LinkedIn pushes back

• Security check or refusal. If LinkedIn shows a security check (a verification or restriction page) or refuses requests with its HTTP 999 response, OutreachGenie pauses everything in the workspace and tells you why. It stays paused until an owner or admin resumes. This needs extension 1.2.14 or later.
• Rate limit. If LinkedIn answers with a rate limit (HTTP 429), that kind of action waits until the following Monday.
• Signed out. If your LinkedIn session ends, work waits until you sign in to LinkedIn again.

No duplicate sends

Before the extension contacts LinkedIn, it confirms the step with OutreachGenie, and the step is recorded once. A step is retried automatically only when LinkedIn was provably never contacted. If the extension cannot tell whether an invitation or message went out, for example because the browser closed mid-send, the step is never resent: it is marked Needs review so you can check LinkedIn yourself.

Automatic contact lookups

When the extension is connected and has no campaign work, it opens the contact-info panel of your existing 1st-degree connections that have no email or phone saved yet, and stores what LinkedIn shows you there. It does at most six of these an hour per workspace on the free plan (Pro workspaces can run a faster pace), and they stop when you pause everything.

How these controls are checked

Caps, sending windows, pausing, stop-after-reply and the no-duplicate rules are covered by automated tests that run on every change before it can be released. If you see behaviour that does not match this page, tell us through the contact page.