rusackas commented on issue #35845:
URL: https://github.com/apache/superset/issues/35845#issuecomment-3481780201

   These are the ones that we have currently and _were_ on the docket to be 
migrated:
   
   ```
   https://widget.kapa.ai/
   https://*.[githubusercontent.com/](http://githubusercontent.com/)
   https://*.scarf.sh/
   https://*.[googleapis.com/](http://googleapis.com/)
   https://*.[google.com/](http://google.com/)
   https://*.run.app/
   https://*.[gstatic.com/](http://gstatic.com/)
   https://*.[github.com/](http://github.com/)
   https://*.[algolia.net/](http://algolia.net/)
   https://*.[algolianet.com/](http://algolianet.com/)
   ```
   
   However, I think all the google related ones are not OK and are no longer 
needed... we can remove those. That leaves us with the following items that are 
NOT on the above allowed-list:
   
   ```
   widget.kapa.ai
   githubusercontent.com
   github.com
   algolia.net
   algolianet.com
   ```
   
   I did find this page:
   https://privacy.apache.org/policies/privacy-policy-public.html
   
   • It lists Kapa.ai as OK to use as long as it's opt-in (which it is, on our 
site)
   • Github is listed for source code, but I must assume that Github (and thus 
githubusercontent) are OK for serving static assets (code, images, etc) in 
general. 
   • Regarding Algolia, I don't see that on the ASF DPA page, but I did find 
this infra ticket: https://issues.apache.org/jira/browse/INFRA-27279
   
   @sebbASF let me know if the above makes sense, and we can add those ones 
(removing all the google-related ones for good measure). 
   
   Thanks,
   
   -e-


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to