Skip to main content

Buyer guide

Engineers on Personal Antigravity Plans: A Data and Terms Checklist

Personal Google accounts put company code under consumer terms, with training on interactions and account bans. How to find these engineers and move them to company terms.

Reading time
2 min read
Sources
10 cited
In this piece
Google Antigravity−16 Mixed

Find engineers using Antigravity on personal Google accounts, set company-code rules, and move them to Gemini Enterprise seats or an approved alternative. Those personal sign-ins follow consumer terms: Google uses interactions to improve products unless users change a setting, and its staff may review interactions. Google can also suspend an account whose Antigravity login is used in another tool.

When you need this

  • Engineers expense or pay for Google AI Pro or Ultra to use Antigravity on company repositories.
  • Gemini CLI users on personal plans moved to Antigravity CLI after June 18, 2026.
  • A security review asks where code and prompts from the agent go.
  • An engineer lost access after a suspected terms violation and work stopped.

Data and terms checklist

  1. Know which terms apply

    Which agreement covers each engineer's use?

    CheckThe Google Antigravity Additional Terms for personal Google accounts, and your administrator's Google Cloud terms for Gemini Enterprise seats and API keys, where the consumer terms do not apply. Under the consumer terms Google uses Interactions to improve its products and machine learning, and its employees and contractors may review them. Users can change the preference in settings or ask for deletion by email.

  2. Set the training preference or ban the route

    Is company code allowed on a personal plan at all?

    CheckA written rule. If you allow it, require the data-collection setting turned off and confirm it. Antigravity's FAQ says users can opt out from Settings, and one engineer had to accept data collection to finish installing the IDE. If you do not allow it, say so and give engineers a governed route.

  3. Account for terms risk

    What happens to a team if one account is suspended?

    CheckGoogle's terms forbid using third-party software with an Antigravity login and name suspension of Antigravity and Gemini CLI access as a remedy. Engineers report bans on suspicion of such use. Keep work recoverable in Git and avoid single points of failure on personal accounts.

  4. Check eligibility

    Can every engineer sign in?

    CheckPersonal accounts in Google's listed countries, holders 18 or older, and Google AI plans where they are sold. Google advises a gmail.com address if a Workspace account fails, which is a sign the route is built for individuals.

  5. Plan the move to company terms

    Where should these engineers work instead?

    CheckGemini Enterprise Standard or Plus seats, which include Antigravity with Google Cloud terms, code not used for training, and admin controls, or an agent your organization already licenses. Date the move and remove reimbursement for personal plans once seats exist.

Questions to settle with each team

  1. How many engineers use Antigravity on personal Google accounts, and on which repositories?
  2. Is the data-collection setting off on each of those accounts, and who checked?
  3. Does any engineer route Antigravity through another tool or proxy?
  4. What is the date by which personal-plan use on company code stops?

Red flags

  • Company code on personal accounts with data collection left on.
  • Expense reports for Google AI plans with no policy on code.
  • Proxies or wrappers that reuse an Antigravity login in other tools.
  • A team that cannot work when one engineer's account is suspended.

Products in this piece

Sources

Official documentation
7
Public source
3
  1. Google Antigravity Additional Terms of ServiceOfficial documentationantigravity.google
  2. Antigravity docs: FAQOfficial documentationantigravity.google
  3. Antigravity docs: PlansOfficial documentationantigravity.google
  4. Antigravity docs: IDE extensionsOfficial documentationantigravity.google
  5. Antigravity docs: Antigravity in Gemini EnterpriseOfficial documentationantigravity.google
  6. Google Developers Blog: Transitioning Gemini CLI to Antigravity CLI (May 19, 2026)Official documentationdevelopers.googleblog.com
  7. Google One: Google AI plansOfficial documentationone.google.com
  8. Hacker News: reading the terms before trying Antigravity on a team codebase (Nov 19, 2025)Public sourcenews.ycombinator.com
  9. Hacker News: data-collection consent during Antigravity IDE install (May 22, 2026)Public sourcenews.ycombinator.com
  10. Hacker News: a user banned on a suspected terms violation (Sep 4, 2026)Public sourcenews.ycombinator.com

Keep reading

  1. Buyer guideGoogle Antigravity Workflow PlaybookSix Antigravity setup and review habits for teams whose engineers get different results from the same agent, or whose quota runs out mid-task.
  2. Buyer guideAntigravity in Gemini Enterprise: Rollout and Controls ChecklistEditions, roles, APIs, sign-in, the admin defaults to change before day one, model approval, logging, and spend caps for a team rollout.
  3. Buyer guideGemini CLI or Antigravity CLI: Planning the DecisionCode Assist sign-in to Gemini CLI ends with each contract, while paid API keys keep working. Set every team a move date to Antigravity CLI ahead of its last renewal.
Read the research