Skip to content

[SSR Agent] Issue Fix (26120): Clarify privacy notice wording and selection options - #28820

Merged
joneba-google merged 1 commit into
google-gemini:mainfrom
JonE01:ssr-agent-26120
Aug 17, 2026
Merged

joneba-google merged 1 commit into
google-gemini:mainfrom
JonE01:ssr-agent-26120

Conversation

@joneba-google

Copy link
Copy Markdown
Contributor

fixes #26120
Original Issue URL: #26120

Context & Problem

The privacy notice wording was misleading and contradictory. The introductory text stated that users could opt out below, but the actual available options under the RadioButtonSelect toggle were simply "Yes" and "No", creating inconsistent and confusing framing regarding data collection permission tracking.

Detailed Changes

  • Modified CloudFreePrivacyNotice.tsx:
    • Updated selection items' labels to explicitly state "Yes, grant permission to use my data for product improvement (Opt-in)" and "No, deny permission to use my data for product improvement (Opt-out)".
    • Aligned introductory text and instructions with these options, explaining explicitly how to opt-in or opt-out.
    • Refined the prompt question to use "improve our products and services".
  • Updated tests in CloudFreePrivacyNotice.test.tsx to assert that the updated privacy notice text, prompt question, and corrected option labels render correctly.

Verification

  • Verified that all unit tests in packages/cli/src/ui/privacy/CloudFreePrivacyNotice.test.tsx pass successfully using Vitest.

@joneba-google
joneba-google requested a review from a team as a code owner August 14, 2026 20:56
@gemini-code-assist

Copy link
Copy Markdown
Contributor

Summary of Changes

Hello, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request addresses misleading and contradictory wording in the privacy notice. By refining the labels for the data collection permission options and providing clearer instructions, the changes ensure that users have a transparent understanding of how their data is used for product improvement.

Highlights

  • Privacy Notice Clarity: Updated the privacy notice labels and instructional text to clearly distinguish between opt-in and opt-out choices.
  • Test Coverage: Added a new test case to verify that the updated privacy notice text and selection labels render correctly in the UI.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize the Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counterproductive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for GitHub and other Google products, sign up here.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

@github-actions github-actions Bot added the size/m A medium sized PR label Aug 14, 2026
@github-actions

github-actions Bot commented Aug 14, 2026 •

Copy link
Copy Markdown

📊 PR Size: size/M

  • Lines changed: 52
  • Additions: +49
  • Deletions: -3
  • Files changed: 2

@google-cla

google-cla Bot commented Aug 14, 2026

Copy link
Copy Markdown

Thanks for your pull request! It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).

View this failed invocation of the CLA check for more information.

For the most up to date status, view the checks section at the bottom of the pull request.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the CloudFreePrivacyNotice component to use more descriptive opt-in and opt-out selection labels, adds an explanatory paragraph about data usage, and includes a test case to verify these changes. Feedback is provided regarding the length of the new labels, which may be truncated on standard 80-column terminals; it is recommended to use a custom renderItem to wrap the text instead of truncating it.

Comment thread packages/cli/src/ui/privacy/CloudFreePrivacyNotice.tsx Outdated
@gemini-cli gemini-cli Bot added priority/p2 Important but can be addressed in a future release. area/extensions Issues related to Gemini CLI extensions capability labels Aug 14, 2026
@joneba-google joneba-google reopened this Aug 16, 2026
…p selection options

$fixes google-gemini#26120
Original Issue URL: google-gemini#26120

### Context & Problem
The privacy notice wording was ambiguous and confusing. The introductory text stated that users could opt out below, but the actual available options under the RadioButtonSelect toggle were simply "Yes" and "No". Furthermore, because longer explicit labels can exceed standard 80-column terminal widths, default `wrap="truncate"` on `RadioButtonSelect` would truncate the critical `(Opt-in)` and `(Opt-out)` suffixes.

### Detailed Changes
- Modified [CloudFreePrivacyNotice.tsx](file:///usr/local/google/home/joneba/ssr-prototype/gcli-intern-project/packages/cli/src/ui/privacy/CloudFreePrivacyNotice.tsx):
  - Updated selection items' labels to explicitly state `"Yes, grant permission to use my data for product improvement (Opt-in)"` and `"No, deny permission to use my data for product improvement (Opt-out)"`.
  - Aligned explanatory notice text to describe how to opt-in or opt-out.
  - Refined prompt question to `"Allow Google to use this data to develop and improve our products and services?"`.
  - Added a custom `renderItem` function with `wrap="wrap"` on `RadioButtonSelect` to ensure full text wrapping on 80-column terminals without truncation.
- Updated tests in [CloudFreePrivacyNotice.test.tsx](file:///usr/local/google/home/joneba/ssr-prototype/gcli-intern-project/packages/cli/src/ui/privacy/CloudFreePrivacyNotice.test.tsx):
  - Added unit test asserting `renderItem` is provided to `RadioButtonSelect` and configures `wrap="wrap"` for all items.

### Verification
- Verified that all unit tests in `packages/cli/src/ui/privacy/CloudFreePrivacyNotice.test.tsx` pass successfully using Vitest.
@joneba-google

Copy link
Copy Markdown
Contributor Author

/gemini review

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the CloudFreePrivacyNotice component to provide more descriptive labels for the opt-in and opt-out choices, along with an explanatory paragraph. It also implements a custom renderItem function for the RadioButtonSelect component to ensure the longer option text wraps correctly without truncation. A corresponding unit test has been added to verify this behavior. There are no review comments, so I have no feedback to provide.

@joneba-google
joneba-google added this pull request to the merge queue Aug 17, 2026
Merged via the queue into google-gemini:main with commit e0e846b Aug 17, 2026
33 checks passed
@joneba-google
joneba-google deleted the ssr-agent-26120 branch August 17, 2026 17:23
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

area/extensions Issues related to Gemini CLI extensions capability priority/p2 Important but can be addressed in a future release. size/m A medium sized PR

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Misleading Gemini Code Assist for individuals Privacy Notice in VScode extension

2 participants