Customer story · Data security & AI architecture

Regal's data never trains the AI. Here's exactly how that works.

Regal Technology Partners, a Tier 2 defense electronics manufacturer, runs its AI platform on its own data, inside its own secure environment. This is a plain explanation of how that platform uses large language models without ever exposing, sharing, or training on Regal's proprietary data.

CustomerRegal Technology Partners
IndustryDefense electronics manufacturing
TopicData security & AI architecture
Reading timeAbout 6 minutes
01The simple answer

Regal uses the AI. Nobody trains it on Regal's data.

The most important thing to understand: the large language model (such as GPT-6 Astra) is a pre-built tool. It was trained by OpenAI on public data, such as books, websites, and research papers, long before it ever reached Regal's environment. nBrain never changes the model. Regal's data is never fed to it to learn from. The platform uses it the way you'd use a calculator: give it a problem, it gives an answer, and it forgets everything immediately.

An analogy

Think of it like hiring a contractor

Imagine hiring a highly skilled engineer who went to the best schools and has decades of general knowledge. You bring them into your secure facility, hand them a specific document, and ask them a question about it. They read the document, give you their expert answer, and then you shred the document and wipe their memory of it.

That's how Regal's platform works. The AI has general knowledge from its training (school). Regal's documents are handed to it one question at a time (the specific task). It answers and immediately forgets. It never takes the documents home. It never learns from them. It never gets smarter from Regal's data.

02How it works, visually

The data flow: what goes where.

Here's what happens when someone on Regal's team asks the platform a question. Follow the arrows.

Regal owns and controls this Encrypted tunnel, nothing kept Pre-trained model, unchanged by Regal's data

The critical point

The arrows are an API call, the same way your phone talks to a weather service. A question goes out, an answer comes back, and nothing is kept on the other end. Microsoft's Azure OpenAI Service terms state that inputs and outputs are not used to train, improve, or modify the model.

03The boundary

What nBrain builds for Regal vs. what the model does.

There are two completely separate things happening. On the left is everything nBrain custom-built for Regal: this is where the intelligence specific to Regal's operations lives. On the right is the general AI model, which never changes.

What nBrain builds for Regal

  • AI agents: custom-built instructions that tell the AI how to behave, what to look for, and how to respond for Regal's specific use cases.
  • System prompts: the detailed rules, logic, and context that shape every AI response to fit Regal's needs.
  • Document retrieval (RAG): the pipeline that finds the right documents in Regal's library and hands them to the AI at question time.
  • Workflow automation: the business logic that routes questions, applies permissions, and manages user interactions.
  • Data connectors: integrations with Regal's ERP, PLM, MES, and other systems.
API boundary

What the language model already is

  • Pre-trained: trained on public data by OpenAI, and run by Microsoft, before it ever reaches Regal's environment.
  • General knowledge: understands language, logic, reasoning, math, and code, but knows nothing about Regal specifically.
  • Stateless: every API call is independent. It has no memory between questions.
  • Unchanged: Regal's usage does not modify, improve, or alter the model in any way.
  • Shared model, isolated processing: the model runs in Azure Government, but Regal's data is processed in isolation and not kept.
What nBrain customizes

The agent layer

This is where all the "training" happens, but it's not training the AI model. It's building the instructions, rules, and logic that wrap around the model.

  • Prompt engineering: crafting the right instructions
  • Agent behavior rules: "when asked about X, look in Y"
  • Response formatting: how answers should be structured
  • Permission logic: who can ask what
  • Document retrieval strategy: which documents to search, and how
What never changes

The AI model itself

The model's weights, the actual "brain" of the AI, stay exactly as they were shipped. Regal's data never touches them.

  • Model weights are frozen; Regal's data cannot alter them
  • No fine-tuning happens with Regal's data
  • No training pipeline exists in Regal's environment
  • No data is sent to OpenAI for model improvement
  • The model is the same whether Regal uses it or not
04Step by step

What happens when a Regal engineer asks a question.

Here's the path from the moment someone types a question to the moment they get an answer.

  1. 1

    An engineer types a question

    "What are the thermal specifications for the connector assembly on this program?"Happens inside Regal's secure environment
  2. 2

    The agent searches Regal's documents

    The custom-built retrieval system searches Regal's document library (its vector database) and finds the three to five most relevant sections. The documents never leave Regal's environment: the search runs entirely inside Regal's Azure subscription.

    Regal's data stays in Regal's environment
  3. 3

    The question and the relevant excerpts go to the API

    The question and the retrieved snippets are packaged together and sent to the Azure OpenAI API over an encrypted connection. Think of a sealed envelope: only the API can open it, and it's processed in an isolated session.

    Encrypted in transit, TLS 1.3
  4. 4

    The model reads, answers, and forgets

    The model reads the question and excerpts, writes a detailed answer, and returns it. Once the response is sent back, the model keeps nothing from the exchange. There is no session, no history, no learning. The next question starts completely fresh.

    No data kept · No learning · No model change
  5. 5

    The answer comes back to the engineer

    The engineer sees the answer in the platform, with citations pointing back to the original source documents so they can check it. The whole interaction is recorded in Regal's audit trail.

    Answer and audit log stay in Regal's environment
05The model provider's commitments

What Microsoft puts in writing.

These aren't only nBrain's promises. They come from Microsoft's contractual commitments for the Azure OpenAI Service, in its data protection terms.

1

Data is not used to train models

Prompts, inputs, outputs, and any data processed through the Azure OpenAI Service are not used to train, retrain, or improve Microsoft or OpenAI models.

2

Data is not shared with OpenAI

With Azure OpenAI (as opposed to using OpenAI directly), Regal's data is not sent to OpenAI. It stays within Microsoft's Azure infrastructure. OpenAI has no access to the prompts or responses.

3

Data is not accessible to other customers

Each API call is processed in isolation. No other Azure customer can see, access, or benefit from Regal's data.

4

Data is processed only where Regal chooses

In Azure Government, Regal's data is processed in U.S. sovereign regions (US Gov Virginia and US Gov Arizona). It doesn't cross international boundaries or leave government-controlled infrastructure.

06Clarifying the language

When we say "training," here's what we actually mean.

The word "training" causes confusion because it means two very different things in AI. Here's the distinction.

nBrain does not do this

Model training

This is what people fear, and it's not what happens with Regal's platform. Model training means feeding data into the AI's neural network to change its weights and make it learn new information permanently.

  • Changes the model's internal parameters
  • Data becomes part of the model permanently
  • Requires massive compute and GPU clusters
  • The model "remembers" the training data for good
  • Other users of the model could potentially reach derived knowledge
This is what nBrain does

Agent configuration

nBrain writes instructions that tell a pre-built model how to behave for Regal's specific use cases. The model itself never changes; it just gets better directions.

  • System prompts: "You are an engineering assistant for Regal Technology Partners..."
  • Retrieval rules: "Search these document categories first..."
  • Response templates: "Format answers with source citations..."
  • Permission logic: "Only show a program's data to users cleared for that program..."
  • Workflow automation: "Route quality questions to the quality agent..."
Another way to think about it

A new language vs. a reference binder

Model training is like teaching someone a new language. It changes who they are. Once they learn it, they can't unlearn it, and they'll use that knowledge with everyone they meet.

Agent configuration (what nBrain does) is like handing someone a job description and a reference binder. They read the instructions before each task, do the work, and hand the binder back. They don't become a different person. They don't remember what was in the binder after the task. And the next person who works with them starts fresh with their own binder.

07The bottom line

How Regal's data is protected, in six lines.

Regal's documents stay in Regal's Azure subscription

All source documents, embeddings, and search indexes live entirely within infrastructure Regal owns and controls.

The AI model is not trained on Regal's data

The model weights are frozen. Regal's usage does not change, improve, or modify the AI in any way.

Every interaction is stateless

Each question is an independent API call. The model keeps nothing between calls: no session, no memory, no history.

Microsoft commits to this in writing

The Azure OpenAI data protection terms prohibit Microsoft from using Regal's data for model training or sharing it with third parties.

No data leaves Regal's controlled cloud

Nothing is sent to OpenAI. Nothing goes to third-party servers. Nothing crosses borders. API calls stay within Azure Government infrastructure.

No model can be built from Regal's data

nBrain never creates derivative, fine-tuned, or trained models from Regal's proprietary information. The model is generic. The data is private.

Regal's data. Regal's control. Always.

nBrain builds the intelligence around the model: the agents, the logic, the workflows. Regal's data never goes inside the model. That is the architecture's core guarantee.

Keep reading

The rest of the story.

Have the same questions?

See how your data would stay yours on a private AI Brain.

In one strategy session we walk through where your Brain would run, which models it would use, and exactly what leaves your environment and what never does.

Book a strategy session

Prefer email? hello@nbrain.ai