Privacy and source files

Ordinary document comparison runs locally. In the comparison engine, Word field instructions, external references, macros and embedded OLE objects are not executed to produce a comparison. Optional Word conversion and Office features use the corresponding desktop application and its own behavior. Licensing, cloud synchronization, email hand-offs and other optional services have separate network requirements. “Local comparison” does not mean that every application or service involved is offline. Trial requests send your email address and hashed device identifiers to the licensing service to verify your email and bind the trial to your computer. Verification credentials stay in memory while Settings is open. Document contents are not included in trial requests. ## Keep source files and results separate Retain the source documents. Save merged or edited results under new filenames and inspect them before replacing another file. In Documents, accepting or rejecting differences changes the comparison result rather than the source files. ## Saved comparisons can contain sensitive content A `.dyd` package can embed complete source documents and is not encrypted. Saved manifests avoid absolute source and cache paths; this does not remove sensitive content from the comparison itself. Redlines, reports and exported difference lists can also reveal wording, comments, names, values or document properties. Handle them like the source files. Use an approved storage location and sharing method. Removing a visible comment from one view does not establish that all sensitive information has been removed from an exported package. ## Word snapshots and temporary files The Word integration creates local DOCX snapshots, including unsaved edits. Snapshots can remain in temporary folders named `DiffyOfficeCompare-*` or `DiffyOfficeSend-*` while the separate comparison process needs them. Wait until the comparison is closed and those copies are no longer needed before removing them through your normal temporary-file cleanup process. Removing them during a comparison can interrupt file access. ## Metadata cleaning If you use MarginDiff Scrub, inspect the selected cleaning actions and the resulting copy. Sending a document to the cleaner is only the start of that workflow. Reopen the cleaned copy in the original application before sharing it. For support, provide a minimal non-confidential example where possible. See [Troubleshooting](/docs/troubleshooting). ## Protected inputs MarginDiff does not bypass document protection. Obtain an authorized readable copy or supply the required credentials through the supported conversion process. Protected inputs that cannot be read fail explicitly.