The problem I see with the tools in general is that to make the request you need to hand over information. Yeah, it might get deleted from their database, but now your info is probably in some intern’s mailbox who’s part of the distribution group.
Open-source data removal workflows are a huge win for privacy transparency. Automating opt-out requests directly without relying on subscription-based brokers gives users real control over their personal data footprints.
Compared to what I use, this does everything a paid service does and more (including the ability to see exactly what happened with verbose logging, custom removal, built in dashboard, etc).
After using a paid service, I don't know of anything they do that this repo doesn't.
but what if the data collected by google search already? i want to know how you clean google search data result.
The problem I see with the tools in general is that to make the request you need to hand over information. Yeah, it might get deleted from their database, but now your info is probably in some intern’s mailbox who’s part of the distribution group.
Open-source data removal workflows are a huge win for privacy transparency. Automating opt-out requests directly without relying on subscription-based brokers gives users real control over their personal data footprints.
Thanks, but I suck at hacker news and this already got deleted. Oh well.
With open‑source code, security is better assured. It works well when you deploy and run it on your own.
How does this differ from the paid services? What do you do that they don’t do? What do they do that this does?
Compared to what I use, this does everything a paid service does and more (including the ability to see exactly what happened with verbose logging, custom removal, built in dashboard, etc).
After using a paid service, I don't know of anything they do that this repo doesn't.