Where does processing occur?
Inside the browser, using Web Workers, Tree-sitter parsers, and the local Rust/WebAssembly comparison engine.
Privacy and security boundary
AlignDiff’s comparison flow parses, pairs, and diffs source text locally in the browser. This page states the current boundary precisely, including what browser-local processing does not protect against.

Direct answers
Inside the browser, using Web Workers, Tree-sitter parsers, and the local Rust/WebAssembly comparison engine.
The comparison flow does not upload the pasted source code to an AlignDiff server. It is also not executed.
The current application does not include an analytics script, and source text is not placed in page URLs. Normal hosting requests can still expose request metadata such as IP address, user agent, and requested page—not the pasted comparison text.
There are no accounts or saved comparisons in the current beta. Comparison text is held in page memory and is lost when the page is reloaded or closed.
Security limitations
Local comparison path
Evaluate the claim
Open the Network panel, paste a non-sensitive sample, run a comparison, and inspect requests. This gives your team direct evidence for the deployed version it is evaluating.
Continue exploring