Ethical Stack.

Gemini Code Assist

IDE coding assistant with chat, completion, code transformation and agent features.

Score calculation

(4 + 8 + 3 + 7 + 3) ÷ 5 = 5.0

Pressure target: −1 overall point. Overall score: 4.0/10.

5 of six dimensions rated. Unrated dimensions are excluded from the average.

Full scoring method ↗
Setup details

Gemini Code Assist Standard and Enterprise in supported IDEs. Prompts and relevant code context are processed by Google Cloud; context and optional logging are configurable.

What fits your needs

Gemini Code Assist Standard and Enterprise in supported IDEs. Prompts and relevant code context are processed by Google Cloud; context and optional logging are configurable.

IDE coding help

Use chat, inline completions, code transformation and agent mode in supported IDEs.

See the evidence

Enterprise controls

Connect a Cloud project and configure access or VPC service controls.

See the evidence
Tradeoffs to expect

Requests go to Google Cloud

Prompt text and selected code context are processed by Google.

See the evidence

Regionality is not guaranteed

Google says regional processing is typical but not guaranteed.

See the evidence
How to switch

Exclude files

Use.aiexclude or.gitignore to keep local files out of context.

See the evidence

Change model route

Using another harness/provider changes the data path and training data assessment.

See the evidence
Practical questions

Review Cloud Logging

Check whether prompt and response logging is configured.

See the evidence

Inspect model/context

Review the selected Gemini model and attached context.

See the evidence

Energy practices

4/10↑

Gemini Code Assist documents a stateless cloud service and context controls, but no energy footprint.

See the evidence

Model choice, context exclusions and optional logging are operational controls and do not measure energy or emissions.

1 + 1 reporting + 0 electricity + 2 controls = 4/10. This grades documented practices and transparency.

No task energy, water, or regional electricity data is published.

Reporting1/3
Google documents the cloud processing boundary but no energy accounting.
Electricity sourcing0/3
No product-level electricity sourcing is reported.
Resource controls2/3
Users can select model/context and exclude files, without measured energy savings.

Water disclosure

Water reporting has not been assessed for this choice.

Training data

—Depends on the model↑

Gemini Code Assist uses Gemini models but does not publish a complete training dataset rights manifest.

See the evidence

Google states that customer data is not used to train models without permission and provides citations for long direct code matches. Those commitments don’t confirm permission covering all training data for model pretraining.

The exact model version, source inventory, dataset licensing and removal process are not fully disclosed.

Your data & privacy

8/10↑

For Standard and Enterprise, Google says prompts and code context are Customer Data and the stateless service does not store prompts and responses unless logging is configured.

See the evidence

Requests include prompts, responses and nearby code context. Google says the stateless API does not store prompts and responses by default, allows Cloud Logging, and does not train on customer data without permission. Processing region is not guaranteed.

This covers Standard and Enterprise, not consumer routes. Telemetry is separate and processing may not stay in a requested region.

Openness

3/10↑

Gemini Code Assist is a managed Google Cloud service with IDE integrations and project governance controls.

See the evidence

The service offers IDE chat and agent features with cloud processing and optional VPC controls. It is not presented as self-hosted software.

The service code and complete model-training data are not exposed in these sources.

Worker protections

7/10↑

Google has a supplier-responsibility system with worker surveys, third-party audits and grievance access, alongside current worker reports describing pay, pace and support concerns among AI raters.

See the evidence

Google says its Supplier Code applies to supplier and staffing-partner work, extended workers can report concerns anonymously through Google’s helpline, and its 2026 FY2025 report describes supplier audits and worker surveys with follow-up. Separately, Alphabet Workers Union-CWA’s 2025 report and raters’ pay-parity letter describe low pay, benefits gaps, insecure contracts and inadequate task-time; The Guardian documented raters’ accounts of rapid task timing, distressing moderation work and limited mental-health support, while Google says suppliers employ these workers and set their employment terms. The company system merits credit, but findings from hardware/supplier programs do not prove every AI rater is covered or remedied. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 2 pay & conditions + 2 worker voice & remedy + 2 evidence & follow-through = 7/10. This grades documented worker safeguards, not a measured rate of mistreatment.

The FY2025 supplier program is risk-prioritized and does not disclose whether its survey/audit cohort included GlobalLogic AI raters; Google’s own policy places wage/benefit setting with suppliers. Worker reports are specific but are not an adjudicated finding about every supplier or rater.

Pay & conditions2/3
Supplier standards and vetting apply to extended workforce and current AI-rater testimony documents concrete working conditions, but rates, coverage and implementation vary by supplier and some worker evidence is self-reported.
Worker voice & remedy2/3
Extended workers have access to Google’s anonymous helpline and supplier feedback channels; union organizing and direct worker reports document voice, though they also describe limited influence over conditions.
Evidence & follow-through2/3
Google reports third-party supplier audits, worker surveys, follow-ups and program improvements; these are company-reported and the published figures don’t confirm coverage of AI annotation contractors specifically.
Workers rubric ↗

Military ties

3/10Broad defense ties↑

Google has a current DoD AI/cloud contract and has demonstrated military training/exercise support, but the reviewed evidence doesn’t confirm combat targeting or strike-intelligence deployment.

See the evidence

Google Public Sector describes a $200 million ceiling DoD CDAO contract and access to AI/cloud capabilities, including classified environments. Its Mobility Guardian 2025 account describes an Air Force exercise/edge workflow processing air-defense data and generating insights for counter-UAS triggers; this is exercise and support evidence, not proof that Google AI selected targets or supplied combat intelligence in an actual operation. Google’s current AI Principles include human oversight and safety commitments but no categorical military-use prohibition. The broad DoD contract leaves substantial enablement potential, so classify as broad-defense and apply the cap; do not call the exercise direct combat use. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

1 + 0 use restrictions + 1 enforcement & oversight + 2 relationship disclosure = 4, capped at 3/10. Known defense ties lower this rating; safeguards can improve it within the relationship’s cap.

Public sources do not disclose all task orders, operational use outcomes, customer-enforceable use restrictions, or independent oversight. The specific models and releases used in every defense workflow are not established.

Use restrictions0/4
The current AI Principles reviewed don’t confirm a binding weapons or harmful-surveillance prohibition for defense contracts; the older 2018 weaponization commitment is not current evidence.
Enforcement & oversight1/3
Google’s public AI Principles describe human oversight and safety practices but do not disclose military-specific independent review, enforcement, or remedies.
Relationship disclosure2/2
Google names the CDAO contract, its ceiling and the Mobility Guardian exercise workflow; the named public materials disclose no actual combat mission or current contract-level safeguards.

Google documents a broad DoD AI/cloud contract and military exercise support, but no confirmed operational use for target selection, strikes, or combat intelligence. Broad-defense cap applies. The relationship limits this grade to 3/10.

Military rubric ↗

BDS targets

Pressure target↑

Google / Alphabet is named as a pressure target in the BNC’s official campaign sources. The product is developed or supplied by Google / Alphabet.

See the evidence

If following this BNC campaign is a requirement, consider alternatives to paid Google / Alphabet products where practical. Check the model and host this tool connects to as well as the company providing the tool. This label follows the named company’s campaign status; it does not claim that BDS separately reviewed this exact product. These findings concern the developer or operator. This product’s use in a particular deployment needs separate evidence.

This review covers the named company or parent in the BNC consumer/pressure guide and No Tech campaign. Lists and ownership can change.

Israel’s procurement administration says Google was selected with AWS for Nimbus public-cloud services and lists the Ministry of Defense and IDF among project partners. The Guardian’s investigation of leaked agreement documents reports that Nimbus terms limited Google’s ability to suspend service, including after alleged policy violations. Who Profits and AFSC describe cloud and AI use by military/security bodies, including surveillance-related capabilities; these are attributed research claims, not proof of Google’s role in a specific attack. Both companies denied circumventing legal obligations in response to the Guardian investigation.

How Gemini CLI is used in this relationship is not established. The government record establishes the contract and project participants; the investigative reporting describes contract controls, and research organizations make broader use claims. The reviewed evidence doesn’t show Google’s contribution to a particular operation, injury, or other specific harm.

More from Google

All sources

Side by side