Safety - FreakySneaky787/Simple-Organizer GitHub Wiki

Safety

Simple Organizer is built around one promise: no file is ever lost. This page lists how that is enforced.

Guarantee How
No deletion Files are only moved. Duplicates go to the Recycle Bin / Trash, never deleted directly; drives without a Recycle Bin are refused or Windows asks first
No overwriting Name conflicts get a _1, _2 … suffix; copies across drives refuse to overwrite an existing file
No stray copies A move to another drive that cannot delete the original removes its copy again (also for read-only files)
Everything can be undone Every run is recorded and can be undone, in any order — see Undo and History
Undo record survives crashes History and staging list are written while files move, atomically
Closing is safe Closing during a task waits until it has finished
One task at a time Buttons and shortcuts are blocked while a task runs or a dialog is open
One instance A second start only brings the running window to the front
Every move is confirmed Organize, Undo, Commit, Revert and Trash ask first; only Auto-Organize runs without a dialog
Files stay inside the folder Rule and category targets are checked; links pointing outside are refused
Important files stay put System files, shortcuts, lock files and running downloads are never moved
No surprise downloads Online-only cloud files are never read or staged
No link traversal Symbolic links and junctions are never followed
Careful with system folders Drive roots, home folders, system folders and Git repositories need confirmation; /proc, /sys are excluded
Self-protection Settings, history and staging folders are never organised; the exe is never moved
Bounded scans Limits on depth, folder count and time
Duplicate groups stay intact At least one file of every group must remain
Recoverable failures Files that fail to commit, revert or undo stay recorded for another try

Found a way to lose a file? That is a bug — please open an issue.