File safety.
In plain words.
Understand the scope, the change and the recovery options before you approve an operation.
What WhimRoom reads
A storage inspection reads paths, types, sizes, timestamps and available filesystem metadata. Content matching, copying and supported cleanup checks can read entire files and hashes. PDF and OCR tools read the documents you select.
Scans, OCR and document categorization run on your PC. Version 0.266 has no WhimRoom account, advertising, analytics upload or crash-upload service. Windows, the Microsoft Store and connected storage providers operate under their own policies.
When files change
Inspection does not approve a file change. Interactive workflows separate the proposed action from its execution: check the selected paths, destination, conflicts and removal method before confirming.
A content match proves that two files match at the time of comparison. It does not prove that a backup, an application file or a separately stored copy is unnecessary.
Automation has a separate policy.
If you explicitly activate automatic document filing, matching documents can move under the saved folder and rule policy while the watch is active. Stop watching or close the app to stop it. Registered scheduled tasks follow their saved scope; they do not require a new interactive preview each time.
The folder-combination workflow copies eligible missing files and keeps existing destination files. Source deletion is a separate operation.
Where information goes
Ordinary file and document tasks work without an AI account. If you connect an assistant, the local MCP process uses that client’s standard input and output and opens no network listener.
The client can receive requested paths, metadata, hashes, analysis and proposed operations. Document page, search and text tools can also return extracted document text. Your assistant provider may process or retain those results. A local connection does not guarantee that returned information stays on your PC.
Approved roots bound file workflows. Explicit system-inventory tools can separately expose application and startup metadata beyond those document folders. A model argument cannot approve an interactive file change.
Read the connection and setup detailsCan a change be undone?
| Operation | What to expect |
|---|---|
| Inspection | Reads the scope and may save local metadata or history. It does not remove the inspected files. |
| Missing-only copy | Creates eligible destination files and retains sources. Check completion and conflicts before changing originals. |
| Duplicate recycling | Uses Windows recycling confirmation and content checks. Restore through the Recycle Bin where available; recycling alone may not free space. |
| Permanent cleanup | Reviewed temporary-file, verified offload-source and selected-history deletion bypass the Recycle Bin. These operations provide no automatic backup or Undo. |
Operation receipts describe what actually completed. They are evidence, not a replacement for a backup. Reported free space can also change because of other applications.
What stays after a task
Settings, rules, history, index metadata, receipts and supported resumable queues are stored locally. Regular records and exports are not automatically encrypted and can contain private paths, hashes or extracted text. Saved outputs can outlive the app.
Cloud-synced folders may upload outputs through their provider. Opening an online-only file may trigger a provider download. Review those providers’ settings when choosing a location.
Read the full notice
This is a practical summary of the 0.266 application notice, reviewed 1 November 2026. The website’s final public controller identification, service address and support-retention terms are still being completed.
For a question about an operation, contact support with its version and outcome. Keep private documents and credentials out of the first message.