01
Assign four responsibilities
A reliable workflow separates request, processing, approval and release. One person may perform more than one role in a small team, but the responsibilities should still be explicit.
The requester defines purpose and scope; the operator produces the protected derivative; the reviewer checks it; the release owner controls delivery.
02
Control the files around the software
Local processing removes a cloud upload, but it does not govern folders, backups or messaging attachments. Use approved storage and restrict the uncensored original more tightly than the release copy.
- Standardise job names.
- Separate source, working and approved folders.
- Set temporary-file retention.
- Record the reviewer and release destination.
03
Improve from measured exceptions
Track the scenes that require corrections: low light, side profiles, crowds, masks, screens or reflections. Use these examples in acceptance testing after product updates.
A small benchmark set owned by the organisation is more useful than a generic accuracy promise because it reflects the cameras and risks the team actually handles.
Apply the workflow
Review real footage locally.
CensorFlow detects and tracks visible faces on your Windows PC, then lets a person correct and approve the result before export.