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.
Your session stays yours
Execution happens in the browser you control. We never ask for LinkedIn passwords to run jobs in the cloud.
Plan gates, not dark patterns
Trial, Plus, and Pro limits are enforced in-product so usage stays clear and upgrade paths are honest.
Operator-grade safety
Risk settings, suppressions, and warm-up are first-class — not afterthoughts bolted on for marketing.
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, Plus, and Pro entitlements gate accounts, campaigns, DAG conditions, 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.
LinkedInYi does not claim LinkedIn ToS compliance for every automation pattern. Operators remain responsible for how they use the product. See Terms and Privacy.