HashDock
HashDock privacy policy
Michael Lip provides HashDock. The app compares selected destination folders with a frozen source manifest. All app processing takes place on your Mac.
Local data
Selected root paths, access bookmarks, destination aliases, manifest identifiers, relative paths, byte counts, SHA256 digests, verification times, and saved summaries stay in the app sandbox container. File bytes are read in local memory for hashing and are not retained as copies.
Selected input files remain in their original locations and are not modified. Saved access bookmarks let the app reopen only the files or folders you authorize. Removing a project, plan, or selected root removes its saved references. Clear local data removes saved app state and bookmarks without deleting source files.
Collection and sharing
The app does not collect data from you. It has no analytics, ads, accounts, cloud sync, telemetry, or automatic network requests. Sample mode uses synthetic local fixtures and separate saved state.
Delivery receipts contain the manifest identifier, destination aliases, verification times, coverage, and mismatches. Hashes and summaries remain local unless you explicitly copy and share report content. Copying a report places the displayed content on the system clipboard only when you choose Copy. Other apps may access the clipboard. Your later sharing is outside this app.
Opening Support or Privacy launches your browser at the relevant page on barframe.com. Your browser may make a normal web request. If you contact support, the email or GitHub service receives the information you send. GitHub issues are public.
Contact
For help, bug reports, or feedback, email lipmichal@gmail.com or open a GitHub issue.
Michael Lip is the developer and seller of HashDock.