Local PII Removal for GDPR Data Minimization
Remove selected identifiers before sharing documents or preparing AI prompts. Document processing stays in your browser; organizational privacy review remains necessary.
Redact PDF, Table, or Image
PDF · CSV · TSV · XLSX · PNG · JPEG · WebP · BMP
Data Minimization and Vendor Review
Assess the recipients, purposes, retention, and transfer arrangements involved in your workflow. Local processing can limit disclosure of document contents, but visiting the website still creates ordinary hosting requests. Consult your privacy team about applicable agreements and transfer requirements.
RedactPDF.tools processes document content within the employee's browser. This can reduce disclosure to external document processors, but it does not remove organizational compliance duties. Pseudonyms and partial masks may still be personal data; review the output and your organization's requirements.
Redaction Is Not Automatic Anonymization
Removing a name does not remove an exact location, a rare job title, or a distinctive transaction history. Keyed CSV pseudonyms retain relationships between repeated values, and partial masks leave identifying fragments. Assess the information remaining in each output and what a recipient could combine it with. The official GDPR text provides the legal context; this tool does not make that assessment for your organization.
Local PII Review Across PDFs, Tables, and Images
In PDFs and images, select the complete sensitive region and inspect all pages or surrounding pixels. In CSV and TSV files, review column actions, headers, free-text fields, and the first row of headerless data. Retain only the information needed for the intended purpose, then independently review the downloaded file and its name before disclosure.
Questions about this workflow
How can I remove PII locally before sharing a document?
Select the minimum content needed for your purpose, redact complete identifiers in PDFs or images, and review every column in tables. Download and independently inspect the result before sharing it. Local processing reduces document disclosure to this website, not your other handling obligations.
What is the difference between redaction, pseudonymization, and anonymization?
Redaction removes selected content. Pseudonymization replaces identifiers but may preserve links between records. Neither action alone proves that a person can no longer be identified from the remaining data. Assess indirect identifiers and other information available to recipients.
Does client-side processing mean the website receives no information?
No. The website serves pages and self-hosted assets, so ordinary hosting logs may include your IP address, requested URL, user agent, and request time. Input document content and filenames are not included in those requests. See Privacy & Security for the processing boundaries.
Can I use keyed CSV pseudonyms in a GDPR workflow?
They can help replace direct identifiers while keeping repeated records consistent, but they are not an automatic anonymization method. Protect the local pseudonym key, review retained columns and relationships, and obtain your organization's approval before sharing outputs.