Processing client data as an insurance broker means handling policy numbers, health questionnaires, claim photos and bank details every day - and every piece of it falls under GDPR. Monday morning, 09:15. Lisa, a broker at a mid-sized Versicherungsmakler office, opens AMEISE to check the week’s renewals. Twelve policies expire within 30 days, three clients sent claim documents over the weekend, and two comparison requests sit unanswered since Friday. Each task touches personal data protected by GDPR Art. 9 and professional secrecy under section 203 StGB. This guide shows how to hand exactly that work to an AI employee, step by step, without putting a single client record at risk. Below you will see how Superkind’s ready-made AI team for insurance brokers processes claims, compares policies and tracks deadlines automatically.
Key takeaways
Get a ready-made AI team for your broker office - Superkind comes with a Claims Processor, Policy Comparator and Deadline Watcher that handle claims, comparisons and renewals automatically in AMEISE, Outlook and Slack. Start for free with unlimited users, or build your own.
Keep control, keep data in Europe - Superkind is hosted in Europe, GDPR compliant, never trains on your data and you decide which steps need your approval before anything reaches a client or an insurer.
AMEISE works without an API - Superkind works with AMEISE natively via computer use, like a colleague at the screen, in the browser or the desktop client.
Section 203 StGB and GDPR Art. 9 covered - health data, financial data and professional secrecy are addressed through EU hosting, a DPA via the Trust Center, no model training and logged access.
Five steps from setup to routine - connect AMEISE, set approval rules, automate claims, run policy comparisons and track deadlines, all in one workflow.
Your AI team for insurance brokers
What does processing client data with AI mean for insurance brokers?
Processing client data with AI means an AI employee reads incoming claim documents, pulls the matching policy from your broker management program, checks coverage, drafts the report for the insurer, compares renewal options across portals and tracks every deadline - while a person approves before anything sensitive leaves the office. The AI handles reading, matching and drafting. The sign-off, the client relationship and the professional judgement stay with the broker. One example is Superkind: a ready-made AI team that processes claims, compares policies and watches deadlines in AMEISE, hosted in Europe and GDPR compliant.
The difference to pasting client data into a generic chatbot: an AI employee does not store your prompts for training. It knows which policy covers which risk, which deadline is closest and which insurer needs which form - because it reads AMEISE the same way you do, via computer use, inside your infrastructure.
How it works with Superkind: your AI team for insurance brokers
You write to Superkind by email, in Microsoft Teams, in Slack or in the web app, like you would write to a colleague, and Superkind does the task in your programs - 1,700+ integrations including Outlook, Excel, SharePoint and Calendly, plus AMEISE natively via computer use. Hosted in Europe, GDPR compliant.
With Superkind you don't start from zero: it comes with ready-made AI employees for insurance broker offices. They run automatically in the background, and you decide where they ask you first. Use them right away, adapt them, or build your own.
Claims Processor
AI employee for claims processing
A client emails a photo of the damage, the expert report and the claim form. The Claims Processor reads the attachments, pulls the matching policy from AMEISE via computer use, checks the coverage and deductible, drafts the claim report for the insurer and posts the status in Outlook. If the claim exceeds your threshold, it waits for your approval before sending.
Policy Comparator
AI employee for policy comparisons
The client asks for a better car insurance rate. The Policy Comparator pulls the current contract from AMEISE, runs the comparison across the portals you use, lists the top three options with price, coverage and deductible side by side, and drafts a recommendation email to the client. You review before it goes out.
Deadline Watcher
AI employee for deadline management
Cancellation deadlines, renewal dates and follow-up reminders pile up across dozens of clients. Every morning the Deadline Watcher checks AMEISE for upcoming dates, posts the ones due this week in Slack with the client name, policy type and days left, and drafts the follow-up email for each. Routine reminders go out on their own; cancellation notices wait for your sign-off.
Every employee is ready to use right away. Or build your own on the platform.
Safe by default
Insurance broker data includes health questionnaires, claim reports and bank details. Superkind keeps them in Europe and never uses them to train models.
- Hosted and processed in Europe
- GDPR compliant
- Aligned with the EU AI Act
- No training on your data
- DPA through the Trust Center
What you need
Checklist before the first task
- AMEISE installed and running (browser or desktop client) with your policy portfolio loaded
- Outlook or Gmail for client correspondence and claim emails
- Microsoft Teams or Slack for internal approvals
- An agreed approval rule: who signs off on claim reports, cancellations and client-facing recommendations
- A free Superkind account at app.superkind.ai - 1,700+ integrations connect these systems, plus AMEISE via computer use
Step by step with Superkind
Five steps from setup to a running workflow. Each step is something you can do today.
Step 1: Set up Superkind with AMEISE access
Sign up at app.superkind.ai and connect your channels: Outlook for client emails, Teams or Slack for approvals. For AMEISE, Superkind works natively via computer use - it logs into the program in the browser or the desktop client the same way you do, reads policy data, enters updates and exports comparison sheets. No API key, no plugin. The session runs inside your infrastructure, not outbound.
Connect to our AMEISE and read all active policies. Outlook is already connected.
Step 2: Configure approval rules for client communication
Insurance data is sensitive - health questionnaires, claim amounts, personal finances. Set a rule for every step that touches a client or an insurer: claim reports over a threshold wait for your OK, cancellation notices always wait, routine renewal reminders go out on their own.
Rules: claim reports always need my approval before sending. Cancellation notices: always approval. Renewal reminders under EUR 500 annual premium: send automatically.
Step 3: Automate claims intake and processing
When a client emails a claim, Superkind reads the attachments (photos, expert reports, claim forms), pulls the matching policy from AMEISE, checks coverage and deductible, drafts the claim report in the insurer’s format and posts the status back in Outlook. If the claim exceeds your threshold, it waits for approval.
Process the claim from Familie Müller. Expert report and photos are attached. Policy HH-2024-7831.
Superkind answers: “Policy HH-2024-7831 covers water damage, EUR 500 deductible. Claim report drafted for the insurer, EUR 4,200 estimated. Waiting for your approval before sending.”
Step 4: Create policy comparison routines
For every renewal coming up, Superkind pulls the current contract from AMEISE, runs the comparison across the portals you use (via computer use), lists the top options with price, coverage and deductible, and drafts the recommendation email. Tell it once and it runs for every renewal.
For every policy that renews within 90 days: pull the current terms from AMEISE, compare with at least three alternatives and draft the recommendation to the client.
Step 5: Set up deadline monitoring and renewals
Cancellation deadlines, renewal dates and follow-up reminders - the Deadline Watcher checks AMEISE every morning, posts the week’s deadlines in Slack or Teams and drafts the follow-up for each. Cancellation notices wait for your sign-off; routine reminders run on their own.
Every morning at 7:00: check AMEISE for deadlines this week. Post them in #deadlines with client name, policy type and days left. Draft the follow-up email for each.
Set it up as a routine
Once the first ten claims and comparisons have run cleanly, turn the workflow into a standing routine. Superkind watches AMEISE for new claims, upcoming renewals and approaching deadlines and handles them according to your rules - no forwarding, no manual check-in.
- Daily - new claims processed, deadline alerts posted, follow-up emails drafted.
- Weekly - renewal comparisons for the next 90 days, status overview of open claims.
- Monthly - portfolio report: how many claims processed, how many renewals saved, average response time.
When the office grows or takes on new lines of business, you do not start over. Build a custom claims dashboard or a client self-service portal on the Superkind platform, on top of everything Superkind already knows about your portfolio. The 1,700+ integrations - including Outlook, Slack, Excel and Calendly - keep it connected without new middleware.
The GDPR checklist for insurance brokers using AI
Insurance brokers operate under a double layer of data protection: GDPR for all personal data and section 203 StGB (professional secrecy) for health and life insurance data. Add GewO section 34d (the licence requirement that ties your operation to regulatory oversight) and GDPR Art. 9 (special categories, including health data for Krankenversicherung), and the bar for any AI tool is high. Here is what to check before handing client data to an AI.
GDPR and professional secrecy checklist
- DPA / AVV signed - GDPR Art. 28 requires a data processing agreement with every AI provider that sees personal data. Superkind offers a DPA through the Trust Center at trust.superkind.ai1
- Health data addressed - GDPR Art. 9 restricts processing of health data. Only process it with a provider that has explicit contractual safeguards and does not train on it2
- Section 203 StGB - insurance intermediaries handling health and life insurance data are bound by professional secrecy. The AI provider must be contractually bound to secrecy under section 203 para. 3 StGB3
- EU hosting - data must be processed in Europe. No transfer to US servers, no unclear data residency
- No model training - the provider must not use your client data to train AI models
- AI literacy - EU AI Act Art. 4 requires that staff who interact with AI are trained. Document your internal AI policy5
- Transparency - if AI is involved in client communication, the client must be informed (EU AI Act Art. 50)5
- Audit log - every AI action on client data must be traceable: which policy was read, which report was drafted, who approved
Other ways to handle broker tasks
| Method | Effort | Error risk | Best for |
|---|---|---|---|
| Superkind | Low: connect systems, write rules in plain language | Low: cross-checks against AMEISE data, approval where you want it, EU hosting | Broker offices running AMEISE with Outlook, Teams or Slack, 1,700+ integrations |
| Manual in AMEISE | High: every claim, comparison and deadline by hand | Medium: missed deadlines, copy errors between systems | Solo brokers with a small portfolio |
| ChatGPT or Claude | Medium: paste data, copy results back | High: no link to AMEISE, health data leaves the workflow, no audit trail | One-off text tasks with no personal data |
| Excel macros | Medium: build and maintain macros | Medium: brittle, no cross-system checks | Simple deadline lists without claims processing |
Common mistakes
- Pasting health data into free AI tools - free tiers of most AI assistants have no DPA and may train on your input. Never enter client names, health conditions or policy numbers into a tool without a signed AVV.
- No approval rule for claim reports - a claim report sent to the wrong insurer or with the wrong amount creates liability. Set approval on every outgoing claim report.
- Skipping the section 203 check - even if the AI provider is GDPR compliant, it may not meet the professional secrecy requirements of section 203 StGB. Check the DPA explicitly for secrecy obligations.
- Ignoring the AI Act transparency rule - since August 2026, clients must be informed when AI is involved in their communication. Add a note to your data protection policy and your email signatures where applicable.
- Not logging AI actions - without an audit trail, you cannot prove what the AI did with client data. Use a provider that logs every access and every action.
6 tips for GDPR-compliant AI in the broker office
1. Start with renewals, not claims
Renewal comparisons are lower risk than claim processing. Let Superkind run ten comparisons from AMEISE before you hand it the first claim with health data.
2. Write approval rules like you would brief a new employee
“Claims over EUR 2,000: my approval. Cancellation notices: always. Renewal reminders for Kfz under EUR 500: send automatically.” Short, concrete sentences work better than a 20-page process document.
3. Keep health data separate
Krankenversicherung data falls under GDPR Art. 9. Set a stricter approval rule for every task that touches health insurance policies: always review before sending.
4. Use the DPA from the Trust Center
Download the DPA from trust.superkind.ai and file it with your data protection documentation. Your Datenschutzbeauftragter or external data protection officer will need it.
5. Document your AI policy
EU AI Act Art. 4 requires AI literacy training. Write a one-page internal policy: which tools are allowed, what data may go in, who approves. This protects you in an audit.
6. Tell your clients
Transparency builds trust. Add a line to your data protection notice that you use AI for administrative tasks, hosted in Europe, GDPR compliant, no training on data. Most clients will not mind - they will appreciate the faster response times.
Conclusion
Processing client data as an insurance broker with AI is not about replacing your judgement. It is about handing the reading, matching, drafting and tracking to an AI employee that works in AMEISE, Outlook and Slack the same way you do - with approval where you want it and every action logged. Superkind is the fastest way to see whether it fits: sign up for free at app.superkind.ai, connect AMEISE via computer use, give it the first renewal comparison and check the result. If you want to go deeper first, read our guide to automating accounting with AI.
Frequently Asked Questions
Yes, if the AI provider signs a data processing agreement (DPA/AVV) under GDPR Art. 28, does not train on your data and processes it in Europe. Insurance brokers handle personal, financial and health data that falls under Art. 9 GDPR. Superkind is hosted and processed in Europe, signs a DPA through the Trust Center and never trains on your data, so the data stays where it belongs.
AMEISE is a desktop and browser-based broker management program (Maklerverwaltungsprogramm). Superkind works with AMEISE natively via computer use - it logs in, reads policy data, enters claim updates and exports comparison data, the same way a colleague would. No API or custom integration is needed. The session runs inside your infrastructure, not outbound.
Insurance intermediaries who handle health and life insurance data are bound by section 203 StGB. When you use an AI processor, the provider must be contractually bound to secrecy. Superkind signs a DPA, processes data in Europe, never trains on it and logs every access. This satisfies the requirements for commissioned processing under section 203 para. 3 StGB.
Only if you set it up that way. For sensitive communication like claim reports, cancellation notices or policy recommendations, you can require approval before Superkind sends. Routine reminders like renewal follow-ups can run on their own. You decide which steps need your OK.
You start for free at app.superkind.ai with up to 150 hours of work, no credit card, unlimited users. The Business plan starts at EUR 50 per month for 50 hours of work for the whole office with unlimited users. No price per seat. As of November 2026.
Superkind has 1,700+ integrations including Outlook, Gmail, Microsoft Teams, Slack, Excel, SharePoint, HubSpot, Pipedrive and Calendly. Programs without an API integration, like AMEISE, work natively via computer use in the browser or the desktop client.
Sources
- EUR-Lex - Regulation (EU) 2016/679 (GDPR), Art. 28 (Processor)
- EUR-Lex - Regulation (EU) 2016/679 (GDPR), Art. 9 (Special categories of personal data)
- Gesetze im Internet - section 203 StGB (Violation of private secrets)
- Gesetze im Internet - section 34d GewO (Licence requirement for insurance intermediaries)
- EUR-Lex - Regulation (EU) 2024/1689 (EU AI Act)
- Versicherungsbote - Maklerverwaltungsprogramme im Test (2026)
- Dr. Datenschutz - Geheimhaltungspflicht nach StGB fuer selbstaendige Versicherungsmakler
- Versicherungsbote - EU AI Act: Was Versicherer jetzt wissen muessen
Send Superkind your first claim.
Start for free in Outlook, Teams or Slack. Or let us show you in 30 minutes how it runs in your AMEISE workflow.

