Skip to main content
TruStacks

Legal

TruStacks Product Privacy Policy

Version: 1.0 (Beta) · Last updated: 2026-10-23 Controller: TruStacks, Inc., a Delaware corporation ("TruStacks", "we", "us")

This policy covers the hosted TruStacks product: app.trustacks.com, api.trustacks.com, and sign-in at auth.trustacks.com. The marketing site has its own notice at https://trustacks.com/legal/privacy.

The short version

  • Your source code stays in your cluster. The TruStacks runner reads your repositories inside your own Kubernetes cluster. We never clone or store your repositories. Some derived content does reach us (see below).
  • Code goes to your AI provider under your key. The agents send repository content to the language-model provider you configure (Anthropic, or OpenRouter routing to Anthropic models), using your API key, under your agreement with that provider.
  • No ads, no trackers, no selling data. The product sets no cookies and uses no third-party analytics.
  • We don't train AI models on your content.

1. What we collect

Account and workspace

  • Your account: your email address and a sign-in identifier. Your password and sign-in records are held by our self-hosted identity service (Zitadel), on our own infrastructure; we never see your password.
  • Your workspace: its name, plan and subscription status, and, if you choose to tell us during setup, company name, team size, primary use case, how you heard about us, and your role.
  • Invitations: the email address of each person invited, who invited them, and the invitation's status.
  • Billing: Stripe customer and subscription identifiers, and subscription status. Stripe processes your card; we never see or store card numbers.
  • Signup records: the email and workspace name you signed up with, linked to the Stripe checkout and to your new account.

Content you and your runner send us

The runner runs in your cluster and sends us results, not repositories:

  • Analyses: a structured description of each service (framework, language, build and test setup), and the run's event log. The event log records which files were read and their sizes, not their contents.
  • Proposals: the full text of the delivery artifacts the agents generate (CI workflows, Dockerfiles, Helm or Kustomize files, ArgoCD manifests), notes on customer content the agent preserved, and the pull request's link and state.
  • Findings: security findings from your scanners and connected sources, including the full SARIF result when you upload one. SARIF can include code snippets, depending on your scanner.
  • GitHub observations: with your read-only token, the runner reports workflow runs, Dependabot, code-scanning and secret-scanning alerts, and repository settings relevant to your delivery posture.
  • Questions you ask TruStacks (Ask) and the answers, with references to the records each answer used.
  • Rules and drafts you write with the Coordinator.
  • Deployment and policy status: ArgoCD sync and health, and which policy your runner is enforcing.
  • Your environment profile: we read it from your platform repository through the GitHub App when needed. We don't store the file; we store the results derived from it, such as gap analyses and maturity scores.
  • Your LLM API key: used only to deliver it, encrypted, to your runner. We keep only its first characters to show you which key is set; the full key is held briefly in memory during delivery and is never written to our database.

What we don't collect

  • Your repositories as a whole, or your source code beyond what's described above.
  • Your password, or card details.
  • Prompts sent to your AI provider (we keep results, not the raw prompts).
  • Cookies, advertising identifiers, or analytics on your activity in the product.

2. How we use it

To run the Service for you: sign-in, your workspace, agents, policy checks, results, billing, and account emails (setting a password, invitations, password resets). Also to secure the Service, provide support, and meet legal obligations.

We don't sell or rent personal data, use it for advertising, or train AI models on your content.

3. Who processes it (subprocessors)

ProviderWhat forWhere
Google CloudHosting the Service, database, secretsUnited States (us-east4)
StripePayments and subscriptionsSee Stripe's privacy policy
SendGrid (Twilio)Sending account emailsUnited States
GitHubThe TruStacks GitHub App you install: repository access you grantSee GitHub's privacy statement

Your AI provider (Anthropic or OpenRouter) receives repository content from your runner, under your API key and your contract with them. It acts for you, not for us. Check their terms for retention and training.

If you use our support Discord (including to send us a privacy or security request), Discord processes your messages and account details under its own privacy policy, as an independent provider rather than for us, and may do so outside your country. If you'd rather not use Discord for a request, say so in a short message and we'll arrange another way to reach you.

We'll update this list before a new subprocessor starts handling your personal data, and announce it in the support Discord.

4. Where it's stored, and how it's protected

The Service runs on Google Cloud in the United States. Connections are encrypted in transit (TLS). Credentials sent to your runner are sealed so that only that runner can open them. Each workspace is isolated from every other. Our images and policy are signed. Data at rest, including database backups, is encrypted by Google Cloud.

If you're outside the United States, your data is transferred to and processed in the United States. If your organisation needs a data processing agreement, ask us.

5. How long we keep it

Today, we keep your workspace's data for as long as your workspace exists, and delete it when you ask us to. Deleted data may remain in encrypted database backups until those backups expire. We'll update this section, with notice, before we start deleting data automatically by age.

Account emails we send are kept by our email provider under its own retention.

6. Your choices and rights

  • See, correct or delete your data: ask us through support. Deleting a workspace deletes its data, including its signup record.
  • Remove access: uninstall the TruStacks GitHub App, remove your runner, or revoke your LLM key at your provider, at any time.
  • Cancel billing: Settings → Billing.
  • If you're in the EU or UK (GDPR) or California (CCPA/CPRA), you have rights to access, correct, delete, port and object. We honour these wherever you live, and respond within thirty (30) days.

7. Browser storage

The product sets no cookies. Your browser stores:

  • your sign-in session, for the current tab (session storage), until you sign out or close the tab;
  • your recent chat with TruStacks, kept in local storage for 24 hours so a refresh doesn't lose it, including the text of your questions;
  • small preference flags, such as whether you've seen the setup guide.

8. Children

The Service is for businesses and isn't directed at anyone under 16.

9. Changes

We'll update the version above when this policy changes, and give at least thirty (30) days' notice in the app or by email for material changes. We won't use data we already hold in a materially new way without telling you first.

10. Contact

Everything goes through the TruStacks support Discord, https://discord.gg/NSpqYrMa2p.

  • Privacy requests and questions: message a TruStacks team member directly, so your request stays private.
  • Security reports: message a TruStacks team member directly. Please don't post vulnerabilities in a public channel.