Tool, account, workspace
Which service was involved, which account was used and is a workspace or tenant administrable?
AI data breach · Incident response DACH
Sensitive or confidential data in an AI system?
We help contain the incident technically, stop active data paths, preserve evidence and establish the next owners. Technical triage starts immediately – without speculation and without a compliance monologue.
Free · No login · Technical triage, not a legal decision
The starting point
A concrete incident needs facts first, not assumptions.
No attacker needed – a helpful team and a convenient tool are enough. Technical triage starts with the account, data, sharing, integrations and possible side effects.
Data and scope
Which data or documents were entered, uploaded or processed – and how far does the technical scope reach?
Sharing and accessibility
Were there shared or public links, exports or further recipients that now need to be contained?
Integrations and side effects
Were connectors, plugins, APIs or automations active – and were there effects outside the visible chat?
Technical first logic
What really matters in the first hours.
Containment before cleanup, evidence before speculation. Technical triage creates the factual basis for incident management, privacy and legal teams.
- Identify and selectively contain active data paths, links and integrations.
- Preserve timestamps, IDs, logs and account references without duplicating sensitive content.
- Establish technical scope, recipients and possible side effects beyond the chat.
- Rotate credentials only if they are exposed or can enable further execution.
- Hand over open facts and containment status to the responsible owners.
Technical first assessment
The wizard creates a structured triage report in a few minutes: facts, active paths, evidence, open questions and next owners.
Start triageInteractive wizard
Technical incident triage: what is known, active and still open?
Nine short questions. At the end you receive a structured facts, containment and escalation report – not a legal decision.
Step 1 of 911%
Which AI service or tool was involved?
Name the provider or product if known. Do not enter prompts or sensitive content.
Technical first assessment, not legal advice. Technical triage starts immediately. A possible 72-hour period under GDPR Art. 33 does not apply to every AI incident and must be assessed professionally from the established facts.
Personal incident help
You don’t want to guess. You want someone who has seen this before.
I am an AI architect, not an agency type. In a focused conversation we classify the incident, stop the data leak and define what happens next technically and organisationally – so you are able to act instead of paralysed.
30 min
Initial assessment
DACH
SME focus
EU/on-prem
Sovereign
In development · Waitlist open
Shadow AI Radar: see which AI your team really uses.
Today’s incident is yesterday’s blind spot. The radar shows which AI tools are in use, which data paths they open and where controls or clear working paths are missing.
01 · Discover
Inventory, not gut feeling
Captures the AI services in use – via browser signal, log import or a short team self-check. Result: an honest list.
02 · Assess
Control status per tool
For each tool, account context, data paths, admin controls, integrations and open technical facts become visible.
03 · Act
Guardrails, not bans
A clear recommendation per tool: approve, secure or replace – plus a lean AI policy the team accepts.
Join the waitlist
Early access, a say in the features and a preferential launch price. No spam – just one message when it starts.
Note: This page and wizard provide technical orientation and do not replace individual legal or data protection advice. Technical triage begins immediately. A possible 72-hour period under GDPR Art. 33 does not apply to every AI incident and must be assessed professionally from the specific incident. Privacy and legal teams assess possible notification or information duties from the established facts.