Will this get my LinkedIn account banned?
No vendor can guarantee that it will not. Crispy applies enforced limits, an invitation ceiling, request pacing, scoped access, and one-way key storage. Those controls reduce avoidable risk; they do not authorize automation or guarantee that LinkedIn will not restrict an account.
LinkedIn's User Agreement section 8.2 prohibits bots and other unauthorized automated methods.
Daily activity limits
Every connected profile starts with a daily cap for each category. Crispy refuses another action after the active cap is reached. The values below come from the same configuration the product enforces.
| Action | Default cap | Override ceiling |
|---|---|---|
| Invitations | 15 per day | 50 per day |
| Messages | 150 per day | No product-enforced maximum |
| Engagements | 100 per day | No product-enforced maximum |
| Posts | 10 per day | No product-enforced maximum |
| Searches | 300 per day | No product-enforced maximum |
| Profile views | 250 per day | No product-enforced maximum |
Invitation overrides stop at a hard ceiling
You can lower the invitation cap or deliberately raise it, but Crispy rejects an override above the enforced ceiling. The ceiling is a power-user bound, not a recommendation and not a promise that every LinkedIn account can sustain it.
High-risk manual actions are spaced apart
A per-profile mutex serializes manual calls. After outreach, messaging, engagement, or publishing actions, a randomized 3–10 second cooldown separates the next high-risk manual call. This controls burstiness; it does not imitate a person and is not ban prevention.
Access is scoped per profile
Each connected LinkedIn profile has an account tool scope. Core covers the normal messaging, outreach, content, campaign, list, and analytics loop. Full access adds advanced and irreversible tools. API keys can be restricted separately by resource scope and granular read or write permissions.
API keys are shown once
Crispy returns the raw API key only when it is created. The stored verifier uses SHA-256 hashing, with a server-side pepper required in production, so the original key cannot be read back from the stored value. Revoke a key from the dashboard if it is lost or exposed.
Security and privacy limits
Managed storage supports features such as Unibox and campaigns. Export and deletion follow the lifecycle and exceptions in the Privacy Policy. Crispy is not SOC 2 certified. Railway hosting and Supabase database controls are represented in the repository, while production regions, transport configuration, and control effectiveness still require verification.
Security FAQ
Will this get my LinkedIn account banned?
No tool can honestly promise that your account will never be restricted. Crispy's controls reduce volume and pace high-risk manual actions, but they cannot guarantee an outcome. LinkedIn's User Agreement section 8.2 prohibits bots and other unauthorized automated methods. These controls do not authorize that activity.
What happens when a daily limit is reached?
Crispy refuses another action in that category until the daily counter resets. A ceiling is a brake, not a target, and setting one does not make a particular volume safe for every account.
Can I change the limits?
You can lower any default. Invitations have a hard override ceiling of 50 per day. The categories marked uncapped do not have a product-enforced override ceiling above the default, so raising them is your decision and adds account risk.
Is Crispy SOC 2 certified?
Crispy itself is not SOC 2 certified. The repository uses Railway hosting and Supabase database controls, including row-level security migrations. Production transport, regions, and control effectiveness still require verification.
Where is connection data stored?
Crispy supports hosted connection and direct credential or session-cookie methods. Connection material can be received, transmitted to the connection provider, and stored where technically necessary to operate and secure the session. Managed storage can also contain contacts, messages, and activity data.
Can I run a pentest against Crispy?
Yes. Contact [email protected] first so the test can be coordinated. We welcome responsible disclosure.
Run LinkedIn workflows from the AI client you already use.
Create your account, connect LinkedIn, create an API key, then add Crispy to your client. Review the docs for supported workflows and safety controls.