Skip to content

Your data

The killer question:
"what leaves my machine?"

Short answer: on Solo with local models, essentially nothing. Full answer: below, with the diagram, the mechanisms, and the limits.

On solo with local models, essentially nothing leaves your machine. With your own key, only your requests — to the provider you chose. On managed sovereign modules, it stays in a private cloud of your own, in Canada. Around that: local personal-information detection, sealed audit logs a third party can verify, per-organization isolation — built to make Law 25 and PIPEDA easier to live with.

  • Your documents
  • Your meeting audio
  • Transcription (Parakeet)
  • Local models (GGUF)
  • Your secrets (1Password)

Processed on your device. Full stop.

  • Calls to YOUR API key (Claude, OpenAI…) — under your agreement
  • Team sync, if you enable a shared workspace
  • Nothing at all, if you run 100% local

Always your choice, never a hidden default.

Local processing first

Inference can run entirely on your device (llama.cpp, GGUF models). So can transcription (Parakeet ONNX). If you plug in your own API key, requests go straight to your provider under your own agreement — Luge is not a middleman reading your traffic.

Secrets on-device

Your secrets (keys, integration passwords) resolve locally through 1Password. The session token lives in the operating system's keychain, not in a config file.

Personal-information detection

PI detection (SIN, health-insurance numbers, emails, phone numbers, cards) runs locally inside the platform — content is not shipped to an external service for analysis.

Audit and isolation

Every significant event lands in audit logs sealed at write time (a per-row integrity hash — tampering is detectable by a third party), exportable as PDF evidence packages. Every resource is isolated per organization. That's the architecture our first vertical customer — Canadian financial services — required, applied to everyone. The illustrated version is here.

Managed sovereign modules

Need managed inference to stay in the country? The managed sovereign modules run on Canadian infrastructure managed by us — the supplier can evolve, the residency doesn't. Details on the pricing page.

The site you're reading

This site uses no tracking cookies and needs no banner. Visit statistics are aggregated and anonymous.

Law 25, PIPEDA — the paragraph our lawyers approve of

Luge is designed to make your compliance easier: local processing, personal-information detection, audit logs, and an option to run inference on infrastructure hosted in Canada. Compliance with Law 25 remains an organizational responsibility — no software can "guarantee" it. If a vendor promises otherwise, worry about the vendor.

Luge's first vertical deployment is operated by Tchat N Sign, whose organization holds SOC 2 Type II, ISO 27001 and ISO 27701 certifications.

Our full privacy policy is here, and the exact mechanics (integrity hashes, round-trip PII masking, the consent chokepoint) are documented under the hood — verifiable, not taken on faith. Questions? luge@nsolutions.ai.

The best test is your own.

Open Luge on the Solo plan, plug in a local model, and watch for yourself what leaves your machine. The Solo plan is free and open — no credit card.

A specific question? We answer at luge@nsolutions.ai