Brain Agents AI

What happens on disconnect

You can leave Brain Agents AI cleanly. There is no contract that prevents disconnection, no penalty for leaving, no data we keep beyond defined retention windows. This page describes exactly what happens in each case.

Summary

| Scenario | What the customer does | What happens | | --- | --- | --- | | Disconnect one cloud (out of multiple) | Removes the IAM binding, IAM role, or Lighthouse delegation that grants Brain Agents AI read access to that cloud's billing export | Soft-delete is immediate. A background purge removes that cloud's data from BigQuery. Other connected clouds keep running. | | Disconnect all clouds, keep account | Removes all cloud-side bindings | Ingestion stops. Historical data already ingested remains visible until purged. The account stays alive and can reconnect at any time. | | Cancel subscription | Cancels via Stripe (or via in-app billing settings) | A 30-day reactivation window begins, during which all data is preserved. After 30 days, data is permanently deleted. | | Delete workspace | Initiated from workspace settings by an Owner | A 7-day cooling period, then a 90-day soft-delete window. After 97 days, deletion is permanent. |

Scenario 1: Disconnect one cloud while keeping others

Action. Cloud-side. For GCP, the customer removes the IAM binding that granted read access to the BigQuery billing export dataset. For AWS, the customer detaches or deletes the IAM role used for the CUR export. For Azure, the customer removes the Lighthouse delegation. See /security/data-flow for the per-cloud access model.

Immediate. The next sync attempt fails because the access we held is gone. The connection is marked disconnected and no new data ingests from that cloud.

Background. A purge job removes that cloud's data from the workspace's BigQuery dataset on a per-table basis. Other connected clouds in the same workspace keep ingesting and remain queryable.

Permanent deletion. Billing data removed from BigQuery once the purge job completes. Raw billing snapshots in Google Cloud Storage are deleted no later than 90 days after they were written, per the standard GCS lifecycle policy.

Reverse. Reconnect at any time by re-granting the cloud-side access and reattaching through the in-app connection flow. No waiting period, no penalty.

Scenario 2: Disconnect all clouds, keep the account

Action. The customer removes every cloud-side binding but does not cancel the subscription or delete the workspace.

Immediate. All ingestion stops. The product becomes effectively read-only against the data last ingested: existing dashboards continue to render historical data, but no new line items, recommendations, or KPIs are added.

Background. Each disconnected cloud follows the per-cloud purge in Scenario 1. After purges complete, dashboards have no data to render and show empty states.

Permanent deletion. Per-cloud BigQuery data after each purge completes; GCS snapshots after the 90-day lifecycle. Account, workspace configuration, user records, and audit logs remain in place.

Reverse. Reconnect any cloud at any time. Ingestion resumes from the reconnect point forward, with a standard 90-day backfill on the reconnected cloud (subject to that cloud's own data availability).

Scenario 3: Cancel subscription

Action. Initiated through in-app billing settings, which writes the cancellation back to Stripe. No conversation required.

Immediate. The subscription is marked cancelled in Stripe. Access continues through the end of the current paid period. Within 7 days of the initial paid signup, a full refund is available on request to privacy@brainagents.ai; outside that window, the prepaid period is not refunded.

Background. When the paid period ends, a 30-day reactivation window begins. All workspace data, cloud connections, dashboards, and configuration remain in place. Reactivation is a standard re-subscribe through Stripe and restores access without re-onboarding.

Permanent deletion. After the 30-day window expires with no reactivation, the workspace and all associated data are permanently deleted: BigQuery datasets, Firestore documents, and any remaining GCS snapshots not already aged out by the 90-day lifecycle.

Reverse. Within 30 days, re-subscribe through Stripe. After 30 days, the customer is treated as new (see "Re-onboarding" below).

Scenario 4: Delete workspace

Action. Initiated by an Owner from workspace settings. Admins are notified by email and any Admin can cancel during the cooling period.

Immediate. A 7-day cooling period begins. The workspace remains fully active; deletion can be cancelled with one click. This is intentional friction between the click and the loss.

Background. After the 7-day cooling period, the workspace is soft-deleted. Data is removed from normal access paths but is retained for an additional 90 days, during which support can restore the workspace on request to privacy@brainagents.ai.

Permanent deletion. 97 days after deletion is triggered (7-day cooling plus 90-day soft-delete), the workspace and all associated data are permanently and irreversibly deleted by an automated cleanup job: BigQuery datasets, Firestore documents, audit logs scoped to the workspace's data, and any remaining GCS snapshots.

Reverse. Cancel during the 7-day cooling period from workspace settings. During the 90-day soft-delete window, contact privacy@brainagents.ai to request restoration. After 97 days, restoration is no longer possible.

What you lose by disconnecting

We are direct about this so the trade-off is clear.

  • Continued ingestion from the disconnected cloud or clouds stops. No new line items, recommendations, or KPI updates from that source.
  • Historical data already ingested remains visible until the background purge completes. This is a short window, not an indefinite one.
  • Agent insights against the disconnected cloud become stale and are removed once the underlying data is purged. Cost Scout, Savings Advisor, and the AI Cost Analyst rely on current ingested data.
  • Cross-cloud comparisons stop including the disconnected cloud as soon as the purge completes.

You can reconnect at any time and resume ingestion. There is no penalty and no waiting period.

What stays behind

When data is deleted under any of the scenarios above, two narrow categories of information may persist:

  • Audit logs related to access events. Cloud Audit Logs that record administrative and data-access events are retained per security and compliance requirements. These logs do not contain customer billing content; they record who did what and when.
  • Anonymized aggregate statistics, only if the customer opted into benchmarking. Benchmarking is opt-in by design. A workspace is never included in cross-customer aggregates by default. If a customer opts in, only de-identified, aggregated metrics persist beyond deletion. No row-level data and no workspace-attributable data is retained.

Nothing else persists. We do not retain raw billing data, recommendations, dashboards, agent outputs, or workspace configuration past the windows above.

How to verify deletion

A customer can request written confirmation of deletion at any point after a deletion has occurred. Email privacy@brainagents.ai from the address associated with the account, identify the workspace, and request a deletion confirmation. We log every deletion event with a timestamp and respond with written confirmation, including the date the deletion completed.

Re-onboarding

Within 30 days of subscription cancellation, no re-onboarding is required. Re-subscribe through Stripe and the workspace, cloud connections, dashboards, and historical data all resume in place.

After 30 days from subscription cancellation, or after a workspace deletion has completed, the customer is treated as new. A new account, new workspace, and new cloud connections must be created. Historical data from the prior account is gone and cannot be recovered.

Related pages

Contact

For deletion-related questions and confirmation requests: privacy@brainagents.ai. For security questions and vulnerability disclosures: security@brainagents.ai.

Last updated: April 28, 2026.