What does Ai4Privacy do?
Ai4Privacy helps teams find personal information in text and replace it with placeholders. The same workflow is available through synthetic datasets, a browser-based chat, a REST API and local Python and JavaScript SDKs.
Do the training datasets contain real personal data?
The datasets presented here use synthetic PII rather than real personal data. Each release has its own coverage, access and license details, so those facts should be checked on the individual release page.
Can PII detection run inside my own application?
Yes. The Python and JavaScript packages are designed for local execution inside your own application or workflow. The REST API is the separate hosted integration path.
Which dataset release should I choose?
Start from the region and languages your text is in. The Asia-Pacific and European releases are built for those regions, the 1M series is the open-core option, and the 400K series and below are smaller sets useful for comparing release sizes. Each release page lists its own coverage, access and license details.
How are the dataset releases licensed?
Each release states its own license. The 1M series is CC-BY-4.0 open core. The 3M and 2M releases are listed as CC-BY-4.0 + Enterprise. The 400K series and below use the Ai4Privacy Dataset and Derivative Products License. The individual release page is the authority for what each of those permits.
REST API or local SDKs — which should I use?
The REST API is hosted: your product sends text and receives detected or masked text back. The Python and JavaScript packages run inside your own application instead. Choose the packages when you want detection to run in your own environment, and the API when you would rather not run it yourself.