Security
Trust is part of the architecture
Companion-first means execution happens where you already are authenticated - your browser - with clear product limits and safety rails around it.
Principles
Your session stays yours
Actions run in the Chrome tab you control. We never take LinkedIn passwords to drive a cloud bot farm.
App + extension, one system
The web app is the brain (campaigns, CRM, analytics). The companion is the hands (DOM actions on LinkedIn).
Operator-grade safety
Daily caps, company throttles, warm-up, suppressions, and canary checks are built in - not bolted on.
Controls in practice
How Lynkin protects the control plane and keeps outreach operator-paced.
Session stays local
Jobs are claimed and executed by the Chrome companion on the LinkedIn tab you already use. We do not operate a residential-proxy farm that logs into LinkedIn as you in the cloud.
Auth & workspace access
NextAuth sessions, email verification, optional 2FA, and role-based Admin controls protect the control plane. API routes require authenticated sessions.
Plan & usage controls
Trial, Personal, Business, and Enterprise entitlements gate accounts, campaigns, Accept/Reply branches, extracts, tools, integrations, and webhooks - so limits are productized, not tribal knowledge.
Outreach safety
Risk caps, company throttles, warm-up, suppressions, and Activity Control help keep automation within operator-defined bounds.
Lynkin does not claim LinkedIn ToS compliance for every automation pattern. Operators remain responsible for how they use the product. See Terms and Privacy.
Contact us about security reviewsSecurity FAQs
Where do LinkedIn sessions live with Lynkin?
On the operator’s machine in their live LinkedIn tab. Lynkin does not take LinkedIn passwords to the cloud to run jobs.
Is companion-first risk-free?
No. Architecture changes credential risk; operators still own pacing, copy, and compliance. See /linkedin-automation-safety.
What controls does Lynkin provide?
Warm-up, daily risk caps, Activity Control, and inbox ownership so humans close reply loops.
How do we brief IT?
Start at /security, then /guides/cloud-vs-companion-linkedin-automation, then a companion pairing demo.