Subprocessors
Last reviewed 6 October 2026
The organization operating this service runs Kinetiq on Google Cloud in a single region and uses the subprocessors below to provide it. Each receives only the personal data its purpose needs.
Current subprocessors
| Service | Provider | Purpose | Region |
|---|---|---|---|
| Cloud Run | Google LLC (Google Cloud) | Runs the web console, the API, the background worker and database migrations. | us-central1 (Iowa, United States) |
| Cloud SQL for PostgreSQL | Google LLC (Google Cloud) | The primary database, holding all customer data. | us-central1 (Iowa, United States) |
| Memorystore for Redis | Google LLC (Google Cloud) | Job queues and short-lived records used to stop abuse, which expire within a day. | us-central1 (Iowa, United States) |
| Compute Engine | Google LLC (Google Cloud) | A virtual machine running a mail catcher, reachable only from the service's private network. It receives the emails the service sends and holds them; no mail leaves it. | us-central1 (Iowa, United States) |
| Cloud Storage | Google LLC (Google Cloud) | Active. Holds organization export files, the full copy of an organization's data its owner requests, in a private bucket; an export can be downloaded for 24 hours after it is ready. | us-central1 (Iowa, United States) |
| Cloud Build | Google LLC (Google Cloud) | Builds the service's container images from source. It handles code, not customer data. | us-central1 (Iowa, United States) |
| Secret Manager | Google LLC (Google Cloud) | Holds the encryption key, the email hashing key and database credentials. | us-central1 (Iowa, United States) |
| Cloud Logging | Google LLC (Google Cloud) | Application and access logs. The application never writes email addresses to its logs. | us-central1 (Iowa, United States) |
| Payment processing | Stripe, Inc. | Subscription billing for the customer's account. It receives the billing contact name, email address and subscription state, never fan data. Active only when billing is configured for the service. | United States |
When a customer connects its own systems by webhook, the messages go to the endpoints the customer chooses. Those systems are the customer's, not subprocessors of the service.
Planned
| Service | Purpose and status |
|---|---|
| Email delivery | Planned: enabled when a relay is configured. An email relay would deliver the emails the service sends, such as sign-in links, fan confirmations and offers, receiving the recipient's email address and the message. Until then, no email leaves the service. |
| AI model provider | Will answer questions in the Kinetiq assistant. Not yet deployed: no customer data is sent to it today. It will be named on this page before it processes any customer data. |
Changes
The organization operating this service updates this page before a new subprocessor begins processing personal data. Customers are notified 30 days before a new subprocessor processes their data, so that a customer can object as their data processing addendum provides.