Security overview

Uploaded files and rendered outputs are processed through the DeletePII workspace, where operators can review findings before final export. Outputs can be downloaded locally, saved to Vault, or delivered by secure link email.

Production deployments should use TLS in transit and encrypted storage at rest for databases, file storage, and backup systems. Secrets such as OpenAI keys, storage credentials, and email provider credentials should be stored only in secured environment variables or a secrets manager.

DeletePII supports authenticated workflows, per-user audit records, and a foundation for shared organization policies. Access to saved artifacts and policy configuration should be restricted to authorized operators and administrators only.

Redaction runs can record source/output hashes, detection metadata, OCR metadata, and export destination details. This gives operators a traceable record of how a document was processed.

Final outputs can be sent as secure-link deliveries instead of raw attachments. This reduces the chance of forwarding sensitive files in plain email flows.

AI review is used as a candidate-generation layer for additional findings. Human review remains the control point before final redaction and export.