Write
You write your prompt as usual. AEGIS reads along in the input field, on the device itself, and does not transmit the text.
BRANE AEGIS protects sensitive data right inside ChatGPT, Claude, Gemini, Microsoft Copilot and Grok, before it reaches the AI model. Your teams keep using their AI tools; AEGIS spots sensitive information as they type and enforces the rules you define centrally.
What it looks like
BRANE AEGIS works where your teams already work. No new AI portal, no extra process: AEGIS lays its control layer directly over the AI use you already have.
Good evening
Claude can make mistakes. Please double-check responses.
Recreated interfaces. ChatGPT, Claude and Gemini are trademarks of their respective owners.
Sequence
You write your prompt as usual. AEGIS reads along in the input field, on the device itself, and does not transmit the text.
AEGIS spots sensitive information right in the input field, here an email address and a phone number. This happens before the content goes to the AI model.
AEGIS enforces your policy: a warning with the number of findings appears above the field, and a click or Enter replaces the values with placeholders.
You stay in your AI tool. The prompt now says [EMAIL_1] instead of the email address. The workflow stays, the sensitive data doesn't.
Centrally managed
ChatGPT today, Claude tomorrow, then Gemini, Copilot or a new service: the same company policy applies. You add further AI services through the administration.
From email addresses to API keys. Each kind can be switched on centrally; for structured data AEGIS also checks the check digit.
chat.example.com is blocked by your policy
Open an approved tool →Allow, warn or block, per AI application: your policy becomes a technical rule. Blocked sites show the way to an approved tool.
Semantic detection
Not every secret has a format: project names, internal systems or unreleased products don't match any rule for an IBAN or an email address. BRANE AEGIS understands what the prompt says.
Summarize where Project Northern Light Project codename stands for the steering committee, including the tolerances from drawing ZN 4471/03-b Your own data type and the prices from the Q4 supplier list Your list.
A semantic model on the device recognizes them in German and English.
Your administrators describe new data types in their own words. No classification project, no training.
Your company provides a simple list of what is confidential, once. AEGIS recognizes every entry in the input field.
Privacy
With a company account, AEGIS reports counts to the console, not content. Everyone in the workspace can read what is recorded.
Administrators can switch off each of these, including attribution to individual people. The database drops switched-off details before they are stored.
BRANE AEGIS + BRANE AIF
One set of company rules, two ways to use AI safely.
Your company policy and your list of confidential terms
Defined once, centrally. Applied everywhere.
In the browser
For the external AI tools your people already use
Too sensitive for external AI?
Continue on the secure path
In your own environment
For AI work that needs a controlled path
A local model answers. Nothing leaves the company.
Sensitive values are pseudonymized and restored in the answer.
Use AI. Protect data. Keep control.
No AI ban
AI has long been part of everyday work. Sensitive information can end up in external AI models by accident, exactly where the work happens: in the AI's input field.
BRANE AEGIS is the third option: allow AI and keep it under control. Not blocking AI, but controlling the risk.
We show you how AEGIS works in the AI applications you already use, and how you configure your AI policies centrally and enforce them technically.