Privacy and security boundary

Browser-local code comparison

AlignDiff’s comparison flow parses, pairs, and diffs supplied source in the browser. This page states the current boundary and its limits without treating local processing as a security guarantee.

Processing and transmission

What happens during a comparison

Where processing happens

Source text is handled in browser memory during a comparison.

What the flow transmits

The comparison flow does not upload source text, file names, snippets, identifiers, comparison results, or manual pairing choices to an AlignDiff server. Compared source is treated as text and is not executed.

What is stored

The current public beta has no accounts or saved comparisons. Active comparison text is held in page memory and is cleared when the page is reloaded or closed.

Boundary

Local processing, no remote code service

Old and new source stay in the browser while the page renders the comparison. AlignDiff does not add a remote code-processing service to this flow.

Limitations

Browser-local does not mean risk-free

A compromised device, browser, extension, or clipboard can still expose source text.
Hosting and network providers may receive ordinary delivery metadata such as requested URLs, timestamps, IP address, and user-agent information; that is separate from comparison text.
Do not paste credentials, tokens, private keys, production data, or other secrets into any public tool.
Very sensitive or regulated source may require an organisation-approved offline workflow and security review.

For a direct check of the deployed version, open browser developer tools, use a non-sensitive sample, run a comparison, and inspect the Network panel. Read the complete privacy policy for the corresponding legal statement.