Privacy Policy

How scanning works

When you scan, the app reads files from folders you select using browser APIs. File bytes are hashed locally (SHA-256) to find exact duplicates. You can verify this in Developer Tools → Network: image data should not be sent to DupShelf's domain during a scan.

Folder permissions (read and write)

DupShelf uses the File System Access API in Chromium browsers (Chrome and Edge on desktop). Permissions are granted by you in a native browser prompt; we cannot access paths you did not choose.

Choose folder (scan)

• Read access — required to list and hash images in the folder you picked, including subfolders.
• You can scan and export a CSV with read access only if you added files via file picker (no folder handle).

Move to dupshelf-duplicate-images

• Read/write access — when you click Move to folder, the browser may ask again to confirm write permission for the same folder.
• We create a subfolder named dupshelf-duplicate-images inside your scanned library and move non-keeper duplicates into grouped subfolders. Keepers stay in their original locations.
• DupShelf does not delete files. You review the duplicate folder in Explorer or Finder and delete when ready.
• Permission applies only to the folder handle you granted. We cannot read or write other directories on your computer.

Revoking access

Close the tab or revoke site permissions in Chrome settings (Site settings → DupShelf → reset permissions). Previously moved files remain on disk; the app does not undo moves automatically.

What we collect

Standard web server logs (if hosted) may include IP address, user agent, and requested URLs for pages like this policy. That does not include your image files or scan results.

Contact

Questions about privacy or permissions: reach out via renderlog.in.

Open workbench →