Trust center
Two execution modes
Mode A is the default. In Mode A every model that touches your data runs on European infrastructure operated by us or by a vetted EU-based subprocessor — never on a US-hosted model. Mode B is opt-in: an organisation administrator activates it, and even then each prompt that would leave the EU triggers a consent dialog with the user and a sensitive-data scan before any forwarding. Switching back to Mode A takes a click and is effective immediately.
Where your data lives
Conversations, uploaded documents and account data are stored in the EU. The default language and reasoning models are hosted on European GPU infrastructure. The full processor list and hosting locations live on the Sub-processors page. We never warehouse your data outside the providers listed there.
What flows where
Your browser holds a JWT and opens a WebSocket to our backend. The backend authenticates the user, applies the organisation's AI policy and quota rules, then asks the AI engine to orchestrate the answer. The AI engine runs a sensitive-data scan, decides whether the question needs internal knowledge (your documents, our help centre) or external lookup, and only then dispatches the work — to EU-hosted models by default, or to an external model under Mode B if the user has consented for that prompt and that provider.
No training on your data
Localign does not use your prompts, your documents or your conversations to train, fine-tune or improve any AI model — neither our own nor a subprocessor's. The same prohibition is mirrored in every Mode B contract with an external model provider, and is restated in the AI Annex you sign with us.
Resilience and continuity
If your tab disconnects mid-answer, processing continues server-side and the conversation state is restored when you come back. If a primary model is unavailable, the request falls back along a pre-declared chain of equivalent models — never silently to a different region or a different consent posture. Operational events that affect customers are published on the Service status page; documentation changes are listed on Updates.