# GDPR & Swiss nFADP Compliant AI Chat Widget

Deploy an AI chat widget compliant with EU GDPR and Swiss nFADP. Zero model training, no ad or analytics cookies in embeds, EU Sentry hosting, and BYOK control.

For website operators in the EU, EEA, and Switzerland, the main compliance question is what happens on **your own site** when a visitor sees or uses `<ai-chat>`. This guide covers embedded widget architecture and rollout steps; full legal terms and platform-wide sub-processors live in our [Privacy Policy](privacy.md) and [Privacy Overview](private.md).

## Embedded Widget vs. Portal Privacy (TDDDG § 25 / ePrivacy)

When you embed `<ai-chat>` on your site, visitors load an isolated sandbox build (`widget-app.html`) rather than the full `aish.li` management portal:

| Area                                | Embedded `<ai-chat>` Widget (`widget-app.html`)                            | Management Portal (`aish.li`)                            |
| :---------------------------------- | :------------------------------------------------------------------------- | :------------------------------------------------------- |
| **Google Analytics (`_ga`)**        | **Not loaded** on your visitors                                            | First-party proxied GA4, Consent Mode v2 (`ad_*` denied) |
| **Advertising / Cross-Site Pixels** | **None**                                                                   | **None**                                                 |
| **Sentry Session Replay**           | **Disabled** inside embeds                                                 | Masked client-side (`de.sentry.io`, EU)                  |
| **Browser Storage Used**            | Essential `anonymous_id` + chat state only                                 | Auth session, locale, currency, `anonymous_id`           |
| **Frame & Origin Security**         | Sandboxed iframe + CSP `frame-ancestors` for [Widget Sites](/keys/widgets) | Same-origin security headers                             |

Because embedded widgets omit Google Analytics, advertising tags, and Session Replay, browser storage is limited solely to keeping an active visitor chat or conversational form working across turns. Only origins explicitly allowlisted under [Widget Sites](/keys/widgets) can frame your public agent.

## Website Operator Checklist (GDPR / revDSG / EU AI Act Art. 50)

Before enabling `<ai-chat>` on an EU, Swiss, or DACH website:

1. **Update Your Website Privacy Notice**: Disclose the embedded AI assistant, processing purpose, and infrastructure providers under Art. 13 GDPR / Art. 19 revDSG (nFADP).
2. **Keep AI Interaction Transparent (EU AI Act Art. 50)**: Name or greet visitors clearly as an AI assistant so automated interaction is obvious.
3. **Avoid Regulated Sensitive Categories**: Instruct agents not to solicit Art. 9 special-category data, payment card details, or data from minors under 16 without an Enterprise agreement (see [Terms of Service](terms.md)).
4. **Lock Down Widget Origins**: Register only your exact production domains in [Widget Sites](/keys/widgets).
5. **Select Paid BYOK If Bringing Your Own Key**: Enterprise [BYOK credentials](/secrets) must use a paid commercial cloud billing tier rather than a provider free tier ([free-tier caveats](key.md#free)).

> [!NOTE]
> This guide documents AIsh.li's technical behavior and configuration options and does not constitute legal advice. Verify your consent and privacy notice obligations (such as TDDDG § 25 in Germany) with your data protection officer or legal counsel.

## Roles, Zero-Training & Sub-Processors

- **Controller / Processor Split**: You act as data controller for your website visitors; AIsh.li processes visitor chat interactions as a service provider / processor on your behalf.
- **Commercial Zero-Training & Sovereignty**: AIsh.li runs on paid commercial inference agreements with zero training or human review, plus Enterprise [BYOK](key.md) and [on-premise / air-gapped licensing](consulting.md) (see [Privacy Overview](private.md)).
- **Sub-Processors**: Anonymous visitor widget chats touch **Google Cloud** (Cloud Run, Firestore, commercial Gemini APIs), **Cloudflare** (CDN/edge delivery), and **Sentry EU** (`de.sentry.io` error diagnostics) — whereas Clerk, Stripe, and first-party portal analytics apply only to signed-in `aish.li` users. See the full breakdown in [Privacy Policy](privacy.md).

## Frequently Asked Questions

### Does embedding `<ai-chat>` require a cookie consent banner?

Embedded widgets do not load Google Analytics, ad pixels, or Session Replay, storing only an essential `anonymous_id` UUID strictly required to keep a visitor's active multi-turn conversation running. Confirm with your legal counsel whether that qualifies as strictly necessary storage under your local rules (e.g., TDDDG § 25(2) Nr. 2 or Art. 6 nFADP), particularly when the widget starts minimized until clicked.

### Is AIsh.li suitable for companies in Germany, Austria, and Switzerland (DACH)?

Yes. Commercial zero-training terms, EU-hosted Sentry error telemetry (`de.sentry.io`), CSP origin allowlisting, paid [BYOK](key.md), and [on-premise options](consulting.md) are designed for EU GDPR and Swiss revDSG/nFADP compliance.

### Can we connect a paid Google Cloud / Gemini API key for direct billing and contract terms?

Yes. On the [Enterprise plan](/pricing), add your commercial API key in [Your Secrets](/secrets) so inference routes under your own cloud terms. Avoid free-tier provider keys in production ([details](key.md#free)).

### How do we request a Data Processing Agreement (DPA) or on-premise deployment?

See [Enterprise & Consulting](consulting.md) and [Pricing](/pricing), reach out via our [Contact page](/contact), or email <a href="#" data-obfuscated-mailto="bWFpbHRvOnN1cHBvcnRAYWlzaC5saQ==" class="obfuscated-email"><span class="email-user">support</span><span class="email-at" aria-hidden="true"></span><span class="email-domain">aish.li</span></a>.
