Security
We never ask for your password. There is nothing to leak.
Two questions come up before anyone connects an account: what can this thing do with my LinkedIn, and what happens if you get breached. Here are both answers, in detail.
The short version
What we hold, and what we refuse to.
The safest way to protect a credential is not to have it. Frosty is built so that the most sensitive thing you own — your LinkedIn password — never enters the system at any point.
And if you run on managed profiles, none of this applies to you at all: there is no account of yours connected in the first place.
How managed profiles avoid the question entirelyNever stored
- Your LinkedIn password — we never ask for it and never receive it
- Your email password, or any other account credential
- Payment details on file with LinkedIn
- Your token, in readable form, anywhere at rest
Stored, to run your campaigns
- An encrypted session token, if you connect your own account
- Your campaigns: ICP criteria, sequences, message settings
- The leads a campaign sourced and the state each one is in
- Replies received, so they show in your inbox
Connecting your own account
What happens to the session token.
If you would rather outreach came from your own name, this is the whole lifecycle of the only thing we hold.
- 01
Connect without a password
You authorise a session rather than handing over credentials. Frosty captures a session token — the same thing your browser holds when you are logged in — and nothing else.
- 02
Encrypted at rest
The token is encrypted before it is stored and decrypted only in the process that runs your campaigns. It is never displayed back to you, logged, or sent anywhere else.
- 03
Used for your campaigns only
It drives the actions you configured — searching, connecting, messaging. It is not used to read your private messages beyond campaign replies, post as you, or touch anything outside the campaign.
- 04
Revoke it whenever you like
Disconnect the account in your dashboard and the token is deleted. You can also end the session from LinkedIn's own security settings, which invalidates it immediately from the other side.
Account safety
How we keep a profile out of trouble.
Restrictions are almost always a pace problem, not a detection problem. Accounts get flagged for doing a month of activity in an afternoon, at perfectly even intervals, at three in the morning.
Frosty is deliberately slower than it could be — on managed profiles and on yours.
On your own account the risk is never mathematically zero, which is the honest answer and precisely why managed profiles exist.
Volume ramps, never starts at the ceiling
A new profile begins well under the safe limit and climbs over days. Starting at maximum is the single most common way accounts get restricted.
Human hours, human gaps
Activity follows the working day in the profile's own timezone, with the irregular spacing a person produces rather than a fixed interval.
Limits we will not let you raise
There is a ceiling you cannot override in the dashboard. Outreach that outruns it performs worse and ages the account faster, so it is not a setting.
Watched, and slowed automatically
Acceptance and response rates are monitored per profile. A profile that starts underperforming slows down on its own before it becomes a problem.
- Campaign and lead data is exportable at any time, in a format you can actually use elsewhere.
- Deleting a campaign removes its leads and messages; closing your account removes everything, including any stored token.
- Data is encrypted in transit and at rest, and access inside our team is limited to the people who need it to support you.
- We do not sell your data, share your leads with other customers, or use your campaigns to train anything for anyone else.
Start without connecting anything.
The trial runs on a managed profile, so you can see the product work before deciding whether your own account is ever involved.