How to read the traffic light

    Your industry: Insurance brokers and intermediaries

    Tailored to insurance brokers and intermediaries: FINMA registration and professional duties, contractual confidentiality and the DPA, health data in life, daily sickness allowance and BVG dossiers with its own rating. Stricter rules apply to insurers (Circular 2018/3 directly, outsourcing in the business plan): talk to us.

    Green: proven and recommended

    Works with client data: the setup is proven, contract and governance are in place. This is exactly how you should do it.

    Yellow: unclear, depends on the setup

    Depends on the contract, configuration and industry: feasible with a documented risk assessment, not without it.

    Red: not possible

    Not defensible for client data in our risk assessment: no contract, no control or no documented safeguards. Often still the best choice for research, marketing and anonymised content.

    In this view the first rating applies to property and commercial client data, the second to dossiers containing health data. Health data is especially sensitive (Art. 5(c) DPA): large-scale processing requires a data protection impact assessment (Art. 22(2)(a) DPA), consent must be explicit (Art. 6(7)(a) DPA), and medical reports and claims narratives can hardly be pseudonymised reliably because diagnosis, accident date and location together identify a person. A small or mid-sized broker rarely manages this effort, so the Swiss pipeline is the more honest advice.

    All AI options at a glance

    Filter the table by traffic-light colour. On a smartphone it scrolls sideways.

    SolutionProperty and commercial clientsWith health dataModelsData locationModel qualityEffortCostWhat to watch
    Azure OpenAI Switzerland (Standard)
    Microsoft Azure, Switzerland North region
    GreenGreen
    With an impact assessment for large volumes
    GPT-4o (until April 2027), Embeddings
    Processing
    Switzerland
    Storage
    Switzerland
    Solid, several generations behind the frontierMedium, integration by IT or partnerLow, per token, no base feeA Swiss data location satisfies the outsourcing rules most easily (Circular 2018/3 for insurers, applied analogously for brokers): choose the Standard deployment type (not Global or Data Zone), contract with confidentiality and audit rights. For new customers, GPT-4o (until April 2027) is effectively the only option; GPT-4.1 is deprecated.
    Azure OpenAI Switzerland (Provisioned)
    Microsoft Azure, Switzerland North, reserved capacity
    GreenGreen
    With an impact assessment for large volumes
    GPT-5.1 (until May 2027)
    Processing
    Switzerland
    Storage
    Switzerland
    Very good, strongest model with CH guaranteeMedium, integration by IT or partnerFrom approx. USD 13,000 per month (minimum 50 PTU)Like the Standard variant, but with regional Provisioned capacity in Switzerland North (not Global or Data Zone Provisioned): GPT-5.1 (until May 2027) from approx. USD 13,000 per month (minimum 50 PTU), and a successor in Switzerland is not guaranteed. Usually too expensive for small and mid-sized brokers, at most an option for insurers with high volume.
    Swiss AI platforms
    e.g. AIgent, Swisscom, Phoenix Technologies (kvant), Infomaniak
    GreenYellow
    Vet the provider in depth
    Open models such as DeepSeek, Qwen, GLM, Apertus
    Processing
    Switzerland
    Storage
    Switzerland
    Good to very good, a step behind the frontierLow, ready-made interface, some with agentsMedium, licence per user, sometimes plus usageWell suited for property and commercial client data; for health data vet the provider in depth, hence yellow in the second rating.
    AI in your industry software
    e.g. practice, law firm, CRM or portfolio systems
    Depends on providerDepends on providerUsually GPT or Claude in the background
    Processing
    Depends on provider
    Storage
    Depends on provider
    Good, tailored to the use caseLow, the system is already in useLow to medium, often as an add-on moduleBroker and claims systems: ask in writing which model runs where. Assess health data separately. Data from insurer portals can be contractually bound, so review the cooperation agreements.
    Microsoft 365 Copilot
    Microsoft, with EU Data Boundary
    YellowYellow
    Exclude health dossiers via sensitivity labels
    GPT models from OpenAI, operated by Microsoft
    Processing
    EU/EFTA
    Storage
    Switzerland (Data Location or ADR)
    Very good, strong in everyday office workLow, licence and configurationMedium, licence per user and monthDefensible for property and commercial client data with Flex Routing disabled and Anthropic models switched off; exclude health dossiers from Copilot via sensitivity labels.
    Azure OpenAI Data Zone EU
    Microsoft Azure, resource in Switzerland North
    YellowRed
    Only structured, pseudonymised data with a DPIA as the exception
    Latest GPT generation, e.g. GPT-5.4 to GPT-6.1
    Processing
    EU Data Boundary, confirm countries with Microsoft before use
    Storage
    Switzerland
    Frontier, latest GPT modelsMedium, integration by IT or partnerLow, per tokenFeasible for property and commercial client data with a risk assessment; weigh the residual CLOUD Act risk explicitly. Red for health data: only structured, pseudonymised data with a DPIA as the exception. The EU Data Boundary can also include EFTA countries: confirm the affected countries with Microsoft before use.
    Claude via AWS Bedrock (EU)
    Amazon Web Services, EU regions
    YellowRed
    Only structured, pseudonymised data with a DPIA as the exception
    Opus 5 and Sonnet 5 in Ireland or Stockholm, Opus 5.5 and Sonnet 5.5 via EU inference
    Processing
    EU
    Storage
    No prompt storage by Bedrock
    Frontier, especially strong for text and analysisMedium to high, AWS account and development neededLow to medium, per tokenLike Data Zone EU: document EU processing, red for health data.
    Gemini via Google Vertex AI (EU)
    Google Cloud, EU regions
    YellowRed
    Only structured, pseudonymised data with a DPIA as the exception
    Gemini models
    Processing
    EU
    Storage
    EU or Switzerland
    Frontier, strong with long documentsMedium to high, Google Cloud project and developmentLow to medium, per tokenLike Data Zone EU; have the processing location verified in writing, red for health data.
    Claude directly from Anthropic
    Claude API, Team and Enterprise
    RedRedClaude Fable 5.1, Opus 5.5, Sonnet 5.5
    Processing
    US or global
    Storage
    US
    Frontier, newest Claude models firstLow, ready to useMedium, licence or per tokenUS processing: unsuitable for policy and claims data; usable for marketing and research.
    Claude in Microsoft Foundry or Copilot
    Microsoft, operated on Anthropic infrastructure
    RedRedClaude models
    Processing
    Outside the EU Data Boundary
    Storage
    Not guaranteed
    Frontier, same as Claude directLow, switchable at a toggleMedium, in licence or per tokenOff by default in Copilot: leave it off until Microsoft offers EU processing.
    Copilot with Flex Routing enabled
    Microsoft 365, setting available since April 2026
    RedRedGPT models
    Processing
    At peak load also US, Canada, Australia
    Storage
    Switzerland
    Very good, same as CopilotLow, a single settingMedium, licence per user and monthDisable: at peak load data moves to the US, Canada or Australia.
    Private AI accounts
    ChatGPT, Claude.ai, Gemini with a private or free account
    RedRedAll of them
    Processing
    Unclear, mostly US
    Storage
    US
    Frontier, which makes it so temptingNone, and that is exactly the problemLow, free or privately paidClient data in private accounts breaches data protection and contractual confidentiality. Professional secrecy (Art. 62 DPA) has covered all confidential personal data since the revised DPA: anyone who wilfully discloses it risks a fine of up to CHF 250,000 upon complaint.

    Note on the US CLOUD Act

    Microsoft, AWS and Google are US corporations and are subject to the US CLOUD Act, even with data centres in Switzerland or the EU. This residual risk belongs in every risk assessment.

    The best solutions: three proven setups for insurance brokers and intermediaries

    Hardly any organisation needs just one tool. What has proven itself is the combination of an AI employee for daily work and a secure interface for automations.

    For brokers we recommend the strict setup: a Swiss platform as the working surface and Azure Switzerland Standard (GPT-4o) for automations. Provisioned with GPT-5.1 is too expensive for small and mid-sized brokers and retires in May 2027.

    Recommended for most SMEs

    Pragmatic: Copilot plus Azure Switzerland

    • M365 Copilot for emails, documents and meetings, with storage in Switzerland and Flex Routing disabled
    • Azure OpenAI Switzerland North for automations with sensitive client data, such as document review or reports: for new customers, GPT-4o (until April 2027) is effectively the only option there
    • A clear policy: what may go into Copilot, what only goes through the Swiss pipeline
    When policy demands «Switzerland only»

    Strict: Swiss platform plus Azure Switzerland

    • A Swiss AI platform as the working surface for all employees
    • Azure OpenAI Switzerland North (GPT-4o) or Provisioned (GPT-5.1, from approx. USD 13,000 per month) for automations
    • External models in the platform selectively disabled per use case
    When quality matters above all

    High performance: reference architecture with frontier models in the EU

    • Frontier model for quotes, comparisons and correspondence
    • Health dossiers stay on the Swiss pipeline
    • Risk assessment, contract and client information with extra care
    How this split works for brokers

    What FINMA and data protection expect

    Independent insurance brokers are registered with FINMA and supervised directly, and supervisory notice 08/2024 applies to them too. Tied agents are supervised by the insurer itself: align AI use with the insurer in advance, its IT policy decides. Insurers face the full programme: Circular 2018/3 applies directly, and outsourcing of significant functions belongs in the business plan under Art. 4 ISA. The DPA applies to everyone, with heightened protection for health data.

    • AI inventory: which applications, which data, which model, which data location
    • Risk assessment per application, including cross-border processing and the US CLOUD Act
    • Policy for employees: approved tools, banned shadow AI, human oversight
    • Outsourcing contract with confidentiality, audit rights and data location (Circular 2018/3 directly for insurers, analogously for brokers)
    • For insurers: file the outsourcing of significant functions in the business plan with FINMA (Art. 4 ISA)
    • Data protection impact assessment for large-scale processing of health data (Art. 22 DPA)
    • Obtain explicit consent where the processing of health data relies on it (Art. 6(7) DPA)
    • Review cooperation agreements with insurers for data transfer and processing clauses
    • Client information in the policy terms or privacy policy reviewed

    This overview does not replace legal advice. Model availability and regions change constantly; October 2026 edition. Verify details with the provider before use.

    Sources

    • FDPIC: Guide to checking the admissibility of transferring personal data to countries without an adequate level of data protection
    • FDPIC: Factsheet on commissioned processing of personal data under the revised DPA
    • Microsoft Learn: Model availability by region in Azure Foundry
    • Microsoft Learn: Deployment types (Global, Data Zone, Standard, Provisioned)
    • AWS: Model availability by region in Amazon Bedrock
    • Google Cloud: Data residency for generative AI
    • FINMA: Supervisory notice 08/2024 on governance and risk management when using AI (insurance intermediaries explicitly included in the AI survey)
    • Insurance Supervision Act (ISA) and Supervision Ordinance (ISO): registration and professional duties of insurance intermediaries
    • Revised DPA: professional secrecy (Art. 62) and data protection impact assessment (Art. 22)

    We implement the recommended setup for you

    Taskstreams builds and operates the pipeline that fits your policy: Switzerland only with Azure OpenAI Switzerland North, or the frontier model in the EU while your client data stays in Switzerland. Contract and governance are included; you receive finished AI employees for your processes, from document review to client reporting, instead of your own infrastructure project.

    • Processing and storage in Switzerland (Azure Switzerland North)
    • Contract, policies and documentation for data protection and supervision included
    • Fixed-price pilot, then ongoing operations by us