KindgiWhat your agents do is your business. Doing it well is ours. Schedule a callBook a call (opens in a new tab)

Kindgi Cloud: sub-processors

Last updated October 18, 2026

These are the companies that process personal data for us when we run Kindgi Cloud for you. The data processing addendum (section 6) says how we choose them and how we tell you about a new one.

Where your data is: in the USA, in Google Cloud’s us-central1 region (Iowa), held by Kindgi Inc., a US company.

Sub-processors

CompanyWhat forWhere
Google Cloud (Google LLC, USA)Hosting Kindgi Cloudus-central1 (Iowa). Database backups: the us multi-region. Logs: us-central1.
SendGrid (Twilio Inc., USA)Sending Kindgi Cloud’s emailsUSA
Cloudflare (Cloudflare, Inc., USA)The bot check (Turnstile) on the sign-up and sign-in pagesCloudflare’s global network
Google Workspace (Google LLC, USA)Our email, for support conversations you startGoogle’s locations

What each one processes

  • Google Cloud runs:

    • the servers and your packs’ services;
    • the database and its backups;
    • the encryption keys and secrets;
    • image builds and storage;
    • the load balancer and firewall;
    • logs and monitoring.

    It holds everything in your workspace (the addendum’s Annex I), encrypted at rest.

  • SendGrid sends:

    • sign-in links: the recipient’s email address and the link;
    • “an approval is waiting” emails to reviewers:
      • the recipient’s email address;
      • the approval’s title, which your pack sets and which can name a person;
      • its project’s name;
      • the reviewer role it needs;
      • when it was asked;
      • a link.

    What the approval is about (its context, a tool call’s arguments, a run’s input) never goes in an email. It stays behind sign-in.

  • Cloudflare sees the visitor’s IP address and browser signals at sign-up and sign-in. It uses them only to tell people from bots (its Turnstile privacy addendum).

  • Google Workspace holds whatever you send us by email.

Each sub-processor is bound by a written contract with us that protects your data at least as well as the addendum. Where one processes data from the EU, the UK or Switzerland outside those places, its contract uses the EU standard contractual clauses, or another safeguard the GDPR allows.

Not on this list, and why

  • The services your packs call: your model provider, under your own key; your client’s store or site; MCP servers and webhook receivers you register.
    • Your packs send them data on your instruction, under your own agreement with each.
    • They aren’t our sub-processors.
  • Sign-in providers: Google, Microsoft, GitHub, or your own identity provider. They tell us who someone is, when that person or your organization chooses them, under their own terms.
  • Software we run ourselves inside Kindgi Cloud: for example the authorization service (OpenFGA) and the sign-in library. No third party operates them.
  • Our own billing: Stripe runs your organization’s subscription and holds its payment card. That’s your account’s data, which we control, not data we process for you. See Privacy at Kindgi.

Changes

Before a new sub-processor starts processing your data, we tell you at least 30 days ahead:

  • by email to your workspace’s admins and billing contact;
  • by updating this page, with its date at the top.

If you object on reasonable data protection grounds within those 30 days, we’ll talk it through. If we can’t resolve it, you can stop using the affected part of Kindgi Cloud, or close your account, without penalty (the addendum, section 6).

Urgent replacements: if we must replace a sub-processor urgently, for security or because it stopped serving us, we tell you as soon as we can. You have the same right to object.

Questions: contact@kindgi.com (subject: “Privacy”).