Security & Trust
Security you can verify, stated honestly
Two things matter for LinkedIn outreach: protecting your data, and protecting your accounts. Below is exactly where we stand on each — clearly labeled as shipped, in progress or planned. We never claim a certification we don't have.
LinkedIn account safety
The security question unique to LinkedIn outreach: keeping accounts healthy and your own profile out of harm's way.
Managed ambassador accounts
Outreach runs on managed accounts rather than your personal profile. That relocates the account risk; it does not remove it, and we will not claim it does.
One dedicated proxy per account
Each sender has its own stable residential IP and geography, isolating risk between accounts.
Human-like pacing & daily caps
Randomized delays, quiet hours and per-account limits keep sending patterns natural.
Automatic warming
Accounts arrive pre-warmed and stay warmed, so you never ramp from cold.
Checkpoint detection & auto-pause
Detecting security checkpoints and pausing affected accounts automatically.
Data & privacy
How we handle the personal data you and your prospects entrust to us.
GDPR & UK GDPR alignment
We process personal data lawfully; see our Privacy Policy for legal bases and your rights.
CCPA alignment
California residents' rights are honored under our Privacy Policy.
Data ownership stays with you
Your leads, messages and campaign data are yours. Export anytime; deletion on request.
Data Processing Agreement (DPA)
A signable DPA for customers who process EU personal data. Request one via security@topclozer.com.
Subprocessor list
A published, current list of the vendors that help us run the service. Available on request today.
Configurable data retention
Self-serve retention windows for campaign and reply data.
Infrastructure & encryption
The technical foundations that protect data in transit and at rest.
Encryption in transit (TLS)
All traffic is served over HTTPS/TLS.
Encryption at rest
Data stores are encrypted at rest by our infrastructure provider.
Backups
Automated, tested backups with defined recovery objectives.
Business continuity plan
Documented continuity and disaster-recovery procedures.
Access & authentication
Controls over who can access what.
Role-based access (workspaces)
Owner/admin/member roles and isolated client workspaces for agencies.
Signed, httpOnly sessions
Authentication uses signed, httpOnly cookies.
SSO / SAML
Enterprise single sign-on. Talk to us if this is a requirement.
Audit log
Admin-visible activity trail across the workspace.
Agent & API access
What a workspace key can do once it is in a client you do not control — the question every developer asks before pasting one into an agent.
Bearer keys, stored as hashes
A tcz_live_ key is shown once at creation; only its SHA-256 is persisted, so it cannot be read back out of our database by us or by anyone who copies it.
Revocation, and a record of use
Any key can be revoked from Settings, which takes effect on the next request. Each key records when it was last used, and key creation and revocation appear in the workspace activity log.
An agent surface that cannot act alone
Every MCP tool is read-only except the 15 propose_* tools, which queue an action for a person to approve, and connect_linkedin_account, add_do_not_contact, pause_campaign and install_product, which change only this workspace. The LinkedIn tools run through a connected sender account and are rate limited to 30 calls per 5 minutes per workspace, because an agent retrying in a loop is the request pattern that gets an account restricted. No tool sends an invite, a message, a comment, a follow or a like by itself: an agent proposes, a person approves in the console, and the action goes out under the account's Smart Limits. The do-not-contact list and the one-person-one-account rule are checked when the agent proposes and again before LinkedIn is called.
Workspace scoping
A key resolves to exactly one workspace and cannot see another, which is what keeps an agency's client workspaces separate under one login.
Per-key scopes and expiry
Today a key carries the full access its interface allows and does not expire. Narrower scopes and time-limited keys are not shipped — rotate manually if that matters to you.
Signed webhook payloads
Deliveries carry an x-topclozer-event header and no signature. Treat the endpoint URL as a secret and verify anything consequential with a read before acting on it.
Compliance & certifications
We only claim what's true. Here's exactly where we stand.
SOC 2
On our roadmap. Not yet certified — we won't claim otherwise.
ISO 27001
Under evaluation for a future stage.
Responsible disclosure
Report a vulnerability to security@topclozer.com; we'll acknowledge and work with you in good faith.
Need something for procurement?
Security questionnaires, a DPA, or a subprocessor list — email security@topclozer.com and we'll help you evaluate us.
security@topclozer.com