Does a Chrome extension reading user-selected text from a webpage count as scraping? #205974
Replies: 1 comment
|
Thank you for your interest in contributing to our community! We currently only accept discussions created through the GitHub UI using our provided discussion templates. Please re-submit your discussion by navigating to the appropriate category and using the template provided. This discussion has been closed because it was not submitted through the expected format. If you believe this was a mistake, please reach out to the maintainers. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I'm building a small personal-use browser extension and I'm trying to understand the compliance boundary around reading webpage content.
The intended workflow is very simple:
The extension would NOT:
I'm particularly interested in the distinction between:
"a user explicitly selects text and asks an extension to process it"
versus
"an extension programmatically extracts content from a website."
From a Chrome extension policy perspective, would the former generally be considered scraping/data collection? Are there any specific permissions, disclosure, or privacy-policy requirements I should be aware of?
I'm trying to design the extension conservatively from the beginning, so practical experience from extension developers would be very helpful.
All reactions