The short answer: The LinkedIn li_at cookie is the cookie LinkedIn sets when you sign in, and its cookie table, read 2026-11-15, describes it as “Used to authenticate Members and API clients.” A tool that holds your li_at can act as your signed-in session until that session ends. We can’t call that safe, so this page says what we keep and what you can do.

We make a tool that connects LinkedIn accounts this way, so we are the party you would be trusting. Pasting cookies is one of two ways to connect; the other is email and password.

It is the cookie that proves a browser is signed in. LinkedIn’s cookie table, read 2026-11-15, lists li_at under authentication with a one-year expiry. LinkedIn’s help page See where you’re signed in, read the same day, says a session is created when you sign in to your account.

What can a tool do with a pasted session?

Whatever the signed-in account can do in that session. We use it to open the account through a proxy, read who it is, then send the steps of a campaign, poll for acceptances and replies, and read the inbox. We don’t tell you it can’t do more, because a session is a session. That is why the sender screen asks you to confirm “Is this you?” before anything is saved, and why limits and working hours are on from day one.

How do we handle the cookies?

We keep them encrypted. Only the service that sends for you can read them. They are stored in a private schema of our database, apart from the data your team sees, they are never shown again in the app and never written to logs.

If you choose email and password instead, we encrypt the email, password and authenticator key with a key held outside the database, and only the service that signs the account in can read them. You can delete the saved password at any time.

What do we not do?

  • We don’t see your LinkedIn password when you paste cookies. Pasting cookies means you never share it.
  • We don’t save anything until you confirm the account is yours. “No, that’s not me” discards the paste.
  • We don’t make Cookie-Editor, the free third-party extension used to export the cookies, and we can’t vouch for later versions.
  • We don’t say “hashed”, because we have to be able to use what we store to sign in. We say encrypted.

How do I end a session I pasted?

Sign out of it on LinkedIn. The Where you’re signed in page, which LinkedIn’s help page says lists each session with its location, IP address, device type, browser and last sign-in, lets you end one session or all sessions except the one you’re using. It asks for your password. LinkedIn also says that if you don’t recognise a login or device, you should change your password.

Our sender will then show as disconnected, and reconnecting means pasting fresh cookies for the same account. Signing out of LinkedIn in the browser the cookies came from ends that session too, so stay signed in there while a sender is connected.

What does a team do about it?

Each person connects their own account and decides whether to use cookies or email and password. The person who connected an account is the only one who can change its inbox privacy. A manager shouldn’t collect teammates’ cookies in a spreadsheet: each teammate pastes their own. The steps are in connect a LinkedIn account with Cookie-Editor.

The honest boundary

Anyone who holds a session cookie can use the session, and we hold yours while a sender is connected. We limit who can read it and we don’t log it, and we can’t promise nothing will go wrong. What LinkedIn does about automated activity is covered in what gets LinkedIn accounts restricted.