CheckIDs Try the redaction API

Privacy and data processing

How the validators and the EU PII Redaction API handle data, so you can assess them before sending anything. This page describes how the service works; it is not a data processing agreement or legal advice.

In short

What the API processes

When you call /redact (or use the demo), the request body, meaning your text, is analysed in memory and the response is returned to you. It is not written to a database, a file or a log by our code.

The hosting platform records request metadata for operations and debugging, such as time, response status, duration and the data centre that handled the request. It does not record request or response bodies.

Website analytics

This website counts page views, referrers and countries with Cloudflare Web Analytics. It loads a small script from Cloudflare, sets no cookies, stores nothing in your browser and does not build profiles of individual visitors.

Where it is processed

The API runs on Cloudflare Workers. Each request is handled by the Cloudflare data centre nearest to where it comes from. For requests from Europe that is usually a European data centre, but we cannot guarantee that processing stays inside the EU.

Service providers

The public demo is called directly, not through RapidAPI. To enforce its limit of 5 requests per minute, the visitor's IP address is used as a short-lived rate-limit counter key.

Your responsibilities

Redaction reduces the personal data you pass on, but detection is rule-based and not exhaustive: for example, street addresses are not detected yet. If you keep the placeholder map, the redacted text is still pseudonymised personal data in your hands. Assess your own use case, and test on a sample of your real data before relying on it.

Contact

Questions about data processing: use Contact Provider on the RapidAPI listing or open an issue on GitHub.