3 ms·
I checked out Github for more info as suggested, and it seems the main ingredient, https://github.com/capeprivacy/private-ai https://github.com/capeprivacy/priv
by luke-stanley 3y ago
I checked out Github for more info as suggested, and it seems the main ingredient, https://github.com/capeprivacy/private-ai https://github.com/capeprivacy/private-ai is forked from udacity/private-ai. Hmmm. I was expecting to find a clever and useful repo to nicely identify and strips out personal info, that's not what it is.
I do think stripping and adding personal info back only when needed is in principle a good idea for some situations. But I have big doubts at the injection of another party into the mix.
- bendecoste 3y agoThanks for checking it out! That repo is not related to this project, did you see it on the main list on https://github.com/capeprivacy https://github.com/capeprivacy or somewhere else? We will try to avoid the confusion in the future.
- gavinuhma 3y agoYikes, we'll have to remove that. It's a really old course on privacy-preserving machine learning from 4 years ago and has nothing to do with this product despite the generic name. Please see https://api.capeprivacy.com/v1/docs#/ https://api.capeprivacy.com/v1/docs#/ for more info.
- luke-stanley 3y agoI can confirm it was forked in the Capeprivacy GitHub repos list. The name is the same as the PII remover mentioned in the link, which I wanted to see how it worked!