If you need to anonymize a dataset (structured, possibly linked tables), I recommend clickhouse-obfuscator - a tool designed specifically for this purpose: https://clickhouse.com/blog/five-methods-of-database-obfusca... Quick Start: curl https://clickhouse.com/ | sh ./clickhouse obfuscator --help Source code: https://github.com/ClickHouse/ClickHouse/tree/master/program... It does not use differential privacy.
Anyone who believes they can anonymize data automatically will be very disappointed... There are so many ways in which data can point to individuals, you'd need to process every datapoint with a lot of care and investigation. For example, rare medical conditions can be a good identification tool if the adversary knows the relation between such a condition and a person. How would an automatic tool know if a medical co…
What obfuscation mainly does is remove the PII that neither side wants to handle before the data gets transferred over so the data is "safe" and the receiver of the data no longer has the burden of stewardship over PII.
Contrary to a lot of handwringing on the internet, almost everyone that handles your data couldn't care less about you as a person. Their overwhelming interest in you is as a bag of attributes that they can statistically correlate with other bags of attributes. It's a relief for them if they can scrub all the PII from their databases while retaining all of the other bag of attribute qualities that they care about. Of course, the few entities that do care about deanonymization are the ones that make this entire process so difficult.