Your files stay yours.
How local file processing, browser permissions, and website requests work.
Local file processing
Scanning and file organization happen in your browser on your device after you grant folder access. The app does not upload selected file contents, names, folder scans, or custom rules to its application server. It has no file upload API or database for those files.
During a scan, the app reads metadata. During copying, moving, verification, and undo, it reads or writes local file bytes through browser APIs. File handles and operation logs remain in the current page session.
Settings stored by your browser
Custom rules and small preferences are stored in localStorage on this browser. No file contents or full folder scan are saved there. You can export rules yourself or remove stored preferences using your browser’s site-data controls.
Closing or reloading the page ends the current in-memory log and undo history. Downloaded exports are files you choose to save on your device.
Ordinary website requests
Opening pages makes HTTP requests for content, scripts, styles, and self-hosted fonts. Hosting providers may receive ordinary request metadata such as IP address, browser information, requested URL, and timing. Local file processing does not prevent those normal website requests.
This implementation does not add analytics, advertising trackers, or account authentication. Infrastructure used to deliver the website may maintain operational logs according to its own policies.
Permissions and choices
Your browser controls local folder permissions. You can decline access, choose a narrower folder, revoke site permissions, or clear local site data. Browsers without the required file APIs can read the website but cannot use direct folder organization.
Do not include sensitive folder names or file contents in URLs or support requests. The privacy behavior described here covers this application, not unrelated extensions or software installed on your device.