Security and data

How GraphKit protects your data: encryption, tenant isolation, sessions and keys, the audit log, data retention, and the DPA.

Encryption

  • In transit. Every request to GraphKit, including on custom domains, is served over HTTPS through Cloudflare. The servers have no public inbound ports: traffic reaches them only through an encrypted tunnel. Database connections are encrypted and verify the server certificate.
  • At rest. Secrets GraphKit holds for you (webhook signing secrets, email platform API keys and OAuth tokens) are encrypted at the application layer with AES-256-GCM and versioned keys, so keys can be rotated. Each secret is bound to its record and cannot be moved to another one. Storage and backups are encrypted by the infrastructure providers.
  • Hashed, not stored. Passwords are hashed with argon2id. Session tokens, API keys, invitation links and report links are stored only as hashes, so a copy of the database cannot be used to sign in or call the API.

Your social accounts

GraphKit stores no passwords, cookies or session tokens for your LinkedIn, Instagram, WhatsApp, Telegram or Facebook accounts. Accounts connect on a screen run by GraphKit's connection partner, which holds the session. Only the account's owner should connect it, after confirming the connect statements.

GraphKit's logs of calls to the connection partner record the operation, status and timing only: no message bodies, search terms or tokens.

Tenant isolation

Every account, lead, list, campaign, conversation, API key and webhook belongs to exactly one workspace. Every query for your data is scoped to a workspace the caller belongs to; a record is never read by its id alone. Requests for another customer's data return "not found", so its existence is not revealed. Automated tests send requests from one organization against another's resources and expect "not found" for every one.

Custom domains decide which brand a page shows, never what someone can access: access comes only from the signed-in session or API key.

Suppressions and lead data are never pooled between customers. There is no shared database of profiles.

Sessions and access

  • Session cookies are HttpOnly, Secure and SameSite=Lax, and every change made from the web app needs an anti-forgery header.
  • Sign-in and sign-up are rate limited.
  • Every request is checked on the server against the caller's permissions, which come from built-in or custom roles. Requests to an endpoint that has not declared its permission are refused, and automated tests check that every endpoint refuses people without its permission. See Roles and permissions.
  • Organizations can require two-factor authentication, limit sign-in methods and invite domains, suspend people and sign out members they manage. See Account security and Members.
  • API keys belong to one workspace, carry scopes and can be revoked at any time. See Authentication.

Audit log

Organization → Audit log lists every recorded action in the organization and its workspaces, and Settings → Audit log lists one workspace's. Both need the View audit log permission (Owners, Managers and workspace Admins have it). Filter by person, action, workspace, date and text, and export the filtered log as CSV (up to 10,000 rows; the export is itself recorded). Each entry shows who acted: a person, an API key, Kit or an MCP client on behalf of a person, or GraphKit itself. Recorded actions include:

  • account connections and reconnections, with the exact statements the owner confirmed, their version, IP address and user agent;
  • invitations (created, resent, accepted, revoked), role changes, suspensions, removals and ownership transfers;
  • custom roles created, edited and deleted, and security policy changes;
  • API keys created and revoked, and every change made with an API key (recorded as made by that key);
  • lead consent changes, lead and list deletions, lead exports and data exports;
  • suppressions added and removed;
  • inbox privacy changes, inbox scopes, replies sent and retried;
  • webhook endpoints disabled after repeated failures.

Brand and domain changes are recorded at organization level.

Data retention

  • Your data stays while your workspace exists. GraphKit does not delete leads or conversations on a schedule; delete what you no longer need, or ask GraphKit to delete a workspace.
  • Deleting a lead removes it with its identities, list memberships and campaign activity at once. Identity suppressions are kept, so a person who opted out stays opted out after a re-import. See Data subject requests.
  • A failed payment never deletes data. See Billing.

Roles under data protection law

For the lead data you put into GraphKit (leads, identities, messages, campaign activity), your organization is the controller and Mindroot Ltd, which operates GraphKit, is the processor. GraphKit's connection partner is a subprocessor. Mindroot Ltd is the controller for your own account, team and billing data.

Platform terms

LinkedIn, Instagram, WhatsApp, Telegram and Facebook restrict automated activity in their terms, and a network can warn, restrict or suspend an account. GraphKit reduces the risk with conservative limits, pacing, back-off, auto-pause, consent rules and opt-out handling, but it cannot remove it or reverse a restriction. See LinkedIn limits explained and Consent and opt-outs.

Reporting a vulnerability

Report security issues through the contact details on the security page.

On this page