Ekaya Cloud Data Residency Statement
Version 1.1, effective 2026-10-13.
This Data Residency Statement describes where Ekaya Inc, a Delaware corporation ("Ekaya"), whose address is 1112 Montana Ave #414, Santa Monica, CA 90403, keeps and processes the data of an Ekaya Cloud Project in a given Region. It forms part of the Ekaya Cloud Terms of Service and the Ekaya Cloud Data Processing Agreement. This statement covers Ekaya Cloud only. It does not apply to Ekaya Enterprise or to any Ekaya software that a customer runs in its own environment.
United States (us-central1)
| Field | Value |
|---|---|
| Region name | United States (GCP us-central1), the name the console shows |
| Region code | us-central1 |
| Cloud provider and location | Google Cloud Platform, region us-central1, Iowa, United States |
| Hosts | Ekaya Admin, Gateway and Data API: https://us-central1.ekaya.ai; the console is https://us.ekaya.ai |
| Live Project data | A Project's live data stays in the Region: Managed Project Databases are Cloud SQL instances in us-central1 with no replicas; Ekaya's platform metadata database, which holds Project configuration, encrypted datasource credentials, Requests, ontology and audit records, is in us-central1; the Request Service database, which holds sealed connection credentials and execution records, is in us-central1. The control plane is outside this commitment. Ekaya Cloud's control plane (Central) is a single deployment, not one per Region: its functions and its Firestore database, which hold Projects, membership, billing configuration, invitations and attribution records, run in us-central1 with point-in-time recovery, but that location is not a Region commitment. |
| Snapshots | None exist. Ekaya does not take snapshots of Project databases. If it begins to, they will stay in the Project's Region. |
| Backups | Managed Project Databases have no backups. Backups of Ekaya's platform metadata database and of the Request Service database are kept in us-central1. The control-plane Firestore database has point-in-time recovery enabled, and its recovery copies expire at the end of that recovery window. |
| Logs | Service logs are held in Google Cloud's default logging location, which Ekaya has not pinned to the Region. |
| Processing outside the Region | (a) Infrastructure secrets use Google's automatic replication, so Google chooses where they are stored; they are credentials for Ekaya's own infrastructure, not Project data. (b) Google's global load balancers and Firebase Hosting terminate TLS at Google edge locations, and the demo BigQuery datasets use the US multi-region; neither holds Project data. (c) Sign-in uses Google Identity Platform, a Google global service. (d) Service datasources connected through Composio (Sampark, Inc. dba Composio): the connection credentials are held at Composio and approved Requests to those services pass through Composio's proxy; Composio's data processing agreement states no location (Ekaya Cloud Subprocessors list, Part A). (e) Service email (Twilio SendGrid), payments (Stripe), console analytics and advertising measurement (Google Analytics and Google Ads) and support email (Google Workspace) process account, billing and usage data, and message content, outside the Region (Ekaya Cloud Subprocessors list, Part B). (f) The customer's own agent sends the data it reads to the model provider the customer chose; that is the customer's transfer, under the customer's identity (Terms Section 3.5). (g) Ekaya's control plane runs in us-central1 and is outside this commitment, as the "Live Project data" row says. |
| Ekaya-side model providers | None. Ekaya Cloud sends Project data to no model provider that Ekaya operates or engages; adding one would change this statement first (Ekaya Cloud Subprocessors list, Part C). |
| Cross-Region movement | Ekaya does not move or replicate a Project's data to another Region unless the Project's owner opts in by written request to support@ekaya.ai. Nothing replicates Project data across Regions today. No other Region exists, and a Project's Region cannot be changed after creation. |
| Effective date | 2026-10-13 |
Changes
Ekaya gives at least 30 days' notice of a change to this statement that moves Project data to a new location, by updating it and emailing the owners of active Projects in the Region, as the Data Processing Agreement provides for new subprocessors.