নিরাপত্তা
Trust architecture-এর অংশ
Companion-first মানে যেখানে already authenticated — browser — সেখানে execution, clear product limit ও safety rail সহ।
নীতি
Session আপনারই
Action আপনি control করা Chrome tab-এ চলে। Cloud bot farm চালাতে LinkedIn password never নিই।
App + extension, এক system
Web app brain (campaign, CRM, analytics)। Companion hand (LinkedIn-এ DOM action)।
Operator-level security
Daily cap, company throttle, warm-up, suppression ও canary check built-in — পরে bolt-on নয়।
Practice-এ control
Lynkin control plane protect ও outreach operator pace-এ রাখে কীভাবে।
Session local
Job Chrome companion আপনি use করা LinkedIn tab-এ claim ও execute। Cloud-এ আপনি হয়ে LinkedIn login করা residential proxy farm operate নই।
Auth ও workspace access
NextAuth session, email verification, optional 2FA ও role-based Admin control control plane protect। API route authenticated session চায়।
Plan ও usage control
Trial, Personal, Business entitlement account, campaign, Accept/Reply branch, extract, tool, integration, webhook gate — limit productized, tribal knowledge নয়।
Outreach safety
Risk cap, company throttle, warm-up, suppression ও Activity Control automation operator-defined bound-এ রাখে।
Lynkin প্রতিটি automation pattern-এ LinkedIn ToS compliance claim করে না। Operator usage-এর জন্য responsible। দেখুন Terms ও Privacy.
Security review সম্পর্কে contactSecurity 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.