Privacy and data handling

Clearer privacy information, without vague wording.

This page summarizes how DirectoryCompare Pro handles local settings, licensing information, optional support submissions, and remote-source workflows such as GitHub, web URL, or FTP/SFTP comparison.

Privacy summary

The product is designed primarily around local workflows. Most compare operations happen on your own machine, not through a hosted service.

Most file comparison activity is local

DirectoryCompare Pro is not a cloud compare service. Local directory comparison, archive analysis, spreadsheet comparison, image diff, patch workflows, exports, bookmarks, sessions, and many other features run locally on your device.

Licensing data may be machine-bound

The product uses machine-bound licensing for paid tiers. That means activation and entitlement logic can be tied to a machine identity or similar device-specific information, depending on the licensing workflow in use.

Remote-source features are different from local-only use

If you compare GitHub repositories, web URLs, or FTP/SFTP sources, those workflows naturally involve communication with the relevant remote service. That is separate from local folder comparison.

In plain English: local compare work stays local; remote compare work has to contact the remote system you asked the app to use.

Types of information involved

This is a practical summary of the kinds of data that may be stored or used while the product is running.

Local configuration and workflow data

  • Window and interface preferences
  • Session history and bookmarks
  • Recent compare targets or related local settings
  • Other app configuration needed to restore your workflow

Licensing and activation information

  • Machine-bound licensing details for paid tiers
  • Activation status and tier entitlements
  • Subscription or expiry state where applicable
  • Support information needed to help with license issues

Optional support or bug-report information

  • Information you choose to send when requesting support
  • Problem descriptions, reproduction steps, and similar troubleshooting details
  • Contact information if you provide it
  • Potential licensing context if required to resolve an activation issue

Remote-source behavior

Some features work only because the app talks to external systems you selected.

GitHub comparison

If you compare GitHub repositories, the app may use repository URLs, API requests, and—where relevant—authentication details needed to access the repository or avoid rate limits.

Web URL comparison

If you compare against a web URL, the app must request content from that URL. That means normal network communication with the target site is part of the feature.

FTP/SFTP comparison

If you compare remote file sources over FTP or SFTP, the app must use the connection information and credentials needed to access those systems.