Security

How GraphKit protects your data.

What we do to keep your workspace, your leads and your connected accounts safe, and what we will not pretend about LinkedIn.

At a glance

Secrets encrypted

Webhook secrets and integration tokens use AES-256-GCM with versioned keys.

No account passwords

Accounts connect through a hosted sign-in. GraphKit never sees the password.

Tenant isolation

Every query is scoped to a workspace. Authorisation comes from the session only.

Audit log

Sender connections, limit changes, launches and team changes are recorded.

Encryption

Traffic to GraphKit is served over HTTPS. Secrets we hold on your behalf, such as webhook signing secrets and integration tokens, are encrypted at the application layer with AES-256-GCM using versioned keys, so keys can be rotated without re-issuing every secret.

Passwords are stored as one-way hashes. Session tokens and API keys are stored hashed too: a database copy alone cannot be used to sign in or call the API.

Tenant isolation

Every lead, campaign, conversation and sender belongs to exactly one workspace. Reads and writes go through helpers that require a resolved tenant and add the workspace scope to the query, so a record is never fetched by its id alone.

Custom domains decide which brand a page shows, never what you can access: authorisation comes only from your session. Requests for another tenant's resources return "not found", so their existence is not revealed.

Accounts and access

Permissions are a fixed matrix checked on the server for every request. Roles range from agency owner and manager to client admin, campaign operator, inbox agent and viewer. Reading private conversations, managing billing, branding, API keys and webhooks are separate permissions.

Session cookies are HttpOnly, Secure and SameSite, and state-changing requests from the web app need an anti-forgery header.

Audit logs

GraphKit keeps a log of sensitive actions with the person and the time: connecting and removing senders, changing limits, launching campaigns, inviting and removing teammates, and managing API keys. Workspace admins can review it in the app.

Data protection tools

For prospect data you process in GraphKit, you are the controller and Mindroot Ltd is your processor under our data processing agreement. GraphKit gives you the tools to meet your obligations:

  • Exclusion lists that block a person from future outreach, per workspace or across your organisation.
  • Only the fields you need: names, titles, companies, profile URLs and your conversations. No email or phone enrichment.
  • No pooling of data between customers, and no resale of lead data.
  • Help with access and deletion requests: write to us and we will act on your instruction.
  • Self-serve per-person export and configurable retention periods. Planned.

Platform terms and your accounts

Please read this before you connect an account

LinkedIn's User Agreement prohibits using bots or other unauthorised automated methods to add contacts, send messages or access the service, so using GraphKit with LinkedIn may break LinkedIn's terms. Instagram, WhatsApp and Telegram have their own terms on automation and unsolicited messages. Any platform may warn, restrict or permanently suspend an account, and can block third-party tools without notice. GraphKit cannot reverse a platform's decision, and no tool can promise that an account will not be restricted. GraphKit is not affiliated with, endorsed by or approved by LinkedIn, Meta, WhatsApp or Telegram.

What we do to reduce the risk:

  • Conservative default limits per account, with strict caps on WhatsApp and Telegram.
  • Actions only inside each account's working hours.
  • WhatsApp and Telegram only for existing contacts and opt-ins, never bulk cold messaging, with STOP and UNSUBSCRIBE replies excluding the lead on every channel.
  • Only the owner of an account can connect it, and they review a short risk notice before connecting each account.
  • No fake accounts, no scraping for resale, and no CAPTCHA or two-factor bypass. Our acceptable use rules forbid them.

You remain responsible for how you use your accounts, for the messages you send, and for complying with each platform's terms and with data protection and marketing law.

Subprocessors

The third parties that process data for GraphKit, including our account-connection partner, Stripe for billing and our hosting providers, are listed on our subprocessors page.

Reporting a vulnerability

If you think you have found a security issue, email team@graphkit.com with "Security report" in the subject. Please give us reasonable time to fix it before disclosing, and do not access other customers' data or disrupt the service while testing. We will acknowledge your report and keep you updated.