PhotoSanitize can produce several kinds of information about an image-processing operation, including the sanitized file, verification results, SHA-256 fingerprints, reports, and, in Enterprise, a Certificate of Sanitization.
Retaining these materials can help you identify which photographs were processed, which output versions were reviewed, and whether a file has changed since the operation.
The amount of recordkeeping needed depends on your circumstances. An individual sharing a few personal photographs may need only the sanitized copies, while an organization preparing images for publication may require a more formal record.
Keeping originals and sanitized files separate
PhotoSanitize creates new outputs rather than overwriting original images. This protects the source material and allows repeated processing, but it also means that unmodified versions remain present.
For personal use, an identifiable suffix or a separate Sanitized folder may be sufficient. For business use, it can be helpful to distinguish incoming originals, sanitized images awaiting review, and files approved for distribution.
Where originals contain personal or confidential information, access to them may need to be more restricted than access to the final sanitized copies.
Recording what was processed
A useful record identifies the source file, sanitized output, selected profile, processing result, and verification outcome. SHA-256 fingerprints provide a way to associate that information with exact file contents.
For example, if an organization distributes photographs to several departments, it can retain the output fingerprints alongside a report showing which files passed verification. If a recipient later asks whether a particular photograph belongs to the approved collection, the fingerprint can help establish whether the file is identical to the recorded output.
Pro and Enterprise offer reporting formats suited to different purposes. PDF is convenient for human review, CSV for spreadsheet-based reconciliation, and JSON for software integration.
Enterprise Certificates of Sanitization provide a more specific record for images that meet the certificate’s successful sanitization and verification requirements.
Reviewing before release
A processing record does not replace inspection of the finished image. Technical verification confirms the applicable checks, not whether every visible detail is appropriate for publication.
For example, a company might sanitize photographs from a staff event and verify their metadata cleanup successfully. A separate review may still be needed to ensure that confidential documents or people who should not be shown are not visible.
It can be useful to record who reviewed an approved collection through the organization’s existing procedures. PhotoSanitize itself is not a centralized approval or records-management system.
Protecting reports and certificates
Processing records may include filenames, directory paths, timestamps, fingerprints, and details about source images. This information can be valuable for internal traceability but may also reveal information that should not be shared with unrelated recipients.
Store reports and certificates in locations with appropriate permissions. If an external customer needs proof of completed processing, review the report or certificate before sending it so that unnecessary internal information is not disclosed.
Retention and later verification
How long you retain original images, sanitized outputs, and processing records depends on their purpose and any applicable contractual, legal, or organizational requirements.
If you later need to confirm that a retained sanitized file has not changed, calculate its current SHA-256 fingerprint and compare it with the recorded value. A match provides practical assurance that the file contents are identical to the recorded version.
If the fingerprint differs, investigate before treating the image as the same approved output. Even a harmless metadata edit changes the file contents and can invalidate that comparison.
Recordkeeping is most effective when files, reports, and certificates remain clearly associated and are protected against accidental deletion, replacement, or unauthorized modification.