HomeLegalResponsible AI

Legal

Intelligence withaccountability.

Sourced answers. Human decisions. Clear limits. The principles and practices behind our production systems.

Talk to usTalk to usHow we deploy
  1. 01 · Model outputOutput
  2. 02 · Sources and limitationsEvidence
  3. 03 · Human reviewReview

01Our principles

Six commitments we design around.

Not a manifesto — the constraints our systems are actually built to meet.

01Principle / 01

Sourced, not asserted

Outputs cite the specific policy clause, document or record behind them. If we can’t show the source, we don’t present it as fact.

02Principle / 02

Humans decide

Newron drafts, scores and recommends; a person makes the decision. Maker-checker and human-in-the-loop are built in, not optional.

03Principle / 03

Calibrated uncertainty

We’d rather a system say “I’m not sure, here’s the clause” than guess with confidence. Abstention is a feature.

04Principle / 04

Auditable by design

Every output is logged, timestamped and exportable, so any decision can be reconstructed and reviewed later.

05Principle / 05

Fairness under scrutiny

We test for disparate impact on the populations our customers serve and document known limitations honestly.

06Principle / 06

Privacy as a default

Data stays in the customer’s environment; we minimise what’s collected and never train shared models on it without consent.

02Last reviewed 1 May 2026

How we put it into practice.

This page sets out how Newron approaches the responsible development and deployment of AI. It applies across our products and custom engagements, and it informs the contracts we sign.

  • Responsible-AI decisions are owned by the same people who build the systems — not delegated to a separate committee that never sees the code. High-impact features are reviewed before deployment for sourcing, oversight and failure modes, and we revisit those decisions as systems change.

  • We train and fine-tune on data we are permitted to use, with attention to provenance and licensing. For customer deployments, customer data is processed under the customer’s instructions and is not used to train shared models without an explicit, contracted agreement. We train on India-hosted data with residency commitments where required.

  • 03Evaluation

    Every production workflow ships with an evaluation harness. We measure accuracy on the tasks that matter, track regressions over time, and — where the workflow affects people — test for disparate impact across relevant groups. We prefer reproducible, honest benchmarks over cherry-picked demos, which is part of why we open-source some of our evaluation tooling.

  • Newron is built to assist expert decision-makers, not replace them. Systems are configured so that consequential actions — approving a loan, settling a claim, responding to a citizen — require a human to review and confirm. Interfaces are designed to surface uncertainty and the underlying evidence rather than hide them.

  • AI systems make mistakes, can reflect biases in their training data, and can be confidently wrong. We document known limitations for each deployment, design for graceful failure and abstention, and we are explicit with customers about what a system should and should not be relied upon to do.

  • 06Raising concerns

    If you believe a Newron system has behaved unfairly or harmfully, we want to know. Contact us via our contact page; concerns are routed to the team responsible for the relevant system and used to improve it.

03Questions

Common questions.

  • Our systems are designed to assist, not to decide autonomously. Consequential actions require human review and confirmation.

  • We test for disparate impact on the populations a workflow affects, document known limitations, and work with customers to monitor outcomes in production.

  • Not without an explicit, contracted agreement. Customer data is processed under the customer’s instructions inside their environment.

  • We design for abstention. A system that surfaces uncertainty and the relevant policy clause is more useful — and safer — than one that always answers.

Responsible AI

Hold us to this.

If you’re deploying AI where the stakes are real, let’s talk about how to do it defensibly — and what we’d refuse to build.

SecurityTalk to usTalk to us