Privacy
How General Augment handles platform, tenant, and agent data.
Last updated May 7, 2026
What we collect
General Augment processes account details, project configuration, API requests, usage records, tool execution logs, and channel metadata needed to provide the service. Tenant apps decide what end-user context they send to the platform.
How we use data
We use data to authenticate requests, run agent turns, route tool calls, store tenant-scoped memory, meter usage, debug reliability issues, and protect the platform from abuse.
Tenant isolation
Project data, credentials, memory, and logs are scoped to the tenant/app that created them. We design the platform so one tenant cannot access another tenant's data.
Credentials and secrets
Provider tokens and tool credentials should be stored through platform-managed secret paths. We do not intentionally expose secrets to model prompts or customer-facing dashboard views except one-time API key reveal flows.
Third-party services
General Augment may use infrastructure and model providers such as GCP, Vertex AI, Cloud SQL, Redis, observability tools, authentication providers, and messaging providers to operate the service.
Analytics and cookies
General Augment may use consent-gated analytics such as PostHog to understand pageviews, product events, conversion paths, and reliability. Optional advertising pixels are reserved for retargeting or campaign measurement after explicit consent.
Browser privacy signals
When a browser sends Global Privacy Control or Do Not Track, we treat it as an advertising opt-out signal and keep retargeting storage denied.
Marketing data boundaries
We do not intentionally send raw API keys, provider tokens, model prompts, tool payloads, or unredacted customer content to marketing analytics.
Your choices
You can reject non-essential cookies in the site banner. To request export, deletion, opt-out, or privacy support, contact support@generalaugment.com. This early-stage policy will evolve as the product and customer requirements mature.