Photo Cleaner: Clean Up Duplicates in Google Photos extension
Security at a glance
Automated estimate from our latest scan (malware, permissions, obfuscation) — not a security audit. Higher safety score is better.
See the full security reportChrome listing ID: aifhbfggponjmfgcmphpdpdmckkelbpj
Permissions (5)
- Execute scripts in pages
Related extensions
Google Photos Duplicate Remover - Delete Duplicate & Similar ImagesTools
Google Photos & iCloud Photos Duplicate Finder by PicSweepTools
PhotoDeduper: Duplicate Photo Cleaner for Google PhotosTools
Duplicate Photo Cleaner for Google PhotosTools
Duplicate Photo Remover for Google Photos™ & iCloud – DoppelgoneTools
Google Photos Duplicate RemoverProductivity
Frequently asked questions
Is Photo Cleaner: Clean Up Duplicates in Google Photos safe to use?
Our latest automated scan rates the Chrome listing of Photo Cleaner: Clean Up Duplicates in Google Photos at 63/100 (elevated risk) — malware, permission and obfuscation checks combined. The full report lists every finding behind the number. This is an automated estimate, not a guarantee of safety.
What permissions does Photo Cleaner: Clean Up Duplicates in Google Photos require?
Photo Cleaner: Clean Up Duplicates in Google Photos requests 5 permissions. The most significant: Execute scripts in pages. See the full breakdown in the security report.
Who develops Photo Cleaner: Clean Up Duplicates in Google Photos?
Photo Cleaner: Clean Up Duplicates in Google Photos is published by Nomadworkz. Impersonators copy popular extension names, so always verify the developer line and listing id on the store page before installing.
What this assessment covers
- Store listing
- Chrome
- Checked version
- 0.5.3
- Current listed version
- 0.5.3
- Scan date (UTC)
- Assessment status
- Completed
Recorded findings: 0 critical and 20 high severity. Read the finding details before interpreting the score; automated flags are not proof of malicious behaviour.
Automated analysis looks for suspicious code, permissions and other risk signals. It does not observe every runtime behaviour or independently audit the publisher’s servers. A low-risk result is not a guarantee of safety. How our checks work.