# How SDRPilot Keeps Your Account Safe

Your LinkedIn account is the asset. Every rule below exists to protect it, and several of them cost volume on purpose.

## What SDRPilot never does

* It never sends from a datacenter connection. Each account gets its own residential IP address, and sign-in is refused without one.
* It never runs two LinkedIn actions at the same time on one account. A message, an accept and an invitation take turns, because two things happening at once is the clearest sign of automation there is.
* It never presents a second browser identity on your session. One fingerprint is captured when you sign in and used for everything after that.
* It never stores your LinkedIn password unless you tick **Remember my password**, and unticking it erases what was stored.
* It never exceeds the daily ceilings, and it never lets a brand new account send at full volume on day one.
* It does not attach a note to connection requests by default. A pitch in the invitation lowers acceptance, so the personal part waits until the person has accepted.

## Human pacing

Actions are spread out rather than fired in bursts. There is a pause between calls, reading and sending are paced separately, and everything stays inside your active hours. A reply that arrives at 02:00 is read but answered when your window opens.

A new account climbs a warm-up ramp over roughly two weeks, one step a day, for messages, connection requests, profile views and searches alike. The numbers are in [Daily Limits and Active Hours](limits-and-active-hours.md).

## Invitations that nobody answered

A large pile of unanswered invitations is itself a signal, and it blocks your own sending. <span data-t="appName">SDRPilot</span> withdraws invitations older than thirty days for you, oldest first and only a few at a time, and pauses sending while too many are outstanding. The ceiling is worked out from your own daily limit, so it scales with how you send.

## If LinkedIn challenges or restricts your account

LinkedIn can end a session at any time, usually by asking you to verify who you are. When that happens:

1. <span data-t="appName">SDRPilot</span> stops using that account immediately and puts it into a cooldown rather than trying again straight away.
2. The account row in **Settings** shows the state, and the activity log records what happened.
3. If you saved your password, one careful automatic sign-in is attempted after a delay, inside the caps described in [Proxy and Session](proxy-and-session.md).
4. Otherwise, open LinkedIn in your own browser, complete whatever it asks for, then use **sign in again** on the account row.

Nothing is lost while an account is disconnected. Leads, conversations and history stay where they are, and work resumes when the session is back.

## How to pause

You have three levels, from lightest to heaviest:

* **Pause the agent** on the **Agents** page. Nothing is sourced and nothing is sent, and your inbox keeps working.
* **Narrow your active hours or lower your daily limits** in **Settings** when you want less volume rather than none.
* **Sign out the LinkedIn account** on the account row. That stops every action on that account at once. Signing back in resumes where you left off.