TucloudLegal centerSubprocessor List
Third parties supporting authentication, payments, domains, deployments, and Kuro.
Last updated August 10, 2026Tucloud policy
This list identifies key third parties integrated into the current Tucloud services. A provider receives data only when the related feature is used. Provider locations and downstream infrastructure may vary, and provider terms and privacy notices govern their independent activities.
Purpose: account authentication, Google sign-in integration, database, and application storage. Data may include account identifiers, email, profile data, subscriptions, domain records, GitHub installation metadata, projects, deployments, and encrypted environment variable records.
Purpose: checkout, recurring subscriptions, payment confirmation, refunds, and fraud prevention. Data may include name, email, billing details, payment credentials handled directly by the provider, transaction identifiers, subscription status, and billing events.
Purpose: repository connection, installation authorization, build workflows, deployments, commit and run metadata, and deployment logs. Data may include GitHub account and installation identifiers, selected repositories, branches, commit metadata, workflow runs, and environment secret names and values submitted to GitHub for deployment.
Purpose: optional account authentication. Data may include the provider account identifier, email, display name, avatar, and authentication metadata made available by the user and provider. Google account data is not used for advertising and Tucloud does not request Google contacts or Drive files.
Purpose: domain availability, pricing, registration, renewal, contact privacy, and lifecycle management. Data may include domain name, registrant contact information, registration period, nameservers, and order identifiers. Relevant registries and registry operators also receive required registration data.
Purpose: AI planning, code and interface generation, revision, conversation, and summaries. The current embedded Tucloud and Dashboard assistants use Opera Aria services. Data may include prompts, instructions, generated output, and relevant excerpts of existing project code.
Purpose: hosting, network delivery, DNS verification, TLS certificates, system administration, backups, and security. Certificate authorities such as Let's Encrypt receive domain names and technical validation data. Infrastructure providers process hosted content, network addresses, logs, and operational metadata as necessary to deliver the service.
Purpose: provisioning and administration of hosting accounts, domains, DNS, mailboxes, usage limits, and service status. Data may include account email, hosting username, domain names, mailbox identifiers, resource usage, and operational metadata.
We update this list when integrations materially change. Questions or reasonable objections concerning a subprocessor may be sent to legal@tucloud.app.