--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/meingpt-vs-omnifact/" data_url: "https://onaihq.com/compare/agents/meingpt-vs-omnifact/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # meinGPT vs Omnifact > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 46 criteria with sourced findings for both products, including 46 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - meinGPT source checks: 2026-10-21 to 2026-10-26. - Omnifact source checks: 2026-10-21. - Canonical HTML: https://onaihq.com/compare/agents/meingpt-vs-omnifact/ - Machine-readable JSON: https://onaihq.com/compare/agents/meingpt-vs-omnifact/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Curated multi-provider models are selected per chat or by context-length routing; the signed DPA and admin approvals affect availability. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business and individually contracted Enterprise web workspace; permitted models depend on workspace approval and DPA; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - auto_routing: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. - providers — Which model providers are available? [supported]: Model authors include OpenAI, Anthropic, Google, Mistral, DeepSeek, Moonshot, Qwen, GLM and MiniMax. Hosts are separate from authors. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2. - current_models — Which current models are selectable on this plan? [supported]: Active table lists GPT-4.1, GPT-4o/Mini, GPT-5/mini/Nano/Thinking/5.2/5.4/5.5/5.6 Luna/Sol/Terra, GPT-6 Luna/Sol/Astra, GPT-6.1 Sol; o3; Claude Haiku 5.5, Opus 4.5/4.6/4.7/4.8/5/5.5, Sonnet 4.6/5/5.5; Gemini 3.5 Flash/Flash-Lite, 3.6/3.7/3.8 Flash and 4 Argon; MeinGPT Web; Mistral Medium 3.5/CodeStral; GPT-OSS 120B; Kimi K2.6/K3; DeepSeek V3.2/V4 Flash/V4 Pro/V4.1 Flash; GLM-5.3/Flash, MiniMax-M3 and Qwen3.8 Max. Duplicate EU/provider routes exist. GPT-6 Astra requires accepted AVV 2.0. Model labels do not guarantee one-to-one public provider variant names. Sources: meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:models-rev2, meingpt:meingpt:rates. - user_choice — Can users pick the model per chat? [supported]: Users select and switch a permitted model per chat. Sources: meingpt:meingpt:models-rev2. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [partial]: Bestes Modell starts with GPT-5 and changes to Gemini 3.5 Flash-Lite only when context is too long. This is length routing, not task routing; visibility of the final routed identity is not established. Sources: meingpt:meingpt:models-rev2. - multimodal_input — Which models accept images, audio or files? [supported]: GPT-4o/5, Claude, Gemini and Mistral Medium/Magistral accept JPEG/PNG/GIF/WEBP; DeepSeek, GPT-OSS, CodeStral and older Kimi K2 do not. Audio uses separate transcription. Sources: meingpt:meingpt:models-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models-rev2, meingpt:meingpt:lifecycle-rev2, meingpt:meingpt:rates #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Manual selection spans OpenAI, Anthropic, Google and Mistral with EU/direct routes and tier controls. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed model catalogue; customer API keys and custom/self-hosted endpoints require Enterprise BYOK; add_ons=Enterprise BYOK for custom provider endpoints; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - current_models: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. - multimodal_input: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. - Unverified auto_routing: No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - providers — Which model providers are available? [partial]: Pro/Enterprise managed provider options include OpenAI/AzureOpenAI, Anthropic, Google/Vertex and Mistral subject to workspace configuration. Customer API keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK. Optional DPA-listed Groq is not treated as a currently selectable managed model. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:models. - current_models — Which current models are selectable on this plan? [partial]: Public text catalogue: GPT6Sol/Luna,5.6Sol/Terra/Luna,5.5,5.4/mini,5.2,5.1,5/mini/nano,4.1/mini/nano,4o/mini,4,3.5; Claude Opus5.5/5/4.8/4.7/4.6/4.5/4.1/4, Sonnet5.5/5/4.6/4.5/4, Haiku5.5/4.5; Gemini4Argon,3.8/3.7/3.6/3.5Flash,3.5Flash Lite,3.1Pro/Flash Lite,3Pro,2.5Pro/Flash,2.0Flash/Flash Lite; Mistral Medium3.5/3, Large3, Small4, Nemo, Ministral8B, Pixtral Large, Codestral, Devstral Small. Each is subject to admin enablement, tier, route and provider availability; not independently tested in picker. Sources: omnifact:omnifact:models. - user_choice — Can users pick the model per chat? [supported]: Picker changes before/within a conversation and shows provider logo, model name and region flag. Reasoning effort has Low/Medium/High/Extra High depending on model. Sources: omnifact:omnifact:select. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [unknown]: Does the product route between models automatically, and is the chosen model shown? Unknown. No documented automatic cross-model routing strategy or chosen-model display after automatic routing was established; autonomous tool selection is separate from model routing. - multimodal_input — Which models accept images, audio or files? [partial]: Image input only for capable selected models; experimental audio uploads need audio-capable models. Extracted document text and code tools are separate paths; no complete model-by-model native audio matrix was established. Sources: omnifact:omnifact:files, omnifact:omnifact:groups-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers-rev2, omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:select, omnifact:omnifact:files, omnifact:omnifact:groups-rev2, omnifact:omnifact:pricing-rev2 ### MOD-02: Model freshness Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A dated changelog and explicit retirement rules exist; comparative release-lag medians were not established. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - version_pinning: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. - Unverified release_lag_days: Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Provider release dates for the last three major releases per provider were not reconciled against product release dates, so no lag or median is asserted. - changelog — Is there a dated public model changelog? [supported]: Public releases include v2.67.0 dated 2026-10-18. Sources: meingpt:meingpt:changes. - deprecation_notice — How much notice is given before a model is removed? [supported]: Normally four weeks, then reminders at two and one week; provider short notice can shorten this. Opus 4.5 is listed for 23 November retirement; other future dates are in the table. Sources: meingpt:meingpt:lifecycle. - version_pinning — Can an admin keep an older model version? [partial]: An available model can be selected, but retirement automatically substitutes a successor in assistants, workflows and chats; indefinite retention of a retired model is excluded. Sources: meingpt:meingpt:lifecycle. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:changes, meingpt:meingpt:lifecycle #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dated model/feature changelog exists; exact release lag and fixed deprecation policy are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Unverified release_lag_days, deprecation_notice, version_pinning: Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - release_lag_days — What was the lag for each of the last three major releases, per provider? [unknown]: What was the lag for each of the last three major releases, per provider? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - changelog — Is there a dated public model changelog? [supported]: Monthly release notes updated2026-10-20; individual feature posts date Gemini4Argon October 13, Haiku5.5 October 8, Sonnet5.5 September 28 and GPT6/Opus5.5 September 22. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. Last-three major releases per provider were not reconciled against provider GA dates; no binding removal notice or Saa S version-pinning guarantee was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:blog ### MOD-03: Bring-your-own keys and provider contracts Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Customer LLM API keys, cloud contracts and arbitrary model endpoints are explicitly excluded from the hosted catalogue. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - own_api_keys: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. - own_cloud_contract: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. - custom_endpoint: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. - byo_pricing: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. - byo_restrictions: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. - own_api_keys — Can the customer use its own provider API keys? [unsupported]: The hosted workspace does not accept customer OpenAI, Azure OpenAI or Anthropic keys. DeepL translation BYOK is separate. Sources: meingpt:meingpt:models. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unsupported]: LLM requests use meinGPT-managed provider accounts, not customer Azure/OpenAI contracts. Sources: meingpt:meingpt:models. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [unsupported]: Admins cannot add a model or provider key to the catalogue. Custom MCP adds tools, not LLM endpoints. Sources: meingpt:meingpt:models. - byo_pricing — Does BYO change the licence price? [partial]: There is no hosted LLM BYOK licence schedule because LLM BYOK is excluded. DeepL BYOK bills translation directly through DeepL. Sources: meingpt:meingpt:models, meingpt:meingpt:translation. - byo_restrictions — Which features stop working with BYO? [partial]: Only DeepL has a documented BYOK exception; it does not replace the workspace model route. Sources: meingpt:meingpt:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:models, meingpt:meingpt:translation #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise BYOK supports own provider accounts and custom OpenAI-compatible connections. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise BYOK, customer provider contracts; add_ons=Customer provider charges separate; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - own_cloud_contract: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. - byo_pricing: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. - Unverified byo_restrictions: No complete BYOK-specific feature failure/parity matrix or public licence discount was established. - own_api_keys — Can the customer use its own provider API keys? [supported]: Enterprise only; connects own provider API keys, charges provider account and bypasses standard Omnifact rate limits. Sources: omnifact:omnifact:providers. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Supported environments include Azure OpenAI, Vertex Anthropic/Vertex Google; model settings mention AWSBedrock via custom endpoints. Customer deployment/contract setup details not fully specified. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [supported]: Custom provider supports OpenAI-compatible endpoints; self-hosted connection enabled with support. Sources: omnifact:omnifact:providers, omnifact:omnifact:terms. - byo_pricing — Does BYO change the licence price? [partial]: BYOK moves model costs to customer account/negotiated rates; Enterprise licence adjustment is quote-only. Sources: omnifact:omnifact:providers. - byo_restrictions — Which features stop working with BYO? [unknown]: Which features stop working with BYO? Unknown. No complete BYOK-specific feature failure/parity matrix or public licence discount was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:providers, omnifact:omnifact:model-settings, omnifact:omnifact:terms ### MOD-04: Local and self-hosted models Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Vendor-operated open-model routes exist; customer-hosted LLM and embedding routes were not verified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - vendor_hosted_open_models: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. - Unverified self_hosted_chat, self_hosted_embeddings, feature_parity: Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - self_hosted_chat — Can chat use a customer-hosted model? [unknown]: Can chat use a customer-hosted model? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. Models documentation excludes adding customer model endpoints. No supported customer-hosted embedding route or parity matrix was found; Outpost stores a local index but does not establish local inference. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Open-weight routes include GPT-OSS via Nebius in Finland, DeepSeek/Kimi via TensorX in Ireland and custom models via Verda in Finland; the active table also lists Melious routes. These are vendor-selected routes, with exact region absent for Melious. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:lifecycle, meingpt:meingpt:subprocessors #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise can integrate customer-hosted models; embedding and tool parity remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise self-hosted model connection; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - vendor_hosted_open_models: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. - Unverified self_hosted_embeddings, feature_parity: No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Enterprise lists self-hosted LLMs; terms6.4 requires coordination with support and custom provider endpoints are documented. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [unknown]: Can retrieval use customer-hosted embeddings? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - feature_parity — Which features fail with self-hosted models? [unknown]: Which features fail with self-hosted models? Unknown. No documented customer-hosted embedding route or exhaustive feature-parity matrix was established; on-premise platform availability alone does not prove either. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: Mistral family appears with EU flags; the operating party and infrastructure for every open-weight route are not fully mapped. It is not proof of Swiss hosting. Sources: omnifact:omnifact:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:providers, omnifact:omnifact:terms, omnifact:omnifact:models ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins set model access and defaults; personal category limits have documented exceptions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - limit_behaviour: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. - Unverified data_bound_models: A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run. - model_allowlist_by_group — Can admins limit models per group? [supported]: Per-team/person allow and deny rules are documented. Workspace admins and free models are exempt; denied chat models fall back, denied API models fail. Sources: meingpt:meingpt:config. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? Unknown. A separate rule binding particular knowledge sources to approved models was not documented; no two-user restriction test was run. - default_model — Can admins set the default model? [supported]: Workspace admins set the default model and chat standards. Sources: meingpt:meingpt:config. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Six usage levels set monthly EUR limits for text, images, API, other services and meeting bots; no single universal message cap. Sources: meingpt:meingpt:limits. - limit_behaviour — What happens when a limit is reached? [partial]: Zero blocks the category; API budget exhaustion returns 403. Running/concurrent meeting recordings can exceed personal limits; scheduled tasks consume workspace credit outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:limits, meingpt:meingpt:api #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Groups add model-tier/capability permissions while organization settings control concrete models/routes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - model_allowlist_by_group: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. - data_bound_models: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. - default_model: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. - user_limits: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. - model_allowlist_by_group — Can admins limit models per group? [partial]: Groups add Base/Standard/Premium-tier and US-hosted-model access. Everyone and overlapping groups union grants; no deny overrides. Concrete model enablement is organization-wide, not an arbitrary per-group model list. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: Admins disable providers/models globally; DPA annexes also describe per-Space provider approval. No tested classifier routes knowledge content to distinct allowed models automatically. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:dpa. - default_model — Can admins set the default model? [partial]: October notes set Haiku5.5 as fast default for new organizations. Image default and Published Space model are configurable; universal organization text-default setting not established. Sources: omnifact:omnifact:changes, omnifact:omnifact:model-settings, omnifact:omnifact:published. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Plan-determined per-user24-hour rolling message quotas show remaining count/reset. Numeric plan quotas are not public; pooled credit and page limits are separate. Sources: omnifact:omnifact:chat. - limit_behaviour — What happens when a limit is reached? [supported]: Daily message exhaustion disables new sends until reset. Monthly credit exhaustion greys premium models and chat falls back; Gateway returns credit error for all models without fallback. Sources: omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:dpa, omnifact:omnifact:changes, omnifact:omnifact:published, omnifact:omnifact:chat, omnifact:omnifact:limits, omnifact:omnifact:gateway ## Company knowledge ### KNOW-01: Files in chat Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat uploads and direct sandbox processing have different document behavior. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - spreadsheets: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. - full_vs_chunked: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. - Unverified ocr: No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test. - formats — Which formats are accepted? [supported]: Text/PDF, images, Word, PowerPoint, Excel, CSV, TXT and URLs are listed; sandbox is needed to read archives and raw mail formats. Sources: meingpt:meingpt:flow. - limits — What size and count limits apply per file and chat? [supported]: 50 files per chat, 50 MB per non-image file; JPEG/PNG/WEBP/GIF are model-readable images. Provider PDF/page/image limits still apply. Sources: meingpt:meingpt:chat, meingpt:meingpt:models. - ocr — Are scanned PDFs read? [unknown]: Are scanned PDFs read? Unknown. No scanned contract or structured spreadsheet fixture was uploaded; OCR behavior for direct scanned attachments was not bounded by a test. - spreadsheets — Are Excel tables read with structure intact? [partial]: Text extraction loses layout; the sandbox reads original Excel files using code and can preserve formulas. No fixture result is claimed. Sources: meingpt:meingpt:chat, meingpt:meingpt:sandbox. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Direct attachments enter model context after extraction and are constrained by the context window; pools retrieve passages instead. Long-chat compression can drop earlier attachment context. Sources: meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:pools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:chat, meingpt:meingpt:models, meingpt:meingpt:sandbox, meingpt:meingpt:pools #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Broad attachment formats and published limits exist; indexing uses OCR/chunks while workbook fidelity is untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - limits: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. - ocr: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. - spreadsheets: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. - full_vs_chunked: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. - formats — Which formats are accepted? [supported]: PDF, Word, Excel, Power Point, Open Document text/presentation, TXT, JSON, Markdown, CSV, SVG; images PNG/JPEG/Web P/HEIC/HEIF/AVIF/BMP/GIF/ICO/TIFF/SVG; audio examples MP3/WAV/AAC/FLAC with group/model restriction. Sources: omnifact:omnifact:files. - limits — What size and count limits apply per file and chat? [partial]: 10 attachments/message;8000 text characters/message;20MB/image;25MB/audio. Space Uploaded Files FAQ says no individual/aggregate file-size limit; ordinary document/chat count ceilings not fully specified. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads. - ocr — Are scanned PDFs read? [partial]: Space upload pipeline documents Apache Tika OCR for scanned PDFs/images; no accuracy fixture. Sources: omnifact:omnifact:uploads. - spreadsheets — Are Excel tables read with structure intact? [partial]: Spreadsheet inputs can be processed with executed Python and native XLSX formulas; structure/merged cells/formula preservation not tested. Sources: omnifact:omnifact:documents. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Space documents are extracted/chunked/embedded and relevant sections retrieved with progress/citation displays. Exact direct-attachment full-text thresholds were not established. Sources: omnifact:omnifact:uploads, omnifact:omnifact:retrieval. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:files, omnifact:omnifact:uploads, omnifact:omnifact:documents, omnifact:omnifact:retrieval ### KNOW-02: Knowledge bases and shared collections Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Cloud pools persist across chats and attach to assistants; Outpost is a separate local index. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - persistent_collections — Can users keep document collections across chats? [supported]: Persistent cloud data sources index SharePoint/OneDrive, Drive, Confluence, S3, WebDAV and web content. Sources: meingpt:meingpt:pools. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Admins share data sources with teams; workspace admins have broad visibility. Sources: meingpt:meingpt:pools. - size_limits — What are the collection limits? [supported]: Standard cloud raw-data budget is 300 GB across the workspace; indexing new content stops when full. Sources: meingpt:meingpt:pools. - assistant_binding — Can collections be bound to an assistant? [supported]: Pools bind to assistants or can be selected in a chat; projects themselves cannot bind pools. Sources: meingpt:meingpt:assistants, meingpt:meingpt:projects. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:assistants, meingpt:meingpt:projects #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist and share uploaded/connected knowledge. The applicable Pro page quota remains unknown; Enterprise advertises unlimited pages. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro up to50users and Enterprise Spaces; actual Pro page quota unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro page quota is excluded from verified limits until the applicable offer is identified. Connected-source and manual-upload accounting are separate. - persistent_collections — Can users keep document collections across chats? [supported]: Uploaded Files and connected folders persist in a Space for multiple conversations; message attachments remain specific to their conversation. Sources: omnifact:omnifact:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Organization users/groups including Everyone; Admin/Editor manage, Member queries. Groups receive view-only membership; edit grants are individual. Sources: omnifact:omnifact:share. - size_limits — What are the collection limits? [partial]: Enterprise pricing advertises unlimited knowledge pages. Actual Pro page quota is unknown because pricing says25000 while Billing says5000; neither is asserted as an independently applicable limit. The Connected Sources documentation says synced files currently do not count against the manual-upload page quota. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync. - assistant_binding — Can collections be bound to an assistant? [supported]: Space agent uses its own instructions and isolated Uploaded Files/Connected Sources knowledge. Sources: omnifact:omnifact:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:sync ### KNOW-03: Enterprise connectors Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02). #### meinGPT Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Cloud document sync and live first-party MCP integrations cover different system/action scopes. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint, OneDrive Business and personal OneDrive document access/sync. No verified native Outlook/Teams connector in current catalogue. Sources: omnifact:omnifact:integrations. - google_workspace — Which Google sources are connected? [supported]: Drive document sync plus MCP Drive, Docs, Sheets, Slides, Gmail, Calendar, Chat tools. Sources: omnifact:omnifact:integrations. - atlassian — Confluence and Jira? [supported]: Atlassian official MCP for Jira/Confluence search and updates. Sources: omnifact:omnifact:directory. - other_systems — Which other business systems? [partial]: Slack, Zoom, Notion, Hub Spot, Zendesk, Box, Egnyte, Asana, Click Up, Linear, Airtable, Canva, Miro, Lucid, Stripe, Pay Pal, Git Hub/Git Lab, Sentry, PostHog, Supabase, Neon, Webflow, Todoist; official XWiki importer is separate unsupported CLI. Sources: omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Custom MCP can expose internal systems but cloud deployment blocks private IP/loopback/subnets by default. XWiki REST importer runs where customer executes it; native file-share/database network support is not established. Sources: omnifact:omnifact:mcp-rev2, omnifact:omnifact:xwiki-sync-rev2. - connector_provider — Who builds and maintains each connector? [partial]: Catalogue MCP servers are supplied by listed software vendors; Omnifact manages installation/governance. Document connectors and XWiki tool are Omnifact; support scope varies. Sources: omnifact:omnifact:directory, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:integrations, omnifact:omnifact:directory, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:mcp-rev2 ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Live OAuth preserves source access; indexed permissions require a separate, default-off setting. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - source_permissions_respected: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. - Unverified revocation_delay, sensitivity_labels: No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. - source_permissions_respected — Are source permissions enforced per user? [partial]: Live M365 tools use each user account. Cloud SharePoint/Drive pools enforce imported source permissions only when request-enabled and switched on; other source types do not inherit them. No two-user test was run. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Live tools execute under user OAuth. Indexed SharePoint/Drive permissions are mirrored and fail closed when stale; source-permission mode is off by default. Sources: meingpt:meingpt:pool-controls. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins select imported sources/folders and control team sharing. Sources: meingpt:meingpt:pools. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No restricted-document/revocation fixture or Purview-label check was run; revocation timing and sensitivity-label behavior remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:m365, meingpt:meingpt:pool-controls, meingpt:meingpt:pools #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal OAuth tools honor source-account rights; synced content is scoped to Space membership, without a verified per-user ACL mirror. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - source_permissions_respected: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. - enforcement_point: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. - revocation_delay: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. - admin_scope_controls: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. - Unverified sensitivity_labels: No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. - source_permissions_respected — Are source permissions enforced per user? [partial]: OAuth MCP executes only within each user account rights. Space indexed knowledge is available under shared Space membership; per-recipient source ACL enforcement was not established. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [partial]: Live OAuth uses source account access. Space retrieval is indexed and checks Space membership; this is not documented as a source-ACL recheck on every query. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync. - revocation_delay — How quickly does a removed permission take effect? [partial]: Removing Space/group membership immediately revokes those grants; source document/ACL revocation timing beyond deletion sync was not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:groups. - admin_scope_controls — Can admins exclude sites, folders or labels? [partial]: Space admins select connected folders; organization enables/removes connectors and tools. No sensitivity-label classifier was established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? Unknown. No cross-group source-ACL/revocation fixture or Microsoft Purview sensitivity-label implementation was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:mcp, omnifact:omnifact:retrieval, omnifact:omnifact:sync, omnifact:omnifact:share, omnifact:omnifact:groups, omnifact:omnifact:integrations ### KNOW-05: Freshness and sync model Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Live connectors query the source; cloud pools copy an index to Germany. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Unverified deletion_propagation: No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified. - live_or_indexed — Is content searched live or copied into an index? [supported]: Native connectors fetch live; cloud data pools index imported documents. Sources: meingpt:meingpt:pools. - sync_interval — How often does an index refresh? [supported]: Cloud import runs every 15 minutes. Sources: meingpt:meingpt:pools. - deletion_propagation — How quickly does a deleted document disappear? [unknown]: How quickly does a deleted document disappear? Unknown. No edit/delete fixture was run and an end-to-end deletion-propagation bound was not verified. - index_location — Where is indexed content stored? [supported]: Cloud pools run at Hetzner in Germany; local Outpost pools stay in the customer network. Sources: meingpt:meingpt:pools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Connected documents are indexed on a five-minute cycle; live MCP queries remain separate. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise cloud document connectors; separately run API-enabled XWiki importer documented at pinned revision; add_ons=Customer-run XWiki sync tool; API access and source credentials required; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - XWiki behavior is documented in a pinned README, with no support/guarantee. It was not implementation-inspected or executed in this pass. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connected Sources index selected cloud files; MCP tools query source systems live. XWiki CLI uploads converted Markdown on customer-run sync. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2. - sync_interval — How often does an index refresh? [supported]: Connected Sources checks every five minutes; initial indexing may take minutes. XWiki tool is one-shot and requires external cron/systemd/Kubernetes scheduling. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - deletion_propagation — How quickly does a deleted document disappear? [supported]: Cloud deletions removed on next five-minute cycle; disconnect permanently removes that source index from Space. XWiki importer tracks deleted/excluded pages on next run. Sources: omnifact:omnifact:sync, omnifact:omnifact:xwiki-sync-rev2. - index_location — Where is indexed content stored? [partial]: DPA maps prefilter files/indexing to Azure Saa S Germany/Frankfurt storage; model embeddings/summaries have provider-dependent paths not fully mapped. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:dpa-rev2 ### KNOW-06: Grounding and retrieval quality Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Source display is documented; grounding quality remains untested. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - no_answer_behaviour: The guide says source search reports no matching result; actual refusals were not tested. - Unverified citation_accuracy, cross_language, observed_accuracy: The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. - citations — Are answers linked to specific sources? [supported]: Cloud source answers always display sources and this cannot be disabled. Sources: meingpt:meingpt:pool-controls. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: The guide says source search reports no matching result; actual refusals were not tested. Sources: meingpt:meingpt:pools. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. The shared multilingual corpus and question set were not run, so link correctness, cross-language retrieval and accuracy counts are unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pool-controls, meingpt:meingpt:pools #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Passage citations and controllable strict grounding are documented; retrieval quality remains unmeasured. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - no_answer_behaviour: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. - Unverified citation_accuracy, cross_language, observed_accuracy: No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - citations — Are answers linked to specific sources? [supported]: Source references identify uploaded document or cloud filename/provider and direct original link; progress shows retrieved document count. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. - no_answer_behaviour — Does it say when the corpus has no answer? [partial]: Space instructions can require answers only from uploaded documents and explicit missing-information statements; default guaranteed abstention is not established. Sources: omnifact:omnifact:retrieval. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No DE/FR/EN corpus fixture, citation entailment, cross-language retrieval measurement or observed score was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:retrieval, omnifact:omnifact:sync ### KNOW-07: Memory and personal context Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal instructions and user-specific assistant memory are documented. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - user_memory_controls: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. - custom_instructions — Can users set persistent instructions? [supported]: Preferences store a persistent system instruction applied with workspace and assistant context. Sources: meingpt:meingpt:preferences. - cross_chat_memory — Does the product remember facts across chats? [supported]: Enabled assistants share a personal user memory store across chats, not a team store. Sources: meingpt:meingpt:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users view and delete one/all memories; direct editing is unavailable in settings, but an assistant can update entries. Sources: meingpt:meingpt:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Admins can disable or remove Memory from the permitted tools. Sources: meingpt:meingpt:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences, meingpt:meingpt:memory #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent personal instructions exist; automatic cross-chat memory was not established. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_memory_controls: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. - Unverified cross_chat_memory, admin_memory_controls: No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - custom_instructions — Can users set persistent instructions? [supported]: Personalization stores role/context and response tone/style/format and sends them in every conversation. These fields bypass the Privacy Filter. Sources: omnifact:omnifact:account. - cross_chat_memory — Does the product remember facts across chats? [unknown]: Does the product remember facts across chats? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users edit/remove their supplied personalization fields. This is not documentation of viewing/deleting automatically learned memories. Sources: omnifact:omnifact:account. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? Unknown. No automatic fact-memory feature or administrator memory-disable setting was established in account, Space and release documentation. Conversation history is not itself cross-chat memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Assistants combine model, instructions, tools and knowledge, with governed creation and sharing. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: The editor supports instructions, model, files, pools, connectors and built-in tools. Sources: meingpt:meingpt:assistants. - creator_permissions — Can admins limit who creates them? [supported]: Request-enabled permissions restrict assistant creation/sharing/publication by team or person; admins are exempt. Sources: meingpt:meingpt:permissions. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Team and direct-person assistant sharing are documented; workspace-wide publication is admin-only by default. Sources: meingpt:meingpt:permissions, meingpt:meingpt:roles. - catalogue — Is there an internal assistant directory? [supported]: The navigation lists personal assistants and shared resources. Sources: meingpt:meingpt:assistants. - prompt_library — Are shared prompt templates available? [supported]: Prompt folders can be personal, workspace or department scoped. Sources: meingpt:meingpt:prompts. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:permissions, meingpt:meingpt:roles, meingpt:meingpt:prompts #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space agents combine custom instructions, knowledge and shared access with starter prompts. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - creator_permissions: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. - prompt_library: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Members create Spaces, become Space Admin and set instructions/examples/knowledge. Workspace-level tool availability is governed separately. Sources: omnifact:omnifact:create, omnifact:omnifact:users. - creator_permissions — Can admins limit who creates them? [partial]: Member role includes Space creation; group permissions control file/code/features. An explicit deny-Space-creation privilege was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:groups. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Users or organization groups including Everyone; group membership grants Member only. Sources: omnifact:omnifact:share. - catalogue — Is there an internal assistant directory? [supported]: All/Favorite Spaces directory shows accessible agents with pin/favorite navigation. Sources: omnifact:omnifact:spaces. - prompt_library — Are shared prompt templates available? [partial]: Space Starters/template previews and example prompts provide shared starting points; a separate centrally managed standalone prompt-library product was not established. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:create, omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:spaces, omnifact:omnifact:changes ### AGT-02: Tools, actions and MCP Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary. #### meinGPT Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Remote MCP has explicit tool policies, personal OAuth and teamwide static-credential access. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed remote MCP; workspace-admin setup and chosen tool policy required; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Configured policies are documented; initial-discovery defaults remain unknown. Static credentials are shared teamwide as documented and do not provide personal source authorization. - Experimental code/output entitlement is unknown; generic Enterprise early-access wording does not identify an eligible Execute code tier. - builtin_tools — Which tools are built in? [partial]: Web search/browse, Space retrieval, image tools and curated MCP business actions are documented for the scoped workspace. Eligibility for the separate Experimental Execute code and its Python/Office outputs is unknown because the documentation does not map it to Pro or Enterprise. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:groups-rev2. - custom_actions — Can admins add API actions? [partial]: Admins add custom remote MCP URL and discovered tools. Arbitrary non-MCP REST wrappers require an external server. Sources: omnifact:omnifact:mcp-rev2. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Remote HTTP MCP supports OAuth, APIkey, Bearer, customheader ornone. Destination validation blocks private/subnet/metadata endpoints by default. Sources: omnifact:omnifact:mcp-rev2. - tool_auth — Do tools act as the user or as a shared account? [partial]: OAuth requires personal sign-in; static APIkey/Bearer/header/none is central and immediately available teamwide, with no current per-user/group permission for those types. Sources: omnifact:omnifact:mcp-rev2. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins explicitly configure each tool as Always, Approval or Disable. Approval displays the exact request payload with Allow/Deny; later refresh adds new tools disabled. Initial-discovery default is unknown because setup and security sections disagree, so no safe or permissive initial default is asserted. Sources: omnifact:omnifact:mcp-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:retrieval, omnifact:omnifact:images, omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:mcp-rev2, omnifact:omnifact:groups-rev2 ### AGT-03: Web search and deep research Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Linkup powers cited web search and Deep Research; admins can restrict app access. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. - web_search — Is web search available? [supported]: Search can be switched on in chat, is always on in MeinGPT Web and runs in the Recherche app. Sources: meingpt:meingpt:web. - admin_toggle — Can admins disable it per organisation or group? [supported]: Request-enabled per-team/person app controls include Web search. Sources: meingpt:meingpt:permissions. - search_provider — Which search provider handles queries, and where? [supported]: Linkup processes search; the register lists Azure France. Prompt terms can enter generated search queries. Sources: meingpt:meingpt:web, meingpt:meingpt:subprocessors. - deep_research — Is multi-step research with a report available? [supported]: The research app has a user-controlled multi-step Deep Research mode. Sources: meingpt:meingpt:web. - web_citations — Are web sources cited? [supported]: Results include source previews and page references. Sources: meingpt:meingpt:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:web, meingpt:meingpt:permissions, meingpt:meingpt:subprocessors #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web research is cited and group-controlled; Brave handles public search. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - search_provider: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. - deep_research: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. - web_search — Is web search available? [supported]: Automatically triggered when needed or explicitly requested; URL reader caps2MB and excludes login/paywall/captcha pages. Sources: omnifact:omnifact:web. - admin_toggle — Can admins disable it per organisation or group? [supported]: Groups grant web search/browsing additively; remove grant from Everyone/allgroups to disable for targeted users. Sources: omnifact:omnifact:groups. - search_provider — Which search provider handles queries, and where? [partial]: DPA names Brave Software US as web-search processor; exact request-processing datacentre is not specified. Masked-sensitive queries are blocked before search. Sources: omnifact:omnifact:dpa, omnifact:omnifact:web. - deep_research — Is multi-step research with a report available? [partial]: Agents can perform multi-step browsing/research; no separately bounded Deep Research report product or benchmark was established. Sources: omnifact:omnifact:changes, omnifact:omnifact:web. - web_citations — Are web sources cited? [supported]: Numbered citations and original source links accompany search/browse results. Sources: omnifact:omnifact:web. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa, omnifact:omnifact:changes ### AGT-04: Workflows and automation Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: supported Multi-step workflows are documented; scheduled/event automations are request-enabled beta. Availability: beta Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Workflow editor is documented separately from request-enabled beta scheduled tasks; beta is not universal plan availability. - workflow_builder — Is there a workflow or chain builder? [supported]: A project editor chains prompts with variables and per-step models, or Buddy drafts the workflow. Sources: meingpt:meingpt:workflows. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Support enables beta tasks with daily, weekly, monthly or selected calendar schedules. Sources: meingpt:meingpt:scheduled. - event_triggers — Can external events start a workflow? [supported]: Beta tasks accept tokenized webhooks and task-specific email addresses. Sources: meingpt:meingpt:scheduled. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Members can build with natural-language Buddy help or manual steps, subject to admin rights. Sources: meingpt:meingpt:workflows. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:workflows, meingpt:meingpt:scheduled #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial External n8n nodes support automation; a native scheduled workflow builder is not established. Availability: generally-available Delivery: official-integration Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Published Spaces/Documents API when enabled; AI Gateway nodes require Enterprise; external n8n runs separately; add_ons=External n8n community-node installation; customer-run scheduler/XWiki importer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - These integrations are pinned README documentation, not executed or source-inspected implementation. A native Omnifact workflow builder/scheduler is not established. - workflow_builder — Is there a workflow or chain builder? [partial]: Vendor-owned repository publishes n8n community nodes for Gateway completions/model list, Published Space chat and document CRUD. The visual builder is external n8n, not an established native Omnifact builder. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: XWiki importer explicitly uses external cron/systemd/Kubernetes Cron Job. Native scheduled prompts/agents were not established. Sources: omnifact:omnifact:xwiki-sync-rev2. - event_triggers — Can external events start a workflow? [unknown]: Can external events start a workflow? Unknown. Native schedule/webhook/event-trigger support was not established from docs, index, changelog and automation integrations. - builder_audience — Is building aimed at business users, IT or developers? [partial]: n8n community-node/API integrations and CLI sync target technical integrators; Space instructions target business users. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:create. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:n8n-nodes-omnifact-rev2, omnifact:omnifact:xwiki-sync-rev2, omnifact:omnifact:create ### AGT-05: Agentic task execution Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Assistants can execute successive tool calls, show progress and stop; per-action confirmation is absent. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - side_effect_confirmation: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Assistant tools run multiple sequential steps within a response and stop at a bounded tool-call budget. Sources: meingpt:meingpt:assistants. - visible_steps — Are steps and tool calls shown? [supported]: Tool/reasoning steps and progress are shown in chat. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat. - side_effect_confirmation — Must the user confirm actions with side effects? [unsupported]: No built-in method-specific permission popup exists at runtime; admin-approved write/dangerous methods can run without an additional dialog. Sources: meingpt:meingpt:tools. - stop_control — Can the user stop a running task? [supported]: The input button changes to Abbrechen and stops response generation while preserving text. Sources: meingpt:meingpt:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:assistants, meingpt:meingpt:chat, meingpt:meingpt:tools #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agentic chat plans tools and streams progress with configurable approvals and Stop. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - visible_steps: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. - side_effect_confirmation: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. - stop_control: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: August release rebuilt chat around multi-step agents with automatic tool selection; API optionally enables agentic workflow. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat. - visible_steps — Are steps and tool calls shown? [partial]: Tool/search/retrieval progress and expandable reasoning show activity; exact full execution trace was not independently inspected. Sources: omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Curated actions wait for confirmation by default; admins choose Always/Approval/Disable. It is not unconditional confirmation for every write under all configurations. Sources: omnifact:omnifact:directory, omnifact:omnifact:mcp. - stop_control — Can the user stop a running task? [partial]: Send becomes Stop while response generates; clicking halts generation. Cancellation of already committed external side effects is not established. Sources: omnifact:omnifact:stop. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:changes, omnifact:omnifact:api-chat, omnifact:omnifact:select, omnifact:omnifact:retrieval, omnifact:omnifact:web, omnifact:omnifact:directory, omnifact:omnifact:mcp, omnifact:omnifact:stop ### AGT-06: Programmable access Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise-enabled APIs cover chat, assistants and workflows with model and budget enforcement. Availability: generally-available Delivery: native Scope: surfaces=meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Enterprise API, explicitly enabled; no public add-on price; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - api_governance: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. - Unverified knowledge_api, mcp_server: A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. - chat_api — Is there an API for chat and assistants? [supported]: Bearer-key chat completions, assistants, workflow runs, embeddings and transcription are documented; personal keys require Enterprise enablement. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook. - knowledge_api — Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Model permission failures return 403; API has a separate personal budget and shared token-rate ceilings; compliance-content logging coverage was not fully established. Sources: meingpt:meingpt:api, meingpt:meingpt:config, meingpt:meingpt:audit. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. A knowledge-ingestion API and product MCP-server endpoint were not established in the API guide. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:api, meingpt:meingpt:outlook, meingpt:meingpt:config, meingpt:meingpt:audit #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces/document API and Enterprise Gateway use organization keys with different filtering/credit behavior. Availability: generally-available Delivery: native Scope: surfaces=Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro published Spaces advertised but support enablement needed; Gateway Enterprise opt-in; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - chat_api: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. - knowledge_api: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. - api_governance: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. - Unverified mcp_server: No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. - chat_api — Is there an API for chat and assistants? [partial]: Published Spaces chat JSON/SSE with source/agentic headers; Enterprise Gateway OpenAI-compatible completions. Gateway V1 explicitly lacks tool calls and structured outputs. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway. - knowledge_api — Can documents be loaded through an API? [partial]: Document upload, list, inspect, rename/delete with Space scope and async ingestion; no agent-configuration CRUD endpoint established. Sources: omnifact:omnifact:api-docs. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Org-level revocable key, enabled-modelcontrols and shared credit budget apply. Gateway hard-stops on exhaustion; Published Space API disables Privacy Filter. Fine-grained API-key scopes/end-user identities/audit parity were not established. Sources: omnifact:omnifact:developer, omnifact:omnifact:gateway, omnifact:omnifact:published, omnifact:omnifact:model-settings. - mcp_server — Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? Unknown. No first-party Omnifact MCP server exposing platform agents was established; inbound MCP client integrations are distinct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-chat, omnifact:omnifact:gateway, omnifact:omnifact:api-docs, omnifact:omnifact:developer, omnifact:omnifact:published, omnifact:omnifact:model-settings ## Daily work ### WORK-01: Clients and access points Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform is browser-based; Outlook has a separate centrally deployed add-in. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace, meinGPT Outlook add-in, meinGPT Enterprise API; version=Public documentation checked 2026-10-21; plan=Business/Enterprise web workspace; Outlook add-in requires Enterprise API enablement and personal API key; add_ons=Enterprise API enabled for Outlook add-in; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - managed_deployment: The Outlook add-in can be assigned to users or groups in Microsoft 365 integrated apps; general desktop/mobile MDM configuration was not found. - Unverified desktop_apps, mobile_apps, browser_extension, client_feature_gaps: No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - web — Is a full web client available? [supported]: The terms define a browser-accessible workspace. Sources: meingpt:meingpt:terms. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. - managed_deployment — Can IT deploy and configure clients through MDM? [partial]: The Enterprise API-enabled Outlook add-in can be assigned to users/groups through Microsoft365 integrated apps. It supports Outlook web, Windows classic/new and Mac; each user needs a personal meinGPT API key. General desktop/mobile MDM configuration was not established. Sources: meingpt:meingpt:outlook. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. No first-party native Windows/macOS/iOS/Android workspace client or browser-extension support matrix was located in the user guide, client setup or official site search; mobile parity was not tested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:outlook #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Browser and mobile web access are advertised; native and managed clients remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - mobile_apps: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. - client_feature_gaps: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. - Unverified desktop_apps, browser_extension, managed_deployment: No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - web — Is a full web client available? [supported]: Full Saa S browser client provides chat and Spaces. Sources: omnifact:omnifact:home. - desktop_apps — Windows and macOS apps? [unknown]: Windows and mac OS apps? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - mobile_apps — iOS and Android apps with SSO? [partial]: Pricing lists Mobile Web App and model picker adapts to small screens; no native i OS/Android app with SSO was established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:select. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. No verified Windows/mac OS native app, browser extension/sidebar or MDM client rollout guide was found. Vendor internal MDM in DPA is not customer client deployment. - client_feature_gaps — Which features are missing on mobile? [partial]: Mobile effort picker is inline rather than flyout; broader mobile feature parity is not specified. Sources: omnifact:omnifact:select. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing, omnifact:omnifact:select ### WORK-02: Office suite and Teams integration Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A documented Outlook add-in operates in the received-message view and needs Enterprise API access. Availability: generally-available Delivery: native Scope: surfaces=meinGPT Outlook add-in; version=Public documentation checked 2026-10-21; plan=Enterprise API enabled workspace; add_ons=Enterprise API; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - licence_prerequisites: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. - Unverified word_excel_powerpoint, teams, google_workspace_apps: Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - outlook — Does it work inside Outlook? [supported]: Outlook Web, Windows classic/new and Mac support summarizing the selected received email and drafting replies; compose view is excluded. Sources: meingpt:meingpt:outlook. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Unknown. Word/Excel/PowerPoint/Teams or Google-editor in-app extensions were not established; connectors that read their content are recorded in KNOW-03. - licence_prerequisites — Which licences or consents are needed? [partial]: Personal meinGPT API key and Enterprise API enablement are required; tenant admins can centrally deploy the add-in. A separate Microsoft licence price is not stated. Sources: meingpt:meingpt:outlook. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:outlook #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Office files and live Google connectors exist; embedded office/Teams apps are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - word_excel_powerpoint: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. - google_workspace_apps: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. - licence_prerequisites: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. - Unverified outlook, teams: No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [partial]: Generates DOCX/XLSX/PPTX and modifies uploaded files, but this does not establish in-Word/Excel/Power Point add-ins. Sources: omnifact:omnifact:documents. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - teams — Is there a Teams app or bot? [unknown]: Is there a Teams app or bot? Unknown. No current native Outlook add-in or Teams chat app/bot was established in documentation/catalogue. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [partial]: Google Docs/Sheets/Slides/Gmail/Calendar/Chat MCP actions run from Omnifact after personal OAuth; embedded add-ons were not established. Sources: omnifact:omnifact:integrations. - licence_prerequisites — Which licences or consents are needed? [partial]: Microsoft document access may require tenantwide admin consent; all OAuth integrations need individual authorized source accounts and third-party entitlements. Exact office-suite licence matrix not established. Sources: omnifact:omnifact:sync, omnifact:omnifact:integrations. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:documents, omnifact:omnifact:integrations, omnifact:omnifact:sync ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dedicated text/document translation uses EU Google/DeepL routes and managed glossaries. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - document_translation: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. - writing_tools: Quick Actions rewrite answers, including more formal and improve options. - Unverified formality_and_variants: Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated. - document_translation — Can whole documents be translated with formatting kept? [partial]: DeepL document translation preserves layout for DOC/DOCX, PPT/PPTX, XLS/XLSX, PDF, HTML, TXT, SRT and XLIFF. Layout quality was not fixture-tested. Sources: meingpt:meingpt:translation. - translation_engine — Which engine translates? [supported]: Default Google Cloud Translate for text and DeepL for documents; own DeepL key switches both to DeepL. Sources: meingpt:meingpt:translation. - glossaries — Are company glossaries supported? [supported]: Workspace admins create per-language-pair glossaries and import CSV; exact word forms must match. Sources: meingpt:meingpt:translation. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Unknown. Formality settings within the translator and guaranteed de-CH spelling were not established; no DE-to-FR/IT contract fixture was translated. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Quick Actions rewrite answers, including more formal and improve options. Sources: meingpt:meingpt:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:translation, meingpt:meingpt:chat #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Persistent style instructions support writing; specialized document translation is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - formality_and_variants: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. - writing_tools: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. - Unverified document_translation, translation_engine, glossaries: Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - translation_engine — Which engine translates? [unknown]: Which engine translates? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Unknown. Formatting-preserving full-document translation, named engine and company glossary were not established in docs, model catalogue or integrations. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Personal response instructions can request formal/casual tone and style. Specific de-CH controls or terminology enforcement were not documented. Sources: omnifact:omnifact:account. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat supports drafting and rewriting via instructions and document generation; a dedicated proofreading/translation toolbar was not established. Sources: omnifact:omnifact:account, omnifact:omnifact:documents. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account, omnifact:omnifact:documents ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Twelve named image variants include reference editing with administrator model controls. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - image_editing: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. - usage_terms: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. - image_generation — Can users generate images, with which models? [supported]: FLUX.2 Klein/Pro/Flex/Max, FLUX 1.1 Pro, FLUX.1 Kontext Max; GPT Image 1/Mini/1.5/2; Gemini 2.5 Flash Image and 3 Pro Image. Sources: meingpt:meingpt:images. - image_editing — Can users edit uploaded images? [partial]: Reference image generation supports model-dependent uploads; app lacks post-generation crop/color editing. Sources: meingpt:meingpt:images. - admin_control — Can admins restrict image generation? [supported]: Admins enable models and default; request-enabled permissions can restrict Image app use by teams or persons. Sources: meingpt:meingpt:image-admin, meingpt:meingpt:permissions. - usage_terms — What usage rights apply to output? [partial]: Terms warn third-party output may carry rights; no blanket unrestricted-use warranty is made. C2PA metadata labels generated output. Sources: meingpt:meingpt:terms, meingpt:meingpt:images. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:images, meingpt:meingpt:image-admin, meingpt:meingpt:permissions, meingpt:meingpt:terms #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image generation and edits use configured OpenAI/Google models under group permission. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - image_generation: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. - admin_control: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. - Unverified usage_terms: Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. - image_generation — Can users generate images, with which models? [partial]: Model Settings lists GPTImage2/1.5/1/1Mini, Nano Banana/Pro/2; September notes add GPTImage2.5Flare/Sunburst and October Nano Banana2.1 direct Google. EU generation remains Nano Banana2 because2.1 is not on Google Cloud EU. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes. - image_editing — Can users edit uploaded images? [supported]: Uploaded reference images can be transformed with text instructions; results appear in gallery and download. Sources: omnifact:omnifact:images. - admin_control — Can admins restrict image generation? [partial]: Generate Images is group-granted; model enablement/default is organization-wide. Image/audio contents bypass PII masking and retain route constraints. Sources: omnifact:omnifact:groups, omnifact:omnifact:model-settings, omnifact:omnifact:privacy. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? Unknown. Model-specific output licence/commercial rights were not established; general software rights do not define image-output ownership. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:model-settings, omnifact:omnifact:changes, omnifact:omnifact:images, omnifact:omnifact:groups, omnifact:omnifact:privacy ### WORK-05: Voice and meetings Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dictation and meeting transcription are documented; speech quality was not tested. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Unverified read_aloud, voice_conversation, swiss_german_speech: No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - dictation — Can users dictate prompts? [supported]: A microphone transcribes prompts into the input field. Sources: meingpt:meingpt:chat. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Audio/video/transcript uploads and meeting-bot notes are documented; storage Hetzner Germany, Gladia transcription France, Vertex EU summaries. Sources: meingpt:meingpt:meeting. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No first-party complete read-aloud/live-voice plan and language matrix or Swiss German recognition fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:meeting #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Experimental dictation/audio input exists; meeting bot/live voice coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dictation: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. - meeting_summaries: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. - Unverified read_aloud, voice_conversation, swiss_german_speech: No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - dictation — Can users dictate prompts? [partial]: Experimental Dictate Messages requires enabled Azure OpenAI; audio bypasses filtering and speech is converted to text. Sources: omnifact:omnifact:groups. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. - meeting_summaries — Are meetings transcribed and summarised? [partial]: Uploaded meeting transcripts can be summarized and Zoom integration searches/recaps recordings; no native automatic meeting-joining/transcription bot was established. Sources: omnifact:omnifact:directory, omnifact:omnifact:documents. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. No live voice conversation, read-aloud capability or Swiss German recognition/quality fixture was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:groups, omnifact:omnifact:directory, omnifact:omnifact:documents ### WORK-06: Data analysis and document output Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial An isolated EU sandbox executes analysis code and generates downloadable Office files. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - canvas_editing: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Python/JavaScript sandbox reads original spreadsheets with pandas/openpyxl and executes code. Sources: meingpt:meingpt:sandbox. - charts — Can it produce charts? [supported]: Executed matplotlib charts can be returned as PNG. Sources: meingpt:meingpt:sandbox. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Sandbox libraries support DOCX/XLSX/PPTX; workflows also generate Word/PDF/Excel/CSV/PowerPoint/JSON. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows. - canvas_editing — Is there a document or canvas editor for iterating on output? [partial]: Downloaded artifacts and an Excel editor exist; editor changes stay local until downloaded and the chat card keeps the original. Sources: meingpt:meingpt:sandbox. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sandbox, meingpt:meingpt:workflows #### Omnifact Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-07: Sharing and team spaces Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat links and shared projects exist; projects preserve private member chat histories. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - group_chat: Each project member has a separate private chat list; shared project chats are not a simultaneous group conversation. - Unverified share_permission_boundary: No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified. - Project chat privacy does not prove absence of every group-chat surface. - share_chats — Can chats be shared inside the organisation? [supported]: A share toggle creates a link displaying the shared conversation. Sources: meingpt:meingpt:chat. - team_spaces — Are shared projects or workspaces available? [supported]: Projects share instructions and workflows with Owner/Editor/Member roles. Sources: meingpt:meingpt:projects. - group_chat — Can several people chat together with the AI? [partial]: Within Projects,each member has a separate private chat list. Simultaneous multi-user group conversation elsewhere was not established. Sources: meingpt:meingpt:projects. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Does sharing respect the recipient's access to sources? Unknown. No cross-group chat-sharing test was run; recipient access to source attachments and restricted knowledge was not verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:chat, meingpt:meingpt:projects #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Spaces organize agents/knowledge; multi-user conversations and complete source-safe redistribution are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - share_permission_boundary: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. - Unverified share_chats, group_chat: Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_chats — Can chats be shared inside the organisation? [unknown]: Can chats be shared inside the organisation? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - team_spaces — Are shared projects or workspaces available? [supported]: Space instructions, knowledge and membership are shared with users/groups; conversations remain organized under the Space. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share. - group_chat — Can several people chat together with the AI? [unknown]: Can several people chat together with the AI? Unknown. Sharing individual chat links and simultaneous group conversation were not explicitly established; shared Space access alone is insufficient evidence. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: Space members can see referenced uploaded knowledge. Personal OAuth MCP follows each source account, but Space source-ACL rechecking and generated-answer resharing boundaries were not tested. Sources: omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:spaces, omnifact:omnifact:share, omnifact:omnifact:mcp, omnifact:omnifact:sync ### WORK-08: Interface languages and accessibility Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Platform-language choice exists, but the full UI and accessibility matrix remains unverified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - ui_languages: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. - Unverified dach_language_quality, accessibility_statement, admin_ui_languages: No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - ui_languages — Which UI languages are offered? [partial]: Preferences provide a platform-language selector distinct from response language; a complete named language list is not published on this page. Sources: meingpt:meingpt:preferences. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. No authenticated DE/FR/IT/EN UI inspection or WCAG conformance statement was located in the user guide or security pages; admin language completeness is untested. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:preferences #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial English and German UI are documented; language quality and accessibility are untested. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - admin_ui_languages: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. - Unverified dach_language_quality, accessibility_statement: No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - ui_languages — Which UI languages are offered? [supported]: Account language selector offers English/German, otherwise browser-language default. Sources: omnifact:omnifact:account. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. No DE/FR/IT UI-quality fixture or WCAG conformance statement was obtained. French/Italian UI is not in the documented EN/DE selector. - admin_ui_languages — Is the admin interface available in German? [partial]: A separate German admin documentation tree is published; this does not verify complete German in-app admin translation. Sources: omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:account ## Administration and governance ### ADM-01: Single sign-on and authentication Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Microsoft/Google login is included; custom OIDC is enabled on request and SAML is excluded. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - sso_plan: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Google and Microsoft sign-in plus custom OpenID Connect for Entra, Keycloak, Okta, PingFederate and Authentik. SAML is not supported. Sources: meingpt:meingpt:sso. - sso_plan — Which plan includes SSO? [partial]: Platform pricing includes Microsoft/Google/Magic Link; own OIDC needs workspace enablement, while Governance prices Entra group sync and provisioning. Exact custom-OIDC fee is not stated. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices. - mfa — Can MFA be enforced? [supported]: MFA is enforced at the customer IdP; disabling a user prevents new sign-ins but does not immediately invalidate an existing session. Sources: meingpt:meingpt:sso. - conditional_access — Do Entra conditional-access policies apply? [supported]: Customer IdP controls Conditional Access. Existing sessions expire normally unless separately removing the membership. Sources: meingpt:meingpt:sso. - domain_capture — Can the company claim its email domain? [supported]: DNS TXT verification enables domain auto-join and optional rejection of invitations into other workspaces; existing external memberships remain. Sources: meingpt:meingpt:sso. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:sso, meingpt:meingpt:prices #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SAML2.0 uses identity-provider MFA and conditional-access policies; nativeTOTP entitlement is outside this finding. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise SAML/SSO only; nativeTOTP entitlement excluded; add_ons=Enterprise SSO enablement; identity-provider MFA/conditional access; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The supported MFA path here is the Enterprise identity provider. Native password/TOTP accounts require separate plan verification. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML2.0 via SSO Ready; Entra ID, Okta, Keycloak and SAML-compatible Id Ps. OIDC was not established. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector. - sso_plan — Which plan includes SSO? [supported]: SSO/SCIM exclusive to Enterprise and support-enabled configuration. Sources: omnifact:omnifact:users. - mfa — Can MFA be enforced? [partial]: For Enterprise SAML/SSO users, authentication and MFA are controlled by the identity provider; Omnifact native2FA setup is hidden. No nativeTOTP entitlement for Pro or Enterprise is asserted. Sources: omnifact:omnifact:security-rev2, omnifact:omnifact:sso-blog. - conditional_access — Do Entra conditional-access policies apply? [partial]: SSO announcement says existing Id P conditional access/MFA/password rules apply; Entra device/location combinations were not tested. Sources: omnifact:omnifact:sso-blog. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. No verified company-domain capture/ownership process was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:sso-blog, omnifact:omnifact:public-sector, omnifact:omnifact:security-rev2, omnifact:omnifact:auth ### ADM-02: User provisioning and lifecycle Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Governance includes SCIM; user provisioning and login-time group sync have separate effects. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform plus Governance provisioning add-on; add_ons=Governance; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - group_sync: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. - deprovisioning: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. - scim — Is SCIM provisioning supported? [supported]: Entra SCIM v1 creates/updates/deactivates users, requires a verified domain and workspace enablement, and replaces manual invitations. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices. - group_sync — Are identity-provider groups synced? [partial]: Entra group-to-team synchronization is separate from user-only SCIM and adds memberships on login. It is not a general bidirectional SCIM-group sync. Sources: meingpt:meingpt:scim, meingpt:meingpt:sso. - jit_provisioning — Are users created at first login? [supported]: Custom OIDC can join a verified-domain workspace on first authenticated login; plain Microsoft sign-in alone does not grant workspace membership. Sources: meingpt:meingpt:sso, meingpt:meingpt:scim. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates membership, preserves data and releases the seat. Shared-asset transfer behavior was not trial-tested. Sources: meingpt:meingpt:scim. - seat_assignment — Can admins assign and reclaim seats? [supported]: New SCIM users start as unlicensed viewers unless automatic seat assignment is on; admins can assign seats. Sources: meingpt:meingpt:scim. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:scim, meingpt:meingpt:prices, meingpt:meingpt:sso #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM synchronizes users/groups; deactivation blocks login while detailed asset disposition remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - jit_provisioning: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. - deprovisioning: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. - seat_assignment: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. - scim — Is SCIM provisioning supported? [supported]: Dedicated sso-sync creates, updates anddeactivates users automatically; manual creation/profile/role/CSV changes are locked under SCIM. Sources: omnifact:omnifact:users. - group_sync — Are identity-provider groups synced? [supported]: Entra, Okta or Google Workspace groups mirror into immutable-membership Synced Groups with Omnifact-managed permissions. Sources: omnifact:omnifact:groups. - jit_provisioning — Are users created at first login? [partial]: Provisioned status includes SSO/SCIM-created accounts before first login; invitations are skipped for SSO. Exact just-in-time account trigger not specified. Sources: omnifact:omnifact:users. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: Deactivated users cannot log in; only unaccepted invitees can be permanently deleted from user list. Space removal keeps prior contributions; full leaver private data/agent ownership effects unspecified. Sources: omnifact:omnifact:users, omnifact:omnifact:share. - seat_assignment — Can admins assign and reclaim seats? [partial]: Active and invited users count as seats; adding prorates cost, removal credits next invoice. Deactivated-seat billing treatment not fully specified. Sources: omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:groups, omnifact:omnifact:share, omnifact:omnifact:billing ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Role and group controls include request-enabled app permissions and model restrictions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - multi_entity: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admin, Member and Viewer; unlimited workspace admins and separate team administrators are documented. Workspace admins consume a seat and bypass restrictions. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions. - groups — Can permissions be set per group? [supported]: Teams control shared resources and models; admins see all team-shared assets. Sources: meingpt:meingpt:roles, meingpt:meingpt:config. - feature_toggles — Which features can be switched on or off per group? [supported]: Request-enabled controls restrict image, meeting notes/bot, translation, web, Voice Agent, Buddy and automation use by teams or persons. Sources: meingpt:meingpt:permissions. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Multiple workspaces can represent separate companies, but each has separate credit and billing; a unified multi-entity contract was not established. Sources: meingpt:meingpt:sso. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:roles, meingpt:meingpt:permissions, meingpt:meingpt:config, meingpt:meingpt:sso #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Owner/Admin/Member and Space roles combine with additive groups. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - multi_entity: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Owner includes Admin/Member, Admin includes Member; Admin manages team users/settings except Owner. Space Admin/Editor is separate, with optional Knowledge Base Manager in DPA. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa. - groups — Can permissions be set per group? [supported]: Everyone, SCIM-synced andmanual groups; permissions union rather than deny. Sources: omnifact:omnifact:groups. - feature_toggles — Which features can be switched on or off per group? [supported]: Group grants file/image uploads, audio, web, imagegeneration, code, dictation, modeltiers, USmodels, filterexemption; organization models/features must also be enabled. Sources: omnifact:omnifact:groups. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Organization tenant separation and department Space/group boundaries are described; terms prohibit multiple accounts for one company and usage beyond own personnel without agreement. Multi-subsidiary contract rights were not established. Sources: omnifact:omnifact:dpa, omnifact:omnifact:terms, omnifact:omnifact:share. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:users, omnifact:omnifact:share, omnifact:omnifact:dpa, omnifact:omnifact:groups, omnifact:omnifact:terms ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Adoption metrics and cost CSVs have team and anonymization options. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - breakdowns: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. - adoption_dashboard — Is there an adoption dashboard? [supported]: Cockpit lists prompts, active users, daily prompts/workflow runs and popular workflows. Sources: meingpt:meingpt:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Usage-based plans report costs by user, team, model and platform/API; complete assistant/feature breakdown is not demonstrated. Sources: meingpt:meingpt:analytics. - export — Can usage data be exported? [supported]: User/team cost statistics export to CSV. Sources: meingpt:meingpt:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Metric anonymization replaces names with IDs; top-user metrics depend on that setting. Sources: meingpt:meingpt:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise adoption analytics show active users and message counts; deeper breakdown/export controls are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Enterprise Usage Analytics & Insights; Pro excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Dashboard scope is organization/day level; additional model/group/assistant breakdowns and export remain unverified. - adoption_dashboard — Is there an adoption dashboard? [supported]: Analytics provides date-range totals and daily active-user/message charts with interactive metric toggles; Enterprise-only in pricing. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Documented dashboard is organization/day level. Model, group, feature andassistant breakdown matrix was not established. Sources: omnifact:omnifact:analytics-rev2. - export — Can usage data be exported? [unknown]: Can usage data be exported? Unknown. No documented analytics export/API or configurable individual-reporting controls were established. Direct HTML retrieval returned403; public cached official page was retrieved through the web tool. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: DPA describes anonymized PostHog feature-use analytics without individual attribution; separate customer-visible reporting privacy toggles were not established. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:analytics-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2 ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Personal category budgets and pooled credit provide controls with documented exceptions. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - budget_enforcement: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. - chargeback: CSV cost exports exist by user/team; formal cost-centre coding is not established. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Usage-based plans show EUR costs per user/model and team, separately for platform and API. Sources: meingpt:meingpt:analytics. - budgets — Can budgets be set per user or group? [supported]: Six personal usage levels configure monthly budgets across five categories and are assigned singly or in bulk. Sources: meingpt:meingpt:limits. - budget_enforcement — Does reaching a budget alert, block or downgrade? [partial]: Zero blocks new category use and API exhaustion returns 403; running meeting bots can overshoot and automated runs are outside personal categories. Sources: meingpt:meingpt:limits, meingpt:meingpt:api. - chargeback — Can costs be exported per cost centre? [partial]: CSV cost exports exist by user/team; formal cost-centre coding is not established. Sources: meingpt:meingpt:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:analytics, meingpt:meingpt:limits, meingpt:meingpt:api #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared pooled credits and model permissions constrain spend; individual financial allocation is unspecified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - cost_visibility: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. - budgets: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. - Unverified chargeback: No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Billing shows pooled real-time consumption andforecast; Enterprise detailed real-time dashboard is described as forthcoming, while total used is available. Sources: omnifact:omnifact:billing. - budgets — Can budgets be set per user or group? [partial]: Organization pooled allowance and manual additional-credit recharge. Model-tier and USroute access can be group-controlled, but per-user/group monetary hard caps were not established. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Monthly budget: chat downgrades to enabled fallbacks; Gateway hard-blocks all calls on exhausted credits. Daily message quota disables send until reset. Sources: omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat. - chargeback — Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? Unknown. No cost-centre chargeback export or complete cost-per-user/group allocation interface was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:billing, omnifact:omnifact:groups, omnifact:omnifact:limits, omnifact:omnifact:gateway, omnifact:omnifact:chat ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Administrative change exports and a separate Outpost search log have distinct retention. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - admin_events: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. - content_logging: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. - siem_export: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. - Unverified ediscovery: No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established. - admin_events — Are admin and security events logged? [partial]: Administrative settings and SCIM changes are logged with actor and changes; a login/security-event coverage inventory and tamper-evidence model were not found. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [partial]: The settings-change log explicitly excludes conversation contents; a separate API-logging setting exists but prompt/response compliance-retention coverage is unclear. Sources: meingpt:meingpt:audit. - siem_export — Can logs stream to a SIEM or be exported? [partial]: CSV/JSON filtered audit export, 10000 entries/20 MiB/two minutes per export; SIEM streaming is not established. Sources: meingpt:meingpt:audit-export. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Unknown. No legal-hold or eDiscovery documentation was located; immutable audit storage and full content-logging configuration were not established. - log_retention — How long are logs kept? [supported]: Administrative settings changes are retained indefinitely; Governance Outpost query records are retained 90 days from enablement. Sources: meingpt:meingpt:audit. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:audit, meingpt:meingpt:scim, meingpt:meingpt:audit-export #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA documents append-only admin logs for at least 90 days; content compliance export is unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - log_retention: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. - Unverified content_logging, siem_export, ediscovery: No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - admin_events — Are admin and security events logged? [supported]: TOM2.5 records user-status changes/resource deletions with user attribution, UTC timestamps, encrypted transport/storage and append-only protection; event coverage can expand. Sources: omnifact:omnifact:dpa. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [unknown]: Can prompts and answers be retained for compliance, and is it configurable? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - siem_export — Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are e Discovery and legal hold supported? Unknown. No full prompts/answers archive configuration, SIEM streaming/export or e Discovery/legal hold interface was established. Id P authentication logs are distinct from platform audit exports. - log_retention — How long are logs kept? [partial]: Administrative logs retained at least 90 days; content retention is customer-configured but not a published compliance archive. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### ADM-07: Data loss prevention and personal data Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome. #### meinGPT Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Default Privacy Filter combines local NER/regex masking with several explicit bypass paths. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise, filter defaults enabled; user exemptions/advanced feature flags qualified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pii_detection: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. - pii_action: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. - custom_patterns: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. - filter_location: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. - Unverified dlp_integration: No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - pii_detection — Is personal data detected in prompts and files? [partial]: Names, addresses, email, phone, IPv4, US/German IDs/passports, tax/pensionnumbers, IBAN/BIC/card/routing/account numbers, companies anddocument filenames. Media bytes are not scanned; AHV recognition untested. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy. - pii_action — Is it redacted, masked, blocked or only warned? [partial]: Detected strings replaced with placeholders then restored in output; web queries containing masked values are blocked. Click-to-Reveal confirms sending individual terms; optional%%exemption defaults off andrequires Support. Group exemptions may disable filtering per agent/Space. Sources: omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:dpa. - custom_patterns — Can admins add custom patterns or terms? [partial]: Vendor detector uses custom-trained SLMNER andregex, but customer-defined pattern/dictionary UI/API was not established. Optional%%syntax bypasses rather than adds detection. Sources: omnifact:omnifact:dpa. - dlp_integration — Does it integrate with an existing DLP product? [unknown]: Does it integrate with an existing DLP product? Unknown. No existing third-party DLP/Purview integration or synthetic AHV/IBAN accuracy fixture was established. - filter_location — Where does filtering run? [partial]: DPA places filter within Azure Germany West Central, Frankfurt before external model. MCP arguments/results, code, sandbox, images/audio bytes, personalization and Published Space API bypass filtering by design. Sources: omnifact:omnifact:dpa, omnifact:omnifact:privacy, omnifact:omnifact:published, omnifact:omnifact:account. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:files, omnifact:omnifact:privacy, omnifact:omnifact:web, omnifact:omnifact:groups, omnifact:omnifact:published, omnifact:omnifact:account ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Workspace instructions and Governance acknowledgements are documented; policy enforcement breadth is limited. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - org_instructions: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. - content_filters: Provider content filtering can stop output; configurable organization-wide topic filters were not established. - Unverified violation_reporting: Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run. - org_instructions — Can admins set organisation-wide instructions? [partial]: Additional Chat Context is a workspace-wide system instruction, not a guaranteed enforcement layer. Sources: meingpt:meingpt:config. - usage_notice — Can users be required to accept a usage policy? [supported]: Governance includes multilingual acceptable-use policies for acknowledgement and mandatory courses that block other pages until complete. Sources: meingpt:meingpt:prices, meingpt:meingpt:audit. - content_filters — Are content filters configurable? [partial]: Provider content filtering can stop output; configurable organization-wide topic filters were not established. Sources: meingpt:meingpt:api. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Admin policy-violation reporting was not established in Compliance Controls; no guardrail fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:config, meingpt:meingpt:prices, meingpt:meingpt:audit, meingpt:meingpt:api #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Company/Space instructions and privacy/tool governance exist; mandatory policy workflows are unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - org_instructions: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. - content_filters: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. - Unverified usage_notice, violation_reporting: No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - org_instructions — Can admins set organisation-wide instructions? [partial]: Teamdescription supplies businesscontext; Spaceinstructions set response behavior and strict grounding. No guaranteed immutable organization safety instruction hierarchy was established. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. - content_filters — Are content filters configurable? [partial]: Organization PIImasking, group capabilities/modelroutes andper-tool approval/block settings are documented. General topic/abusefilter customization was not established. Sources: omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. No mandatory AI-use-policy acknowledgement, admin policy-hit dashboard or configurable general content-filter taxonomy was established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:company, omnifact:omnifact:create, omnifact:omnifact:retrieval, omnifact:omnifact:privacy, omnifact:omnifact:groups, omnifact:omnifact:mcp ## Data protection and sovereignty ### DATA-01: Hosting location and data residency Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Germany platform storage and model-specific EU/global routes must be scoped separately. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - inference_region: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. - backups_logs_region: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. - residency_plan: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. - Unverified support_access_region, swiss_hosting: No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - storage_region — Where are chats, files and indexes stored? [supported]: Hetzner Germany hosts chats, accounts, documents and cloud indexes; register identifies Nürnberg/Falkenstein. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors. - inference_region — Where do model calls run, per provider? [partial]: Azure Sweden/France, Vertex Frankfurt, Mistral France/Sweden, OpenAI EU endpoint, Nebius Finland, TensorX Ireland and other conditional routes. Some image variants remain Global; the accepted DPA governs authorized exceptions. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Scaleway France is conditional backup infrastructure; log/telemetry locations are not separately specified. Sources: meingpt:meingpt:subprocessors, meingpt:meingpt:dpa. - support_access_region — From where can vendor staff access data? [unknown]: From where can vendor staff access data? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No Swiss hosting entitlement or complete geographical support-access and log/telemetry matrix was found. - residency_plan — Which plan or option provides residency? [partial]: DPA 2.0.1 governs new acceptance since 24 September; existing customers retain agreed versions. EU inference depends on selected/approved routes; section 4(3) permits listed/instructed third-country transfers. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:pools, meingpt:meingpt:subprocessors, meingpt:meingpt:image-admin, meingpt:meingpt:dpa, meingpt:meingpt:dpa-page #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted primary workspace storage is in Azure EU. Germany-only processing and complete backup/log/support residency are not established; model and metadata routes differ. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted Azure platform storage; model and edge-metadata routes separately scoped; add_ons=Enterprise AI Gateway where named; provider/model route and eu/ prefix selected explicitly; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The storage finding covers primary workspace content, not every model/edge/support processing path. No Germany-only or whole-service EU-only guarantee is made. - storage_region — Where are chats, files and indexes stored? [partial]: Hosted raw chats/files/indexed workspace content uses Azure infrastructure in the EU. DPA identifies GermanyWestCentral/Frankfurt; the live infrastructure register also names NL/SE/IE. Only EU primary-platform storage is claimed here; a Germany-only deployment footprint is not established. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2. - inference_region — Where do model calls run, per provider? [supported]: EU routes include Azure OpenAI, Google Cloud EU for Gemini/Anthropic, and Mistral EU. Direct OpenAI/Anthropic US and Google API global routes also exist. Gateway needs eu/ prefix; unprefixed IDs never use EU backends. Sources: omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Unknown per-service backup/log geography for a particular contract. DPA Frankfurt/EU wording and the broader Azure DE/NL/SE/IE register do not map each backup stream. Cloudflare EU/US edge metadata/security logs are separate from platform document storage. - support_access_region — From where can vendor staff access data? [partial]: Pricing names German and US service teams; DPA permits justified, time-limited production access. Staff physical access locations by task are not specified. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:dpa-rev2. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Unknown. No full Swiss platform/backup/support hosting option was established. - residency_plan — Which plan or option provides residency? [partial]: Pro/Enterprise pricing offers EU cloud storage and EU model routes. This does not establish all-service EU residency. Enterprise Gateway requests require eu/ model IDs for EU backends; direct/global model routes and edge metadata have different geography. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:gateway, omnifact:omnifact:providers-rev2, omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:models, omnifact:omnifact:vertex, omnifact:omnifact:gateway, omnifact:omnifact:trust-rev2, omnifact:omnifact:pricing-rev2, omnifact:omnifact:groups-rev2, omnifact:omnifact:providers-rev2 ### DATA-02: Deployment options Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial SaaS is offered; terms permit individually agreed on-premise use, while Outpost is a connector. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace, meinGPT Outpost local connector; version=Public documentation checked 2026-10-21; plan=Public SaaS; on-premise only if specifically contracted; add_ons=none stated; deployment_mode=not specified; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - on_premise: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. - mode_feature_gaps: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. - Unverified dedicated_instance, customer_cloud, air_gapped: Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - multi_tenant_saas — Is a shared SaaS offered? [supported]: The public web workspace and shared organization API limits establish the managed SaaS offer. Sources: meingpt:meingpt:terms, meingpt:meingpt:api. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - customer_cloud — Can it run in the customer's own cloud account, from what size? [unknown]: Can it run in the customer's own cloud account, from what size? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Terms section 1a permits the whole software in customer data centres when agreed in the licence contract. The linked on-premise-requirements URL redirects to the generic security page; minimum seats and setup/operator terms are not public. Sources: meingpt:meingpt:terms. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Dedicated-instance, customer-cloud and air-gapped entitlements, operators, minimum seats and prices were not established. Outpost is a local connector, not evidence for those modes. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: The code sandbox remains in Frankfurt cloud even for on-premise customers; there is no complete mode parity list. Sources: meingpt:meingpt:sandbox. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:api, meingpt:meingpt:sandbox #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Saa S, customer-cloud and on-premise are offered without published private-deployment minimums. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Enterprise customer-cloud/on-premise; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise Saa S; Enterprise quoted private deployment; add_ons=Deployment/infrastructure/operator costs quoted; deployment_mode=not specified; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dedicated_instance: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. - customer_cloud: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. - on_premise: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. - Unverified air_gapped, mode_feature_gaps: Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Cloud Saa S uses logical organization/client separation. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Managed, own-cloud and on-premise are advertised; a distinct dedicated Saa S specification and seat threshold were not established. Sources: omnifact:omnifact:home. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Own/private cloud is available on request; minimum seats/spend, operating roles and supported infrastructure are not public. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Enterprise on-premise option includes municipal datacenters; numeric minimum and architecture requirements are unpublished. Sources: omnifact:omnifact:pricing, omnifact:omnifact:public-sector. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. - mode_feature_gaps — Which features are missing outside SaaS? [unknown]: Which features are missing outside Saa S? Unknown. Air-gapped operation and per-mode feature/egress parity were not established; a general self-hosting article is not a deployment specification. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:dpa, omnifact:omnifact:home, omnifact:omnifact:public-sector, omnifact:omnifact:pricing ### DATA-03: Training use and provider retention Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA 2.0.1 prohibits training and marks conditional AI services for no permanent provider content copy. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - provider_retention: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. - zero_retention: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. - Unverified human_review: Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide. - vendor_training — Does the vendor train on customer content? [supported]: Section 5(5) restricts processing to service delivery and excludes other purposes. Sources: meingpt:meingpt:dpa. - provider_training — Do model providers train on it under this product's contracts? [supported]: Section 5(5) states no subprocessor uses customer data to train its own AI model. Sources: meingpt:meingpt:dpa. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: Annex 4 defines ZDR as no permanent copy on the provider infrastructure; exact abuse-monitoring time and exceptions are not specified. Sources: meingpt:meingpt:dpa. - zero_retention — Is zero data retention available, and on which plan? [partial]: Conditional AI/function services in Annex 4 carry ZDR, while SelectCode-controlled storage remains separate; applies to the accepted DPA version. Sources: meingpt:meingpt:dpa. - human_review — Can provider staff review content? [unknown]: Can provider staff review content? Unknown. Human provider-review rights and per-model transient/abuse-retention durations are not disclosed in the accepted-form DPA or data-flow guide. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed-route documentation promises no model training. Applicable upstream retention, ZDR eligibility and human-review exceptions remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise managed chat routes; AI Gateway statements apply only to the Enterprise API module; actual upstream retention unverified; add_ons=Enterprise AI Gateway enablement where explicitly named; BYOK under customer-provider agreement; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - No universal provider ZDR finding is made. The advertised ZDR option is not treated as unsupported; its applicable terms remain a gap. - vendor_training — Does the vendor train on customer content? [supported]: Vendor says it never uses customer data to train its own models. Sources: omnifact:omnifact:privacy-intro. - provider_training — Do model providers train on it under this product's contracts? [partial]: The vendor promises no underlying-provider training for the Enterprise AI Gateway. BYOK processing is under the customer-provider agreement; no managed-route promise is extended to arbitrary customer keys. Sources: omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [unknown]: Unknown applicable duration per enabled model/provider/project. The Trust register describes typical directOpenAI30-day retention and configuration-dependent Google logging, while EU-route pages advertise ZDR. These are not mapped to an actual customer route/contract, so no model-specific retention guarantee is asserted. - zero_retention — Is zero data retention available, and on which plan? [unknown]: Unknown verified ZDR eligibility and scope per Pro/Enterprise model route. Gateway payload handling and EU-route marketing do not establish the upstream provider agreement or every safety/logging exception. Workspace database storage is separate. - human_review — Can provider staff review content? [partial]: Provider processing summaries are request-only in Trust Center; human abuse-review exceptions by provider/model were not established. Sources: omnifact:omnifact:trust-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:privacy-intro, omnifact:omnifact:gateway-web, omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:vertex ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Ordinary chat removal archives; admin retention and contractual deletion use different mechanisms. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - user_deletion: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. - default_retention — What is retained and for how long by default? [supported]: Chat/file data stays until instructed deletion; UI Chat löschen archives. Text translations remain until user deletion; document translations persist until account/workspace deletion. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation. - admin_retention — Can admins set retention periods? [supported]: Release 2.67.0 adds disabled-by-default deletion periods for chats, meetings and automation runs, with a 24-hour wait before a new/shorter period applies. Sources: meingpt:meingpt:changes. - user_deletion — Can users delete their chats and files permanently? [partial]: Chat removal does not permanently delete messages or attachments; final account deletion is requested by the administrator via support. Generated images/text translations have their own deletion controls. Sources: meingpt:meingpt:flow, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:translation. - contract_end_deletion — What is deleted at contract end, and when? [supported]: DPA section 12 requires return or requested deletion, including backups, within 30 days after termination or an agreed export window; statutory retention exceptions apply and proof is available on request. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:flow, meingpt:meingpt:translation, meingpt:meingpt:changes, meingpt:meingpt:security, meingpt:meingpt:images, meingpt:meingpt:dpa #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA contract-end return/approved-destruction duties are separate from support-request deletion and backup retention. A guaranteed runtime exit window remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise published DPA return/deletion obligations; actual runtime exit and account-deletion timing unverified; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - The finding states separate contractual and documented operational procedures. It does not turn a support-request clock into an exit grace period. - default_retention — What is retained and for how long by default? [partial]: DPA: database PITR30 days with daily snapshots/continuous WAL; weekly pg_dump fallback; blob soft-delete14 days. Universal default chat/file retention is unspecified. Sources: omnifact:omnifact:dpa-rev2. - admin_retention — Can admins set retention periods? [partial]: DPA permits organization administrators to set customer-data retention; UI range and per-object options are not published. Sources: omnifact:omnifact:dpa-rev2. - user_deletion — Can users delete their chats and files permanently? [partial]: The Space uploaded-file guide describes permanent deletion of a selected file. Registered-user/profile and whole-organization runtime deletion semantics are not established here; the user-list Delete operation applies to unaccepted invitations. Sources: omnifact:omnifact:uploads, omnifact:omnifact:users. - contract_end_deletion — What is deleted at contract end, and when? [partial]: DPA9.2 requires return or controller-approved destruction no later than contract end, except legal retention;9.3 permits proof-of-processing documentation retention. The TOM separately describes support-request organization deletion within30days and backups aging out. No guaranteed post-termination self-service access window or tested runtime completion time is inferred. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:users, omnifact:omnifact:uploads ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA and processing register name providers, conditional use and advance change notices. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - parent_jurisdiction: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. - subprocessor_list — Is a dated sub-processor list published? [supported]: DPA Annex 4 is dated 24 September 2026; live function/region register is also public. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors. - subprocessor_countries — Which countries do sub-processors operate in? [supported]: Contract entities include Germany, Netherlands, Slovenia, Luxembourg, France, Ireland and Finland. Processing register names Germany platform, France backups, Finland, Ireland, Sweden/France and Frankfurt inference routes; EU symbol is processing, not ownership. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors. - change_notification — Are customers notified of sub-processor changes? [supported]: Section 9 requires notice before additions/replacements and gives two weeks to object on important data-protection grounds, with specified termination rights. Sources: meingpt:meingpt:dpa. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: SelectCode GmbH is a German entity; the security site describes it as independent. A separately owned parent was not identified. Sources: meingpt:meingpt:terms, meingpt:meingpt:subprocessors. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [supported]: DPA section 4(3) uses GDPR Article 45 adequacy or Article 46 safeguards for disclosed/instructed transfers; it does not promise a blanket absence of third-country processing. Sources: meingpt:meingpt:dpa. - government_access_policy — Is there a published government-access or transparency policy? [supported]: Section 7 requires notification where lawful, review/challenge of disproportionate requests, minimization and no compliance with unrecognized third-country requests. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:subprocessors, meingpt:meingpt:terms #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA defines processor-change notice and transfer safeguards; a complete current contract-specific supplier/entity/country register remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise standard hosted DPA; optional model-provider routes only under the applicable contract/instruction; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Neither public list is silently treated as complete. Ordinary notification/transfer contract terms remain distinct from a verified current processing inventory. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Unknown complete current plan-specific processor inventory. DPAAnnex4 and the live Trust register publish different sets; no source establishes a consolidated applicable list or the role of every listed provider for a given contract. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Unknown complete country/legal-entity matrix for the scoped contract. Azure infrastructure and Cloudflare metadata have different roles, and optional model-provider routes depend on selection. The differing DPA/Trust entries are not combined into one asserted authoritative list. - change_notification — Are customers notified of sub-processor changes? [supported]: DPA6.3 requires written/text notice at least 30 days before new/replaced subprocessor and objection opportunity before start. Sources: omnifact:omnifact:dpa-rev2. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: Omnifact Gmb H, Frankfurt, Germany, HRB131357. Ultimate parent/shareholding was not established. Sources: omnifact:omnifact:imprint. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: DPA1.4 permits nonEEA processing after prior information and safeguards under Articles44-49. Optional BYOK/provider routes depend on their applicable agreements. A specific current SCC/DPF basis for every Trust entry was not verified. Sources: omnifact:omnifact:dpa-rev2. - government_access_policy — Is there a published government-access or transparency policy? [partial]: DPA11.2 requires seizure/confiscation notice unless prohibited by court/authority; Terms15.3 require advance compelled-disclosure notice where legal. Separate request statistics were not verified. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa-rev2, omnifact:omnifact:trust-rev2, omnifact:omnifact:imprint, omnifact:omnifact:terms ### DATA-06: Contracts and regulatory coverage Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public GDPR DPA and German-law terms are available; sector coverage needs qualification. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - dpa: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. - revdsg_gdpr: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. - ai_act_materials: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. - sector_materials: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. - dpa — Is a DPA available, and is it negotiable? [partial]: Version 2.0.1 is a public signed-form or electronic-acceptance DPA; negotiability is not promised. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR Article 28 governs the DPA; an explicit Swiss revDSG annex was not found. Sources: meingpt:meingpt:dpa. - governing_law — Which law and court govern the contract? [supported]: DPA section 13 uses German law; terms choose the competent court at the vendor seat. Sources: meingpt:meingpt:dpa, meingpt:meingpt:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Governance includes usage policies and mandatory training; automated EU AI Act use-case checks are labelled Coming soon, so a complete current provider/deployer dossier was not established. Sources: meingpt:meingpt:prices. - sector_materials — Are FINMA or other sector materials provided? [partial]: Governance offers a separate section 203 German professional-secrecy agreement; FINMA-specific materials were not found. Sources: meingpt:meingpt:prices. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa-page, meingpt:meingpt:dpa, meingpt:meingpt:terms, meingpt:meingpt:prices #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public GDPR DPA is binding in German; Swiss and sector-specific contract coverage remains incomplete. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - dpa: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. - revdsg_gdpr: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. - ai_act_materials: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. - sector_materials: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. - dpa — Is a DPA available, and is it negotiable? [partial]: Article28 DPA accepted at registration. German text prevails; English is a translation. Written amendments are possible but negotiability is not promised. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: GDPR is explicit; revised Swiss DSG coverage/addendum and Swiss SCC modifications were not established. Sources: omnifact:omnifact:dpa. - governing_law — Which law and court govern the contract? [supported]: German law and Frankfurt exclusive jurisdiction under Terms18; German legal version prevails. Sources: omnifact:omnifact:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Public AI Act whitepaper and Academy literacy/certification training are advertised; these are not product conformity attestations. Sources: omnifact:omnifact:whitepapers, omnifact:omnifact:pricing. - sector_materials — Are FINMA or other sector materials provided? [partial]: Public-administration, banking and healthcare positioning/private hosting are advertised; actual FINMA/DORA/§203 contract pack was not verified. Sources: omnifact:omnifact:home, omnifact:omnifact:public-sector. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa, omnifact:omnifact:dpa-de, omnifact:omnifact:terms, omnifact:omnifact:whitepapers, omnifact:omnifact:pricing, omnifact:omnifact:home, omnifact:omnifact:public-sector ### DATA-07: Certifications and attestations Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial ISO and penetration-test documents are advertised behind email access; certificates were not independently verified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - iso_27001: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. - c5: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. - pentest: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. - Unverified soc2, other_certifications: SOC 2 and other product attestations were not established. No email-gated report was requested. - iso_27001 — ISO 27001 with scope and validity? [partial]: DPA Annex 3 states ISO/IEC 27001:2022 certificate DE-IS-20250256, Proks Certification GmbH, development/operation of MeinGPT SaaS and custom services, valid to 2028-12-16. The certificate/issuer record was not obtained, so this remains a vendor claim. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested. - c5 — BSI C5 attestation? [partial]: The register attributes BSI C5 to Hetzner infrastructure, not to the MeinGPT service. Sources: meingpt:meingpt:subprocessors. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. SOC 2 and other product attestations were not established. No email-gated report was requested. - report_access — How can customers obtain reports? [supported]: The trust centre asks for email-based access for ISO and SySS 2025 penetration-test documents. Sources: meingpt:meingpt:trust. - pentest — Are independent penetration test summaries available? [partial]: A SySS 2025 penetration-test certificate is listed but its result/scope and validity were not retrieved. Sources: meingpt:meingpt:trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:dpa, meingpt:meingpt:trust, meingpt:meingpt:subprocessors #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public ISO27001 certificate verifies platform/Spaces ISMS through 2029-04-06. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - pentest: DPA states annual external pentests with remediation; actual report/period/summary was not verified. - Unverified soc2, c5, other_certifications: No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - iso_27001 — ISO 27001 with scope and validity? [supported]: Prescient Security LLC certificate123228 issue1, ISO/IEC27001:2022, issued/certified 2026-04-07, valid until 2029-04-06 subject to surveillance. Covers ISMS supporting Platform/Spaces, data, Azure infrastructure, software, people and procedures; So A1.4 dated 2026-03-30. All in-scope activities conducted remotely. Sources: omnifact:omnifact:iso. - soc2 — SOC 2 type, period and covered service? [unknown]: SOC 2 type, period and covered service? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Unknown. No Omnifact-specific SOC2 type/period, C5, ISO27701/42001 or TISAX attestation was verified. - report_access — How can customers obtain reports? [supported]: ISO PDF is public and downloadable through Trust Center. Eight AI-provider processing summaries are request-only and were not requested. Sources: omnifact:omnifact:trust. - pentest — Are independent penetration test summaries available? [partial]: DPA states annual external pentests with remediation; actual report/period/summary was not verified. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:iso, omnifact:omnifact:trust, omnifact:omnifact:dpa ### DATA-08: Encryption and key control Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN). #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Encryption and logical tenancy are documented; key and private-networking details remain incomplete. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Business/Enterprise hosted workspace; CMK entitlement excluded from verified findings; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - CMK is an access/entitlement gap, not an absent capability. - encryption_at_rest — Is data encrypted at rest? [supported]: Security guide states AES-256 at rest and TLS 1.3; DPA Annex 3 includes encryption at rest/transit. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Unknown for Business or Enterprise. The security FAQ says Customer Managed Keys are on request but does not identify an eligible tier, price, key custody or location. No plan-scoped CMK commitment was verified. - private_networking — Is private connectivity or IP restriction available? [unknown]: Is private connectivity or IP restriction available? Unknown. A private-link/IP allowlist/VPN product entitlement was not established; Outpost outbound TLS is a source connector rather than a private SaaS endpoint. - tenant_isolation — How are customers separated in shared SaaS? [partial]: DPA Annex 3 specifies logical tenant separation and network segmentation; no independent isolation test was run. Sources: meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:dpa #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial AES256/TLS and logical tenant separation are documented; customer-held keys remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - private_networking: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. - Unverified customer_managed_keys: No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - encryption_at_rest — Is data encrypted at rest? [supported]: DPA requires AES256 at rest for Postgre SQL, Blob Storage and other persistent Azure services; HTTPS/TLS in transit. Sources: omnifact:omnifact:dpa. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Unknown. No customer-managed/held encryption-key configuration was established; sovereignty discussion does not establish key-management functionality. - private_networking — Is private connectivity or IP restriction available? [partial]: Vendor internal services use NSGs/Private Endpoints and NetBird JIT VPN for privileged production access; public app is Cloudflare-fronted. A customer private-link/IP-allowlist option was not established. Sources: omnifact:omnifact:dpa. - tenant_isolation — How are customers separated in shared SaaS? [supported]: Organization-scoped data/roles, separate production/development/test Azure environments, no customer data in tests. This is logical tenant separation. Sources: omnifact:omnifact:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:dpa ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The base AGB contains conditional professional-secrecy duties. Eligibility and executed terms of the separately marketed Governance addendum remain unknown. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked2026-10-21; plan=Business/Enterprise customer contracts incorporating AGB section12(4); only the base-terms obligation is assessed; add_ons=Separate Governance addendum excluded from verified entitlement; contract required; deployment_mode=multi-tenant-saas; region=Germany/EU platform; model route and deployment exceptions apply; os=not specified. Limitations: - The base-terms duties and a separately executed Governance addendum are separate legal documents. No claim that one depends on purchase of the other is made. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [partial]: For contracts incorporating the published AGB, section12(4) applies when processed data fall under professional secrecy, including §203. It imposes indefinite confidentiality, access only as necessary to perform services and acknowledgement of criminal duties. The clause states no Governance prerequisite. It does not establish a separately executed addendum or Swiss Art321 coverage. Sources: meingpt:meingpt:secrecy-contract-rev2. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [partial]: Section12(4) requires staff/subcontractors who can access covered data to be bound in at least text form. Subcontracting and services outside the EU require text consent, deemed granted for known providers at contract start. Provider-specific executed undertakings were not retrieved. Sources: meingpt:meingpt:secrecy-contract-rev2. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: Unknown whether the separate Governance §203 addendum is available with self-service Business or only a contracted platform offer. The calculator lists it under Governance at EUR1.35/user/month annually, but this is not proof of eligibility or a fee for the base AGB duties. Sources: meingpt:meingpt:prices-rev2. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The base AGB restrict knowledge of covered data to what is necessary for the contracted service. The clause does not promise that staff or model providers can never see plaintext. Agreement-specific access restrictions beyond section12(4) were not verified. Sources: meingpt:meingpt:secrecy-contract-rev2. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [partial]: The public AGB section12(4) is the verified contract text. A separately executed/template Governance addendum and provider-by-provider undertakings were not obtained. Sources: meingpt:meingpt:secrecy-contract-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:secrecy-contract-rev2, meingpt:meingpt:prices-rev2 #### Omnifact Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ## Commercials and vendor ### VEN-01: Pricing model and list prices Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Self-service Business costs EUR29/user/month excluding VAT and includes standard-model use. Enterprise and platform-module pricing are outside this scoped offer. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business, monthly billing only; contracted Enterprise/platform calculator excluded; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - The progressive platform calculator is not used as a Business tariff. Its contract eligibility remains outside this finding. - pricing_unit — What is the pricing unit? [supported]: Business is sold per user per month through self-service Stripe checkout. Premium/reasoning models, API use and meeting-bot recordings are separately metered. Sources: meingpt:meingpt:billing-rev2. - list_prices — What are list prices per plan, with date and currency? [supported]: Self-service Business is EUR29/user/month, excluding VAT, on monthly billing. No annual discount or progressive marginal tiers are applied to this offer. Sources: meingpt:meingpt:billing-rev2. - included_usage — What usage is included? [partial]: Standard-model use in Business is unlimited according to the billing guide. Premium/reasoning models, API and meeting bots remain additional; the exact standard-model catalog and any applicable workload restrictions are not fixed by this page. Sources: meingpt:meingpt:billing-rev2. - add_ons — Which features cost extra? [unknown]: Unknown for self-service Business. The separate platform calculator has Governance/Outpost modules, but their Business eligibility and package prices were not established. - overage — What do usage beyond limits and premium models cost? [partial]: Business standard models do not consume additional billed usage under the billing guide. Premium/reasoning, API and meeting-bot use draw on workspace credit; meeting bots cost EUR0.80/audio hour. Other route-specific charges depend on the selected service. Sources: meingpt:meingpt:billing-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro costs EUR25/user/month annually up to50users. Its binding credit currency/value and recharge tariff remain unknown; Enterprise Gateway costs are outside this offer. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro hosted workspace up to50users; Enterprise/API Gateway quote and markup excluded; add_ons=Optional Academy separately quoted; Enterprise terms require separate offer; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Pro Chat/Spaces pricing is not mixed with Enterprise Gateway billing. The conflicting credit examples remain a named allowance gap. - pricing_unit — What is the pricing unit? [supported]: Pro uses named seats with monthly or annual billing and pooled premium-model credit; this finding covers the hosted Chat/Spaces subscription. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - list_prices — What are list prices per plan, with date and currency? [partial]: Checked2026-10-21: Pro EUR25/user/month billed annually, advertised16% discount versus monthly. Exact monthly rate was not verified. Pro up to50 users; Enterprise custom with unlimited team size. VAT excluded under terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - included_usage — What usage is included? [partial]: Unknown applicable monetary allowance currency/value for the contract: pricing statesEUR5/user/month while Billing usesUSD5 examples. Pooling, monthly expiry and continued base-tier access subject to fair-use limits are documented, but no definitive currency-denominated allowance is asserted. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing. - add_ons — Which features cost extra? [partial]: Academy training is separately quoted. Enterprise is a separate custom offer adding SSO/SCIM, BYOK/self-hosted models, analytics and custom deployment/SLA. No Enterprise Gateway markup is applied to Pro Chat/Spaces pricing. Sources: omnifact:omnifact:pricing-rev2. - overage — What do usage beyond limits and premium models cost? [partial]: The Pro billing guide directs admins to discuss additional credits; a public recharge tariff was not established. Base-tier chat remains available after included premium credit is used subject to usage limits. Enterprise Gateway billing/markup is outside this Pro finding. Sources: omnifact:omnifact:billing, omnifact:omnifact:pricing-rev2, omnifact:omnifact:limits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:limits, omnifact:omnifact:users, omnifact:omnifact:gateway, omnifact:omnifact:developer ### VEN-02: Scenario cost Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business-only seat floors are EUR69600 / EUR348000 / EUR1740000 for200/1000/5000 users over12months, each plus unknown workload and contract components. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Self-service Business at EUR29/user/month, paid monthly for12months; Business standard-chat floor only; add_ons=No paid add-ons included; required extras unknown; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12months, list prices, excluding VAT;60% light100,30% regular400,10% power1500 messages/user/month;3000 input and600 output tokens/message. Weighted330messages,0.99M input/0.198M output per user/month. Token mix is used only on separately billed routes; this Business standard-chat floor has included usage. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237. Vendor currency EUR is primary. Contract-specific extras remain unknown. - cost_200 — Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 200 users over12months: from EUR69600.00 / CHF64289.52 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - cost_1000 — Year-one cost at 1,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 1000 users over12months: from EUR348000.00 / CHF321447.60 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - cost_5000 — Year-one cost at 5,000 users? [partial]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Self-service Business seat floor for 5000 users over12months: from EUR1740000.00 / CHF1607238.00 + unknown, excluding VAT. Uses EUR29/user/month with monthly billing and no invented annual discount. Standard-model chat is included, so no separate token bill is added for that included route. Eligibility at this size, the exact standard-model catalog needed for the workload, premium/API/meeting use, add-ons and Enterprise services remain unknown. This is a Business floor, not an Enterprise quote. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx. - variable_share — Which part depends on usage? [partial]: Business standard-model chat is included. A model-preserving workload outside that standard catalog, premium/reasoning models, API and meeting-bot charges cannot be quantified without the actual route and contract; the variable remainder stays unknown. No provider proxy or progressive-platform tariff is substituted. Sources: meingpt:meingpt:billing-rev2. - unknown_parts — Which costs could not be priced? [partial]: Business eligibility for200/1000/5000 users, standard-model mapping, premium/tool use, required Governance/Outpost, rollout and Enterprise services remain unknown. No progressive-platform amount is mixed into the Business floor. Sources: meingpt:meingpt:billing-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing-rev2, meingpt:meingpt:ecb-fx #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared v1.4 costs remain unknown for200/1000/5000 users because all exceed the50-seat Pro cap. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. - ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 200 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 1000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Unknown for 5000 users:Pro caps50 users,so Enterprise licence,allowance and deployment/support quote are required. No quote requested; do not extrapolate EUR25 Pro rate. ALM-14 shared cost assumptions v1.4, 2026-10-21:12 months at public list prices, excluding VAT and invented discounts.60% light at100 messages/user/month,30% regular at400,10% power at1500;3000 input+600 output tokens/message including retrieval context,weighted330 messages and0.99M input/0.198M output per seat/month. Use this token mix only where usage is billed separately. Unknown quoted components remain unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; USD1=EUR0.89166206. Retrieved2026-10-21. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx. - variable_share — Which part depends on usage? [partial]: Enterprise base,pooled credit allowance,model/route rates,additional credits and Gateway markup are unknown. Quote base plus usage beyond included credit plus deployment/services; convert known EUR components at0.9237 CHF/EUR. No substitute vendor tariff/model assumed. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing, omnifact:omnifact:ecb-fx. - unknown_parts — Which costs could not be priced? [supported]: Enterprise seat/volume rate,minimum spend,credit allowance,recharge tariff,model/route rates,Gateway markup percentage,private hosting and Academy service fees are unknown. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway, omnifact:omnifact:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:ecb-fx, omnifact:omnifact:gateway, omnifact:omnifact:billing ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial A self-serve 10-day trial exists, while several enterprise features still need enablement. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - free_tier: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. - trial_scope: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. - sales_gate: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. - free_tier — Is there a free tier for business use? [partial]: Trial expiry locks the workspace even for free models; the guide does not describe a permanent free business workspace. Sources: meingpt:meingpt:billing. - self_serve_trial — Is a self-serve business trial available? [supported]: 10 days, EUR 5 after phone verification, no payment details or automatic paid conversion, up to ten emailed invitees. Sources: meingpt:meingpt:billing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Most base functions are included; personal API keys are off, and request-only meeting/live recording and automations are initially off as in paid plans. SCIM/SSO enterprise enablement is not guaranteed. Sources: meingpt:meingpt:billing. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base trial is self-serve; request-enabled features and Enterprise terms are not self-service. No sales contact was made. Sources: meingpt:meingpt:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:billing #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Ten-day no-card Pro trial is self-serve; enterprise setup is gated. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - free_tier: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. - trial_scope: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. - sales_gate: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. - free_tier — Is there a free tier for business use? [partial]: Time-limited free trial; billing requires a paid subscription afterward. No permanent business free tier established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing. - self_serve_trial — Is a self-serve business trial available? [supported]: Ten-day trial, no credit card, teams up to50 users via account signup. Sources: omnifact:omnifact:pricing. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Pro chat, Spaces, Privacy Filter and platform access advertised; terms call trial scope limited. Enterprise SSO/SCIM/BYOK/private deployment and support-enabled APIs are not established trial entitlements. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:developer. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Base Pro trial is self-serve; Enterprise quotes, SSO and advanced API activation require vendor interaction. No vendor contact was made. Sources: omnifact:omnifact:pricing, omnifact:omnifact:users, omnifact:omnifact:developer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:billing, omnifact:omnifact:terms, omnifact:omnifact:developer, omnifact:omnifact:users ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public price fields and German contract defaults exist; customer-specific terms and CHF invoicing remain open. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - minimum_commitment: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. - local_invoicing: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. - transparency_class: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. - minimum_commitment — What seat or spend minimum applies? [partial]: Public calculator starts at one user; individually negotiated Enterprise or on-prem minimums are not stated. Sources: meingpt:meingpt:prices. - contract_length — What contract lengths are offered? [supported]: Public calculator has annual/monthly options; terms default to one year absent another agreement. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms. - cancellation — How can the contract be cancelled or reduced? [supported]: Absent other terms, three months before term-end, text/email or admin cancellation; downgrades/user reductions effective following month, no current-month refund. Price changes require the stated notice/consent procedure. Sources: meingpt:meingpt:terms. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: SelectCode GmbH is the German contracting entity and prices are EUR; CHF invoices were not confirmed. Sources: meingpt:meingpt:terms. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partially specified: public marginal seat/model/add-on rates, but PII base, services and deployments are quote-only and Business packaging differs. Sources: meingpt:meingpt:prices, meingpt:meingpt:billing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms, meingpt:meingpt:billing #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro monthly/annual terms are public; Enterprise minimum and CHF invoicing are unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - minimum_commitment: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. - local_invoicing: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. - transparency_class: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. - minimum_commitment — What seat or spend minimum applies? [partial]: Pro maximum 50 users, Enterprise no team-size cap; public Enterprise minimum seat/spend and private-deployment minimum not established. Sources: omnifact:omnifact:pricing. - contract_length — What contract lengths are offered? [supported]: Monthly/annual terms; Enterprise flexible agreement. Annual renews yearly, monthly renews monthly. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. - cancellation — How can the contract be cancelled or reduced? [supported]: Annual notice three months before term end; monthly cancel for following month; text/email accepted. Seat removal gives prorated credit on next invoice per billing doc. Sources: omnifact:omnifact:terms, omnifact:omnifact:billing. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Omnifact Gmb H Frankfurt invoices EUR public prices, supports invoice/SEPA and payment within 14 days. CHF billing not established. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:imprint. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: Partial: public Pro price/credits/team cap but Enterprise, deployment, additional credits and services quote-only; Gateway markup not quantified. Sources: omnifact:omnifact:pricing, omnifact:omnifact:gateway. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms, omnifact:omnifact:billing, omnifact:omnifact:imprint, omnifact:omnifact:gateway ### VEN-05: Source licence Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public AGB establish a commercial subscription/rental use licence with contract-limited rights. Public component source licences and a distinct enterprise source-edition mapping remain unverified. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - Contractual service-use rights do not establish the licence of every server/client/connector dependency. - No public implementation repository or enterprise source-edition map was identified. - licence_type — Which licence applies to each component? [partial]: SelectCode AGB describe the software as a subscription/rental and grant a non-exclusive use right limited to the contract term. Public display, adaptation, translation and decompilation of the software are restricted subject to statutory rights. This establishes the commercial service-use licence; a client/server/connector source-licence inventory and current implementation revision remain unpublished. Sources: meingpt:meingpt:terms-20261026. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: AGB require purchased licences for majority-owned affiliates and give no independent right to sublicense or transfer usage rights. They restrict adapting the software. A numerical user cap or a component-specific branding licence is not established by these clauses. Sources: meingpt:meingpt:terms-20261026. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? Unknown. The public commercial terms describe rented software, but no public client/server/connector source licence or current repository revision was located. Repository visibility was not treated as a licence. Rechecked 2026-10-26 in Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Official links and targeted first-party searches yielded no further plan-scoped specification for the remaining atom. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: meingpt:meingpt:terms-20261026 #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Platform is proprietary; four inspected public integration/client components have MIT licences. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - licence_type — Which licence applies to each component? [supported]: Terms grant contract-term nontransferable/non-sublicensable software use; platform source excluded unless expressly agreed. CLI, widget, n8n nodes and XWiki sync carry MIT licences at pinned commits; these do not license the hosted platform. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Platform use limited to agreed user count/own business personnel. Widget can theme colors/title under MIT notice obligations; MIT integrations do not impose seat limits. Platform branding-removal rules were not fully established. Sources: omnifact:omnifact:terms, omnifact:omnifact:widget-rev2, omnifact:omnifact:widget-licence-rev2. - enterprise_features_closed — Are enterprise features in a separate closed edition? [partial]: Enterprise is a commercial feature/deployment tier; no open-core platform edition was established. Source may be included by separate agreement under terms3.3. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:terms, omnifact:omnifact:cli-licence-rev2, omnifact:omnifact:widget-licence-rev2, omnifact:omnifact:n8n-nodes-omnifact-licence-rev2, omnifact:omnifact:xwiki-sync-licence-rev2, omnifact:omnifact:widget-rev2, omnifact:omnifact:pricing-rev2 ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Individual downloads exist but a bulk chat export is explicitly unavailable. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - chat_export: Security FAQ explicitly says there is currently no function to export all chats at once. - export_format: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. - post_termination_window: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. - Unverified assistant_export, knowledge_export: No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - chat_export — Can admins export all chats? [unsupported]: Security FAQ explicitly says there is currently no function to export all chats at once. Sources: meingpt:meingpt:security. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. No reusable assistant/prompt or knowledge-bundle export specification was located and no admin export fixture was run. - export_format — Are formats documented and machine-readable? [partial]: Individual artifacts/slides/files/images can be downloaded; administrative logs have CSV/JSON exports. This does not establish portable assistants or a complete knowledge export. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export. - post_termination_window — How long can data be retrieved after termination? [partial]: Terms permit export until termination takes effect; later access is blocked. DPA allows an individually agreed export window and return/deletion within 30 days after it. Sources: meingpt:meingpt:terms, meingpt:meingpt:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:security, meingpt:meingpt:audit-export, meingpt:meingpt:terms, meingpt:meingpt:dpa #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial DPA promises data handover; documented APIs do not establish a complete workspace export. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace, Omnifact Published Spaces, Public API and Enterprise AI Gateway, Omnifact document/chat CLI and XWiki sync, Omnifact example embeddable widget; version=Public documentation checked 2026-10-21; plan=Pro/Enterprise hosted licence; separately MIT-licensed client/integration tools at pinned revisions; API enablement required; add_ons=Customer-run CLI/widget tools; Published Spaces/API access and resource permissions as needed; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Client/integration capabilities are documented in pinned README/licence files, not implementation-inspected or tested; they do not license the hosted platform. - chat_export — Can admins export all chats? [unknown]: Can admins export all chats? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. No admin export-all-chats or reusable complete Space/agent/prompt export was established. No exit fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Documents API/CLI list metadata and manage Space files, while native generated files download. Full original-source, index and ACL export bundle was not established. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents. - export_format — Are formats documented and machine-readable? [partial]: Document metadata via JSON; native outputs DOCX/XLSX/PPTX and chart images. Widget stores only its own conversation in browser local Storage; this is not an admin export of platform chats. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2. - post_termination_window — How long can data be retrieved after termination? [partial]: DPA9.2 requires handover or approved destruction at completion/end; no guaranteed post-termination self-service download window specified. TOM gives30-day support organization deletion. Sources: omnifact:omnifact:dpa-rev2. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:api-docs, omnifact:omnifact:cli-rev2, omnifact:omnifact:documents, omnifact:omnifact:widget-rev2, omnifact:omnifact:dpa-rev2 ### VEN-07: Support and service levels Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial German vendor support and a public incident history are documented; an uptime credit schedule was not found. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - support_channels: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. - Unverified support_languages, uptime_sla: Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - support_channels — Which support channels are available on each plan? [partial]: Terms provide email support Monday-Friday 09:00-17:00; timezone and plan-specific guaranteed response times are not stated. Sources: meingpt:meingpt:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: SelectCode GmbH contracts from Unterhaching, Germany. Sources: meingpt:meingpt:terms. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? Unknown. Contractual German/French/Italian support coverage, uptime commitments and credits were not established in public terms; German documentation alone does not prove language coverage. - status_page — Is there a public status page with history? [supported]: Public status.meingpt.com lists the platform and historical incidents; uptime is not an SLA. Sources: meingpt:meingpt:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:terms, meingpt:meingpt:status #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro email support and Enterprise custom support are documented; a single applicable platform uptime SLA remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro published support terms; Enterprise support and negotiated SLA only under its contract; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - Network and system availability percentages are not interchangeable. Enterprise SLA terms require the actual contract. - support_channels — Which support channels are available on each plan? [partial]: Pro pricing promises email within 24 hours; terms process M–F usually09–17 and answer within one working day. Enterprise dedicated support/account manager/custom SLA; timezone not specified in terms. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: Omnifact Gmb H Frankfurt, Germany; pricing also mentions German and US service teams. No Swiss entity established. Sources: omnifact:omnifact:imprint, omnifact:omnifact:pricing-rev2. - uptime_sla — Is there an uptime SLA with credits? [unknown]: Unknown applicable end-to-end service guarantee. Terms7.3 specify99.5% annual pure-network availability while DPA TOM states99.9% system availability, and Enterprise offers a custom SLA. No order-form/service mapping or fixed credit schedule was retrieved, so no single platform SLA is asserted. - status_page — Is there a public status page with history? [unknown]: Is there a public status page with history? Unknown. No verified public incident-history status page or contracted DE/FR/IT support-language matrix was located; status.omnifact.ai did not resolve. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing-rev2, omnifact:omnifact:terms, omnifact:omnifact:imprint, omnifact:omnifact:dpa-rev2 ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### meinGPT Verification status: Agent cross-checked (agent-cross-checked) Support: partial Learning paths and business examples are built in; personal rollout services are quote-based. Availability: generally-available Delivery: native Scope: surfaces=meinGPT hosted workspace; version=Public documentation checked 2026-10-21; plan=Platform licence; Governance, Enterprise API and request-only features identified below; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Germany platform storage; model processing depends on provider, model and agreed DPA; os=not specified. Limitations: - onboarding_service: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. - user_training: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. - adoption_programme: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. - onboarding_service — Is guided onboarding included? [partial]: Personal guidance covers selection, pilot and rollout on an individual offer; universal included consulting is not promised. Sources: meingpt:meingpt:prices. - user_training — Is end-user training offered, in which languages? [partial]: The learning area has guided practical courses; Governance enables mandatory assignments. Complete course language coverage was not stated. Sources: meingpt:meingpt:academy, meingpt:meingpt:audit. - use_case_library — Are role-based use cases and templates provided? [supported]: Role/department personalization and business-use-case material are documented. Sources: meingpt:meingpt:academy. - adoption_programme — Is there a champion or adoption programme? [partial]: Pilot/adoption workspaces typically run a three-month fixed-price pilot with workshops; a defined champion programme was not found. Sources: meingpt:meingpt:billing. - service_cost — Which services cost extra? [supported]: Personal guidance is quote-only; terms bill services by time/person-days or individually agreed fixed price. Sources: meingpt:meingpt:prices, meingpt:meingpt:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: meingpt:meingpt:prices, meingpt:meingpt:academy, meingpt:meingpt:audit, meingpt:meingpt:billing, meingpt:meingpt:terms #### Omnifact Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pro has learning material/webinar; Enterprise workshops and Academy are tailored. Availability: generally-available Delivery: native Scope: surfaces=Omnifact hosted workspace; version=Public documentation checked 2026-10-21; plan=Pro Saa S up to50 users; Enterprise/BYOK/API options named per finding; unspecified entitlement where documentation does not map it; add_ons=none stated; deployment_mode=multi-tenant-saas; region=Omnifact Azure Germany West Central/Frankfurt storage; model-specific EU/direct routes, not a universal processing residency promise; os=not specified. Limitations: - user_training: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. - adoption_programme: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. - service_cost: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. - onboarding_service — Is guided onboarding included? [supported]: Pro onboarding documentation/e-learning and webinar; Enterprise custom onboarding/use-case workshops and account manager. Sources: omnifact:omnifact:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Academy offers foundational/advanced courses, individual training and certificate options supporting AI literacy; complete delivery-language/volume entitlement not published. Sources: omnifact:omnifact:pricing. - use_case_library — Are role-based use cases and templates provided? [supported]: Space Starter templates include content creation, knowledge queries, professional development; release notes add meeting-minutes/mail-triage/helpdesk template previews. Sources: omnifact:omnifact:create, omnifact:omnifact:changes. - adoption_programme — Is there a champion or adoption programme? [partial]: Enterprise rollout/admin enablement/use-case workshops and Academy strategy/governance workshops advertised; a formal champion programme was not established. Sources: omnifact:omnifact:home, omnifact:omnifact:pricing. - service_cost — Which services cost extra? [partial]: Academy/additional training separately quoted; terms3.6 generally make installations, instruction/training chargeable under separate agreement. Sources: omnifact:omnifact:pricing, omnifact:omnifact:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: omnifact:omnifact:pricing, omnifact:omnifact:create, omnifact:omnifact:changes, omnifact:omnifact:home, omnifact:omnifact:terms ## Sources ### meingpt:meingpt:rates Alle Modelle | MeinGPT Docs. Public EUR token and service rates include GPT-5 mini at EUR 0.30 input and EUR 2.40 output per million tokens. - URL: https://meingpt.com/docs/admin-guide/pricing - Locator: Text-generation, translation, images and other-functions tables - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:models-rev2 Modelle | MeinGPT Docs. Current documentation lists selectable non-Meta model families, per-chat selection and context-length routing; the lifecycle table contains no current selectable Meta model. - URL: https://meingpt.com/docs/platform/models - Locator: Model picker, model tables and own-LLM-key FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:lifecycle-rev2 Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published. - URL: https://meingpt.com/docs/admin-guide/model-lifecycle - Locator: Phases, notice period and current-model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:models Models: All Leading AI Models on One Platform – Omnifact. Current catalogue lists model families, tiers and EU/global region flags. - URL: https://omnifact.ai/models - Locator: OpenAI, Anthropic, Google and Mistral tables - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:select Selecting an AI Model - Omnifact. Manual model picker shows provider/model/region and reasoning effort; browser stores per-model effort. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/model-selection - Locator: Model selector, effort and reasoning trace - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:files Attaching Documents & Images - Omnifact. Attachments have type-specific limits and media bypasses text filtering. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/attaching-documents - Locator: Formats, input limits and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing-rev2 Pricing Plans – Omnifact. Pro is EUR25/user/month annually up to50users. Enterprise adds BYOK/self-hosted models, analytics, SSO and custom SLA. The page is not used to establish an eligible Gateway markup or reconcile conflicting credit examples. - URL: https://omnifact.ai/pricing - Locator: Pro/Enterprise tier table, annual price and credit footnote - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:providers-rev2 Providers - Omnifact. Customer keys, custom OpenAI-compatible endpoints and self-hosted model connections require Enterprise BYOK; managed model access is separate. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers and Enterprise-only Bring Your Own Key - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:groups-rev2 Group Management - Omnifact. The Python/code execution tool is explicitly Experimental, has internet access and bypasses the Privacy Filter for sandbox inputs. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Execute code (Experimental), tool controls and security note - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-rev2 Data Processing Agreement – Omnifact. DPA states return/approved destruction at contract end, distinct support-request deletion within30days, backup schedules and30-day subprocessor-change notice. This does not resolve runtime/plan-specific implementation or a complete current supplier mapping. - URL: https://omnifact.ai/dpa - Locator: Sections6.3,9.2/9.3; Annex3 deletion and backups; Annex4 subprocessor terms - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### meingpt:meingpt:lifecycle Modell-Lifecycle | MeinGPT Docs. Active models, future retirement dates and automatic replacement rules are published. - URL: https://meingpt.com/docs/admin-guide/model-lifecycle - Locator: Phases, notice period and current-model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:changes Was wir zuletzt released haben | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. Release 2.67.0 on 18 October adds Gemini 4 Argon, retires named models and adds configurable deletion periods. - URL: https://meingpt.com/changelog - Locator: v2.67.0, model retirement and deletion periods - Evidence kind: documented - Source date: 2026-10-18 - Retrieved: 2026-10-21 ### omnifact:omnifact:changes Release Notes – Omnifact. Dated release notes through October 20 add models, agents, code, MCP, groups and 2FA. - URL: https://omnifact.ai/release-notes - Locator: October–May2026 and earlier entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### omnifact:omnifact:blog Blog – Omnifact. Feature announcements include Gemini4Argon October 13 and integrations October 6. - URL: https://omnifact.ai/blog - Locator: Current dated feature drops - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:models Modelle | MeinGPT Docs. Users choose models per chat; automatic selection is based on context length; customer LLM keys and endpoints cannot be added. - URL: https://meingpt.com/docs/platform/models - Locator: Model picker, model tables and own-LLM-key FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:translation Übersetzer | MeinGPT Docs. Default text translation uses Google Cloud Translate and document translation uses DeepL through EU endpoints; glossaries and layout preservation are documented. - URL: https://meingpt.com/docs/platform/translation - Locator: Engine/hosting, formats and glossary management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:terms Terms of Service – Omnifact. Terms define proprietary rights,99.5% annual network availability, support and cancellation. - URL: https://omnifact.ai/terms - Locator: Sections3/6–8/10–11/14–18 - Evidence kind: documented - Source date: 2024-08-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:providers Providers - Omnifact. Enterprise BYOK supports direct providers, Azure/Vertex and custom OpenAI-compatible endpoints. - URL: https://docs.omnifact.ai/en/platform/team-administration/providers - Locator: Supported Providers, BYOK and connection management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:model-settings Model Management - Omnifact. Model enablement applies to chat, Published Spaces and Gateway; image defaults and tiers are configurable. - URL: https://docs.omnifact.ai/en/platform/team-administration/models - Locator: Availability, Image Models and Model Providers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:subprocessors Subdienstleister & Verarbeitungsregionen | MeinGPT. The register separates Germany platform storage, France backups and provider-specific EU inference regions. - URL: https://meingpt.com/sicherheit/subdienstleister - Locator: Register by function and processing region - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:pricing Pricing Plans – Omnifact. Pro annual EUR25 includes pooled EUR5 monthly AI credits per seat up to50 users; Enterprise and Academy are quoted. - URL: https://omnifact.ai/pricing - Locator: Pro, Enterprise, comparison and footnote1 - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:config Workspace-Konfiguration | MeinGPT Docs. Admins can restrict models by teams or people and supply workspace-wide instructions; denied API models return an error. - URL: https://meingpt.com/docs/admin-guide/workspace-configuration - Locator: Model access, default settings and additional chat context - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:limits Nutzungslimits | MeinGPT Docs. Personal category budgets block new use at zero; running meeting bots can overrun limits and scheduled runs are outside personal categories. - URL: https://meingpt.com/docs/admin-guide/usage-limits - Locator: Usage levels, meeting limits and user consumption table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:api Einführung | MeinGPT Docs. Chat, embeddings, assistants, workflows and transcription APIs use bearer keys and published token rate limits; translation is UI-only. - URL: https://meingpt.com/docs/api - Locator: API overview, rate limits and errors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa Data Processing Agreement – Omnifact. DPA includes Frankfurt infrastructure/TOMs, retention, audit requirements and approved subprocessors. - URL: https://omnifact.ai/dpa - Locator: Sections1/6/9/11, Annex1, TOMs2.1–2.10 and Annex4 - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:groups Group Management - Omnifact. Additive groups govern capabilities, model tiers, US routes and filter exemptions; Enterprise SCIM mirrors groups. - URL: https://docs.omnifact.ai/en/platform/team-administration/groups - Locator: Group types, SCIM, permissions and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:gateway AI Gateway - Omnifact. Enterprise opt-in OpenAI-compatible gateway uses eu/ routing and hard credit enforcement; V1 lacks tools/structured output. - URL: https://docs.omnifact.ai/en/platform/team-administration/ai-gateway - Locator: Prerequisites, EU routes, constraints, billing and errors - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:published Published Spaces - Omnifact. Support-enabled Published Space APIs disable the Privacy Filter and use secret endpoint URLs. - URL: https://docs.omnifact.ai/en/platform/team-administration/published-spaces - Locator: Activation, model management and security - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:chat Introduction to Chats - Omnifact. Chat retains conversations and supports document output, sources and daily message quotas. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/introduction - Locator: Features, quotas and message limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:limits AI Credits and Usage Limits - Omnifact. Exhausted monthly credits fall back in chat; Gateway blocks all calls without base fallback. - URL: https://docs.omnifact.ai/en/guides/troubleshooting/usage-and-credits - Locator: Credit exhaustion and fallback models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:pools Datenquellen & RAG | MeinGPT Docs. Cloud pools index six source types in Germany, refresh every 15 minutes and share a 300 GB raw-data budget. - URL: https://meingpt.com/docs/integrations/data-pools-rag - Locator: Cloud-source table, connector comparison and normal-chat search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:chat Eingabefeld | MeinGPT Docs. Chat has stop, model choice, file upload, dictation and sharing links, with 50 files and 50 MB per non-image file. - URL: https://meingpt.com/docs/platform/chats/eingabefeld - Locator: Input controls, file limits, dictation and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:flow Datenfluss bei MeinGPT Chats | MeinGPT Docs. Chat deletion archives content; prompts have provider-dependent processing, and platform data stays until instructed deletion. - URL: https://meingpt.com/docs/privacy-security/faq-chats-datenfluss - Locator: Processing steps, providers and deletion rights - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:sandbox Code-Sandbox | MeinGPT Docs. Python/JavaScript analysis and Office generation run in an isolated Unikraft Cloud VM in Frankfurt, including for on-premise customers. - URL: https://meingpt.com/docs/platform/code-sandbox - Locator: Execution flow, hosting, lifetime and limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:documents Document Creation - Omnifact. Isolated Python code creates XLSX/DOCX/PPTX/charts with internet egress and group controls. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/document-creation - Locator: Document types, editing, formulas and sandbox - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:uploads Managing Uploaded Files - Omnifact. Space file pipeline uses Tika OCR, chunking, embeddings and summaries; documents can be deleted permanently. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/managing-uploaded-files - Locator: Processing, deletion and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:retrieval Uploaded Files Retrieval - Omnifact. Agents retrieve source passages under Space membership and show citations/progress; strict no-answer grounding is instructed. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/uploaded-files-retrieval - Locator: Retrieval and source behavior - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:assistants Assistenten | MeinGPT Docs. Assistants combine model, instructions, files, pools, connectors, tools and memory. - URL: https://meingpt.com/docs/platform/assistants - Locator: Creation guide and editor sections - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:projects Projekte | MeinGPT Docs. Projects share instructions and workflows while each member keeps a private chat history. - URL: https://meingpt.com/docs/platform/projects - Locator: Collaboration, roles and deletion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:billing Billing & Usage - Omnifact. Billing describes proration, pooled credit and plan changes but uses USD5 examples and5000-page Pro quota. - URL: https://docs.omnifact.ai/en/platform/team-administration/billing - Locator: Seat Management, Monthly Usage Credit and Plan Management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:spaces What are Spaces? - Omnifact. Spaces persist instructions/knowledge and conversations with shared member access. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/introduction - Locator: Concepts, benefits and examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:share Sharing Spaces with Colleagues - Omnifact. Organization users/groups share Spaces; group access is view-only and removal is immediate. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/sharing-spaces - Locator: Roles, group sharing and removal - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:sync Connected Sources - Omnifact. Connected sources index selected Drive/OneDrive/SharePoint folders every five minutes and remove deleted content next cycle. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/connected-sources - Locator: Setup, privacy and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:integrations Integrations - Omnifact. Curated first-party MCP and document connectors use separate live-versus-indexed access patterns. - URL: https://docs.omnifact.ai/en/platform/team-administration/integrations - Locator: Catalog, integration types and privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:directory Integrations: Connect the Tools Your Team Uses – Omnifact. Current catalogue names cloud storage, Google, Atlassian, CRM, design, communications and developer systems. - URL: https://omnifact.ai/integrations/catalog - Locator: Integration cards and custom MCP - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-rev2 omnifact-xwiki-sync pinned README. omnifact-xwiki-sync documents incremental XWiki page/attachment ingestion with delete propagation. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/README.md - Locator: Pinned README.md documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:mcp-rev2 MCP Servers - Omnifact. Tools have Always/Approval/Disable policies; Approval shows the request payload. Documentation conflicts on initial discovery defaults, which remain unknown. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Per-tool policies, authentication and later tool refresh; initial discovery defaults excluded - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:m365 Microsoft 365 | MeinGPT Docs. Separate Outlook, Teams, SharePoint and OneDrive connectors run under user OAuth; Outlook can write, the other three read. - URL: https://meingpt.com/docs/integrations/connectors/microsoft365 - Locator: Overview, setup, tenant consent and permission model - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:pool-controls Sucheinstellungen am Datenpool | MeinGPT Docs. Source-permission import is off by default and request-enabled for SharePoint and Drive only; answers always show sources. - URL: https://meingpt.com/docs/integrations/data-pool-search-settings - Locator: Settings table and source-permission section - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:mcp MCP Servers - Omnifact. Remote MCP has personal OAuth/shared static credentials, per-tool Always/Approval/Disable policies and private-network restrictions. - URL: https://docs.omnifact.ai/en/platform/team-administration/mcp-servers - Locator: Setup, policies, OAuth, approvals and privacy boundaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:memory Memory | MeinGPT Docs. Memory persists per user across enabled assistants; users can inspect/delete it and admins can disable the tool. - URL: https://meingpt.com/docs/platform/memory - Locator: How memory works, management and admin controls - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:preferences Präferenzen | MeinGPT Docs. Users can set persistent system instructions and a platform-language preference. - URL: https://meingpt.com/docs/platform/preferences - Locator: Chat settings and appearance - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:account Account Settings - Omnifact. English/German UI and persistent personal context/instructions are documented; personalization is unfiltered. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/user-profile-and-personalization - Locator: Language Preferences and Personalization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:roles Rollen & Zugriffsmodell | MeinGPT Docs. Admin, Member and Viewer roles differ in settings access and seat use; admins see all team-shared assets. - URL: https://meingpt.com/docs/admin-guide/roles-and-access-model - Locator: Role table, admin exception and support visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:permissions Berechtigungen | MeinGPT Docs. Support-enabled permissions control creation, sharing and app use per person or team. - URL: https://meingpt.com/docs/admin-guide/permissions - Locator: Availability, permissions table and app restrictions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:prompts Prompt-Bibliothek | MeinGPT Docs. Saved prompt folders have private, workspace or department visibility. - URL: https://meingpt.com/docs/platform/prompt-library - Locator: Core functions, visibility and sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:users User Management - Omnifact. User roles and Enterprise SSO/SCIM automate lifecycle while locking manual changes. - URL: https://docs.omnifact.ai/en/platform/team-administration/users - Locator: Roles, statuses, lifecycle and SSO/SCIM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:create Creating New Spaces - Omnifact. Users create custom Space agents with instructions and starter examples. - URL: https://docs.omnifact.ai/en/platform/core-features/spaces/creating-spaces - Locator: Space Starters and configuration - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:images Image Generation - Omnifact. Images are generated/edited from references and retained in an Assets gallery. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/image-generation - Locator: Generation, reference images and gallery - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:web Web Search and Browsing - Omnifact. Web search displays citations and blocks queries with masked sensitive values. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/web-search-browsing - Locator: Search, privacy and limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:web Websuche | MeinGPT Docs. Linkup powers chat search and a multi-step Deep Research app with cited sources. - URL: https://meingpt.com/docs/platform/web-search - Locator: Three routes, query creation, Linkup and research app - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:workflows Workflows erstellen und ausführen | MeinGPT Docs. Project workflows support multiple models, variables, documents and downloadable Office, PDF or JSON output. - URL: https://meingpt.com/docs/platform/workflows-create - Locator: Workflow editor and output format - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:scheduled Geplante Aufgaben | MeinGPT Docs. Scheduled tasks are support-enabled beta with schedule, webhook and email triggers under the creator account. - URL: https://meingpt.com/docs/platform/scheduled-tasks - Locator: Beta availability, triggers and execution account - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:n8n-nodes-omnifact-rev2 n8n-nodes-omnifact pinned README. n8n-nodes-omnifact documents n8n community nodes for Gateway/chat/documents. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/README.md - Locator: Pinned README.md documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### meingpt:meingpt:tools Tool-Zugriffsrichtlinien | MeinGPT Docs. Tool methods are intersected across admin and assistant policies; there is no interactive per-action permission dialog. - URL: https://meingpt.com/docs/admin-guide/tool-access-policy - Locator: Security warning and four enforcement layers - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:api-chat Published Spaces Chat API - Omnifact. Published chat provides JSON/SSE and optional inline sources/agentic workflow headers. - URL: https://docs.omnifact.ai/en/api-reference/published-space-chat - Locator: Headers, responses and SSE events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:stop Stopping and Regenerating Responses - Omnifact. Send changes to a Stop button during response generation. - URL: https://docs.omnifact.ai/en/platform/core-features/chats/stopping-regenerating-responses - Locator: How to Stop - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:audit Compliance Controls | MeinGPT Docs. Administrative settings logs exclude chat contents and are retained indefinitely; Governance Outpost search records are retained 90 days. - URL: https://meingpt.com/docs/admin-guide/compliance-controls - Locator: Core controls and Outpost search log - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:outlook Outlook Add-in | MeinGPT Docs. The Outlook add-in requires Enterprise API enablement and a personal API key and works in the received-mail reading view. - URL: https://meingpt.com/docs/integrations/connectors/outlook-addin - Locator: Prerequisites, supported clients and central deployment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:developer Developer Tools - Omnifact. API enablement is gated and organization key regeneration/revocation is centralized. - URL: https://docs.omnifact.ai/en/platform/team-administration/developer-tools - Locator: Activation and API key management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:api-docs Documents API - Omnifact. Document APIs upload/list/inspect/update/delete Space files asynchronously. - URL: https://docs.omnifact.ai/en/api-reference/documents - Locator: Endpoints and schema examples - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:terms Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination. - URL: https://meingpt.com/agb - Locator: Sections 1a, 2, 3, 5 and final provisions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:home AI for the Public Sector & Regulated Industries – Omnifact. Platform offers governed multi-model chat, Spaces, Privacy Filter and private deployment. - URL: https://omnifact.ai/ - Locator: Product, governance and deployment overview - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:images Bilder Generieren | MeinGPT Docs. The image app supports FLUX, GPT Image and Gemini image models with reference images and downloadable files. - URL: https://meingpt.com/docs/platform/image-generator - Locator: Model list, references and output management - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:image-admin Bildmodelle verwalten | MeinGPT Docs. Admins enable image models and set a default; the table distinguishes manufacturer, host and EU/global processing. - URL: https://meingpt.com/docs/admin-guide/image-models - Locator: Image-model controls and complete table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:privacy Data Privacy - Omnifact. Filter defaults on but MCP, code, image/audio paths bypass it; code sandbox has internet egress. - URL: https://docs.omnifact.ai/en/platform/team-administration/data-privacy - Locator: Privacy Filter Control and boundaries - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:meeting Meetings | MeinGPT Docs. Recordings and transcripts become searchable meeting notes; Hetzner, Gladia and Vertex EU form the processing path. - URL: https://meingpt.com/docs/platform/meetings - Locator: Formats/limits, data flow and prices - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:prices prices. The public calculator uses marginal seat tiers plus model consumption and optional Governance and Outpost fees. - URL: https://meingpt.com/preise - Locator: Annual price tiers, included functions, add-ons and model-cost sections - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:sso Access & Login Security | MeinGPT Docs. OIDC, Google and Microsoft login, verified domains and additive Entra group synchronization are documented; SAML is explicitly excluded. - URL: https://meingpt.com/docs/admin-guide/access-and-login-security - Locator: Own identity provider, authentication methods and Entra synchronization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:sso-blog Single Sign-On (SSO) for Enterprise Authentication – Omnifact. Enterprise SAML2.0 supports optional SCIM, Id P policies and disabled email sign-in. - URL: https://omnifact.ai/blog/feature-drop-introducing-sso - Locator: Setup, benefits and changes - Evidence kind: documented - Source date: 2024-11-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:public-sector GDPR-Compliant AI for Public Administration – Omnifact. Public-sector page names Entra/Okta/Keycloak and Germany/municipal on-premise options. - URL: https://omnifact.ai/solutions/public-administration - Locator: SSO, deployment and onboarding - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:auth Authentication - Omnifact. TOTP, recovery codes and account/IP-specific throttling are described. - URL: https://docs.omnifact.ai/en/platform/core-features/account-settings/authentication - Locator: 2FA setup and failure handling - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:security-rev2 Security and Access - Omnifact. SSO/SAML users rely on identity-provider authentication and MFA and do not see native2FA setup. This does not establish nativeTOTP inclusion in a plan. - URL: https://docs.omnifact.ai/en/platform/team-administration/security-and-access - Locator: SSO/SAML identity-provider authentication; native2FA tier not established - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:scim Entra ID SCIM-Provisionierung | MeinGPT Docs. SCIM v1 provisions users only; deactivated accounts retain data and release their seat. - URL: https://meingpt.com/docs/admin-guide/entra-scim-provisioning - Locator: SCIM versus SSO, prerequisites, effects and seat assignment - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:analytics KI-Cockpit | MeinGPT Docs. Adoption and cost reports include user, model, API/platform and team breakdowns with CSV and ID-based anonymization. - URL: https://meingpt.com/docs/admin-guide/ai-cockpit - Locator: Typical metrics, user/team costs and knowledge search - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:analytics-rev2 Analytics - Omnifact. Enterprise dashboard presents daily active users and messages with date ranges and toggles; export and additional breakdowns are not established. - URL: https://docs.omnifact.ai/en/platform/team-administration/team-analytics - Locator: Analytics heading, date-range selector, summary cards, activity chart; HTTP200 re-read2026-10-21 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:audit-export Änderungsprotokoll exportieren | MeinGPT Docs. Admins export filtered administrative changes as CSV or JSON, capped at 10000 entries, 20 MiB and two minutes. - URL: https://meingpt.com/docs/admin-guide/admin-settings-map - Locator: Export procedure, fields and limits - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:company Company Profile - Omnifact. Company description and business context shape AI responses. - URL: https://docs.omnifact.ai/en/platform/team-administration/company-profile - Locator: Team Description and company identity - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:dpa-page Auftragsverarbeitungsvertrag | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. DPA 2.0.1 dated 24 September 2026 needs signature or recorded electronic acceptance; existing customers retain their agreed version. - URL: https://meingpt.com/avv - Locator: Version and effectiveness - Evidence kind: documented - Source date: 2026-09-24 - Retrieved: 2026-10-21 ### meingpt:meingpt:dpa MeinGPT DPA 2.0.1. The signed-form DPA prohibits training, lists conditional subprocessors, defines authority-request handling and requires return or deletion within 30 days. - URL: https://meingpt.com/legal/avv/v2.0.1.pdf - Locator: Version 2.0.1; sections 4, 5(5), 7, 9, 12, 13 and Annexes 3/4, pages 3-12 - Evidence kind: documented - Source date: 2026-09-24 - Retrieved: 2026-10-21 ### omnifact:omnifact:vertex EU Data Residency for Claude and Gemini via Google Cloud – Omnifact. Google/Anthropic EU via Google Cloud are advertised with zero retention and EU-only configuration. - URL: https://omnifact.ai/blog/feature-drop-eu-data-residency-vertex-ai - Locator: What is new, compliance and EU model configuration - Evidence kind: vendor-claimed - Source date: 2026-04-01 - Retrieved: 2026-10-21 ### omnifact:omnifact:trust-rev2 https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public register lists Azure DE/NL/SE/IE infrastructure and Cloudflare EU/US edge metadata, plus model-provider routes; it is not a plan-specific processor/data-flow inventory. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: Public JSON subprocessors, lastUpdatedAt; infrastructure/metadata roles distinguished - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:gateway-web AI Gateway: One API for Every Model – Omnifact. Gateway consumes organization budget, does not store payloads and requires ZDR-capable models for strict retention. - URL: https://omnifact.ai/ai-gateway - Locator: Regional routing, budget and governance - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:privacy-intro Why Data Privacy Matters - Omnifact. Vendor explicitly excludes training its own models on customer data and distinguishes EU/self-hosted routes. - URL: https://docs.omnifact.ai/en/platform/core-features/privacy-security/introduction - Locator: Privacy Commitment and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:security Sind meine Daten sicher? | MeinGPT Docs. Security documentation states TLS 1.3, AES-256, customer-managed keys on request, and no bulk chat/file export. - URL: https://meingpt.com/docs/privacy-security/faq-data-security - Locator: Technical security, deletion and data portability - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:imprint Legal Notice – Omnifact. Omnifact Gmb H is registered in Frankfurt, Germany, HRB131357. - URL: https://omnifact.ai/legal-notice - Locator: Company address and register - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:dpa-de Auftragsverarbeitungsvertrag – Omnifact. Binding German DPA confirms region, transfer, retention and processor terms. - URL: https://omnifact.ai/de/dpa - Locator: Anlagen and main agreement - Evidence kind: documented - Source date: 2026-04-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:whitepapers Get Instant Access to our Full Enterprise Whitepaper – Omnifact. Public library includes AI Act, workplace enablement, self-hosting and RAG guides. - URL: https://omnifact.ai/whitepapers - Locator: Whitepaper catalogue - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:trust Sicherheitsnachweise & Trust Center | MeinGPT. ISO 27001 and a 2025 SySS penetration-test certificate are listed behind email-gated access. - URL: https://meingpt.com/sicherheit/nachweise - Locator: Certificates, assessments and document access - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### omnifact:omnifact:trust https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust. Public Trust Center JSON exposes certificate access and named processor locations, including US direct model routes and Cloudflare telemetry. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust - Locator: documents, subprocessors and lastUpdatedAt - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### omnifact:omnifact:iso Omnifact GmbH ISO/IEC27001:2022 official certificate. Certificate123228 issue1 from Prescient Security LLC covers Omnifact Platform/Spaces and Azure ISMS; valid2026-04-07 through 2029-04-06 subject to surveillance. - URL: https://api.oneleet.com/api/v1/tenants/trust.omnifact.ai/trust/documents/bb9dd08f-c61a-48f3-be41-9fbcdf24e9c3/download-url - Locator: Public Trust Center certificate PDF, one page: scope, issuer, issue date and validity - Evidence kind: certificate-verified - Source date: 2026-04-07 - Retrieved: 2026-10-21 - Issuer: Prescient Security LLC - Certificate scope: ISMS supporting Omnifact GmbH, Omnifact Platform and Spaces, associated data, infrastructure, software, personnel and procedures, including Microsoft Azure; SoA1.4 dated2026-03-30. - Valid: 2026-04-07 to 2029-04-06 - Registry: https://trust.omnifact.ai/ ### meingpt:meingpt:prices-rev2 Preise für Plattform, Add-ons und KI-Nutzung | MeinGPT. The contracted platform is offered with optional Governance and Outpost modules; local files are Early Access and local MCP/PostgreSQL Private Beta. The price calculator requires a binding individual offer. - URL: https://meingpt.com/preise - Locator: Feature table: Outpost release states; Governance separate agreement; calculator explicitly nonbinding - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:secrecy-contract-rev2 meinGPT terms: professional secrecy. Section12(4) itself imposes indefinite professional secrecy and text-form staff/subcontractor obligations when covered data are processed; it does not state a Governance prerequisite. A separate addendum is outside the verified base-terms finding. - URL: https://meingpt.com/agb - Locator: Section12(4), conditional duties for professional-secret data; no Governance prerequisite stated - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:billing-rev2 Abrechnung verwalten | MeinGPT Docs. Self-service Business is EUR29 per user/month excluding VAT, billed monthly, with unlimited standard-model use; premium/reasoning, API and meeting-bot use are separately metered. - URL: https://meingpt.com/docs/admin-guide/billing - Locator: Workspace types; Business upgrade card; standard-model inclusion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:ecb-fx ECB historical euro reference rates, 20 October 2026. ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF currency entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### omnifact:omnifact:ecb-fx ECB historical euro reference rates, 20 October 2026. ECB2026-10-20 reference rates:EUR1=USD1.1215=CHF0.9237, implying USD1=EUR0.89166206. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF currency entries - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### meingpt:meingpt:billing Abrechnung verwalten | MeinGPT Docs. A separate Business offer includes standard models; the trial lasts 10 days with EUR 5 credit and no payment details. - URL: https://meingpt.com/docs/admin-guide/billing - Locator: Workspace types, trial differences and Business upgrade - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:terms-20261026 Allgemeine Geschäftsbedingungen | MeinGPT | KI-Use-Case-Plattform für den Mittelstand. German commercial terms distinguish SaaS from contract-agreed on-premise deployment and describe subscriptions, export and termination. - URL: https://meingpt.com/agb - Locator: Sections 1a, 2, 3, 5 and final provisions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### omnifact:omnifact:widget-rev2 omnifact-widget pinned README. omnifact-widget documents an unsupported demonstration web component with local Storage conversations. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/README.md - Locator: Pinned README.md documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:cli-licence-rev2 omnifact-cli MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/LICENSE - Locator: Pinned LICENSE documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### omnifact:omnifact:widget-licence-rev2 omnifact-widget MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-widget/blob/9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2/LICENSE - Locator: Pinned LICENSE documentation at commit 9d53cadfbfe1bd9a0e31b7da49b74a1dfc2626f2; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-02-06 - Retrieved: 2026-10-21 ### omnifact:omnifact:n8n-nodes-omnifact-licence-rev2 n8n-nodes-omnifact MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/n8n-nodes-omnifact/blob/7a3947c620206d4e195064421db525aaa4dfb50a/LICENSE - Locator: Pinned LICENSE documentation at commit 7a3947c620206d4e195064421db525aaa4dfb50a; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-09-10 - Retrieved: 2026-10-21 ### omnifact:omnifact:xwiki-sync-licence-rev2 omnifact-xwiki-sync MIT licence. MIT licence applies to this integration/client component, not to the Omnifact platform. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-xwiki-sync/blob/599db2ec0c7f28ddb2a22c4a09a9242e5781316b/LICENSE - Locator: Pinned LICENSE documentation at commit 599db2ec0c7f28ddb2a22c4a09a9242e5781316b; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-08-25 - Retrieved: 2026-10-21 ### omnifact:omnifact:cli-rev2 omnifact-cli pinned README. omnifact-cli documents document management and conversational CLI commands. This finding is documented at the pinned revision; no implementation behavior was tested or inspected. - URL: https://github.com/OmnifactAI/omnifact-cli/blob/576aea6a6c0ce195de08a1d2b9b385d18efe3d06/README.md - Locator: Pinned README.md documentation at commit 576aea6a6c0ce195de08a1d2b9b385d18efe3d06; retrieved with GitHub file connector - Evidence kind: documented - Source date: 2026-05-12 - Retrieved: 2026-10-21 ### meingpt:meingpt:status status. A public service-status page exposes incident history. - URL: https://status.meingpt.com/ - Locator: Platform component and incidents - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### meingpt:meingpt:academy Lernen & Entdecken | MeinGPT Docs. The learning area includes guided learning paths and business use cases. - URL: https://meingpt.com/docs/platform/academy - Locator: Learning area content and personalization - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21