Security & data handling

The website, the NuRoute platform and its database run on servers in Frankfurt am Main, Germany, operated by Hostinger International Ltd. as our processor. Backups are stored by the same provider in Vilnius, Lithuania. Neither leaves the EU.

The content of each request is sent to the AI model provider that NuRoute selects for it, from the providers your organisation has connected or allowed. Several major providers are based outside the EU. To keep requests inside a region, set a data residency rule: if no compliant model is available, NuRoute rejects the request rather than routing it elsewhere.

Cloud. Requests routed through NuRoute Cloud, including their content and outcomes (model chosen, cost, latency and quality), are used to train NuRoute's own routing models: the models that decide which AI model should handle a request. They are not used to train any general-purpose language model, and NuRoute does not sell or share your content for anyone else's training. You can opt your organisation out at any time by emailing support@nuroute.ai; we then exclude your content from future training. See the Privacy Policy for the legal basis.

Enterprise. NuRoute runs on your own infrastructure and your traffic is not used to train anything. Per-tenant learning, where routing improves from your own traffic only, is planned and will be opt-in.

Request and response content is logged so that every routing decision can be inspected and replayed in the Request Explorer, and so that usage can be audited. Logs are kept for as long as your organisation's account exists. You can ask for your account and its data to be deleted at any time by writing to support@nuroute.ai. Invoicing records are kept for as long as German commercial and tax law requires.

When PII redaction is enabled, outbound prompts are scanned with Microsoft Presidio and detected personal data is replaced with placeholders before the request leaves NuRoute. The original values are restored only in the response shown back to you. Each project can run in fail-closed mode, which rejects a request if redaction cannot complete, or fail-open mode, which sends it anyway. Both are available on every plan.

All traffic to nuroute.ai is served over HTTPS, accepting TLS 1.2 and 1.3 only. Provider API keys you connect (BYOK) are encrypted at rest with AES-256-GCM, per organisation, and are never returned in plaintext through any interface. API keys you use to authenticate to NuRoute are stored only as SHA-256 hashes.

You can sign in to the dashboard with email and password, or with Google or GitHub. Enterprise deployments support single sign-on. Within an organisation, access is governed by four roles: owner, admin, member and viewer. Enterprise adds a full admin audit log.

On our side, access to production data is limited to what is operationally necessary to run the service.

Data residency rules, model allowlists and blocklists, and per-project budget caps are evaluated on every request, before any provider is called. See Gateway for how they work.

These companies process personal data on our behalf. AI model providers are not listed: your organisation chooses and connects them, and they process each request under their own terms.

NuRoute is operated from Berlin and processes personal data under the GDPR. Our lead supervisory authority is the Berlin Commissioner for Data Protection and Freedom of Information. ISO 27001 certification is in progress; we are not certified yet.

A data processing agreement (Art. 28 GDPR) is available on request from support@nuroute.ai. For how we handle personal data as a controller, see the Privacy Policy.

If you believe you have found a security issue in NuRoute, email security@nuroute.ai with enough detail to reproduce it. Please give us reasonable time to fix it before disclosing it publicly, and do not access or change data that is not yours while testing. Our security.txt has the same contact.