Skip to content

docs: Copilot privacy concerns#4325

Merged
peholmst merged 4 commits intov24from
doc/copilot-privacy
Aug 26, 2025
Merged

docs: Copilot privacy concerns#4325
peholmst merged 4 commits intov24from
doc/copilot-privacy

Conversation

@MarcinVaadin
Copy link
Copy Markdown
Contributor

Added Privacy Concerns section with more detailed information about what is being sent and how to opt out.

@MarcinVaadin MarcinVaadin requested a review from emarc May 22, 2025 09:02
@github-actions
Copy link
Copy Markdown

github-actions Bot commented May 22, 2025

AI Language Review

The file "Copilot" appears to have only one textual change related to privacy information, which is the inclusion of the new 'Privacy' section. Here are some observations and suggestions related to the newly added content:

  1. Tone and Clarity: The tone is generally appropriate, but ensure it remains clear and professional. A sentence like "Copilot can send information..." could be rephrased for clarity, e.g., "In certain situations, Copilot may send information related to your project outside your local environment. Please review the summary below for details."

  2. Mixed-Case Labels: The "Use case," "Shared data," and "How to opt out" labels in the privacy section are inconsistently capitalized. Consider capitalizing these to maintain consistency, e.g., "Use Case," "Shared Data," and "How to Opt Out."

  3. Punctuation: In the sentence "It is possible to block all outbound Copilot requests (excluding license checking) for given users by license owner," there's a missing comma after "requests." It should read: "It is possible to block all outbound Copilot requests, excluding license checking, for given users by the license owner."

These suggestions aim to enhance clarity and maintain consistency in the document.

@emarc
Copy link
Copy Markdown
Contributor

emarc commented Jun 23, 2025

Looks goo, I suggest the following adjustments:

  1. Name the section just "Privacy" (drop "concerns")
  2. "User is asked before first operation if AI usage is allowed." -> "User asked for permission before operation. This can be changed via Settings > AI Usage"
  3. "Command Window prompt submitted": add "User asked for permission before operation (same as above.)"
  4. "User Activity" -> "Copilot usage" (not super good, but works well with the next one)
  5. "Copilot error happened" -> "Copilot error"

@emarc
Copy link
Copy Markdown
Contributor

emarc commented Jun 23, 2025

"Command Window prompt submitted": add "User asked for permission before operation (same as above.)"

Now the part about settings about settings on vaadin.com is completely dropped?

@peholmst peholmst added the target/main cherry pick to main branch label Aug 8, 2025
@peholmst
Copy link
Copy Markdown
Member

peholmst commented Aug 8, 2025

What's the status of this PR?

@MarcinVaadin
Copy link
Copy Markdown
Contributor Author

What's the status of this PR?

Applied Marc last comment, ready for review

@peholmst
Copy link
Copy Markdown
Member

@emarc Can you do a re-review?

Copy link
Copy Markdown
Contributor

@emarc emarc left a comment

Choose a reason for hiding this comment

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

lgtm

@peholmst peholmst enabled auto-merge (squash) August 26, 2025 09:46
@peholmst peholmst merged commit 49ec356 into v24 Aug 26, 2025
4 checks passed
@peholmst peholmst deleted the doc/copilot-privacy branch August 26, 2025 09:46
vaadin-bot pushed a commit that referenced this pull request Aug 26, 2025
* Copilot privacy concerns

* review notes

* include info about vaadin.com profile settings

---------

Co-authored-by: Petter Holmström <petter@vaadin.com>
peholmst added a commit that referenced this pull request Aug 26, 2025
* Copilot privacy concerns

* review notes

* include info about vaadin.com profile settings

---------

Co-authored-by: marcin <marcin@vaadin.com>
Co-authored-by: Petter Holmström <petter@vaadin.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants