Will This Get My LinkedIn Account Restricted?

SDR Pilot logs in once and holds the session cookie, encrypted at rest and never written to a log. It does not need your password. There is an optional encrypted auto reconnect you can switch on so a dropped session can come back without you, and it is off by default. Nothing stores a password unless you tick that box yourself.

Every sender gets its own residential IP address in the account's own country, bought before it logs in for the first time. No datacenter IPs, no shared pool, and no second account behind the same address. An account that has always signed in from one city and then appears from a datacenter in another continent is the easiest automation signal there is, and it is the first one this removes.

The user agent, timezone and locale are captured from the real browser at login and every request the sender makes carries that same identity. A second browser fingerprint on one session reads to LinkedIn as a stolen cookie, and its answer to that is to destroy the session rather than challenge it. A test fails our build if a hardcoded browser string ever appears in the codebase.

A sender performs exactly one LinkedIn write at a time. An invitation accept landing while a message is half sent, or two threads answered in the same second, is the shape automation has and a person does not. Every write path takes the same per account lock, and reads take a separate one so a long profile sweep can never sit in front of a reply. Requests, profile reads and replies are queued and paced, never fired in a burst.

The connection ceiling of 25 a day is LinkedIn's own weekly invitation allowance of roughly 100, not a number we chose. The profile read cap cannot be raised: the per sender setting only lets a sender read less, which is the point, because read volume is what draws attention. A day means the workspace's own calendar day in your timezone, not the server's, so a cap can never be spent twice inside one local afternoon.

A new sender does not start at the default. It climbs a linear ramp, one step per calendar day, with no cliff anywhere in it: connection requests start at 5 and add one a day, reaching 20 on day 16. Messages start at 30 and add 5 a day, reaching 100 on day 15. Profile reads start at 50 and searches at 5, and both reach their defaults inside the same window. The ramp is a ceiling, so a sender you configured lower keeps its own smaller number.

• No browser extension. Nothing is installed on your machine and nothing needs your browser to be open.
• No engagement pods, no auto likes and no comment automation on other people's posts.
• No mass anything. Every request is preceded by a profile read and an ICP score, and most people get a no.
• No shared IP pool and no second account on your address.
• No password stored unless you explicitly opt in.

You set the hours and days the sender is allowed to act, on your own calendar. Outside them it does nothing. Unanswered sent invitations are capped at 30 days of that sender's own sending, so a sender at 20 a day carries at most 600 outstanding, and invitations older than 30 days are withdrawn automatically. A pile of stale unanswered invitations is itself a signal, and it also quietly stops a sender sending anything new.

The founder's own LinkedIn account has run on SDR Pilot since June 2026 and has been fully autonomous since August 2026. That is one account, not a statistic, and it is the reason the caps in the table are conservative: they were set from what actually happened on it.