Most retrieval and embedding services require sending your data to an external API. That means your documents, your queries, and your users' intent all leave your infrastructure. For regulated industries, sensitive data, or privacy-conscious products, that's a non-starter.

The Clace SDK runs entirely on the local machine. Embeddings are generated in-process using a built-in model. The index lives on local disk. Queries never leave the device. There is no network component.

Because no data leaves the device, there is no third-party data processing agreement to negotiate, no sub-processor list to audit, and no cross-border data transfer to evaluate. The SDK simplifies compliance with GDPR, HIPAA, SOC 2, and any framework that restricts where data can be processed.

Air-gapped environments, on-premise deployments, and offline-first applications all work without modification. The SDK has zero network dependencies—no license servers, no telemetry, no update checks.

For enterprise teams, this means your security review is straightforward: the SDK is a library that reads and writes local files. Nothing more.