Safety & privacy
Updated August 12, 2026 · min read
Which Duplicate Copy Should You Keep?
Choose the canonical item using path, sharing, ownership, history, and workflow—not timestamp alone.
Exact content evidence proves the file bodies match but leaves each cloud item’s identity intact. One copy may anchor a client link, another may carry useful history, and a third may sit in a disposable import folder.
Compare the candidates across location, owner, sharing, version history, activity, retention, and integrations. Mark protected formats and unclear cases for manual review instead of forcing a single automatic winner.
A practical checklist
- 1Confirm every item is an exact size-and-fingerprint match.
- 2Identify the canonical folder and business owner.
- 3Compare sharing, links, permissions, and version history.
- 4Check retention and protected-file policy.
- 5Select one or more keepers and export the plan.
Understand the situation
Exact content evidence proves the file bodies match but leaves each cloud item’s identity intact. One copy may anchor a client link, another may carry useful history, and a third may sit in a disposable import folder.
A permission label describes technical access, not the provider’s entire security posture. Review the exact scope, token handling, retention, operator access, and purpose of every data field before connecting an account.
Use a controlled workflow
Compare the candidates across location, owner, sharing, version history, activity, retention, and integrations. Mark protected formats and unclear cases for manual review instead of forcing a single automatic winner.
Use least privilege in stages: read-only access for inventory and review, followed by separate write consent only if the user chooses an approved cleanup. A report-only workflow should remain possible.
- Identify the canonical folder and business owner.
- Compare sharing, links, permissions, and version history.
- Check retention and protected-file policy.
Make the final decision
Prefer the item already embedded in the correct workflow. Keep more than one when access boundaries are intentional. Record the keeper ID and path in the plan so the decision is clear before any separate cleanup permission is requested.
Metadata is not harmless just because it excludes file bodies. Names, paths, sizes, account IDs, and sharing state can reveal sensitive business or personal context and need deliberate protection.
Limits and risks to check
- — Newest does not always mean most authoritative.
- — Shared links can target the candidate you remove.
- — Version history does not transfer automatically between items.
- — Some duplicates are intentional controls or delivery copies.
Official references
Frequently asked questions
Should I always keep the oldest copy?
No. Age is only context; choose the item tied to the intended location, owner, links, and history.
Can I keep two exact copies?
Yes. The review model should allow multiple keepers whenever there is a real operational reason.
Can a tool choose automatically?
It can rank contextual signals, but ambiguous, shared, protected, or policy-controlled groups need human judgment.
Scan first. Decide with evidence.
ClearCopies reads supported cloud-drive metadata and groups exact copies by byte size plus a provider-supplied content fingerprint. Original file bodies are not downloaded for the scan. You review the result and export a plan before any separate write step.