Privacy policy

Last updated 22 November 2026

SendCrew ("we", "us") runs LinkedIn actions for AI agents on behalf of our customers. We are an execution service, not a profile database: we keep only what a workspace needs to run its own outreach, and we never sell or share personal data across customers.

This policy covers sendcrew.io, the SendCrew dashboard, API, MCP server and Chrome extension.

Two kinds of people

  • Customers and their team members, who sign up and use SendCrew. For their account data we are the controller.
  • Contacts, the LinkedIn members our customers reach out to. Our customer decides who to contact and why; for that data the customer is the controller and we process it on their instructions.

What we collect

  • Account data: name, email, password hash or Google sign-in identifier, organisation and workspace names, roles.
  • Waitlist: the email address you give us on the landing page.
  • Connected LinkedIn accounts ("senders"): the LinkedIn session captured by our Chrome extension, the account's name, profile URL, timezone and health. Session cookies are encrypted at rest (AES-256-GCM), are never logged, and are never returned by our API or shown in the dashboard.
  • Outreach data: the actions your agents queue (invites, messages, replies and their text), the contacts they target (LinkedIn identifier and the few fields needed to avoid contacting someone twice), and the message threads we sync from your senders' inboxes.
  • Billing: handled by Stripe. We store your plan, Stripe customer and subscription ids; we never see full card numbers.
  • How you found us: the campaign tags (UTM parameters) and referring website of your first visit, saved to your account when you sign up.
  • Technical data: API request logs, IP addresses and error logs used to run, secure and debug the service.

We don't use advertising trackers. Besides the cookies that keep you signed in, we use Google Analytics to count visits and sign-ups (with ad features switched off). In the EEA, the UK and Switzerland its cookies are only set if you allow them in the cookie banner. Analytics never receive your LinkedIn data or your contacts. Feedback you send through the in-app feedback widget is handled by UserJot.

Why we use it

  • To provide the service: queue and run your actions, sync your inbox, send webhooks, and show you results.
  • To protect your LinkedIn accounts: rate limits, warmup, duplicate checks and pausing a sender when LinkedIn raises a checkpoint.
  • To bill you, provide support, and send service emails such as sign-in links, invites and sender alerts.
  • To keep the service secure and meet legal obligations.

The legal bases are performing our contract with you, our legitimate interest in running a secure service, and legal obligations. Customers are responsible for having a lawful basis for contacting the people their agents reach.

Retention and deletion

  • Profile data fetched from LinkedIn is deleted after 30 days.
  • Disconnecting a sender deletes its session and the data held only for it.
  • When you ask us to delete your account or a workspace, we delete its data. Backups roll off within 30 days.
  • Billing records are kept as long as tax law requires.

Who processes data for us

We use these providers to run SendCrew, under contracts that limit them to providing their service:

  • Our cloud hosting and database provider, and Cloudflare (DNS, network protection, backup storage).
  • Trigger.dev (background job processing).
  • Stripe (payments).
  • Google (optional sign-in, and Google Analytics for site visits; its cookies are consent-gated in the EEA, UK and Switzerland).
  • UserJot (in-app feedback and roadmap widget; receives your name, email and organisation name when you use it).
  • Our transactional email provider.
  • Proxy providers, which route each sender's traffic through a fixed IP address.

Some of these providers process data outside your country. Where required we rely on standard contractual clauses or equivalent safeguards.

Your rights

You can ask to access, correct, export or delete your personal data, or object to how we use it, by emailing [email protected]. If you were contacted through SendCrew and want your data removed, email us with your LinkedIn profile URL; we will delete it and pass the request to the customer concerned. You may also complain to your data protection authority.

Security

Traffic between you and SendCrew is encrypted, session secrets are encrypted at rest, API keys are stored hashed, and every workspace's data is kept separate from every other's.

Changes

We will post changes here and update the date above. For significant changes we will also email account owners.