File privacy checklist

A simple metadata privacy checklist for safer file sharing.

Metadata cleaning works best when it becomes a routine. Use this checklist before uploading photos, videos, screenshots, documents converted to images, marketplace assets, press kits, and client files.

Before cleaning

Start by separating originals from public copies. Original files may be useful for private archives, legal records, editing history, or internal documentation. Public copies should carry only what the recipient needs.

  • Create a folder for files you plan to share.
  • Rename files so private names, project codes, or client details are not exposed.
  • Review visible content for addresses, screens, badges, reflections, and paperwork.

During cleaning

Upload files to Fenwick DataClean, run the metadata cleaner, and review the status notes. Guests can clean up to 5 files per batch. Free accounts can clean up to 10 files per batch, which is useful for repeat workflows.

  • Batch similar file types together when possible.
  • Download the cleaned copies immediately after processing.
  • Keep cleaned outputs separate from untouched originals.

After cleaning

Open the cleaned file and confirm it still displays or plays correctly. Then share only the sanitized copy. This small habit can reduce accidental disclosure across social networks, email, cloud folders, marketplaces, client portals, and public websites.

  • Open every important image and verify that orientation, transparency, and color still look right.
  • Play every important video and confirm that audio, timing, and visual content still work.
  • Use the cleaned file for public upload and keep the original in private storage.

For personal sharing

Before posting family photos, travel images, school pictures, event clips, or home videos, remove hidden details from the copy you plan to share. Pay special attention to location metadata and visible clues in the image or video itself. A cleaned copy helps reduce accidental exposure without changing the memory you keep privately.

For professional sharing

Agencies, freelancers, educators, sellers, and client-facing teams should build metadata cleaning into the final export step. The person sending a file should know which copy is public, which copy is original, and where each version is stored. This prevents private production details from moving into a public website, listing, pitch deck, client portal, or social post.

For sensitive work

If a file relates to legal matters, health information, employment records, journalism, safety, minors, or confidential client work, metadata cleaning may not be enough. Preserve originals, follow the rules of that workflow, and use specialized review tools when the situation requires a stronger process.

Batch review routine

When you clean several files at once, review the batch before you upload it anywhere. Confirm that every item has a clear status, delete failed outputs from the public folder, and retry only the files that need attention. A small review step prevents one missed file from becoming the original that gets shared.

Filenames and folders

Metadata is not the only hidden clue. Folder names and filenames can reveal client names, project codes, locations, dates, or private labels. Rename public copies with neutral, useful names before sharing them with a broad audience.

Review after platform upload

After uploading a cleaned file to a public platform, view it the way an outside person would. Confirm the right copy was uploaded, the caption is accurate, and no private version appears in the same folder, gallery, post, or downloadable attachment.

A one-minute version

For everyday files, remember the short version: duplicate the original, rename the public copy, clean the metadata, open the output, check what is visible, and share only the cleaned version. That routine is easy enough to repeat before every upload.

A stronger version for teams

Teams can assign one person to prepare public copies, keep a shared naming convention, and review cleaned outputs before publishing. A simple checklist prevents rushed uploads from exposing private project names, location hints, software history, or client information.