Omnifact vs T3 Chat

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Paid-account vendor replies establish manual model switching and provider routes, while the current plan-specific catalogue is unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 vendor-support context; no Free or Premier catalogue parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• providers Which model providers are available? [partial]: Pro-context vendor replies discuss Gemini, Claude and GPT routes; the FAQ separately describes OpenAI/Anthropic/Google/OpenRouter data handling. Those policy/provider names are not a complete tier-entitlement or underlying-lab catalogue. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls.
• current_models Which current models are selectable on this plan? [unknown]: A complete current selectable-model list for Pro, Free or Premier is unverified. The FAQ claude-4.6-sonnet URL is an example, and undated support model names are not a current plan catalogue.
• user_choice Can users pick the model per chat? [partial]: In the USD8 context discussion the vendor recommends manually switching to Gemini Flash or summarizing into a new chat with another chosen model. This supports Pro model selection as described there, but not a current all-model, effort or Free/Premier entitlement matrix. Sources: t3-chat:t3-chat:r2-pro-context-byok.
• 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? The public T3 FAQ, Terms, Privacy/Security policies, official feedback statuses and identifiable vendor replies did not establish this detail. No authenticated account, enterprise quote or bounded fixture was used.
• multimodal_input Which models accept images, audio or files? [unknown]: No current Pro model-by-model image/audio/file compatibility matrix was retrieved. The generic privacy upload categories do not establish a plan entitlement.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:faq-training, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Public feature-release information is described; plan-specific pinning and version guarantees remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Public T3 Chat release information; no verified Free/Pro/Premier picker/pinning entitlement; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• 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? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
• changelog Is there a dated public model changelog? [partial]: A vendor reply says major-feature changelog lives in Discord and a website version is planned. No accessible dated model-by-model release ledger was retrieved. Sources: t3-chat:t3-chat:changelog.
• deprecation_notice How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? No matched dates for the last three provider releases, fixed removal notice or contractual model-version retention was retrieved.
• version_pinning Can an admin keep an older model version? [unknown]: The vendor describes pinning and a Legacy designation in the general picker discussion, without a named individual tier. Plan-specific pinning, retained model versions and admin locks remain unverified.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:changelog.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Vendor replies support a Pro own-OpenRouter-key route, without establishing universal provider/model coverage.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 with optional customer OpenRouter key; no Free BYOK entitlement asserted; add_ons=Customer-paid OpenRouter/provider usage; model routing and verification prerequisites apply; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• own_api_keys Can the customer use its own provider API keys? [supported]: In the paid USD8 usage discussion, staff explicitly offers a customer OpenRouter key for direct request billing; the USD8 context discussion describes OpenRouter fallback. No all-provider/all-model BYOK entitlement follows. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.
• own_cloud_contract Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [unknown]: Can it use its own Azure OpenAI, Bedrock or Vertex deployment? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
• custom_endpoint Can an admin add any OpenAI-compatible endpoint? [unknown]: Can an admin add any OpenAI-compatible endpoint? No supported customer Azure OpenAI/Bedrock/Vertex setup or arbitrary OpenAI-compatible/custom endpoint configuration was retrieved.
• byo_pricing Does BYO change the licence price? [partial]: The paid subscription and direct-provider charges are separate in the vendor discussion. A discounted BYOK-only licence and exact customer provider rates are not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
• byo_restrictions Which features stop working with BYO? [unknown]: Current all-model BYOK compatibility is unknown: the OpenRouter-coverage request is marked Completed while the vendor says those model routes do not run through OpenRouter and rerouting requires future work. The old OpenAI GPT5 setup reply does not establish a complete current route matrix.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-pro-context-byok.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Individuals have cost-based refill limits; enterprise group governance is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 cost-limit discussion and Premier account bucket reply; Free excluded from this mechanics finding; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• model_allowlist_by_group Can admins limit models per group? [unknown]: Can admins limit models per group? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• data_bound_models Can admins restrict which models receive connector or knowledge content? [unknown]: Can admins restrict which models receive connector or knowledge content? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• default_model Can admins set the default model? [unknown]: Can admins set the default model? No organization/group model allowlists, data-bound model policy, administrator default model or fixed per-user token/message quota was established.
• user_limits What per-user message or token limits apply, and are they published? [supported]: Pro cost-limit replies and a Premier-specific vendor support reply tie paid usage to the FAQ Base/Overage mechanics: four-hour Base refill and monthly Overage refill. No fixed token/message allowance is published;20/200 example points are illustrative, not plan capacities. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
• limit_behaviour What happens when a limit is reached? [supported]: For these documented paid-account bucket routes, expected request cost is reserved then settled after completion; when both balances are exhausted the FAQ says to wait for refill. No Free-tier behaviour is inferred. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets, t3-chat:t3-chat:r2-paid-tier-controls.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Paid Pro context limits and own-key fallback are documented; plan-specific upload formats/caps remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 context restrictions and optional BYOK fallback; exact upload entitlement by tier unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• formats Which formats are accepted? [unknown]: The privacy policy mentions PDF/images/text and the request is Completed, but no current individual-tier format entitlement was verified. The earlier sentence attributing browser/file-specific PDF upload bugs to a vendor reply is withdrawn because no precise reply locator was reproduced.
• limits What size and count limits apply per file and chat? [partial]: Vendor replies distinguish context restrictions on USD8 Pro from higher-tier allowances and own-key fallback. They do not publish a complete current per-model file size/count or context-cap matrix; no32K or user-suggested MB cap is adopted. Sources: t3-chat:t3-chat:r2-pro-context-byok.
• ocr Are scanned PDFs read? [unknown]: Are scanned PDFs read? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
• spreadsheets Are Excel tables read with structure intact? [unknown]: Are Excel tables read with structure intact? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.
• full_vs_chunked Is the whole file used or only retrieved parts, and does the user see which? [unknown]: Is the whole file used or only retrieved parts, and does the user see which? No scanned-PDF OCR fixture, Excel structure/formula test, full-vs-chunked processing specification or current numerical upload matrix was retrieved. Community complaints and example sizes are not treated as product limits.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-pro-context-byok.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Paid Pro search is discussed by the vendor; image-tier entitlement, custom actions and MCP remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 for evidenced search use; image and MCP plan entitlement unknown; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• builtin_tools Which tools are built in? [partial]: The Pro/Premier pricing discussion explicitly describes frequent search and search-token overhead in the USD8 paid context. An OpenAI image integration has separate support evidence, but its plan entitlement is not verified and is not included as a Pro tool promise. Sources: t3-chat:t3-chat:r2-paid-tier-controls.
• custom_actions Can admins add API actions? [unknown]: Can admins add API actions? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• mcp_client Can it use remote MCP servers, and with what admin control? [unknown]: Can it use remote MCP servers, and with what admin control? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• tool_auth Do tools act as the user or as a shared account? [unknown]: Do tools act as the user or as a shared account? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.
• tool_approval Can admins approve or block tools, and can users confirm actions before they run? [unknown]: Can admins approve or block tools, and can users confirm actions before they run? The MCP request is Closed but has no retrieved released setup guide. Remote MCP configuration, custom API actions, user/shared tool credentials and administrator/user approval policies were not established.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Search is user-selectable, with a documented one-to-five search limit; a separate deep-research product is unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 paid-search discussion; no Free parity asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• web_search Is web search available? [partial]: Staff’s paid USD8 discussion confirms search consumes API/query and context costs. The FAQ exposes search on/off and1..5 URL limits, but a complete current tier-specific limit/feature matrix was not verified. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.
• admin_toggle Can admins disable it per organisation or group? [unknown]: Can admins disable it per organisation or group? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• search_provider Which search provider handles queries, and where? [unknown]: Which search provider handles queries, and where? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• deep_research Is multi-step research with a report available? [unknown]: Is multi-step research with a report available? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.
• web_citations Are web sources cited? [unknown]: Are web sources cited? No organization/group switch, named search provider and query country, dedicated multi-step research/report mode or precise web-citation contract was established. The FAQ says search improves recency without guaranteeing correctness.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:faq-url.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

No official programmable enterprise interface was established; subscription-backed external-agent API usage was rejected.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• chat_api Is there an API for chat and assistants? [partial]: An official feedback request asks to apply subscription quota to external coding agents/API; staff closes it because the economics do not work. The FAQ URL launches a browser chat and is not a documented chat API. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.
• knowledge_api Can documents be loaded through an API? [unknown]: Can documents be loaded through an API? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
• api_governance Do audit, budgets and model rules apply to API use? [unknown]: Do audit, budgets and model rules apply to API use? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.
• mcp_server Does the product expose itself to other agents over MCP? [unknown]: Does the product expose itself to other agents over MCP? No supported general chat/assistant API, document-ingestion API, API governance or MCP server exposure was retrieved. Third-party cookie/API clients and T3 Code repositories are not official T3 Chat API evidence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:api-request, t3-chat:t3-chat:faq-url.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

A browser client and iOS TestFlight beta are documented; desktop, Android release and managed clients remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application, T3 Chat iOS TestFlight beta; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Browser account plan; iOS TestFlight beta; enterprise SSO unverified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=iOS.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• web Is a full web client available? [supported]: T3 Chat is delivered as a browser service; the FAQ documents launching new conversations through public URLs. Sources: t3-chat:t3-chat:faq-url.
• desktop_apps Windows and macOS apps? [unknown]: Windows and macOS apps? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• mobile_apps iOS and Android apps with SSO? [partial]: The vendor’s September10,2026 announcement releases iOS via TestFlight explicitly as beta; Android beta is coming soon. Neither corporate SSO nor a production app-store release was verified. Sources: t3-chat:t3-chat:mobile.
• browser_extension Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• managed_deployment Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.
• client_feature_gaps Which features are missing on mobile? [unknown]: Which features are missing on mobile? No native Windows/macOS distribution, supported browser extension/sidebar, MDM configuration or complete mobile feature-gap matrix was established. Community extension links are not vendor clients.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-url, t3-chat:t3-chat:mobile.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

The security policy asserts MFA support without documenting enterprise SAML/OIDC administration.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• sso_protocols Which SSO protocols and identity providers work? [partial]: Security policy refers to OAuth provider accounts and standard authentication without naming enterprise SAML/OIDC protocols or supported corporate IdPs. Sources: t3-chat:t3-chat:security.
• sso_plan Which plan includes SSO? [unknown]: Which plan includes SSO? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
• mfa Can MFA be enforced? [partial]: The vendor asserts MFA support and recommends two-factor protection at the OAuth provider. Enforceable organization-wide MFA settings were not established. Sources: t3-chat:t3-chat:security.
• conditional_access Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.
• domain_capture Can the company claim its email domain? [unknown]: Can the company claim its email domain? No business-plan SSO entitlement, Entra conditional-access integration or email-domain capture policy was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:security.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Individual consumption indicators exist; organization budgets and chargeback remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Pro USD8 and Premier account consumption mechanics; no organization/admin budget offer asserted; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• cost_visibility Can admins see cost or consumption per user and group? [partial]: The paid Pro discussion and Premier support reply describe per-account cost/bucket consumption. The FAQ describes separate balance displays; exact placement and model-cost indicators are not a customer organization reporting entitlement. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.
• budgets Can budgets be set per user or group? [unknown]: Can budgets be set per user or group? No customer organization/user-group budget assignment or cost-centre export was retrieved.
• budget_enforcement Does reaching a budget alert, block or downgrade? [partial]: For the documented paid-account bucket routes, exhausting both balances requires waiting for refill. This does not establish configurable user/group currency budgets, alerts or downgrade policies. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-premier-buckets.
• chargeback Can costs be exported per cost centre? [unknown]: Can costs be exported per cost centre? No customer organization/user-group budget assignment or cost-centre export was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:r2-paid-tier-controls, t3-chat:t3-chat:r2-premier-buckets.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

The privacy policy describes vendor telemetry, not a customer compliance logging service.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• admin_events Are admin and security events logged? [unknown]: Are admin and security events logged? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• content_logging Can prompts and answers be retained for compliance, and is it configurable? [partial]: The privacy policy collects prompts/uploads and Terms reserve review/removal for violations. A configurable customer prompt/answer compliance archive was not established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• siem_export Can logs stream to a SIEM or be exported? [unknown]: Can logs stream to a SIEM or be exported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• ediscovery Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.
• log_retention How long are logs kept? [unknown]: How long are logs kept? No customer admin/security-event catalogue, SIEM stream/export, eDiscovery/legal hold or fixed log retention was retrieved. Vendor monitoring in the security policy is not evidence of customer audit access.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Acceptable-use terms apply, while organization policy controls remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• org_instructions Can admins set organisation-wide instructions? [unknown]: Can admins set organisation-wide instructions? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
• usage_notice Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.
• content_filters Are content filters configurable? [partial]: Terms prohibit categories of unlawful/harmful content and permit vendor review/removal or suspension. Customer configurable content filters are not established. Sources: t3-chat:t3-chat:terms.
• violation_reporting Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? No admin global-instruction policy, mandatory company policy acknowledgement, configurable deterministic filter or customer violation-hit reporting was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

The privacy policy places the service under US/international processing; no EU/Swiss end-to-end option was established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• storage_region Where are chats, files and indexes stored? [partial]: The policy says services are provided in the United States and information is processed there or in other countries; Azure, AWS and Vercel are named. Component-specific chat/file/index storage regions are not enumerated. Sources: t3-chat:t3-chat:privacy.
• inference_region Where do model calls run, per provider? [partial]: The policy names OpenAI, Google, Anthropic and OpenRouter processing, but no provider-by-provider region, EU-only switch or customer region guarantee is supplied. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.
• backups_logs_region Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• support_access_region From where can vendor staff access data? [unknown]: From where can vendor staff access data? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• swiss_hosting Is Swiss hosting available? [unknown]: Is Swiss hosting available? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.
• residency_plan Which plan or option provides residency? [unknown]: Which plan or option provides residency? No exact backup/log/telemetry country matrix, support-access location, Swiss hosting offer or residency-plan entitlement was retrieved.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:faq-training.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

A hosted web service is offered; tenant architecture and alternative deployment contracts remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• multi_tenant_saas Is a shared SaaS offered? [partial]: The public web service accepts individual accounts and processes content with hosting/model providers. Its exact multitenant architecture and boundaries are not documented in the retrieved public material. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.
• dedicated_instance Is a dedicated single-tenant instance offered, from what size? [unknown]: Is a dedicated single-tenant instance offered, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• 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? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• on_premise Can the whole platform run on customer infrastructure, from what size? [unknown]: Can the whole platform run on customer infrastructure, from what size? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• air_gapped Can it run without internet access? [unknown]: Can it run without internet access? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.
• mode_feature_gaps Which features are missing outside SaaS? [unknown]: Which features are missing outside SaaS? No vendor-operated dedicated tenant, customer-cloud/on-premise package, offline licence or deployment-specific feature matrix was retrieved. Independent T3 clones and the distinct T3 Code product do not establish a self-host licence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:privacy.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

No vendor training is asserted, with provider exceptions and customer-key responsibility explicitly retained.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• vendor_training Does the vendor train on customer content? [supported]: FAQ says T3 does not train its own models and the privacy policy says personal information is not used to train AI models. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.
• provider_training Do model providers train on it under this product's contracts? [supported]: The FAQ says OpenAI/Anthropic defaults are not opted into training, Google paid models disable training and OpenRouter training routes are disabled. Some new models may require training and are labeled; BYOK customers manage their own provider settings. Sources: t3-chat:t3-chat:faq-training.
• provider_retention How long do model providers keep prompts, including for abuse monitoring? [unknown]: How long do model providers keep prompts, including for abuse monitoring? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
• zero_retention Is zero data retention available, and on which plan? [unknown]: Is zero data retention available, and on which plan? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.
• human_review Can provider staff review content? [unknown]: Can provider staff review content? The FAQ does not establish provider prompt/abuse-monitoring retention, uniform ZDR entitlement or all provider human-review exceptions. No universal no-training/no-retention promise is inferred.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-training, t3-chat:t3-chat:privacy.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Termination export responsibilities are contractual; plan-specific temporary-chat behaviour and retention remain unknown.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual T3 Chat service Terms; temporary-chat Free/Pro/Premier entitlement not established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.
• No complete Free/Pro/Premier entitlement matrix or authenticated model/feature menu was retrieved.

• default_retention What is retained and for how long by default? [unknown]: The generic URL FAQ distinguishes temporary and persisted threads but does not map that feature to a named individual tier or specify server/provider/file/backup retention. No plan-specific temporary-chat retention claim is made.
• admin_retention Can admins set retention periods? [unknown]: Can admins set retention periods? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
• user_deletion Can users delete their chats and files permanently? [unknown]: Can users delete their chats and files permanently? No administrator retention controls, user permanent-deletion completion guarantee, backup erasure interval or fixed contract-end deletion deadline was retrieved.
• contract_end_deletion What is deleted at contract end, and when? [partial]: Terms put responsibility on users to export before termination and endeavor to provide a reasonable retrieval opportunity only for vendor-convenience termination; deletion timing and certificate are unspecified. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Named providers and a US vendor address are public, without a complete processor-country or transfer contract matrix.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• subprocessor_list Is a dated sub-processor list published? [partial]: The May31,2025 privacy policy names Azure, AWS, Vercel, OpenAI, Google, Anthropic and OpenRouter, explicitly non-exhaustively. This is not established as a complete Article28 subprocessor schedule. Sources: t3-chat:t3-chat:privacy.
• subprocessor_countries Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
• change_notification Are customers notified of sub-processor changes? [partial]: Privacy policy says material changes are posted with an updated effective date. A processor-addition notice period and objection right are not specified. Sources: t3-chat:t3-chat:privacy.
• parent_jurisdiction Which jurisdiction governs the vendor and its parent? [partial]: The policy and Terms identify T3 Tools Inc with a San Francisco address and US/California legal context. A separate parent entity, incorporation jurisdiction and ownership were not independently established. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• transfer_mechanism Which transfer mechanism applies to non-EU/CH processing? [unknown]: Which transfer mechanism applies to non-EU/CH processing? No exhaustive processor operation-country matrix, signed SCC/Swiss transfer mechanism or subprocessor objection schedule was retrieved.
• government_access_policy Is there a published government-access or transparency policy? [partial]: The policy allows disclosures for subpoenas, warrants and legal investigations. No separate transparency report or detailed challenge/notification policy was retrieved. Sources: t3-chat:t3-chat:privacy.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Public consumer/service terms use California law; an enterprise GDPR/Swiss DPA remains unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• dpa Is a DPA available, and is it negotiable? [unknown]: Is a DPA available, and is it negotiable? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• revdsg_gdpr Does the DPA cover revDSG and GDPR? [unknown]: Does the DPA cover revDSG and GDPR? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• governing_law Which law and court govern the contract? [supported]: Terms section19 uses California law and individual JAMS arbitration in Santa Clara County, with small-claims/injunction exceptions and state/federal Santa Clara courts where arbitration does not apply. Sources: t3-chat:t3-chat:terms.
• ai_act_materials Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.
• sector_materials Are FINMA or other sector materials provided? [unknown]: Are FINMA or other sector materials provided? No public negotiable Article28 DPA, explicit revDSG/GDPR processor undertaking, EU AI Act pack or FINMA/sector material was retrieved. The guessed/dpa route did not expose readable content; that is an access gap, not proof of absence.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

Omnifact

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.

T3 Chat

Agent cross-checked Support: partial

Public policies describe vendor/provider content processing, but professional-secrecy contracts and a business plan remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual account service; no business/professional-secrecy offer verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US/international policy; no DE/CH-specific arrangement verified; os=not specified.

Limitations

• No-training statements and personal account terms are not a professional-secrecy undertaking.
• No legal suitability or compliance conclusion.

• secrecy_undertaking Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public DPA or signed/signon §203 StGB/Art321 StGB professional-secrecy undertaking covering T3 staff was retrieved from the Terms, privacy/security policies or targeted first-party searches.
• subprocessor_coverage Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy names hosting/model services but does not establish a dedicated professional-secrecy undertaking binding them. Its existence and flow-down are unknown.
• secrecy_offering Is it a dedicated offering or add-on, and on which plan? [unknown]: A team/business offer itself remains unverified; no professional-secrecy-specific tier, dedicated package or paid add-on was established.
• content_access Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: Privacy policy sends input to selected OpenAI/Google/Anthropic/OpenRouter services; Terms reserve vendor review/removal of content upon apparent violations. This establishes processing/review possibilities, not an exhaustive plaintext staff/provider access matrix or protected-profession arrangement. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.
• secrecy_documentation Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Public consumer/service Terms and privacy/security pages were reviewed, with targeted §203/Art321/professional-secrecy searches. No specific template, protected-profession data-flow statement or professional-body guidance was retrieved; no private agreement was requested.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:privacy, t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Individual subscription prices are supported by vendor replies; quotas are cost-based and checkout/organization details are incomplete.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Staff pricing replies are first-party but undated; current checkout amounts and tax/plan availability were not observed.

• pricing_unit What is the pricing unit? [supported]: Evidence describes monthly individual Pro/Premier subscriptions, optional customer provider keys and cost-based included use. No organizational seat/pool contract is established. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage.
• list_prices What are list prices per plan, with date and currency? [partial]: Vendor replies confirm USD8/month paid-tier context and Premier USD50/month plus applicable tax. No checkout was completed and no business price was retrieved; dates of the undated replies are unknown. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility.
• included_usage What usage is included? [supported]: Included usage is represented by Base and Overage balances, refilling four-hourly/monthly. The FAQ’s20/200 example is not the actual plan quota and the former1500+100 message claim is not used. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:billing-change.
• add_ons Which features cost extra? [partial]: Customer OpenRouter/OpenAI API keys incur direct provider charges. Staff says a top-up product has not been offered since the new billing model and options are only being considered. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai.
• overage What do usage beyond limits and premium models cost? [partial]: The Overage bucket is a monthly included-usage bucket, not an established published dollar-per-token overage tariff. Extra usage via own keys is billed by the customer provider; current model/route tariffs are not fully mapped. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:premier.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:overage, t3-chat:t3-chat:byok-openai.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Multiplying individual list prices yields conditional licence floors, not a verified organization quote or usage-complete TCO.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Conditional independent Pro/Premier account multiplication; no organization plan verified; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Known price floor + unknown components; no complete year-one TCO, seat commitment or sufficient-usage guarantee.

• cost_200 Year-one cost at 200 users? [partial]: ALM-14 shared cost assumptions v1.4,2026-10-21:12 months,list prices,exVAT,no negotiated discounts;60% light100/30% regular400/10% power1500 messages/user/month =>330,each3000 input+600 output tokens incl retrieval. Vendor subscription usage remains subject to cost/refill limits; no fixed default/recommended model or complete tariff is published, so coverage and variable extra cost stay unknown. ECB2026-10-20 EUR1=USD1.1215=CHF0.9237; divideUSD by1.1215 then multiplyEUR by0.9237. For200 separate accounts: Pro from USD19,200/EUR17,119.93/CHF15,813.68 + unknown; Premier reference USD120,000/EUR106,999.55/CHF98,835.49 + unknown. Bulk purchase and business-governance fit unverified. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• cost_1000 Year-one cost at 1,000 users? [partial]: Same assumptions,1000 separate accounts: Pro from USD96,000/EUR85,599.64/CHF79,068.39 + unknown; Premier reference USD600,000/EUR534,997.77/CHF494,177.44 + unknown. Not a1000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• cost_5000 Year-one cost at 5,000 users? [partial]: Same assumptions,5000 separate accounts: Pro from USD480,000/EUR427,998.22/CHF395,341.95 + unknown; Premier reference USD3,000,000/EUR2,674,988.85/CHF2,470,887.20 + unknown. Not a5000-seat quote. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx.
• variable_share Which part depends on usage? [partial]: Included usage consumes a cost meter with no complete published tariff/default model. For an optional direct-provider BYOK comparison only, the shared gpt-6-luna effort-none Standard proxy is USD0.10 input/USD0.50 output per1M and USD2.376/user/year at the shared mix, excluding cache/tools/embeddings/regional uplift. This exact model/route is not verified selectable in T3 and is not added to the subscription floor as though it were a vendor tariff. Sources: t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model.
• unknown_parts Which costs could not be priced? [supported]: Unpriced: enterprise/bulk entitlement, organization features, exact current checkout prices, model availability and complete token/search/file tariff, whether the shared workload fits refill quotas, direct-provider/OpenRouter route charges, regional processing and support/implementation. No assumed wholesale discount or model-cost subsidy. Sources: t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:byok-router.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:billing-change, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage, t3-chat:t3-chat:fx, t3-chat:t3-chat:openai-price, t3-chat:t3-chat:openai-model, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:byok-router.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Free usage is in the Terms; a business-specific trial and enterprise evaluation path remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• free_tier Is there a free tier for business use? [partial]: Terms say services are free up to unspecified usage limits and paid resources may be required. Organizational acceptance is allowed, but no free business admin entitlement is established. Sources: t3-chat:t3-chat:terms.
• self_serve_trial Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
• trial_scope Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? No timed self-serve business trial, SSO/connector/admin trial entitlement or enterprise evaluation agreement was retrieved. No account was created.
• sales_gate Does meaningful evaluation require sales contact? [partial]: A public browser service and free-limited offer are documented; business-specific meaningful evaluation and any sales gate cannot be determined without an established business offer. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Individual monthly upgrades/downgrades are documented; business minimums and European invoicing remain unverified.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• minimum_commitment What seat or spend minimum applies? [partial]: The public evidence concerns individual accounts and monthly prices, not a minimum team-seat/spend commitment. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
• contract_length What contract lengths are offered? [supported]: Vendor replies confirm monthly Premier pricing and billing periods; no signed annual or business-term offer was retrieved. Sources: t3-chat:t3-chat:premier.
• cancellation How can the contract be cancelled or reduced? [supported]: Terms permit account cancellation at any time without refunds. Staff says upgrades take effect immediately and downgrades at the billing-period end. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier.
• local_invoicing Can it be invoiced in CHF or EUR from a European entity? [unknown]: Can it be invoiced in CHF or EUR from a European entity? No team minimum, European contracting entity or CHF/EUR invoice entitlement was retrieved.
• transparency_class Is pricing transparent, partial, quote-only or unknown? [supported]: Partial: some individual prices are confirmed in undated staff replies, complete final checkout requires billing information, quotas are not a public token tariff, and a business offer remains unverified. Sources: t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:premier, t3-chat:t3-chat:faq-usage.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms, t3-chat:t3-chat:premier, t3-chat:t3-chat:price-visibility, t3-chat:t3-chat:faq-usage.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

The hosted service is proprietary; clone hackathons and T3 Code are separate products.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• licence_type Which licence applies to each component? [supported]: Terms grant a personal nonassignable service licence and prohibit copying, modification, reverse engineering and source extraction, subject to third-party software rights. Sources: t3-chat:t3-chat:terms.
• branding_restrictions Do licence terms restrict branding or user counts? [supported]: Terms reserve vendor trademarks and prohibit sublicensing/renting/providing service access to others; each account is personal and cannot be shared. Sources: t3-chat:t3-chat:terms.
• enterprise_features_closed Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? No supported self-host licence, open-source core/enterprise split or enterprise edition licence was retrieved. Public third-party clones are not licensed distributions of the hosted product.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Terms require pre-termination export, but a documented organizational export package was not established.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• chat_export Can admins export all chats? [unknown]: Can admins export all chats? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• assistant_export Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• knowledge_export Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• export_format Are formats documented and machine-readable? [unknown]: Are formats documented and machine-readable? No first-party complete-admin-chat export procedure/format, reusable assistant/prompt export or KB/source export was retrieved. Community migration scripts and export comments are leads, not supported portability guarantees.
• post_termination_window How long can data be retrieved after termination? [partial]: Users must export before termination. If the vendor terminates for convenience it will endeavor to allow a reasonable retrieval opportunity; no fixed post-termination window is guaranteed. Sources: t3-chat:t3-chat:terms.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:terms.

Omnifact

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.

T3 Chat

Agent cross-checked Support: partial

Email support and official feedback are public, without a retrieved SLA or regional-language contract.

Availability: generally-available · Delivery: native
Scope: surfaces=T3 Chat browser application; version=Public FAQ, legal pages and vendor replies retrieved 2026-10-21; no authenticated deployment observed; plan=Individual Free, Pro and Premier evidence; no organizational plan or entitlement established; add_ons=Optional customer API keys; plan-specific quotas and checkout details not fully public; deployment_mode=not specified; region=US-hosted service with provider processing in US or other countries; no EU/CH-only option established; os=not specified.

Limitations

• Documented findings only; unestablished atomic questions remain explicit gaps.

• support_channels Which support channels are available on each plan? [supported]: The FAQ lists a support email and official feature/bug board; plan-specific response targets are not published there. Sources: t3-chat:t3-chat:faq-support.
• support_languages Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
• regional_presence Is there a DACH or Swiss entity, team or partner? [partial]: The vendor publishes a San Francisco contact address. A DACH/Swiss entity, partner or support team was not established. Sources: t3-chat:t3-chat:privacy.
• uptime_sla Is there an uptime SLA with credits? [unknown]: Is there an uptime SLA with credits? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.
• status_page Is there a public status page with history? [unknown]: Is there a public status page with history? No German/French/Italian support commitment, credit-bearing uptime SLA or verified public status/history service was retrieved. Guessed status.t3.chat failed certificate validation; no incident conclusion follows.

Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: t3-chat:t3-chat:faq-support, t3-chat:t3-chat:privacy.

Omnifact

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.

T3 Chat

No public information found Support: not-published

We found no public information on this. A missing finding is not evidence that the product lacks the capability.