# Security
## Steps We Take to Protect your Account
### Rate Limiting
We rate limit your automations to ensure you stay within the limits you're supposed to. Instead of sending a ton of messages at once, we will space them out over time.
{% content-ref url="/pages/RARQQ2iYJlgSmHSTJU1O" %}
[Limits](/apps/linkedin-outreach/security/limits.md)
{% endcontent-ref %}
### Proxy with a Dedicated IP Address
Each account has a dedicated IP address that's unique to that account. You will never log in with the same IP address as another user.
### Session Cookie Authentication
We use session cookies to access your account. The difference is that rather than inputting a username or password, having to bypass captcha, and dealing with all the security that comes with the login page, we skip this step by **accessing an already logged in session rather than creating a new login.**
## What happens if I see a warning message about automation?
It's not uncommon to see a warning message about the use of automation tools. Not to worry as most accounts that use automation see this at some point. It's not a big deal and we've never had an account be permanently suspended.
Why isn't this a big deal? It's not so much that they are actually detecting automation software being used, it's that there was a change in the activity levels of your account. If you go from not sending connection requests at all to sending the maximum allowed weekly limit, they might see this as a big jump in the activity on your account. Once they've gotten used to your increased level of activity, they will no longer be detecting big changes to your activity and the security measures we take will keep your account safe.
{% hint style="info" %}
They would ban a lot of real user accounts that aren't using automation if they banned based on session cookies. Session cookie based authentication protects your account.
{% endhint %}
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.big-brain.co/apps/linkedin-outreach/security.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.