--- schema_version: 1 rubric_version: "1.1" kind: pair canonical_url: "https://onaihq.com/compare/agents/dust-vs-unique-ai/" data_url: "https://onaihq.com/compare/agents/dust-vs-unique-ai/data.json" generated_at: 2026-10-27 last_checked_at: 2026-10-26 last_cross_checked_at: 2026-10-26 next_check_at: 2026-12-20 publisher: "onAI" --- # Dust vs Unique AI > Published by onAI. onAI also sells one of the products compared here. Findings about other products link to public sources so you can check them; statements about onAI are marked as stated by onAI. This comparison has 46 criteria with sourced findings for both products, including 46 that a second agent cross-checked for both. 51 criteria have a sourced finding for at least one product. "Sourced" findings passed publication validation: they are scoped, fresh and cite public resolved sources. "Agent cross-checked" findings also received a separate agent source pass, not necessarily a hands-on test. "Stated by onAI" marks the publisher's own statements about its product (evidence type vendor-statement), which cite no third-party source. Humans approve the rubric, templates and generator; they do not review every finding. It does not declare a winner. A missing sourced finding is not evidence that a capability is absent. - Dust source checks: 2026-10-21. - Unique AI source checks: 2026-10-21 to 2026-10-26. - Canonical HTML: https://onaihq.com/compare/agents/dust-vs-unique-ai/ - Machine-readable JSON: https://onaihq.com/compare/agents/dust-vs-unique-ai/data.json - Methodology: https://onaihq.com/compare/agents/methodology/ ## Models ### MOD-01: Model catalogue and providers Judgment rule: List each available model by provider and plan, including reasoning, fast and multimodal variants. Record whether the user picks the model, the product routes automatically, or both. A provider counts only if at least one of its current models is selectable on the scoped plan. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust offers per-message model choice and ordered auto-model lists, with access-tier and region controls. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit plan (Free/Pro/Max); Enterprise model access inherits the published catalogue; model-tier and EU eligibility separately constrained; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - The catalogue finding is restricted to named documentation entries; conflicting Gemini4 Argon EU eligibility is an explicit gap. - providers — Which model providers are available? [supported]: Docs list OpenAI, Anthropic, Google, Mistral and Fireworks-served models; exact enabled models depend on workspace and tier. Sources: dust:dust:models, dust:dust:eu-models. - current_models — Which current models are selectable on this plan? [partial]: The model-selection document lists GPT6.1 Sol, Claude Opus5.5/Sonnet5.5, Gemini3.8 Flash and Mistral models. Gemini4 Argon is excluded from this current-EU availability finding: its release note conflicts with the EU table, and the documented authoritative picker flag was not observed. No complete current tenant catalogue is claimed. Sources: dust:dust:models, dust:dust:changelog, dust:dust:eu-models, dust:dust:pricing. - user_choice — Can users pick the model per chat? [supported]: The composer chooses a model for the next message; Agent Builder sets a persistent agent default. Sources: dust:dust:models. - auto_routing — Does the product route between models automatically, and is the chosen model shown? [supported]: Basic/Standard/Premium use ordered candidate lists and availability fallback, not prompt-dependent task routing. A replacement indicator names the fallback during a detected outage. Sources: dust:dust:models. - multimodal_input — Which models accept images, audio or files? [partial]: Conversation files support images, documents and audio transcripts; the exact input capability for every current model is not fully tabulated. Sources: dust:dust:files. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:models, dust:dust:eu-models, dust:dust:changelog, dust:dust:pricing, dust:dust:files #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform catalogue supports several providers, subject to tenant credentials, contracts and validation status. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - providers — Which model providers are available? [partial]: Catalogue includes Azure OpenAI/OpenAI, Anthropic, Google Gemini/Vertex, Together AI and xAI. Provider use must be agreed with each client; a catalogue row is not proof every tenant has it. Sources: unique-ai:unique-ai:models. - current_models — Which current models are selectable on this plan? [partial]: Release 2026.42, hosted 14 October, explicitly adds Azure GPT-6.1 Sol and Claude Opus/Sonnet 5.5 through Anthropic/Vertex. Availability overview also lists Gemini3.8 Flash; provider/tenant credentials and validation differ. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:models. - user_choice — Can users pick the model per chat? [partial]: Space admins set enabled models; release notes describe chat model switching and API per-message model selection under the same rules. Conduct choices depend on administrator configuration. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - 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. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. - multimodal_input — Which models accept images, audio or files? [unknown]: Which models accept images, audio or files? Unknown. Exact contracted/activated models, automatic cross-model routing and a complete image/audio/file matrix were not established. Catalogue dates include future release identifiers; dated additions and tenant eligibility take precedence over a release number. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### MOD-02: Model freshness Judgment rule: Measure the days from a provider's general release to availability in the product for the last three major releases from OpenAI, Anthropic and Google (and Mistral where offered). Use dated changelogs or observation. Record deprecation notice for retired models. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public changelog and exact agent model selection are documented; release-lag and removal notice remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - 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? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - changelog — Is there a dated public model changelog? [supported]: The public changelog contains dated model releases including Gemini 4 Argon on October 14, 2026. Sources: dust:dust:changelog. - deprecation_notice — How much notice is given before a model is removed? [unknown]: How much notice is given before a model is removed? The dated changelog and model-selection docs were checked; last-three-release/provider lag measurements and a fixed advance deprecation-notice period were not established. - version_pinning — Can an admin keep an older model version? [partial]: An agent can select a specific model and keeps it until changed, subject to continued provider/workspace availability. No indefinite old-version entitlement is established. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog, dust:dust:models #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique publishes dated model additions and retirement/migration notes; a complete provider-release lag series remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - 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. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. - changelog — Is there a dated public model changelog? [supported]: Availability overview has a dated Recent changes table through 13 October 2026, with provider retirement sources. Sources: unique-ai:unique-ai:models. - deprecation_notice — How much notice is given before a model is removed? [partial]: Dated 14 October release announces migrations ahead of o-series provider retirement on 19 November 2026. No guaranteed Unique contractual notice period is established. Sources: unique-ai:unique-ai:release42. - version_pinning — Can an admin keep an older model version? [unknown]: Can an admin keep an older model version? Unknown. A provider-verified last-three-major-release lag series for OpenAI, Anthropic and Google was not assembled; availability can depend on each contract. Admin version-pinning guarantees are not documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:models, unique-ai:unique-ai:release42 ### MOD-03: Bring-your-own keys and provider contracts Judgment rule: Record customer-held API keys, customer cloud accounts (Azure OpenAI, Bedrock, Vertex), and aggregator routes (OpenRouter, LiteLLM) as separate routes. Record what still works without a vendor-provided model, whether prices change with BYO, and documented restrictions. API-key support does not imply support for the customer's own Azure contract. #### Dust Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Operators can configure customer model endpoints and credentials through GraphQL. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - own_api_keys — Can the customer use its own provider API keys? [supported]: ExternalLanguageModel accepts provider API credentials stored encrypted as immutable write-only values; OAuth2 is also documented. Sources: unique-ai:unique-ai:customllm. - own_cloud_contract — Can it use its own Azure OpenAI, Bedrock or Vertex deployment? [partial]: Custom Azure OpenAI deployment examples specify customer endpoint, deployment, API version and token. Compliance docs mention Bedrock; exact supported Bedrock/Vertex contract routes need deployment scoping. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance. - custom_endpoint — Can an admin add any OpenAI-compatible endpoint? [partial]: Documents self/cloud-hosted LXM endpoints and an Azure-compatible connection object. Universal support for any OpenAI-compatible endpoint is not guaranteed. Sources: unique-ai:unique-ai:customllm. - byo_pricing — Does BYO change the licence price? [unknown]: Does BYO change the licence price? Unknown. BYO licence discounts, provider-by-provider contract onboarding and a full tool/RAG/embedding parity matrix are not public. - byo_restrictions — Which features stop working with BYO? [partial]: Azure Chat Code Execution requires compatible Azure Responses models; switching a custom model group name/deleting an in-use group can break configured assistants. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:code. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code ### MOD-04: Local and self-hosted models Judgment rule: Record support for models running in the customer's environment (vLLM, Ollama, TGI or similar) and which features work with them: chat, RAG, tools, embeddings. Distinguish a documented, supported route from a generic endpoint that happens to work. #### Dust Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The platform documents custom model and embedding connections. Tool parity depends on the selected route: Code Execution lists Azure and LiteLLM OpenAI compatibility, while arbitrary self-hosted model parity is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform; custom-model/embedding connectors and optional Code Execution availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Code Execution has a listed Responses-capability/model matrix, not universal support for every custom-hosted model. Azure sandbox controls are not extended to every LiteLLM route. - No customer runtime or feature-parity fixture was used; QA-only Phoeniqs is not presented as GA. - self_hosted_chat — Can chat use a customer-hosted model? [supported]: Custom LXM and on-premises architecture allow customer-hosted model connections. Models, endpoint compatibility and enabled modules are selected for the contracted deployment. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity. - self_hosted_embeddings — Can retrieval use customer-hosted embeddings? [partial]: An instance maintainer can configure embedding endpoint, key and deployment; the operator overview allows self-hosted embeddings. Supported non-Azure runtimes and a particular customer configuration were not verified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators. - feature_parity — Which features fail with self-hosted models? [partial]: Changing embeddings requires re-embedding existing files. The Code Execution compatibility section explicitly lists Azure Responses-capable IDs and LiteLLM OpenAI IDs, so no blanket Azure-only restriction is asserted. Its introduction/security section describes an Azure sandbox; the actual LiteLLM execution route and parity for arbitrary self-hosted models remain unverified. Sources: unique-ai:unique-ai:embeddings, unique-ai:unique-ai:review2-code. - vendor_hosted_open_models — Does the vendor host open-weight models in EU/CH? [partial]: The model catalogue describes Swiss Phoeniqs open models in QA only, not the UAT01/Prod offer. Production entitlement to a vendor-hosted Swiss open model was not established. Sources: unique-ai:unique-ai:review2-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:customllm, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:embeddings, unique-ai:unique-ai:operators, unique-ai:unique-ai:review2-code, unique-ai:unique-ai:review2-models ### MOD-05: Model control and usage limits Judgment rule: Record admin allow-lists per group, default models, restrictions on which models may see which data, and per-user rate or fair-use limits. Test one restriction with two users in different groups. Record limits as enforced stops, warnings or undocumented fair use. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins cap models by workspace, group and member, with explicit published-agent exceptions and credit limits. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No two-user enforcement test. Published agents can run above member tiers if the separate admin setting permits it. - model_allowlist_by_group — Can admins limit models per group? [supported]: Model access ceilings apply to the workspace, groups or individuals and cover reasoning efforts as well as auto selections. Sources: dust:dust:tiers. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: EU-only mode restricts all active agents and pickers to EU-hosted models. Spaces bound knowledge and agent access; arbitrary per-data-class model rules were not established. Sources: dust:dust:eu-models, dust:dust:spaces. - default_model — Can admins set the default model? [supported]: Builders configure an agent default, which may be exact or Basic/Standard/Premium. Composer changes do not edit it for others. Sources: dust:dust:models. - user_limits — What per-user message or token limits apply, and are they published? [supported]: Free seats have 500 lifetime credits, Pro 8,000/month and Max 40,000/month, plus applicable shared-pool rules and member spend limits. Sources: dust:dust:credits, dust:dust:credit-management. - limit_behaviour — What happens when a limit is reached? [supported]: Members block when applicable sources/caps are exhausted. A message begun under a cap can finish above it; new messages then block. A separate root-task checkpoint can pause at 600 AWU. Sources: dust:dust:credit-management, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:tiers, dust:dust:eu-models, dust:dust:spaces, dust:dust:models, dust:dust:credits, dust:dust:credit-management #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Models and knowledge/tools are configured per access-controlled Space; optional beta daily spending caps block calls. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-group restriction fixture was run. Exact contract token/message limits, platform-wide model allow-lists and provider data-routing policy remain unverified. - model_allowlist_by_group — Can admins limit models per group? [partial]: Admins bind deployed/approved models to Spaces and grant people/groups space access. Direct per-group model lists across all chats are not documented. Sources: unique-ai:unique-ai:agent. - data_bound_models — Can admins restrict which models receive connector or knowledge content? [partial]: A Space binds one model, selected KB sources and tools, and people/group access. A global connector-content model policy is not established. Sources: unique-ai:unique-ai:agent. - default_model — Can admins set the default model? [supported]: Administrators select the model for each Space. Sources: unique-ai:unique-ai:agent. - user_limits — What per-user message or token limits apply, and are they published? [partial]: Off-by-default beta cost management supports daily USD limits at company/group/user levels, reset at user-local midnight. Public fixed token/message quotas are not established. Sources: unique-ai:unique-ai:cost. - limit_behaviour — What happens when a limit is reached? [supported]: With limits enabled, the next model call is blocked when daily spend reaches the cap. Most permissive group limit wins unless a user override exists. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:cost ## Company knowledge ### KNOW-01: Files in chat Judgment rule: Record supported formats, size and count limits, scanned-PDF OCR, tables and spreadsheets, images inside documents, and whether a file is read in full or retrieved in chunks. Upload the shared fixture set (long German PDF, scanned contract, Excel with formulas, PowerPoint) and record failures. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Conversation files and code/OCR handling are documented; conflicting effective upload caps are explicitly unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No common PDF/scan/Excel/PowerPoint fixture run. - Do not use either disputed cap set as the effective Business upload limit. - formats — Which formats are accepted? [supported]: Conversation uploads accept documents/PDF, text/code, Excel/CSV/TSV, images and supported audio. Direct video uploads are explicitly excluded by the limits FAQ. Sources: dust:dust:files, dust:dust:file-limits. - limits — What size and count limits apply per file and chat? [unknown]: Effective image/audio/tabular maximums and file counts are unknown: Conversation Files lists5/25/50MB while File size limits lists20/100/350MB. Both mention50MB general data files, but neither resolves the actual current per-plan upload route. No logged-in upload test was performed. - ocr — Are scanned PDFs read? [partial]: Computer documents OCR for English, French and mixed scans with page-level caveats. Drive connector itself ignores image-only files; upload to a conversation is the documented route. Sources: dust:dust:computer, dust:dust:drive. - spreadsheets — Are Excel tables read with structure intact? [partial]: Computer can read, calculate and edit uploaded Excel with code. Formula/style preservation must be checked; no fixture fidelity result is available. Sources: dust:dust:computer. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [partial]: Conversation uploads are not indexed in workspace sources. Computer can inspect full files, while knowledge search retrieves relevant context; complete chunk visibility was not verified. Sources: dust:dust:files, dust:dust:computer, dust:dust:search. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:files, dust:dust:file-limits, dust:dust:computer, dust:dust:drive, dust:dust:search #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat upload defaults are 512 MB/file and 30 files/batch, with source retrieval for large documents. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Configured scanned-PDF OCR is documented: MDI supports image-based PDFs, Docling has partial support, and Base Unique Ingestion does not support them. MDI must be provisioned and enabled for the folder or chat Space. - Scanned-PDF accuracy, formula preservation, embedded-figure extraction and shared fixture outcomes were not measured. Older general ingestion limits differ from current production chat defaults. - formats — Which formats are accepted? [supported]: Chat supports PDF, DOCX, XLSX, PPTX, CSV, HTML, MD and TXT; PNG/JPEG when enabled per Space. Sources: unique-ai:unique-ai:files. - limits — What size and count limits apply per file and chat? [partial]: Production Chat defaults 512 MB/file, 30 files/upload. Code Execution has separate 100 MB and 10-file limits. Environment overrides and aggregate chat caps need tenant confirmation. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code. - ocr — Are scanned PDFs read? [partial]: The file-ingestion guide explicitly distinguishes methods: Base Unique Ingestion does not support image-based scanned PDFs, MDI supports them, and Docling has partial support. MDI must be provisioned and enabled for the folder or in the chat Space ingestion settings. Experimental image-content extraction and deprecated agentic ingestion are separate. No scanned-document fixture or accuracy measurement was run. Sources: unique-ai:unique-ai:file-ingestion-20261026. - spreadsheets — Are Excel tables read with structure intact? [partial]: Chat guide says default extraction can fail beyond 5,000 rows x 100 columns. General format guide lists 1,000 x 40; formulas and structure retention were not tested. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:filetypes. - full_vs_chunked — Is the whole file used or only retrieved parts, and does the user see which? [supported]: Checked uploads force retrieval each turn. Large files contribute selected chunks, not necessarily the full file, and users do not see full coverage. Experimental full-PDF mode is separate. Sources: unique-ai:unique-ai:files. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:code, unique-ai:unique-ai:filetypes, unique-ai:unique-ai:file-ingestion-20261026 ### KNOW-02: Knowledge bases and shared collections Judgment rule: Record curated document collections that persist across chats, who can create and share them, size limits, and how they attach to assistants. Distinguish personal, group and organisation-wide scope. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Spaces persist shared knowledge and bind it to agent tools. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - persistent_collections — Can users keep document collections across chats? [supported]: Open and restricted Spaces retain connected sources, folders and other data across conversations. Sources: dust:dust:spaces. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: Open Spaces are workspace-wide; restricted Spaces have explicit members or provisioned groups. Sources: dust:dust:spaces. - size_limits — What are the collection limits? [partial]: Business supports five Spaces and Enterprise 100. Complete per-Space storage/document quotas were not established. Sources: dust:dust:spaces. - assistant_binding — Can collections be bound to an assistant? [supported]: An agent tool can use selected Space data; Space membership governs agent visibility and use. Sources: dust:dust:spaces. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:spaces #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge folders persist and can be scoped to users/groups and bound to Spaces. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - persistent_collections — Can users keep document collections across chats? [supported]: Ingested content lives in knowledge-base folders/scopes beyond a chat. Sources: unique-ai:unique-ai:kbpermissions. - sharing_scope — Can collections be shared with users, groups or the whole organisation? [supported]: ScopeAccess grants users or groups read/write access. A flat folder permission does not automatically grant subfolder access. Sources: unique-ai:unique-ai:kbpermissions. - size_limits — What are the collection limits? [unknown]: What are the collection limits? Unknown. Public total collection/document/token caps and organisation-wide sharing defaults are not specified; chat-only uploads are separately private and expiring. - assistant_binding — Can collections be bound to an assistant? [supported]: Space Internal Search binds selected folders/files and further narrows user permissions. Sources: unique-ai:unique-ai:agent. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:agent ### KNOW-03: Enterprise connectors Judgment rule: List each connector separately with plan, availability and setup owner: SharePoint, OneDrive, Outlook, Teams, Google Drive, Gmail, Confluence, Jira, Notion, Box, Salesforce, ServiceNow, file shares. Record whether the vendor or a third party (or the customer via MCP) provides it, and whether it needs admin consent. A connector listed on a roadmap or partner page is `announced`. An on-prem connector or gateway proves access to local data, not a self-hosted platform (DATA-02). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed content connectors coexist with MCP tools and beta imports; Microsoft content indexing is account-scoped. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business: up to3 connections and5 remote MCP servers; Enterprise: unlimited connection/MCP packaging; beta imports identified separately; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Managed sources, metadata/table-query connections, MCP tools and beta imports are separate routes; no all-systems managed-index promise. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: The Microsoft connection syncs selected SharePoint drives/documents within the connecting account permissions. Teams-associated SharePoint content is described; this does not establish Outlook mail or all Teams messages as indexed sources. Sources: dust:dust:microsoft. - google_workspace — Which Google sources are connected? [partial]: Drive documents, Sheets, Slides and text PDFs can sync. Gmail is separately available as an MCP tool in the credits/tool catalog, not established as the same managed content index. Sources: dust:dust:drive, dust:dust:credits. - atlassian — Confluence and Jira? [partial]: Confluence indexes selected global spaces, excluding restricted pages. Jira has a beta custom import and MCP tool route; do not count the beta import as a general managed connector. Sources: dust:dust:confluence, dust:dust:jira, dust:dust:credits. - other_systems — Which other business systems? [partial]: Documented routes include managed Slack/Notion/GitHub and Salesforce/Zendesk/Snowflake sources/tools. BigQuery specifically uses a dedicated-service-account table-query connection: Dust keeps metadata, not a synchronized table-content index; queries stay within the chosen BigQuery dataset location and Space admins select tables. General Business/Enterprise connection limits apply; a BigQuery-specific commercial add-on is not separately specified. Sources: dust:dust:sources, dust:dust:credits, dust:dust:r2-bigquery, dust:dust:pricing. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Admins can connect a customer-hosted MCP server at a reachable secured URL. This is tool access, not evidence of a native SMB/file-share connector or on-premises Dust deployment. Sources: dust:dust:tools. - connector_provider — Who builds and maintains each connector? [supported]: Dust manages built-in connections; external MCP servers can be vendor/community/customer hosted and authenticated separately. Sources: dust:dust:permissions, dust:dust:tools. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:credits, dust:dust:confluence, dust:dust:jira, dust:dust:sources, dust:dust:r2-bigquery, dust:dust:pricing, dust:dust:tools, dust:dust:permissions #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Indexed SharePoint and Confluence are documented. Current architecture also names Google Drive/Salesforce, and release notes describe Salesforce/Yahoo Finance MCP connector dashboards; detailed entitlements and source permissions remain connector-specific. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Architecture labels and release examples do not prove that every source is enabled or included in every contract. - Future items on the roadmap are not promoted to current connector support. - No source-connection or two-user permission fixture was run. - microsoft_365 — Which M365 sources (SharePoint, OneDrive, Outlook, Teams) are connected? [partial]: SharePoint Online connector copies selected content with application consent and optional permission sync. Platform documentation also exposes Teams and Outlook MCP operator guides, but their exact contracted scope and OneDrive coverage were not verified. Sources: unique-ai:unique-ai:sharepoint. - google_workspace — Which Google sources are connected? [partial]: The current Platform Overview names Google Drive as a Knowledge Source feeding the Knowledge Base. It does not establish Gmail/Calendar coverage, a deployment guide, source consent scopes or inclusion in a particular customer contract. This is a documented architecture listing, not an observed enabled connector. Sources: unique-ai:unique-ai:platform-overview-20261026. - atlassian — Confluence and Jira? [partial]: Official Confluence connector supports Cloud and Data Center; Jira connector coverage was not established. Sources: unique-ai:unique-ai:confluence. - other_systems — Which other business systems? [partial]: Release 2026.40 names Salesforce and Yahoo Finance as examples in GA MCP connector dashboards that admins can list, enable and sign in to. Platform Overview also names Salesforce as a Knowledge Source. Exact origin implementation, connector rights, credentials and commercial inclusion vary by configured connector and contract. Sources: unique-ai:unique-ai:release40-20261026, unique-ai:unique-ai:platform-overview-20261026. - on_prem_sources — Can on-prem file shares or databases be connected? [partial]: Confluence Data Center sources are supported via REST. Generic file-share/database connector scope was not established. Sources: unique-ai:unique-ai:confluence. - connector_provider — Who builds and maintains each connector? [supported]: Unique publishes Kubernetes operator guides for SharePoint and Confluence; client IT supplies source credentials, consent, scope and deployment configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:platform-overview-20261026, unique-ai:unique-ai:release40-20261026 ### KNOW-04: Permission-aware retrieval Judgment rule: Using two test users, verify that a restricted document in the fixture tenant is never cited or summarised for the user without access, including after a permission change. Record whether permissions are enforced at query time by the source system, mirrored into an index, or not enforced. Record the propagation delay of a revocation. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge access is documented through connection-account scope and Dust Spaces; per-user source-ACL mirroring is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Connector access through one account is not counted as demonstrated per-user source permission preservation. - source_permissions_respected — Are source permissions enforced per user? [partial]: Drive and Microsoft content available to Dust follows the connecting account and admin-selected data. Users then access agent knowledge through Space membership. Individual source ACL inheritance for each querying user was not established. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Managed content is synchronized under the connection identity and gated through open/restricted Spaces; personal tool credentials are a separate per-user route. Sources: dust:dust:permissions, dust:dust:credentials. - revocation_delay — How quickly does a removed permission take effect? [unknown]: How quickly does a removed permission take effect? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins choose connector folders/documents/sites and control restricted Space membership. Sources: dust:dust:spaces, dust:dust:microsoft. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [unknown]: Are Microsoft Purview or similar labels respected? No two-user restricted-document or revocation fixture was run. Checked connector/Space docs did not establish per-query source ACL mirrors, a source-permission revocation SLA, or Microsoft Purview-label enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:drive, dust:dust:microsoft, dust:dust:permissions, dust:dust:credentials, dust:dust:spaces #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint permission mirroring is optional; Confluence does not synchronise source permissions. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user restricted-document/revocation fixture was run. End-to-end revocation SLA and label enforcement are not established. Older folder-permissions documentation says SharePoint never mirrors permissions, conflicting with the newer optional-sync guide. - source_permissions_respected — Are source permissions enforced per user? [partial]: SharePoint content_and_permissions mirrors source rights, while content_only uses Unique scope rules. Confluence explicitly has no source-permission sync, so Unique folder access needs configuration. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - enforcement_point — Does the source system, a mirrored index or nothing enforce them? [supported]: Indexed content is filtered through Unique user/group ScopeAccess. This is not source-system live query-time enforcement. Sources: unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:sharepoint. - revocation_delay — How quickly does a removed permission take effect? [partial]: SharePoint source rights refresh periodically, default scans 15 minutes. Internal gatekeeper changes usually propagate under one second but have no hard upper bound; degraded/missed broadcasts can leave old rules active. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:permissioncache. - admin_scope_controls — Can admins exclude sites, folders or labels? [supported]: Admins allow SharePoint sites/libraries and require a sync flag, Confluence labels, and Space KB restrictions. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:agent. - sensitivity_labels — Are Microsoft Purview or similar labels respected? [partial]: July SharePoint connector explicitly excludes sensitivity/classification-level detection. Separately, release2026.42 documents experimental Purview-protected-file decryption using uploader rights, gated by MIP_DECRYPTION_ENABLED and Entra/operator changes. This is not proof of general label-policy enforcement. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:sharepoint. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:kbpermissions, unique-ai:unique-ai:permissioncache, unique-ai:unique-ai:agent, unique-ai:unique-ai:release42 ### KNOW-05: Freshness and sync model Judgment rule: Record live (federated) search versus a copied index, sync interval, deletion propagation, and where the index is stored. Edit and delete one fixture document and record when answers change. A copied index adds storage location to DATA-01. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Managed connectors copy and synchronize content, with source-specific refresh and deletion timing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connections synchronize content into Dust; conversation uploads remain scoped to the chat. MCP tools can access live services separately. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools. - sync_interval — How often does an index refresh? [supported]: Microsoft describes five-minute sync cycles; Drive says a few minutes; Confluence describes event updates plus an approximate hourly check. Sources: dust:dust:microsoft, dust:dust:drive, dust:dust:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Microsoft changes/deletions appear on a subsequent sync and large batches can take longer. Drive deletions occur during its sync. No measured end-to-end bound was tested. Sources: dust:dust:microsoft, dust:dust:drive. - index_location — Where is indexed content stored? [partial]: Dust markets EU or US hosting; exact per-index country, cloud provider and backup location were not established. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:permissions, dust:dust:files, dust:dust:tools, dust:dust:microsoft, dust:dust:drive, dust:dust:confluence, dust:dust:security #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SharePoint and Confluence copy content to Unique indexes on configurable scans, default every 15 minutes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No source-edit/delete fixture was run. Actual sync duration, strict deletion SLA and index/backup region per contract remain unverified. - live_or_indexed — Is content searched live or copied into an index? [supported]: Connectors ingest documents/page attachments into the Unique knowledge base for RAG. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - sync_interval — How often does an index refresh? [supported]: Default 15-minute scan for both connectors; schedules are configurable. Real-time sync is explicitly not supported. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - deletion_propagation — How quickly does a deleted document disappear? [partial]: Diff processing detects deleted source files/pages and removes them on a sync run. A strict completion bound is not provided. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence. - index_location — Where is indexed content stored? [partial]: Hosted documents use Azure storage; embeddings Qdrant and search vectors on managed disks in the selected deployment. Exact per-client index region needs the MSA/architecture. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:keys. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:confluence, unique-ai:unique-ai:retention, unique-ai:unique-ai:keys ### KNOW-06: Grounding and retrieval quality Judgment rule: Run the shared question set over the fixture corpus: factual lookups, cross-document questions, German document with an English question, a question with no answer in the corpus. Record citation presence, link accuracy, correct answers and refusals to invent. Disclose model, settings, attempt count and failures. Single runs support a case study, not a ranking. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Knowledge and research tools cite sources; observed retrieval quality remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - citations — Are answers linked to specific sources? [supported]: Deep-dive documents citations to documents, web pages and data queries. Sources: dust:dust:deep. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - cross_language — Does a question in one language find documents in another? [unknown]: Does a question in one language find documents in another? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? No multilingual shared corpus or question set was run. Citation accuracy, cross-language retrieval success, no-answer behavior and correct-answer counts remain unmeasured; model multilingual ability is not a retrieval-quality test. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents source-linked answers and reference limits, without a shared-corpus accuracy result. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - citations — Are answers linked to specific sources? [supported]: Chat retrieval cites sources; Conduct links source facts, with PDF/Word page-level references and other formats at document level. Generated files are not citation-linked or hallucination-checked. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct. - citation_accuracy — Do the cited passages support the answer? [unknown]: Do the cited passages support the answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - 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 shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - no_answer_behaviour — Does it say when the corpus has no answer? [unknown]: Does it say when the corpus has no answer? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. - observed_accuracy — How many of the question set were answered correctly? [unknown]: How many of the question set were answered correctly? Unknown. No shared question set was run. Citation correctness, cross-language recall, no-answer behaviour and observed accuracy remain unmeasured. Vendor evaluation tools are not our benchmark results. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:conduct ### KNOW-07: Memory and personal context Judgment rule: Record personal custom instructions, cross-chat memory, project or workspace context, and user controls to view, edit, delete or disable memory. Record whether admins can disable memory organisation-wide. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agent-specific private memory persists across chats and can be viewed or deleted. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - custom_instructions — Can users set persistent instructions? [partial]: Agent instructions persist in the agent configuration and saved memory can contain user preferences; a separate personal global-instructions setting was not established. Sources: dust:dust:builder, dust:dust:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: The Memory tool retains user-specific information across conversations per agent. Sources: dust:dust:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users can view and delete agent memories, which persist until deletion. Direct editing or a global personal off switch was not established. Sources: dust:dust:memory. - admin_memory_controls — Can admins turn memory off? [unknown]: Can admins turn memory off? The Agent Memory and governance guides were checked; an admin-wide switch to disable all memory was not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:memory #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Context Memory provides a private cross-chat user profile with edit and opt-out controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No authenticated memory fixture or permanent deletion test was run. The guide explicitly contradicts the settings deletion promise. - custom_instructions — Can users set persistent instructions? [partial]: Admins configure Space instructions; memory learns preferences. A separate persistent user-authored global instruction field was not established. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory. - cross_chat_memory — Does the product remember facts across chats? [supported]: One per-user profile is loaded across enabled spaces/chats and updated after answers; stored in a private unindexed KB folder. Sources: unique-ai:unique-ai:memory. - user_memory_controls — Can users view, edit and delete memories? [partial]: Users view/edit the profile and disable updates/loading. Docs explicitly say disabling does not delete the profile despite contrary settings text; a delete control is not established. Sources: unique-ai:unique-ai:memory. - admin_memory_controls — Can admins turn memory off? [supported]: Release2026.42 makes Context Memory GA, with per-company enable/disable feature flag and per-Space activation. Users can opt out; Web Search combinations remain restricted by default. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:memory. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:memory, unique-ai:unique-ai:release42 ## Assistants and agents ### AGT-01: Custom assistants Judgment rule: Record creation of assistants with instructions, model, knowledge and tools; who can create; sharing scope; versioning; and an internal catalogue or directory. Build one HR policy assistant on the fixture and share it with one group. Prompt templates and a prompt library are recorded here. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Custom agents have instructions, models, knowledge and tools with group-governed creation and sharing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Agent Builder configures instructions, models, knowledge and tools. Sources: dust:dust:builder. - creator_permissions — Can admins limit who creates them? [supported]: Create/publish agent and skill permissions can be Everyone, Groups or Admin only. Sources: dust:dust:governance. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Agents and their knowledge access are controlled by sharing and Space memberships; group governance regulates publishing. Sources: dust:dust:builder, dust:dust:spaces, dust:dust:governance. - catalogue — Is there an internal assistant directory? [partial]: Published/shared agents and default agents are discoverable in the workspace; exact catalog configuration was not observed. Sources: dust:dust:builder, dust:dust:models. - prompt_library — Are shared prompt templates available? [partial]: Reusable agents and skills package instructions, knowledge and tools. A separate legacy prompt-library feature is not assumed. Sources: dust:dust:governance, dust:dust:builder. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:spaces, dust:dust:models #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Admins configure Spaces with instructions, models, knowledge, tools, prompts and group access. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Assistant versioning, organisation-wide directory discovery and unrestricted end-user creation were not established. - create_assistants — Can users create assistants with instructions, knowledge and tools? [supported]: Space setup includes model, instructions, knowledge sources and tools. Sources: unique-ai:unique-ai:agent. - creator_permissions — Can admins limit who creates them? [supported]: Space creation/management requires delegated role permissions; Can manage grants space configuration access. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - sharing_scope — Can assistants be shared with users, groups or everyone? [supported]: Share through Access with people/groups as Can chat or Can manage. Sources: unique-ai:unique-ai:agent. - catalogue — Is there an internal assistant directory? [partial]: Space Management lists configured workspaces; a dedicated employee assistant-discovery directory is not described. Sources: unique-ai:unique-ai:agent. - prompt_library — Are shared prompt templates available? [supported]: Admins publish Suggested Prompts with a Space; users also have personal saved prompts. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:roles, unique-ai:unique-ai:chat ### AGT-02: Tools, actions and MCP Judgment rule: Record built-in tools, custom actions (OpenAPI), MCP client support (local and remote servers), authentication model per tool (shared service account or per-user OAuth), and admin approval of tools. Verify one external-tool call and its access boundary. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust supports built-in tools, customer MCP servers and personal or shared credentials. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No external-tool call or access-boundary fixture was run. - builtin_tools — Which tools are built in? [supported]: Documented tools include knowledge search, table queries, web search, Computer, images, speech and agent orchestration. Sources: dust:dust:credits, dust:dust:computer. - custom_actions — Can admins add API actions? [supported]: Admins can connect customer-written MCP tools over secured publicly reachable URLs. Sources: dust:dust:tools. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: Admins add remote MCP servers with automatic/static OAuth or bearer-token authentication and can restrict tools to skills. Sources: dust:dust:tools. - tool_auth — Do tools act as the user or as a shared account? [supported]: Shared credentials act as one service account; personal credentials use each user OAuth after initial admin setup. Sources: dust:dust:credentials. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Computer network domains can require user approval; dated connector releases describe approval for writes. A universal confirmation rule for every tool and unattended trigger was not established. Sources: dust:dust:computer, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:computer, dust:dust:tools, dust:dust:credentials, dust:dust:changelog #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Built-in tools and beta MCP connectors are governed at organisation and Space levels. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted platform with MCP beta feature flag and configured connectors; add_ons=MCP entitlement and enablement per contract; deployment_mode=not specified; region=Tenant plus downstream connector/provider regions; os=not specified. Limitations: - Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - builtin_tools — Which tools are built in? [supported]: Internal search, web search, Deep Research and Code Execution are documented; Deep Research is experimental and code has model restrictions. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch. - custom_actions — Can admins add API actions? [unknown]: Can admins add API actions? Unknown. Arbitrary OpenAPI action import, local stdio MCP support, each connector auth mode and universal side-effect approval are not established. Hub planned DLP/elicitation pipeline is not treated as released. - mcp_client — Can it use remote MCP servers, and with what admin control? [supported]: MCP Tools for Spaces is beta, off until enabled for the organisation; connector admins and space managers can selectively expose connectors/tools. Sources: unique-ai:unique-ai:mcp. - tool_auth — Do tools act as the user or as a shared account? [supported]: MCP Hub maps user hub tokens to downstream per-user OAuth tokens; secrets are injected server-side. Sources: unique-ai:unique-ai:hub. - tool_approval — Can admins approve or block tools, and can users confirm actions before they run? [partial]: Admins restrict origin/connector/tool exposure. Conduct can pause for approve/deny of configured sensitive actions; it is not a universal confirmation guarantee. Sources: unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:code, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:mcp, unique-ai:unique-ai:hub, unique-ai:unique-ai:conduct ### AGT-03: Web search and deep research Judgment rule: Record web search on/off control per organisation and group, search provider, citation of web sources, deep or multi-step research, and whether queries leave the residency boundary. Admins of regulated companies often need web search off. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can search the web and run multi-step Deep-dive research. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web_search — Is web search available? [supported]: Web Search & Browse runs Google queries and reads result pages. Sources: dust:dust:web. - admin_toggle — Can admins disable it per organisation or group? [partial]: Web tools are selected in agent configuration; default Deep-dive can be disabled by admins. A universal per-group web-off rule was not established. Sources: dust:dust:web, dust:dust:deep. - search_provider — Which search provider handles queries, and where? [partial]: The guide calls the search a Google query. The intermediary provider and countries handling queries/crawling were not established. Sources: dust:dust:web. - deep_research — Is multi-step research with a report available? [supported]: Deep-dive plans, spawns parallel specialists and produces a research report. It searches Company Data and cannot use Table Query. Sources: dust:dust:deep. - web_citations — Are web sources cited? [supported]: Deep-dive promises citations to web and company sources. Sources: dust:dust:deep. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:web, dust:dust:deep #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web search has provider/strategy controls; separate Deep Research is experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No search/report fixture was run. Exact query/provider regions, contract enablement and current Deep Research production readiness remain unverified. - web_search — Is web search available? [supported]: Real-time web search/read is a Space tool, with stable V1/V2 modes and experimental V3. Sources: unique-ai:unique-ai:websearch. - admin_toggle — Can admins disable it per organisation or group? [supported]: Admins enable/disable tools per Space shared with groups. Deep Research tools are configured separately; disabling ordinary Web Search is not a universal external-search block. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch. - search_provider — Which search provider handles queries, and where? [partial]: Configured engines can include Google, Bing, Brave, Jina, Tavily, Firecrawl, Vertex or custom API; query context can leave the tenant. Exact provider region must be set per contract. Sources: unique-ai:unique-ai:websearch. - deep_research — Is multi-step research with a report available? [supported]: Experimental tool creates multi-source research and reports. Unique engine can use internal/web sources; OpenAI-native engine requires direct OpenAI-hosted models and lacks internal sources/hosting-location control. Sources: unique-ai:unique-ai:deepresearch. - web_citations — Are web sources cited? [supported]: Web answers include source references; Deep Research documents citation-linked reports. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:deepresearch. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:websearch, unique-ai:unique-ai:agent, unique-ai:unique-ai:deepresearch ### AGT-04: Workflows and automation Judgment rule: Record no-code or low-code workflows, scheduled prompts, triggers from email, forms or business systems, and multi-step chains. Name where they run and who can build them. A shared prompt template is not a workflow. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents support schedules and webhook automation with admin-created event sources. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - workflow_builder — Is there a workflow or chain builder? [partial]: Agents orchestrate tools and sub-agents; external n8n and trigger workflows are documented. A separate visual multi-step chain canvas was not established. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog. - scheduled_tasks — Can prompts or assistants run on a schedule? [supported]: Agents can run on recurring schedules. Sources: dust:dust:schedules. - event_triggers — Can external events start a workflow? [supported]: Built-in webhook sources include GitHub, Jira, Linear, Zendesk and Fathom; signed custom webhooks are supported. Sources: dust:dust:webhooks. - builder_audience — Is building aimed at business users, IT or developers? [supported]: Admins connect event sources; builders/members attach filtered triggers in Agent Builder and can use natural-language trigger creation through Dust Default. Sources: dust:dust:webhooks, dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:triggers, dust:dust:changelog, dust:dust:schedules, dust:dust:webhooks #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Recurring Scheduled Tasks run with user permissions; current release notes label the feature experimental. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - workflow_builder — Is there a workflow or chain builder? [unknown]: Is there a workflow or chain builder? Unknown. No general no-code workflow/chain builder or complete event-source trigger catalogue was established. Automated runs may stop for manual approval/questions and are subject to normal usage limits. - scheduled_tasks — Can prompts or assistants run on a schedule? [partial]: User guide labels recurring Chat/Conduct tasks beta and off by default; release2026.42 instead labels Scheduled Tasks experimental, off by default, enabled on request, and describes scheduling/eligibility fixes. Sources: unique-ai:unique-ai:release42, unique-ai:unique-ai:scheduled. - event_triggers — Can external events start a workflow? [partial]: SDK documents webhook-driven applications, which require developer-hosted modules; a packaged no-code external-event builder was not established. Sources: unique-ai:unique-ai:sdk. - builder_audience — Is building aimed at business users, IT or developers? [partial]: Business users author recurring tasks in the UI or Conduct; developers host webhook-driven SDK modules. Availability and scheduling behaviour depend on deployed release. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scheduled, unique-ai:unique-ai:sdk, unique-ai:unique-ai:conduct, unique-ai:unique-ai:release42 ### AGT-05: Agentic task execution Judgment rule: Record an agent mode that plans and carries out multi-step tasks with tools (browser, files, connectors), with visible steps, user confirmation of side effects and stop control. Run one fixture task (gather three documents, draft a summary, propose an email). Record interventions and what ran. A final claim of success is not proof. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Multi-step agent work and visible Deep-dive progress are documented; safety controls depend on tool and trigger. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No shared gather/documents/email fixture or side-effect audit was run. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Deep-dive plans, delegates and synthesizes, and Computer can execute deterministic file/code work. Sources: dust:dust:deep, dust:dust:computer. - visible_steps — Are steps and tool calls shown? [supported]: Deep-dive documentation shows reasoning and sub-agent progress in real time. Sources: dust:dust:deep. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Computer domains may require user approval and selected connector write actions ask for approval. Pods agents can also act without a human, so universal write confirmation is not claimed. Sources: dust:dust:computer, dust:dust:changelog, dust:dust:pods. - stop_control — Can the user stop a running task? [partial]: The 600-AWU root-task checkpoint offers Stop or Continue. A complete general stop/rollback behavior was not tested. Sources: dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:deep, dust:dust:computer, dust:dust:changelog, dust:dust:pods, dust:dust:credits #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Contract-enabled Conduct plans and executes multi-step tasks with visible tools and stop controls. Sensitive actions can ask for approval; separately enabled Experimental Scheduled Tasks offer automatic approval. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Conduct; version=Conduct 2026.40+; scheduling status/flags per 2026.42; plan=Contracted Unique AI platform; Conduct; Scheduled Tasks separately enabled per contract and feature flag availability and deployment/provider configuration depend on the customer agreement; add_ons=Conduct; optional Scheduled Tasks feature flag; deployment_mode=not specified; region=Configured tenant/models/tools; scheduled actions run with the owner permissions and configured approval policy; os=not specified. Limitations: - No agent fixture was run. Interactive sensitive-action approval and separately enabled unattended automatic approval are different execution modes. - Actual tools, entitlement, approval policy and deployed release depend on the customer contract/configuration. - agent_mode — Is there an agent mode for multi-step tasks? [supported]: Plans and executes Python/Bash, files, internal search and configured MCP tools in an autonomous workspace. Sources: unique-ai:unique-ai:conduct. - visible_steps — Are steps and tool calls shown? [supported]: Shows checklist, progress, code/tool inputs and outputs, and waiting/working indicators. Sources: unique-ai:unique-ai:conduct. - side_effect_confirmation — Must the user confirm actions with side effects? [partial]: Conduct shows approve/deny for actions configured as sensitive. The separate Scheduled Tasks guide offers Automatic or Manual approval for Chat/Conduct unattended runs. Release 2026.42 labels scheduling Experimental and feature-flagged. Mandatory human approval of every side effect is therefore not established for all configured runs. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42. - stop_control — Can the user stop a running task? [supported]: Stop ends the turn within seconds; completed steps/files remain and interrupted work can be resumed. Sources: unique-ai:unique-ai:conduct. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:conduct, unique-ai:unique-ai:review2-scheduled, unique-ai:unique-ai:review2-release42 ### AGT-06: Programmable access Judgment rule: Record a public API for chat, assistants and knowledge, SDKs, API authentication, rate limits and whether API use counts against the same governance (audit, budgets, model restrictions). Being an MCP client is different from exposing the product over MCP. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Dust offers conversation/knowledge APIs, enforceable API-key caps and OAuth MCP access. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business conversation API; Enterprise adds Data Source API per pricing; MCP subject to workspace enablement; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. - chat_api — Is there an API for chat and assistants? [supported]: Documented APIs retrieve/create conversations and messages with scoped API keys. Sources: dust:dust:get-conversation, dust:dust:api-keys. - knowledge_api — Can documents be loaded through an API? [supported]: The data-source API upserts documents into scoped data sources. Sources: dust:dust:upsert. - api_governance — Do audit, budgets and model rules apply to API use? [supported]: Per-key caps reject further API usage at the limit. Model overrides obey workspace/tier rules; programmatic usage uses the workspace pool and does not count toward beta pooled group budgets. Sources: dust:dust:api-keys, dust:dust:models, dust:dust:credit-management. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Global and EU MCP URLs expose authorized Dust knowledge, conversations, agents, files and Pods via OAuth; admins can disable access and control redirects. Sources: dust:dust:mcp-server. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:api-keys, dust:dust:upsert, dust:dust:models, dust:dust:credit-management, dust:dust:mcp-server #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public API/Python SDK and Knowledge Base MCP are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique API and Python SDK, Unique MCP Hub and Knowledge Base MCP; version=not specified; plan=Contracted APIs and KB MCP deployment; model tracking requires enablement; add_ons=KB MCP and usage-tracking enablement per contract; deployment_mode=not specified; region=Configured deployment and external client region; os=not specified. Limitations: - No API/SDK fixture was run; complete endpoint catalogue, rate limits, budget enforcement and all-services audit parity remain unverified. - chat_api — Is there an API for chat and assistants? [partial]: SDK exposes the Unique public API, personal/app keys and webhook signatures. Exact endpoint entitlements/rate limits require the contracted deployment. Sources: unique-ai:unique-ai:sdk. - knowledge_api — Can documents be loaded through an API? [partial]: Connector/operator docs describe ingestion and knowledge APIs; public SDK supports platform integrations. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint. - api_governance — Do audit, budgets and model rules apply to API use? [partial]: Feature-flagged model-use tracking covers public API/SDK/agentic and Azure SDK calls with company/user/app metadata. Complete budget/model-rule enforcement across all internal services is not established. Sources: unique-ai:unique-ai:api-usage. - mcp_server — Does the product expose itself to other agents over MCP? [supported]: Knowledge Base MCP lets external assistants search/read the Unique KB with the user permissions and admin scope restrictions. The documentation-only MCP endpoint is distinct. Sources: unique-ai:unique-ai:mcpkb. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sdk, unique-ai:unique-ai:sharepoint, unique-ai:unique-ai:api-usage, unique-ai:unique-ai:mcpkb ## Daily work ### WORK-01: Clients and access points Judgment rule: List web, desktop (Windows, macOS), iOS, Android, mobile browser and browser extension separately. For each, record login with company SSO, feature gaps against web, and MDM/Intune deployability. An installable app is different from a mobile website. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Web, browser extension and Teams access are documented; native desktop/mobile availability remains unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust browser extension; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - web — Is a full web client available? [supported]: Dust provides the hosted web workspace, including the EU region. Sources: dust:dust:pricing, dust:dust:models. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - browser_extension — Is there a browser extension or sidebar? [supported]: The extension guide covers Chrome, Firefox and Chromium browsers. Sources: dust:dust:browser. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? The documentation index, extension page, pricing and integration guides were checked. Native Windows/macOS apps, iOS/Android SSO apps, managed MDM configuration and a mobile parity matrix were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:models, dust:dust:browser #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A web workspace is documented; native-client and managed-deployment coverage is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - web — Is a full web client available? [supported]: Public documentation describes browser chat, Space Management and administration. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent. - desktop_apps — Windows and macOS apps? [unknown]: Windows and macOS apps? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - mobile_apps — iOS and Android apps with SSO? [unknown]: iOS and Android apps with SSO? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - browser_extension — Is there a browser extension or sidebar? [unknown]: Is there a browser extension or sidebar? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - managed_deployment — Can IT deploy and configure clients through MDM? [unknown]: Can IT deploy and configure clients through MDM? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. - client_feature_gaps — Which features are missing on mobile? [unknown]: Which features are missing on mobile? Unknown. The public material references an app and mobile voice/browser usage without a current Windows/macOS/iOS/Android SSO/MDM matrix. Browser extension/sidebar entitlement and mobile parity remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:chat, unique-ai:unique-ai:agent ### WORK-02: Office suite and Teams integration Judgment rule: Record presence inside Word, Excel, PowerPoint, Outlook and Teams (and Google Docs, Gmail), with what the assistant can do in each: read the open document, write into it, act on mail. Record extra licences and admin consent needed. A connector that searches Office files is KNOW-03, not WORK-02. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial An official Teams integration runs agents in Teams; document connectors do not imply Office add-ins. Availability: generally-available Delivery: official-integration Scope: surfaces=Dust in Microsoft Teams; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - word_excel_powerpoint — Does it work inside Word, Excel and PowerPoint? [unknown]: Does it work inside Word, Excel and PowerPoint? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - outlook — Does it work inside Outlook? [unknown]: Does it work inside Outlook? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - teams — Is there a Teams app or bot? [supported]: Dust in Teams has an official integration guide and admin setup. Sources: dust:dust:teams. - google_workspace_apps — Does it work inside Docs, Sheets or Gmail? [unknown]: Does it work inside Docs, Sheets or Gmail? Teams and Microsoft connector guides were checked. Embedded assistance inside Word/Excel/PowerPoint, Outlook, Docs/Sheets/Gmail was not established; MCP tool access is recorded separately. - licence_prerequisites — Which licences or consents are needed? [partial]: The Teams guide requires integration/admin authorization in a Dust workspace. Extra Microsoft/Dust licence charges were not established. Sources: dust:dust:teams. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:teams #### Unique AI Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-03: Translation and writing Judgment rule: Record document translation preserving layout, the translation engine (LLM or dedicated such as DeepL), glossaries, formality control, supported languages including Swiss German conventions (no ß), and rewriting/proofreading tools. Translate the shared German contract into French and Italian and record layout and glossary results. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents can perform language work, but document-translation fidelity and controlled terminology are untested. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - document_translation — Can whole documents be translated with formatting kept? [unknown]: Can whole documents be translated with formatting kept? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - translation_engine — Which engine translates? [unknown]: Which engine translates? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - glossaries — Are company glossaries supported? [unknown]: Are company glossaries supported? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - formality_and_variants — Can formality and regional variants (de-CH) be set? [unknown]: Can formality and regional variants (de-CH) be set? Builder, file-processing and language documentation were checked. Whole-document translation with layout retention, a dedicated engine, company glossaries, formality/de-CH controls and DE-to-FR/IT fixture outcomes were not established. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Configurable agent instructions and Computer document editing support writing workflows; a separate dedicated proofreading product was not established. Sources: dust:dust:builder, dust:dust:computer. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:computer #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A beta Translator Space translates Office files and text with configurable glossaries. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No translated-contract fixture was run. Exact engine/model, formality/de-CH controls, supported glossary language pairs and layout fidelity need verification. - document_translation — Can whole documents be translated with formatting kept? [partial]: DOCX, XLSX and PPTX document translation is documented, with possible layout disruption. PDF input is explicitly excluded in this Translator mode. Sources: unique-ai:unique-ai:translation. - translation_engine — Which engine translates? [partial]: Translator V2 is a standalone AI module configured with a model; no dedicated DeepL engine was established. Sources: unique-ai:unique-ai:translation. - glossaries — Are company glossaries supported? [supported]: Admins can configure glossary pre/postprocessing. Sources: unique-ai:unique-ai:translation. - formality_and_variants — Can formality and regional variants (de-CH) be set? [partial]: Postprocessing can change regional spelling, exemplified by US-to-UK English. Formality or de-CH-specific support was not verified. Sources: unique-ai:unique-ai:translation. - writing_tools — Are dedicated rewrite and proofreading tools available? [partial]: Chat generates and iterates on text; no distinct proofreading/rewriting tool scope was established. Sources: unique-ai:unique-ai:chat. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:translation, unique-ai:unique-ai:chat ### WORK-04: Image generation and editing Judgment rule: Record available image models, editing (inpainting, reference images), admin control and per-image cost visibility, and licence or usage terms for generated images. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Image tools use reference images and parallel generation; exact model and output-right terms need further evidence. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - image_generation — Can users generate images, with which models? [partial]: Image Generation is a configurable agent capability with SynthID-marked output. The exact current model identifier is not named in the checked guide. Sources: dust:dust:images. - image_editing — Can users edit uploaded images? [partial]: Uploaded and prior generated images can be used as references, with up to 14 references. Precise inpainting/masking controls were not established. Sources: dust:dust:images. - admin_control — Can admins restrict image generation? [partial]: Builders enable image tools in an agent, while group governance controls who creates/publishes agents. A separate organization/group image-off switch was not established. Sources: dust:dust:images, dust:dust:governance. - usage_terms — What usage rights apply to output? [unknown]: What usage rights apply to output? The image guide and legal entry points were checked. Current model identifier, per-image tariff and contractual output usage rights were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:images, dust:dust:governance #### Unique AI Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. ### WORK-05: Voice and meetings Judgment rule: Record dictation, read-aloud, live voice conversation, meeting transcription and summarisation, supported languages including Swiss German speech, and where audio is processed. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Speech generation and meeting-transcript integrations are documented; live voice and Swiss German recognition remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dictation — Can users dictate prompts? [unknown]: Can users dictate prompts? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - read_aloud — Can answers be read aloud? [partial]: Speech Generator converts written text to MP3 audio with selectable voices/languages; a one-click read-aloud mode for all responses was not established. Sources: dust:dust:speech. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. - meeting_summaries — Are meetings transcribed and summarised? [supported]: Connected Granola/Fathom/Gong/Praiz transcripts can feed summaries; private Gong transcripts are excluded. This is not a native meeting recorder claim. Sources: dust:dust:meetings. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Speech, upload and meeting guides were checked. Prompt dictation, live two-way voice, Swiss German accuracy and audio-processing countries were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:speech, dust:dust:meetings #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Voice dictation is documented with Azure Speech prerequisites; recording use is separately described in the DPA. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - dictation — Can users dictate prompts? [supported]: Microphone transcribes into the prompt field, with audio discarded after live transcription. Requires configured Azure AI Speech Services; EN/DE/FR/IT are listed. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user. - read_aloud — Can answers be read aloud? [unknown]: Can answers be read aloud? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - voice_conversation — Is a live voice mode available? [unknown]: Is a live voice mode available? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. - meeting_summaries — Are meetings transcribed and summarised? [partial]: DPA recording use case covers audio/transcripts, optional video and GPT summaries/follow-up emails. This is a contracted recording use case, not proof every Chat plan includes meeting capture. Sources: unique-ai:unique-ai:dpa. - swiss_german_speech — Is Swiss German speech recognised? [unknown]: Is Swiss German speech recognised? Unknown. Read-aloud and full voice conversation, recording-specific plans/limits and verified Swiss German recognition are not established. Voice guide warns about dialects; audio route may traverse public internet/Azure backbone. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:voice, unique-ai:unique-ai:voice-user, unique-ai:unique-ai:dpa ### WORK-06: Data analysis and document output Judgment rule: Record code execution for data analysis, charts, and generation of downloadable Word, Excel, PowerPoint and PDF files. Analyse the fixture Excel and request a PowerPoint summary. Record where code runs and whether files are editable. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: supported Computer executes analysis and creates real Office files; Frames provide editable interactive output. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No Excel/PowerPoint fixture or artifact fidelity test. File Generation is deprecated in favor of Computer as of October 14, 2026. - data_analysis — Can it analyse spreadsheets with executed code? [supported]: Computer executes code to inspect and transform Excel/CSV, compute every-row results and return edited workbooks. Sources: dust:dust:computer. - charts — Can it produce charts? [supported]: Computer documents chart generation from spreadsheet data and inclusion in reports/decks. Sources: dust:dust:computer. - office_file_output — Can it create Word, Excel or PowerPoint files? [supported]: Computer creates/edits Word, Excel and PowerPoint files and returns downloadable artifacts, with fidelity caveats. Sources: dust:dust:computer. - canvas_editing — Is there a document or canvas editor for iterating on output? [supported]: Frames are persistent interactive content that can be revised through agents and shared. Sources: dust:dust:frames. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:computer, dust:dust:frames #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enabled Chat Code Execution and Conduct can analyse data and produce downloadable files. Selected KB documents can be preloaded into the code container; ordinary unrestricted KB retrieval is separate. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique AI Conduct; version=not specified; plan=Contracted Unique AI platform; Chat Code Execution or Conduct; model compatibility and flags configured separately availability and deployment/provider configuration depend on the customer agreement; add_ons=Code Execution / Conduct enablement per contract; deployment_mode=not specified; region=Documented Azure code container for the Azure route; LiteLLM execution region unverified; Conduct sandbox per contracted deployment; os=not specified. Limitations: - Selected admin-preloaded KB files are supported; this is not arbitrary sandbox retrieval of the whole Knowledge Base. - The page lists Azure and LiteLLM-compatible model IDs but describes Azure-specific container controls. Actual provider execution routing and entitlement require deployment configuration. - No generated-file quality/editability fixture was run. - data_analysis — Can it analyse spreadsheets with executed code? [partial]: Chat Code Execution runs Python for CSV/XLSX analysis. The general limitation says KB files are not directly accessible, but admin configuration additionalUploadedDocuments preloads selected KB content_ids, for example templates, into the container. The documented Azure route has no outbound internet/runtime installs and a ten-file/100 MB per-file limit. The compatibility table also lists LiteLLM OpenAI models; that does not establish the same execution-region controls for every route. Conduct separately runs Python/Bash. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - charts — Can it produce charts? [supported]: The Code Execution guide documents matplotlib PNG/SVG and inline charts. Its described Azure container lacks kaleido, limiting Plotly static exports; no statement about every alternative runtime is inferred. Sources: unique-ai:unique-ai:review2-code. - office_file_output — Can it create Word, Excel or PowerPoint files? [partial]: The guide documents DOCX/XLSX generation and PPTX from supplied templates, with variable presentation quality. KB templates can be supplied by the admin preload setting. Generated files remain outside Conduct source-citation/hallucination checks. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct. - canvas_editing — Is there a document or canvas editor for iterating on output? [unknown]: No dedicated canvas editor or editable spreadsheet-to-PowerPoint fixture result was established. Downloadable file generation does not establish in-product canvas editing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-code, unique-ai:unique-ai:conduct ### WORK-07: Sharing and team spaces Judgment rule: Record chat sharing (link, user, group), shared projects or team spaces, channels or group chat with AI, and commenting. Test sharing a chat with a colleague in another group and record what the recipient sees, including knowledge they lack access to. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Pods provide shared team conversations, files and tasks; source-sharing effects still need testing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No cross-group sharing fixture. Do not infer source-ACL propagation from Pod membership. - share_chats — Can chats be shared inside the organisation? [supported]: Pod conversations are visible to all members, who can contribute. Sources: dust:dust:pod-chats. - team_spaces — Are shared projects or workspaces available? [supported]: Open/Restricted Pods group conversations, files and tasks; restricted access is invite-only. Sources: dust:dust:pods. - group_chat — Can several people chat together with the AI? [supported]: Teammates and agents participate in the same Pod thread and can be mentioned. Sources: dust:dust:pod-chats. - share_permission_boundary — Does sharing respect the recipient's access to sources? [partial]: All Pod members read conversation contents. Spaces restrict source/agent use and personal tools act under their user; recipient-safe redaction of previously generated text was not established. Sources: dust:dust:pod-chats, dust:dust:permissions, dust:dust:credentials. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pod-chats, dust:dust:pods, dust:dust:permissions, dust:dust:credentials #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Shared Chats is GA in release 2026.42, with company settings and a per-Space toggle. Simultaneous group conversation and recipient source-permission handling remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=2026.42 or later; plan=Contracted Unique AI platform; Shared Chats and Spaces; sharing settings and deployed release availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - A shared conversation is not evidence of simultaneous group participation or recipient access to every source. - No cross-group shared-chat permission fixture was run. - share_chats — Can chats be shared inside the organisation? [supported]: Release 2026.42 makes whole-chat sharing GA and on by default for companies, while each Space still needs its Shared chat toggle. Explicit existing company preferences are preserved. Owners can search recipients and copy share links. Sources: unique-ai:unique-ai:review2-release42. - team_spaces — Are shared projects or workspaces available? [partial]: Admins publish shared Spaces with people/group Can chat and Can manage roles. These share agent configuration/knowledge, not necessarily a conversation. Sources: unique-ai:unique-ai:agent. - group_chat — Can several people chat together with the AI? [unknown]: Whole-chat sharing is documented. A simultaneous multi-person AI conversation, collaborative commenting or live co-editing mode was not established or tested. - share_permission_boundary — Does sharing respect the recipient's access to sources? [unknown]: Whole-chat sharing is documented, but whether a recipient can open every cited source or inherits source permissions was not established in the retrieved release/Space documentation. No cross-group fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:review2-release42 ### WORK-08: Interface languages and accessibility Judgment rule: Record UI languages, focusing on German, French, Italian and English, with translation quality observed (complete, partial, machine-translated). Record response language handling and WCAG conformance statements. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial German and French UI releases are documented alongside English, with remaining English areas. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - ui_languages — Which UI languages are offered? [supported]: October 21, 2026 release adds German; October 16 adds French alongside English US/UK, across product, Frames, extension, Sidekick and Slack/Teams. Sources: dust:dust:changelog. - dach_language_quality — Are German, French and Italian UIs complete and natural? [partial]: Release notes explicitly leave agent/skill names and instructions in English. German/French naturalness and completeness were not observed; Italian UI was not established. Sources: dust:dust:changelog. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? The dated locale announcements were checked; Italian UI and a WCAG conformance statement/report were not established. - admin_ui_languages — Is the admin interface available in German? [partial]: Admins can set a workspace default language. A complete German admin-screen walkthrough was not observed. Sources: dust:dust:changelog. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:changelog #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current release notes document German, French and Swiss German UI language behaviour; completeness and accessibility remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Release notes describe locale fixes, not a full UI audit or conformance statement. No authenticated UI was reviewed. - ui_languages — Which UI languages are offered? [partial]: Release2026.42 describes German/French label translations and selected-language login/notices/errors/side-panels, including Swiss German spellings. A complete language matrix was not provided. Sources: unique-ai:unique-ai:release42. - dach_language_quality — Are German, French and Italian UIs complete and natural? [unknown]: Are German, French and Italian UIs complete and natural? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - accessibility_statement — Is there a WCAG conformance statement? [unknown]: Is there a WCAG conformance statement? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. - admin_ui_languages — Is the admin interface available in German? [unknown]: Is the admin interface available in German? Unknown. DE/FR/IT/EN voice and text-language capabilities are not a UI-localisation matrix. No authenticated user/admin language-quality pass or current WCAG conformance statement was obtained. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:release42 ## Administration and governance ### ADM-01: Single sign-on and authentication Judgment rule: Record SAML, OIDC, Microsoft Entra ID, Google, LDAP, MFA enforcement, conditional-access compatibility, domain verification and plan restrictions. Test one SSO login on a trial where possible. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SAML SSO can be enforced; Business offers it from five seats on demand. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - No self-serve SSO login test. - sso_protocols — Which SSO protocols and identity providers work? [supported]: SAML SSO is documented, with Okta, Entra ID and JumpCloud named on pricing. Enterprise marketing also names OIDC; a full provider/protocol matrix was not verified. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise. - sso_plan — Which plan includes SSO? [supported]: Business pricing lists SSO for 5+ seats on demand; Enterprise includes it. Sources: dust:dust:pricing. - mfa — Can MFA be enforced? [partial]: Enforced SAML routes sign-in through the IdP. Specific MFA enforcement behavior was not tested or established in the checked setup guide. Sources: dust:dust:sso. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? SSO and plan guides were checked; conditional-access compatibility and verified-domain capture/migration semantics were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:sso, dust:dust:pricing, dust:dust:enterprise #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Zitadel supports Entra OIDC, generic OIDC and SAML across documented deployment types. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - sso_protocols — Which SSO protocols and identity providers work? [supported]: Setup guides explicitly cover Entra ID OIDC, generic OIDC and SAML, including IdP metadata for closed networks. Sources: unique-ai:unique-ai:sso. - sso_plan — Which plan includes SSO? [partial]: Compliance matrix lists SSO for multi-tenant, single-tenant, client-hosted and on-premise modes. Numeric tariff prerequisites are not public. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - mfa — Can MFA be enforced? [partial]: Hosted compliance matrix lists enforced 2FA; SSO setup delegates authentication to the external IdP. Exact customer MFA policy controls need verification. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance. - conditional_access — Do Entra conditional-access policies apply? [unknown]: Do Entra conditional-access policies apply? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. - domain_capture — Can the company claim its email domain? [unknown]: Can the company claim its email domain? Unknown. Entra conditional-access compatibility, verified domain capture and tariff-specific SSO/MFA entitlements were not tested/documented. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:sso, unique-ai:unique-ai:compliance ### ADM-02: User provisioning and lifecycle Judgment rule: Record SCIM, just-in-time provisioning, group sync from the identity provider, deprovisioning effects (chats, assistants, knowledge ownership transfer) and licence assignment. Deprovision a test user and record what happens to their content. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise SCIM and group roles are documented, with specific annual-seat reclaim behavior. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise for SCIM; seat-management differences stated; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - scim — Is SCIM provisioning supported? [supported]: SCIM 2.0 creates, updates and deactivates users from an IdP as an Enterprise feature. Sources: dust:dust:provision. - group_sync — Are identity-provider groups synced? [supported]: Provisioned IdP groups govern Space access and can map to Admin/Manager roles. Sources: dust:dust:provision, dust:dust:spaces. - jit_provisioning — Are users created at first login? [unknown]: Are users created at first login? Provisioning and seat docs were checked. First-login JIT creation and complete leaver-data transfer were not established. - deprovisioning — What happens to a removed user's data and shared assets? [partial]: SCIM deactivates users; removal/reassignment affects seats but exact chat/agent/knowledge ownership transfer was not tested. Sources: dust:dust:provision, dust:dust:seats. - seat_assignment — Can admins assign and reclaim seats? [supported]: Admins assign seat types independent of roles. Unassigned members cannot interact with agents; annual seats return to stock, and already-granted credits can persist to period end. Sources: dust:dust:seats. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:provision, dust:dust:spaces, dust:dust:seats #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial SCIM, group sync and SAML automatic user creation are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - scim — Is SCIM provisioning supported? [supported]: Unique supplies SCIM URL/key for IdP synchronisation, with an Entra guide. Sources: unique-ai:unique-ai:scim. - group_sync — Are identity-provider groups synced? [supported]: SCIM syncs users/groups; SSO group claims can also sync on login, requiring optional Graph group permission/admin consent. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso. - jit_provisioning — Are users created at first login? [supported]: SAML setup explicitly enables automatic creation/update and account creation. Sources: unique-ai:unique-ai:sso. - deprovisioning — What happens to a removed user's data and shared assets? [unknown]: What happens to a removed user's data and shared assets? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. - seat_assignment — Can admins assign and reclaim seats? [unknown]: Can admins assign and reclaim seats? Unknown. Leaver-content ownership transfer, deletion effects and licence assignment/reclamation are not specified; no deprovisioning fixture was run. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:scim, unique-ai:unique-ai:sso ### ADM-03: Roles, groups and feature permissions Judgment rule: Record admin roles, delegated admins, groups, per-feature permissions (web search, image generation, connectors, file upload, agents), separation of subsidiaries or departments, and enforcement. Test one disabled feature for one group. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust separates Admin, Manager, Member and group-manager permissions and supports restricted knowledge spaces. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: Admins control all governance; Managers delegate member/group/usage administration; group managers administer selected groups. Sources: dust:dust:governance. - groups — Can permissions be set per group? [supported]: Permissions go to manual or provisioned groups using Everyone, Groups or Admin-only modes. Multiple grants combine additively. Sources: dust:dust:governance. - feature_toggles — Which features can be switched on or off per group? [partial]: Group controls cover agent/skill creation and publishing, automation charging, billing/security and model ceilings. An exhaustive per-feature toggle matrix for uploads/web/images was not established. Sources: dust:dust:governance, dust:dust:tiers. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Restricted Spaces and Pods separate audiences inside a workspace; separate legal/subsidiary tenant boundaries within one contract were not established. Sources: dust:dust:spaces, dust:dust:pods. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:governance, dust:dust:tiers, dust:dust:spaces, dust:dust:pods #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Four role/access layers separate identity, feature, Space and knowledge controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No two-user disabled-feature test was run. Full cross-Space per-group controls and legal-entity separation require contracted setup. - admin_roles — Which admin roles exist, and can admin rights be delegated? [supported]: IAM owner/viewer/org-manager plus Unique application roles delegate administration; Space Can manage grants local configuration. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent. - groups — Can permissions be set per group? [supported]: Users/groups receive Space and ScopeAccess permissions. Sources: unique-ai:unique-ai:roles. - feature_toggles — Which features can be switched on or off per group? [partial]: Tools and upload settings are configured per Space, then Spaces shared to groups. A global group-feature matrix is not established. Sources: unique-ai:unique-ai:agent. - multi_entity — Can subsidiaries or departments be separated within one contract? [partial]: Compliance docs describe workspace isolation for departments/client engagements. Multi-subsidiary contractual/billing boundaries are not specified. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:roles, unique-ai:unique-ai:agent, unique-ai:unique-ai:compliance ### ADM-04: Usage and adoption analytics Judgment rule: Record dashboards for active users, usage by feature, model, group and assistant, export, and privacy controls (aggregation, pseudonymisation, works-council-friendly settings). Distinguish aggregate adoption metrics from per-person monitoring. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Consumption analytics has detailed attribution and exports without message content. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - adoption_dashboard — Is there an adoption dashboard? [partial]: Pricing lists usage/adoption reporting; the Analytics guide focuses on credit consumption and attribution rather than a complete active-user adoption scorecard. Sources: dust:dust:pricing, dust:dust:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [supported]: Analytics filters/ranks agents, members, groups, models, tools, sources, API keys, skills and Pods. Group attribution may count a member in several groups. Sources: dust:dust:analytics. - export — Can usage data be exported? [supported]: Raw CSV consumption export and API analytics export are documented, with workspace enablement and key-scope restrictions. Sources: dust:dust:analytics. - privacy_modes — Can per-person reporting be limited or pseudonymised? [partial]: Analytics exports omit message content, but contain member/message/conversation identifiers. Pseudonymous or works-council privacy modes were not established. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:analytics #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Analytics exports cover adoption, assistants, models and tools with privacy controls. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Exact group breakdowns, every dashboard entitlement and suppression beyond exported identifiers need verification. - adoption_dashboard — Is there an adoption dashboard? [supported]: Reports cover daily/weekly/monthly active users, assistant interactions and document reference statistics. Sources: unique-ai:unique-ai:analytics. - breakdowns — Can usage be broken down by group, model, feature and assistant? [partial]: Detailed exports include assistant/model, tool calls, skills, cost and tokens. Group and cost-centre breakdowns were not established. Sources: unique-ai:unique-ai:analytics. - export — Can usage data be exported? [supported]: Admins request and download reports with date/assistant filtering; model usage supports CSV. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost. - privacy_modes — Can per-person reporting be limited or pseudonymised? [supported]: Environment flags anonymise export emails, optionally with stable pseudonyms; detailed exports respect organisation settings. Sources: unique-ai:unique-ai:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost ### ADM-05: Spend controls and cost allocation Judgment rule: Record cost visibility per user, group and cost centre, budgets and their behaviour (alert, block, downgrade model), pooled credits, and chargeback exports. Test a small budget on a trial where possible. Distinguish billed amounts, estimates and unavailable amounts. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Credit plans offer consumption visibility, member limits and plan-specific pooled budgets, with programmatic exceptions. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Group budgets are beta and exclude programmatic usage. No budget fixture test. - cost_visibility — Can admins see cost or consumption per user and group? [supported]: Analytics and Credits show consumed credits by member, group, model, tool and agent. Credits are not assumed to be invoice currency. Sources: dust:dust:analytics, dust:dust:credit-management. - budgets — Can budgets be set per user or group? [supported]: Members have shared-pool spend limits; beta group budgets require Enterprise Pooled. Programmatic monthly and API-key caps are separate. Sources: dust:dust:credit-management, dust:dust:api-keys. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Pool limits/group budgets block further requests; an in-progress message can finish above its starting cap. API calls reject at per-key caps. Optional automatic seat upgrades may increase billed subscriptions. Sources: dust:dust:credit-management, dust:dust:api-keys. - chargeback — Can costs be exported per cost centre? [partial]: Consumption CSV includes groups and identifiers, but group attribution can duplicate usage and is not a guaranteed invoice-ready cost-center chargeback. Sources: dust:dust:analytics. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:analytics, dust:dust:credit-management, dust:dust:api-keys #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Off-by-default beta cost management offers estimated spend and enforced daily caps. Availability: beta Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No small-budget fixture was run. Estimates are configurable cost-sheet values, not a public billing tariff; cost-centre and full invoice reconciliation remain gaps. - cost_visibility — Can admins see cost or consumption per user and group? [partial]: Tracks estimated USD/input/output tokens by user, model, assistant/app; a billed invoice reconciliation or group cost view is not established. Sources: unique-ai:unique-ai:cost. - budgets — Can budgets be set per user or group? [supported]: Company fallback, group and user daily USD caps; user override first, highest applicable group limit next. Sources: unique-ai:unique-ai:cost. - budget_enforcement — Does reaching a budget alert, block or downgrade? [supported]: Before the next call, accumulated daily spend at cap blocks the model call; resets at local midnight. Docs warn caps may break background-job SLAs. Sources: unique-ai:unique-ai:cost. - chargeback — Can costs be exported per cost centre? [partial]: CSV exports contain user/app/assistant/model/token/cost metadata, with privacy controls. Cost-centre attribution is not documented. Sources: unique-ai:unique-ai:cost. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:cost ### ADM-06: Audit logs and compliance export Judgment rule: Record which events are logged (logins, admin changes, prompts, responses, file access, connector queries), retention, export or SIEM streaming, and eDiscovery/legal hold. Use the word audit only with a defined retention and integrity model. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise has documented event logs and SIEM delivery; content logging and legal hold remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust APIs and MCP server; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - admin_events — Are admin and security events logged? [supported]: Enterprise Audit Logs record significant admin/security, user, API-key, system and tool events with timestamps, targets and actor metadata. Sources: dust:dust:audit. - 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? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - siem_export — Can logs stream to a SIEM or be exported? [supported]: CSV export and continuous destinations include Datadog, Splunk, S3, GCS and custom HTTPS. Sources: dust:dust:audit. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: Are eDiscovery and legal hold supported? Audit, analytics and public legal entry points were checked. Prompt/response compliance capture, eDiscovery/legal hold and detailed log-integrity implementation/retention contract were not established. - log_retention — How long are logs kept? [partial]: Enterprise marketing states 365-day audit retention; no underlying report/contract or configurable retention details were retrieved. Sources: dust:dust:enterprise. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:audit, dust:dust:enterprise #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial API audit events, detailed interaction exports and Single-Tenant security-event streaming are documented. A single authoritative retention period for the customer's audit records is not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Audit Logs, Analytics and Single-Tenant Security Events Export availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE for the contracted Single-Tenant deployment; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - API security-event records, detailed prompt/answer interaction exports, SEE replay and generic operational logging are separate sources/data flows. Their public retention figures are not substituted for each other. - No executed customer retention override or legal-hold/eDiscovery fixture was inspected. - admin_events — Are admin and security events logged? [supported]: Event logging covers privileged public/internal API interactions; many self-identity/chat operations are excluded. Basic mode is default; verbose content mode is opt-in. Sources: unique-ai:unique-ai:audit. - content_logging — Can prompts and answers be retained for compliance, and is it configurable? [supported]: Detailed chat interaction exports contain prompts/answers for authorised admins and respect configured privacy. Verbose event logging can include CID but is discouraged. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:audit. - siem_export — Can logs stream to a SIEM or be exported? [supported]: SEE offers Single-Tenant Azure Defender and Activity events via Event Hub to Sentinel/Splunk, seven-day replay. It excludes tenant-level Entra events and is not a prompt-content audit stream. Sources: unique-ai:unique-ai:security-export. - ediscovery — Are eDiscovery and legal hold supported? [unknown]: No public legal-hold/eDiscovery workflow or complete event-log immutability design was established. - log_retention — How long are logs kept? [unknown]: Different sources describe different record scopes. The API event guide gives basic-mode MT events 90 days and ST events five years, including post-termination ST retention. DPA 3.15 says audit logs ten years without mapping its audit-log category to those API events. The generic hosted policy says logging up to one year after termination or longer if legally required. SEE has a separate seven-day Event Hub replay window, not the lifetime of all audit records. No customer agreement or authoritative record-class/precedence mapping was retrieved; the applicable audit retention period is unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-audit, unique-ai:unique-ai:analytics, unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-retention ### ADM-07: Data loss prevention and personal data Judgment rule: Record detection and handling of personal and confidential data before it reaches a model: redaction, masking, blocking, warning. Record integration with Purview, Netskope or similar, and whether filtering runs locally or at a third party. Send a fixture prompt with a Swiss AHV number and IBAN and record the outcome. #### Dust Verification status: No public information found (not-published) Support: not-published We found no public information on this. A missing finding is not evidence that the product lacks the capability. #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial DLP is primarily customer infrastructure and integration; it is not a verified default native redaction feature. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_detection — Is personal data detected in prompts and files? [unknown]: Is personal data detected in prompts and files? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - pii_action — Is it redacted, masked, blocked or only warned? [unknown]: Is it redacted, masked, blocked or only warned? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - custom_patterns — Can admins add custom patterns or terms? [unknown]: Can admins add custom patterns or terms? Unknown. Default prompt/file PII detection, specific redaction/block behaviour, custom patterns, supported Purview/Netskope policies and native AHV/IBAN handling were not established or tested. Data redaction docs concern retention, not PII masking. - dlp_integration — Does it integrate with an existing DLP product? [partial]: Documents customer HTTPS proxy/interceptor DLP and post-chat Analytics API scanning; Compliance Layer says pre-LLM calls can be implemented. Multi-Tenant matrix explicitly excludes DLP integration. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. - filter_location — Where does filtering run? [partial]: Proxy inspection runs in customer egress infrastructure; Analytics API supports customer post-chat inspection. A deployment-specific pre-LLM service may be implemented. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dlp, unique-ai:unique-ai:compliance ### ADM-08: AI policy and guardrails Judgment rule: Record organisation-wide system instructions, acceptable-use notices and acknowledgement, content filters, topic restrictions, AI-output labelling, and admin visibility of policy violations. Separate enforced policy from instructions the model is expected to follow. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Agents have persistent instructions and workspace governance; broad enforced content-policy administration is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins/builders configure agent instructions; an enforced single organization-wide instruction applied to every agent/message was not established. Sources: dust:dust:builder, dust:dust:governance. - usage_notice — Can users be required to accept a usage policy? [unknown]: Can users be required to accept a usage policy? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. - content_filters — Are content filters configurable? [partial]: Image Generation documents NSFW/celebrity safety filtering. Custom organization-wide topic/content rules were not established. Sources: dust:dust:images. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Agent, governance and security pages were checked. Mandatory usage-policy acknowledgement and administrator policy-violation reporting were not established. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:builder, dust:dust:governance, dust:dust:images #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Space instructions/banners and customer-specific login terms are documented. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. - org_instructions — Can admins set organisation-wide instructions? [partial]: Admins set Space-level system instructions and persistent banners. A mandatory organisation-wide instruction hierarchy is not specified. Sources: unique-ai:unique-ai:agent. - usage_notice — Can users be required to accept a usage policy? [supported]: First login requires terms acceptance; custom terms/editing/deactivation depend on MSA eligibility and admin GraphQL role. Acceptance/version data can be exported. Sources: unique-ai:unique-ai:policy. - content_filters — Are content filters configurable? [partial]: Single-tenant Azure prompts pass through Azure content filters; Compliance matrix marks hosted modes with content filtering. Customer filter configuration and scope remain unspecified. Sources: unique-ai:unique-ai:single, unique-ai:unique-ai:compliance. - violation_reporting — Are policy hits visible to admins? [unknown]: Are policy hits visible to admins? Unknown. Org-wide instruction enforcement, customer content-filter policy controls and administrator violation reports are not established. Prompt guidance is not guaranteed enforcement. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:agent, unique-ai:unique-ai:policy, unique-ai:unique-ai:single, unique-ai:unique-ai:compliance ## Data protection and sovereignty ### DATA-01: Hosting location and data residency Judgment rule: Record country or region separately for chat storage, files and indexes, model inference, backups, logs and telemetry, and support access. Name the cloud provider. Record whether residency is default, a paid option or plan-dependent. "EU data boundary" programmes are recorded with their documented exceptions. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial EU workspace and EU model controls are distinct from general hosting and global subprocessing. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - storage_region — Where are chats, files and indexes stored? [partial]: Pricing/security advertise EU or US workspace hosting. Exact cloud provider, storage country and index location were not established. Sources: dust:dust:pricing, dust:dust:security. - inference_region — Where do model calls run, per provider? [supported]: EU credit-priced workspaces using Dust-hosted models can enable EU-hosted models only after all active agents comply. BYOK is outside this setting; not every model is eligible. Sources: dust:dust:eu-models. - backups_logs_region — Where are backups, logs and telemetry? [unknown]: Where are backups, logs and telemetry? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - support_access_region — From where can vendor staff access data? [partial]: The controller privacy policy permits non-EEA access/processing including the US; it does not establish customer-content support access by staff country. Sources: dust:dust:privacy. - swiss_hosting — Is Swiss hosting available? [unknown]: Is Swiss hosting available? Hosting, EU-model and privacy pages were checked. Backup/log/telemetry countries, customer-content support-access geography and Swiss hosting were not established. - residency_plan — Which plan or option provides residency? [supported]: Business and Enterprise list EU/US residency; EU-only model restrictions additionally require EU region and credit pricing with Dust model hosting. Sources: dust:dust:pricing, dust:dust:eu-models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:eu-models, dust:dust:privacy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Documentation offers CH North multitenant hosting and selectable single/customer-hosted regions, with model processing configured separately. The customer's binding residency schedule and full backup/log/support map remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted or customer-hosted platform; separately selected model/tool routes availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Documented options: CH North hosted MT; selected ST/customer region; provider/SKU/tool inference region separately configured; actual contracted boundaries unverified; os=not specified. Limitations: - Available architecture/region options are not a signed residency schedule. Storage, model inference, backups/logs, support access and external tools must be scoped separately. - DPA CH-storage and chosen-location statements are not reconciled by silently treating one as the current customer contract. - storage_region — Where are chats, files and indexes stored? [partial]: The deployment matrix documents Azure Switzerland North for hosted multitenant and chosen supported regions for Single Tenant. Tenant storage includes PostgreSQL, documents and vector data. These are configuration options; no customer-specific storage schedule was inspected. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-keys. - inference_region — Where do model calls run, per provider? [partial]: The model catalogue separates Azure regional/Data Zone/Global SKUs and external provider routes, with some Swiss deployments and some global-only services. Actual selected provider/SKU/tool routing must be configured for the contracted deployment. CH storage is not a verified CH inference guarantee. Sources: unique-ai:unique-ai:review2-models, unique-ai:unique-ai:deepresearch. - backups_logs_region — Where are backups, logs and telemetry? [partial]: Single-tenant backup resources follow the configured landing-zone design and SEE sends events to a separately selected consumer region. An exhaustive physical replica/backup/log/telemetry country matrix was not retrieved. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - support_access_region — From where can vendor staff access data? [unknown]: The public DPA gives need-to-know access controls and customer-controlled on-premises support, but not an exhaustive physical country list for vendor/subprocessor support access. Office addresses are not used as support-access locations. - swiss_hosting — Is Swiss hosting available? [partial]: CH North is a documented hosted-MT option, and selected-region ST can be Swiss. This records available deployment options, not the customer's end-to-end storage/inference/support contract. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models. - residency_plan — Which plan or option provides residency? [unknown]: DPA 6.1 says storage stays in Switzerland, while its Appendix A allows a client-chosen Microsoft location and current platform docs offer selected jurisdictions. No current customer MSA, precedence clause or deployment schedule was inspected to resolve the binding scope. A contractual CH-wide residency commitment is not asserted. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:security-export, unique-ai:unique-ai:deepresearch ### DATA-02: Deployment options Judgment rule: Record multi-tenant SaaS, dedicated single-tenant instance, deployment in the customer's cloud account, on-premise and air-gapped as separate options with plan and availability. Record which features are missing in each mode, who operates it, and the documented seat or contract threshold for each mode, which can differ from the enterprise plan threshold (e.g. dedicated SaaS from 2,000 seats, own cloud from 5,000). A local-network connector or gateway that reaches on-prem data from a vendor-hosted platform is KNOW-03, not on-premise deployment. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Business and Enterprise single-tenant offers are public; supported customer-operated whole-platform modes are unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace, Dust Enterprise single-tenant deployment; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=not specified; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - multi_tenant_saas — Is a shared SaaS offered? [partial]: Business is a self-serve hosted workspace; exact shared-infrastructure isolation architecture is not documented in the checked pages. Sources: dust:dust:pricing, dust:dust:privacy. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [supported]: Enterprise pricing advertises single-tenant deployment. Numerical seat/spend minimum, supported countries and operating terms were not established. Sources: dust:dust:pricing. - 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? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - 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? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - air_gapped — Can it run without internet access? [unknown]: Can it run without internet access? Pricing, security and the public repository were checked. Customer-cloud, whole-platform on-premise/air-gapped support and their thresholds were not established; MIT source alone does not promise a supported product deployment. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Business/Enterprise packaging differs in connectors, MCP, Spaces, APIs and governance. No customer-operated hosting feature-parity contract was established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:privacy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current docs offer shared SaaS, dedicated instances, customer cloud and customer-operated on-premise/air-gapped modes. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No deployed tenant was inspected. Seat/contract thresholds and an exhaustive offline feature-parity matrix remain unknown; docs establish an option, not universal entitlement. - multi_tenant_saas — Is a shared SaaS offered? [supported]: Installation overview lists Multi Tenant on Unique cloud. Sources: unique-ai:unique-ai:install. - dedicated_instance — Is a dedicated single-tenant instance offered, from what size? [partial]: Unique-managed Single Tenant has its own Azure landing zone separated from other customers. Minimum seats/contract value are unpublished. Sources: unique-ai:unique-ai:single. - customer_cloud — Can it run in the customer's own cloud account, from what size? [partial]: Operator guide documents deployment in customer cloud account with Unique software/support; cloud-specific rollout is contracted. Sources: unique-ai:unique-ai:operators. - on_premise — Can the whole platform run on customer infrastructure, from what size? [partial]: Customer provisions/manages infrastructure on own premises, may run own models and can exclude Unique access. Minimum commitment not published. Sources: unique-ai:unique-ai:onpremsecurity. - air_gapped — Can it run without internet access? [partial]: IT-operator overview explicitly offers a full air-gapped on-premise deployment. Compatibility and feature limitations depend on customer setup. Sources: unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity. - mode_feature_gaps — Which features are missing outside SaaS? [partial]: Compliance matrix separates SSO/content filter/DLP/PAM/key capabilities by mode. Azure Chat Code Execution/voice and external web/providers require those services and cannot be assumed in an isolated environment. Sources: unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:install, unique-ai:unique-ai:single, unique-ai:unique-ai:operators, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance, unique-ai:unique-ai:code, unique-ai:unique-ai:voice ### DATA-03: Training use and provider retention Judgment rule: Record whether customer content trains vendor or provider models, by plan and default; zero-data-retention arrangements with model providers; abuse-monitoring retention and human review; and the model provider's terms that apply. A "no training" claim on a marketing page is `vendor-claimed` until the contract or DPA says so. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust publishes no-training and provider-retention claims; the customer DPA was not retrieved. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Controller privacy-policy scope is distinct from processor DPA coverage. - vendor_training — Does the vendor train on customer content? [partial]: The security page claims customer data is never used for model training. This remains vendor-claimed because no customer DPA/contract clause was retrieved. Sources: dust:dust:security. - provider_training — Do model providers train on it under this product's contracts? [partial]: The privacy policy names OpenAI, Anthropic, Mistral, Google and Fireworks as prohibited from training on customer/personal content; BYOK arrangements need separate confirmation. Sources: dust:dust:training-policy. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [partial]: The policy states providers do not log Customer Content for human review or save it to disk. Exception/abuse-retention periods were not established from customer contracts. Sources: dust:dust:training-policy. - zero_retention — Is zero data retention available, and on which plan? [partial]: Security and privacy pages assert provider zero retention, but applicable plan/model exceptions were not contract-verified. Sources: dust:dust:security, dust:dust:training-policy. - human_review — Can provider staff review content? [partial]: The published policy says listed providers do not log Customer Content for human review. This is a vendor assertion, not an independently reviewed model-provider contract. Sources: dust:dust:training-policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:training-policy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Hosted Azure documentation says no model training and disabled Microsoft prompt storage/human review; other provider routes require separate terms. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No signed Azure amendment was inspected. Retention and review conditions for Anthropic, Gemini, Together, xAI and direct OpenAI research remain unverified; do not generalise the Azure-only policy. - vendor_training — Does the vendor train on customer content? [supported]: Hosted retention policy says no customer data is used for AI/neural-network training. Public terms allow service development and anonymised metadata use; that is not a blanket prohibition of all secondary processing. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms. - provider_training — Do model providers train on it under this product's contracts? [partial]: Hosted Azure deployment is separate from public OpenAI and training is excluded. Other catalogue providers/direct OpenAI research need their applicable customer terms. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch. - provider_retention — How long do model providers keep prompts, including for abuse monitoring? [supported]: For hosted Azure OpenAI, documents/prompts/answers process in memory only, with logging/human-review opt-out. Ordinary application chats persist in Unique databases. Sources: unique-ai:unique-ai:retention. - zero_retention — Is zero data retention available, and on which plan? [partial]: Hosted Azure model calls use no provider content storage per opt-out; this is not zero retention of Unique application history, logs or other provider routes. Sources: unique-ai:unique-ai:retention. - human_review — Can provider staff review content? [partial]: Hosted Azure guide says Microsoft prompt/response human review is disabled. Vendor staff need-to-know access and alternate model-provider review conditions are separate. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:retention, unique-ai:unique-ai:terms, unique-ai:unique-ai:models, unique-ai:unique-ai:deepresearch, unique-ai:unique-ai:dpa ### DATA-04: Retention and deletion Judgment rule: Record default retention for chats, files, indexes and logs; admin-configured retention; user deletion; deletion after contract end; and deletion confirmation. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Some user deletion and memory retention behavior is documented; tenant-wide retention schedules remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - default_retention — What is retained and for how long by default? [partial]: Agent memories persist until manually deleted. This does not define default retention for all conversations, files, indexes or logs. Sources: dust:dust:memory. - admin_retention — Can admins set retention periods? [partial]: Enterprise pricing offers custom data retention; periods, deletion mechanics and exceptions were not retrieved. Sources: dust:dust:pricing. - user_deletion — Can users delete their chats and files permanently? [partial]: Users can delete conversations and agent memories. Backup erasure timing and all attached-file deletion behavior were not established. Sources: dust:dust:delete-chat, dust:dust:memory. - contract_end_deletion — What is deleted at contract end, and when? [unknown]: What is deleted at contract end, and when? Conversation/memory docs, Enterprise pricing and unreadable legal entry points were checked. Contract-end erasure timing and complete storage/index/log retention defaults remain unknown. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:memory, dust:dust:pricing, dust:dust:delete-chat #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Chat content clearing, chat uploads, KB documents, contract-end content deletion, recoverable files, backups and audit records have separate policies. No common purge deadline is established for all copies. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; Chat, Knowledge Base and hosted retention configuration; customer-hosted policy separately controlled availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted storage/provider region; hosted-policy timings not extended to every customer-hosted system; os=not specified. Limitations: - Hosted content policy expressly permits contract-specific variation. Its timings do not define API/DPA audit-record retention. - No tenant configuration, customer MSA, final backup purge or external-provider deletion fixture was inspected. - default_retention — What is retained and for how long by default? [partial]: The chat-upload guide describes an admin-configured expiry, typically two weeks, for chat uploads. Hosted policy lists no minimum for KB/blob/vector/database content. Neither figure defines audit-event retention or proves a tenant's configured default. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:review2-retention. - admin_retention — Can admins set retention periods? [supported]: DATA_RETENTION_IN_DAYS drives the daily midnight chat-content clearing job; unset/zero disables it. This clears the content categories named by the redaction guide, not all uploads, KB, external tool records or audit events. Sources: unique-ai:unique-ai:redaction. - user_deletion — Can users delete their chats and files permanently? [partial]: The redaction guide says deleting a chat removes its Unique chat-content copy and marks the chat record deleted. Separate upload, KB, external-tool, soft-delete, backup and audit policies are not collapsed into that action. Sources: unique-ai:unique-ai:redaction. - contract_end_deletion — What is deleted at contract end, and when? [partial]: For Unique-hosted ordinary content, the published policy states a standard 30-day post-termination period unless the customer contract differs. It separately describes recoverable files for 30 days after deletion and database backups for two further weeks. DPA 6.1 requires return/deletion subject to legal record-keeping. Audit-log classes and their contractual lifetime remain unknown under ADM-06; this is not a deadline for deletion of every copy. Sources: unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:files, unique-ai:unique-ai:redaction, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-dpa ### DATA-05: Sub-processors and foreign-law exposure Judgment rule: Record the published sub-processor list with countries, change-notification rules, the vendor's and parent company's jurisdiction, transfer mechanisms (EU-US Data Privacy Framework, Swiss-US DPF, SCCs) and the vendor's documented position on foreign government access requests (e.g. US CLOUD Act). Record facts, not a legal assessment. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust identifies a French operating entity; customer subprocessor inventory and notice rules remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - subprocessor_list — Is a dated sub-processor list published? [unknown]: Is a dated sub-processor list published? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: Which countries do sub-processors operate in? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - change_notification — Are customers notified of sub-processor changes? [unknown]: Are customers notified of sub-processor changes? The privacy policy refers to a Sub-Processors list, but the official Terms/Notion and trust-center routes were not readable. A dated customer-processor list, complete countries and change-notification rules were not established. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The public policy identifies Permutation Labs at a Paris, France address. A separate parent company or controlling entity was not established. Sources: dust:dust:privacy. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [partial]: For its controller processing, the privacy policy describes adequacy or EU SCC safeguards for non-EU transfers, including the US. Customer processor transfer terms were not retrieved. Sources: dust:dust:privacy. - government_access_policy — Is there a published government-access or transparency policy? [partial]: The controller policy allows legally required disclosure to authorities; a dedicated government-request transparency policy for customer content was not established. Sources: dust:dust:privacy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The dated public DPA lists Microsoft, but a complete applicable current subprocessor/country schedule for all contracted model/tool routes was not retrieved. A technical provider catalogue is not substituted for that legal schedule. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; current platform infrastructure and enabled model/tool integrations availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Actual customer provider/country/transfer schedule unverified; os=not specified. Limitations: - The provider catalogue establishes technical choices, not each party's processor role or the legal schedule for a customer contract. - No sales contact, executed current MSA or nonpublic schedule was obtained. - subprocessor_list — Is a dated sub-processor list published? [unknown]: The July 2025 public DPA Appendix A lists Microsoft for infrastructure, Cognitive/Azure OpenAI and email. The current technical catalogue offers other provider/tool routes, which may have different contractual roles. No applicable complete current legal schedule or executed customer supplement was retrieved; the Microsoft-only list is not presented as complete. - subprocessor_countries — Which countries do sub-processors operate in? [unknown]: DPA Appendix A names CH or a client-chosen Microsoft location; technical model routes separately include regional and global processing. A complete current legal provider/country and support-access schedule for the chosen deployment was not retrieved. - change_notification — Are customers notified of sub-processor changes? [unknown]: No applicable current processor-change notification/objection clause for the customer's full provider schedule was retrieved from the DPA or current contract-access documentation. - parent_jurisdiction — Which jurisdiction governs the vendor and its parent? [partial]: The current contact page identifies Unique AI AG in Switzerland and regional entities. The public DPA uses Unique AG. Ultimate parent/beneficial-owner jurisdiction and a customer-specific contracting entity were not independently established. Sources: unique-ai:unique-ai:contact, unique-ai:unique-ai:review2-dpa. - transfer_mechanism — Which transfer mechanism applies to non-EU/CH processing? [unknown]: No complete customer-content transfer-instrument mapping per non-CH/EU provider was retrieved. The website visitor privacy policy is not substituted for customer-content terms. - government_access_policy — Is there a published government-access or transparency policy? [unknown]: No current customer-content government-request/transparency policy was retrieved for the complete contracted provider chain. General banking/DPA assurances do not establish such a policy. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:review2-models, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:contact ### DATA-06: Contracts and regulatory coverage Judgment rule: Record DPA availability and form (click-through, negotiable), reference to Swiss revDSG and GDPR, governing law and court, EU AI Act documentation (provider or deployer role, transparency materials), and sector-specific materials (FINMA outsourcing, banking secrecy, public sector). No compliance verdict. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise offers custom MSA/DPA terms, while the underlying legal materials were inaccessible. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - dpa — Is a DPA available, and is it negotiable? [partial]: Enterprise pricing explicitly offers custom MSA/DPA terms. The form, sign-up incorporation and negotiability boundaries were not inspected. Sources: dust:dust:pricing. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: Marketing and privacy materials reference GDPR; explicit Swiss revDSG coverage in the customer DPA was not established. Sources: dust:dust:security, dust:dust:privacy. - governing_law — Which law and court govern the contract? [unknown]: Which law and court govern the contract? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - ai_act_materials — Is EU AI Act documentation provided? [unknown]: Is EU AI Act documentation provided? Official Terms & Policies redirects to a Notion page that returned no readable terms; trust.dust.com also exposed no report text. Governing law/court and EU AI Act technical/role materials were not established. - sector_materials — Are FINMA or other sector materials provided? [partial]: Security marketing says the service enables HIPAA compliance. A BAA, FINMA or banking-secrecy outsourcing pack was not retrieved. Sources: dust:dust:security. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:security, dust:dust:privacy #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial A public DPA and finance-specific compliance material are available; actual contractual amendments were not inspected. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - DPA negotiability and signed sector amendments, product-specific EU AI Act roles and exact sector assurance scope remain unverified. This records materials, not a compliance verdict. - dpa — Is a DPA available, and is it negotiable? [partial]: DPA accepts click-through/use or signature and defines Unique as processor for hosted MT/ST. Negotiability is not specified. Sources: unique-ai:unique-ai:dpa. - revdsg_gdpr — Does the DPA cover revDSG and GDPR? [partial]: DPA addresses GDPR, Swiss FDPIC oversight and MSA-defined laws; Compliance Layer identifies nFDAP/Swiss M329 amendment. Exact signed revDSG/GDPR scope requires MSA. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance. - governing_law — Which law and court govern the contract? [supported]: DPA 7 specifies Swiss substantive law and Zürich 1 courts unless mandatory GDPR/MSA otherwise. Public ToS similarly names Swiss law. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms. - ai_act_materials — Is EU AI Act documentation provided? [partial]: Trust centre describes per-use-case conformity assessments; ISO42001 and AI governance material are public. A complete provider/deployer AI Act technical file is not established. Sources: unique-ai:unique-ai:trust, unique-ai:unique-ai:compliance. - sector_materials — Are FINMA or other sector materials provided? [partial]: Compliance Layer names Microsoft M453 FINMA audit-rights amendment, M744 professional/banking secrecy and M329 CH-DPA for Unique-hosted deployments. Actual annexes and current signed scope are not public. Sources: unique-ai:unique-ai:compliance. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:compliance, unique-ai:unique-ai:terms, unique-ai:unique-ai:trust ### DATA-07: Certifications and attestations Judgment rule: Record each certificate or report separately: ISO 27001, 27017, 27018, 27701, 42001; SOC 2 Type I/II with period; BSI C5; TISAX; national schemes. Record issuer, scope (which product and entity), validity and access route. A cloud provider's certificate does not certify the product. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial SOC 2 Type II is claimed publicly, without a verified report or certificate. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - iso_27001 — ISO 27001 with scope and validity? [unknown]: ISO 27001 with scope and validity? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - soc2 — SOC 2 type, period and covered service? [partial]: Dust security/pricing claim SOC 2 Type II. Auditor, reporting period and exact service scope were not verified. Sources: dust:dust:security, dust:dust:pricing. - c5 — BSI C5 attestation? [unknown]: BSI C5 attestation? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - other_certifications — Which other certificates (27701, 42001, TISAX)? [unknown]: Which other certificates (27701, 42001, TISAX)? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. - report_access — How can customers obtain reports? [partial]: The security page directs customers to trust.dust.com; underlying reports were not accessible in this public source pass. Sources: dust:dust:security. - pentest — Are independent penetration test summaries available? [unknown]: Are independent penetration test summaries available? Security/pricing and the trust center were checked. ISO 27001, C5, other scoped certificates and independent penetration-test summaries were not established; no evidence is certificate-verified. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:pricing #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial New public 2026 ATTESTA renewals establish ISO27001 and ISO9001 validity to 31 May 2029; the public TÜV SÜD ISO42001 certificate runs to 6 March 2028. SOC2 Type2 is vendor-documented, with full report evidence NDA-gated. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=ATTESTA 10 June 2026 renewals; TÜV SÜD 7 March 2025 certificate; plan=Contracted Unique AI platform; platform assurance; certificates cover the named legal entity and stated scopes, not every module/provider availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Certificates name Unique AG, Zurich, Switzerland; module/provider coverage depends on the stated audit scope; os=not specified. Limitations: - Current ISO27001/9001 evidence is the 2026 renewal plus matching register entries; the stale website-linked PDF is not used to deny current certification. - SOC chronology and access process are vendor-documented, not a reviewed independent SOC report. Certificate scopes are entity-specific and not a universal module/provider assurance. - iso_27001 — ISO 27001 with scope and validity? [supported]: Inspected the 2026 ATTESTA Schweizer Zertifizierungsgesellschaft AG ISO27001:2022 certificate for Unique AG, registration 223-06-018.I. It covers software development/operation/trading/distribution and IT services, is issued 10 June 2026 after 4 June surveillance and expires 31 May 2029. The certificate-linked public register matches the number and expiry. The marketing-linked 2025 PDF is an older artifact, not the current renewal. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs. - soc2 — SOC 2 type, period and covered service? [partial]: The dedicated SOC page documents Type1 in December 2023 followed by Type2 in January 2025. This explains the historical Type1 references rather than proving an ongoing Type1-only state. Current Type2 status is a vendor claim; the auditor, actual report period and service/control scope were not inspected because the full report is NDA-gated. Sources: unique-ai:unique-ai:review2-soc. - c5 — BSI C5 attestation? [unknown]: No public BSI C5 attestation was retrieved from the certification pages/trust centre or targeted first-party search. - other_certifications — Which other certificates (27701, 42001, TISAX)? [partial]: Inspected ATTESTA ISO9001:2015 renewal 223-06-017.Q for the same Unique AG software/IT scope, expiring 31 May 2029, matched in the public register. Separately inspected TÜV SÜD South Asia ISO42001:2023 certificate 99 420 00001, valid 7 March 2025 to 6 March 2028, for development/deployment of financial-services SaaS using foundation or client models. Current full ISAE/FINMA report scope was not inspected. Sources: unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:iso42001. - report_access — How can customers obtain reports? [supported]: The ISO documentation provides public certificate downloads. It says the ISO27001 Statement of Applicability requires a valid NDA. The dedicated SOC page likewise makes the audit report/certificate available on request after NDA. No NDA or sales request was made. Sources: unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:review2-soc. - pentest — Are independent penetration test summaries available? [partial]: The public DPA describes internal/external security testing and the trust page describes tests/bug bounty. An independent penetration-test report, current scope or summary was not inspected. Sources: unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-iso27001, unique-ai:unique-ai:review2-iso9001, unique-ai:unique-ai:review2-iso-register, unique-ai:unique-ai:review2-iso-docs, unique-ai:unique-ai:iso42001, unique-ai:unique-ai:review2-soc, unique-ai:unique-ai:review2-dpa, unique-ai:unique-ai:trust ### DATA-08: Encryption and key control Judgment rule: Record encryption at rest and in transit, customer-managed keys (BYOK/HYOK), key location, and private networking (private link, IP allow-lists, VPN). #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust claims AES-256/TLS and advertises Enterprise single tenancy; customer key custody is unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - encryption_at_rest — Is data encrypted at rest? [supported]: The security page states AES-256 at rest and TLS in transit; this is a vendor claim. Sources: dust:dust:security. - customer_managed_keys — Can the customer manage or hold the keys? [unknown]: Can the customer manage or hold the keys? Security, pricing and network/MCP docs were checked. Customer-managed/held data-encryption keys and key-location guarantees were not established. Provider API BYOK is not encryption-key custody. - private_networking — Is private connectivity or IP restriction available? [partial]: Custom MCP servers can restrict access and use documented static egress on verified domains. This is tool connectivity, not proof of private connectivity to the whole service. Sources: dust:dust:tools. - tenant_isolation — How are customers separated in shared SaaS? [partial]: Enterprise offers single tenancy; shared Business tenancy and lower-level isolation mechanics were not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:security, dust:dust:tools, dust:dust:pricing #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Deployment guides document encryption, isolated Single Tenant resources and optional IP filtering. Exact current MT PMK/CMK/HSM configuration and key sizes are not established across the conflicting pages. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; hosted MT/ST encryption and optional customer-controlled self-hosting availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=Contracted Azure tenant/storage/backup region; actual key-vault/HSM location unverified; os=not specified. Limitations: - No exact RSA/HSM key size or actual MT PMK/CMK design is asserted. A customer-specific deployment/key diagram and key-vault region were not inspected. - Customer-generated imported keys held by Unique do not establish customer-exclusive key custody; full control is a separate self-hosting option. - encryption_at_rest — Is data encrypted at rest? [partial]: The compliance matrix documents encryption at rest and in transit across deployment options, with AES256/TLS1.2+ in its controls text. No exact current RSA key size is asserted: the ST architecture says 2048-bit RSA-HSM while the hosted retention page says 4096-bit. An implementation-specific key design was not retrieved. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention. - customer_managed_keys — Can the customer manage or hold the keys? [partial]: The infrastructure key guide allows a customer-generated key to be imported for a Unique-hosted Single Tenant, with Unique holding/managing it. It directs clients needing exclusive control of all storage keys to customer self-hosting. This is not HYOK or exclusive customer custody in Unique hosting. Actual MT PMK/CMK/HSM configuration is unknown because the key guide and hosted retention matrix disagree. Sources: unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:review2-retention. - private_networking — Is private connectivity or IP restriction available? [partial]: The Single-Tenant WAF supports optional IP blocking. The separate SEE consumer endpoint is public TLS with optional allow-list and no standard private endpoint/peering. These are distinct scopes; other private-link options for the customer deployment were not verified. Sources: unique-ai:unique-ai:review2-single, unique-ai:unique-ai:security-export. - tenant_isolation — How are customers separated in shared SaaS? [supported]: The Single-Tenant architecture describes a separate customer landing zone under Unique's subscription, isolating its storage/processing from other customers. This documents that ST architecture, not the isolation configuration of every hosted or customer-managed instance. Sources: unique-ai:unique-ai:review2-single. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-compliance, unique-ai:unique-ai:review2-single, unique-ai:unique-ai:review2-retention, unique-ai:unique-ai:review2-keys, unique-ai:unique-ai:security-export ### DATA-09: Professional secrecy Judgment rule: For professional secrecy holders (Berufsgeheimnisträger: lawyers, doctors, auditors, tax advisers) under § 203 StGB (DE) and Art. 321 StGB (CH), record whether the vendor signs a contractual secrecy undertaking or a § 203 agreement that binds its staff and its sub-processors; whether this comes as a dedicated offering or a paid add-on, and on which plan; who can access content in plain text (vendor staff, sub-processors, model providers); and the documentation provided. A DPA or a no-training clause alone is not a secrecy undertaking. Banking secrecy and FINMA outsourcing belong to DATA-06, not here. Record contract facts, not a legal assessment. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Public personnel/model handling statements exist; an explicit professional-secrecy contract and subprocessor flow-down remain unverified. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Dust Business/Enterprise public policy; Enterprise and BYOK routes differ; add_ons=none stated; deployment_mode=multi-tenant-saas; region=EU/US storage and provider routes; no DE/CH-specific secrecy contract verified; os=not specified. Limitations: - No-training, ZDR marketing/policy assertions, EU hosting and a general privacy policy do not establish 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]: The public security and platform privacy pages do not establish a signed §203 StGB/Art321 StGB professional-secrecy undertaking covering Dust staff. The Terms/Policies link did not expose readable contractual text in this pass. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The privacy policy describes service-provider data-protection agreements and model no-training/retention conditions, but no dedicated professional-secrecy undertaking or its binding subprocessor flow-down was retrieved. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No publicly documented German/Swiss professional-secrecy-specific plan or paid add-on was established. Enterprise single-tenancy/EU model options are not treated as such a contractual undertaking. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: The platform privacy policy limits personnel access to authorized staff and says customer context is processed by selected foundation-model providers; it asserts no provider disk retention/human-review logging. This vendor statement does not establish the complete customer-content plaintext access matrix, support countries, private contracts or every BYOK/MCP/tool route. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: Reviewed public security, privacy, EU-hosted model documentation and Enterprise plan scope plus targeted first-party secrecy search. Trust Center content was not available and Terms/Policies routed to unreadable external content. No public §203/Art321 template or professional-body guidance was retrieved. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:privacy, dust:dust:training-policy, dust:dust:eu-models #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Unique documents general staff/external-party access controls and customer-controlled on-premises access. A professional-secrecy undertaking under § 203 StGB or Art. 321 StGB, its subprocessor flow-down and qualifying plan/add-on remain unverified. Financial-sector banking-secrecy amendments are recorded separately under DATA-06. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI; profession-specific eligibility and fees unpublished; add_ons=none stated; deployment_mode=not specified; region=Contracted hosting jurisdiction; customer-controlled on-premises access described separately from Unique-hosted access; os=not specified. Limitations: - No executed professional-secrecy undertaking or § 203 / Art. 321 contract was inspected. General DPA confidentiality is not treated as such an undertaking. - The M744 professional-secrecy wording appears in a banking-secrecy/financial-services framework; no inference is made to lawyers, doctors, auditors or tax advisers. - Customer-controlled on-premises access does not establish the same access conditions for Unique-hosted deployments or all model-provider routes. Full plaintext-access mapping remains unknown. - secrecy_undertaking — Does the vendor sign a secrecy undertaking or § 203 StGB / Art. 321 StGB agreement covering its own staff? [unknown]: No public Unique AI-specific § 203 StGB or Art. 321 StGB secrecy undertaking covering staff was located in the DPA, compliance documentation or targeted first-party search on 21 October 2026. The DPA confidentiality commitment alone does not establish a professional-secrecy undertaking. No executed or negotiated customer agreement was inspected. - subprocessor_coverage — Does the undertaking extend to its sub-processors, and is that documented? [unknown]: The DPA says employees, contractual subprocessors and other service providers are bound to confidentiality of sensitive information. A professional-secrecy-specific obligation extending through the subprocessor/model-provider chain was not verified. The Microsoft M744 banking-secrecy amendment mentioned in the financial-services framework is not counted as evidence of § 203 / Art. 321 coverage for professional secrecy holders. - secrecy_offering — Is it a dedicated offering or add-on, and on which plan? [unknown]: No qualifying professional-secrecy plan, dedicated offering, add-on tariff or named eligibility rule was located. The documented financial-services amendments and general deployment choices do not establish a separate § 203 / Art. 321 offering. Contract-specific terms and fees remain unknown. - content_access — Who can access content in plain text: vendor staff, sub-processors, model providers? [partial]: DPA Appendix B permits employees or external parties access to personal/confidential information on a need-to-know basis. For on-premises support, customers control remote connections and Unique staff cannot access a customer system without customer knowledge or full active participation. The on-premises architecture also allows operation without any Unique access under customer control. These sources do not exhaustively identify plaintext access at each hosted subprocessor/model provider or profession-specific access conditions. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity. - secrecy_documentation — Is the offering publicly documented (contract template, data-flow description, professional-body guidance)? [unknown]: A public DPA and on-premises architecture describe confidentiality and access controls, but no profession-specific secrecy template or professional-body guidance was located. The compliance page describes Microsoft M453/M744/M329 in a financial-services context; those banking/FINMA disclosures belong to DATA-06 and do not establish the missing professional-secrecy contract. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:dpa, unique-ai:unique-ai:onpremsecurity, unique-ai:unique-ai:compliance ## Commercials and vendor ### VEN-01: Pricing model and list prices Judgment rule: Record pricing unit (per seat, per active user, usage-based, platform fee, hybrid), list prices per plan in original currency with date, included usage and credits, add-on prices (connectors, agents, image generation) and overage rates. Cite public prices or dated quotes. Per-seat versus usage is a fact, not a quality judgment. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business seat prices are public; only the documented prepaid route is described here, while conflicting Business overage eligibility remains unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Free/Pro/Max seat list pricing; Enterprise quoted pool and programmatic contracts are separate; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - Do not present Business PAYG as established; retain list seat prices separately from the unresolved overage route. - pricing_unit — What is the pricing unit? [partial]: Business publishes per-seat subscriptions and included credits. Detailed Credit management describes prepaid Business top-ups and Enterprise PAYG; pricing FAQ separately describes enabled Business workspace overage, so Business post-allocation billing eligibility is unverified. Sources: dust:dust:pricing, dust:dust:credit-management. - list_prices — What are list prices per plan, with date and currency? [supported]: As retrieved 2026-10-21, ex-VAT Business Free is EUR 0; Pro EUR 30/month or EUR 24/month annually; Max EUR 150/month or EUR 120/month annually. Enterprise is quote-only. Sources: dust:dust:pricing. - included_usage — What usage is included? [supported]: Free has 500 lifetime credits, Pro 8,000/month and Max 40,000/month. Monthly credits do not roll over; Workspace seats draw from a contracted pool. Sources: dust:dust:credits, dust:dust:seats. - add_ons — Which features cost extra? [partial]: Business limits include three connectors, five remote MCP servers and five Spaces. Enterprise adds unlimited connector/MCP packaging, SCIM, audit, retention and support. Individual add-on tariffs are not published. Sources: dust:dust:pricing. - overage — What do usage beyond limits and premium models cost? [unknown]: Effective Business post-allocation billing is unknown: current pricing FAQ allows Pro/Max workspace overage, while Credit management reserves PAYG for Enterprise and describes prepaid Business top-ups. The USD0.01/credit Business programmatic rate does not resolve whether interactive overage is PAYG or prepaid. No account/contract test resolved this. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:credit-management, dust:dust:credits, dust:dust:seats #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Applicable current platform pricing unit, list tariff, included usage and overages remain unknown. A separately documented Single-Tenant SEE consumption/engineering charge is retained; legacy sales-conversation terms are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform subscription and separately enabled Single-Tenant SEE availability and deployment/provider configuration depend on the customer agreement; add_ons=SEE scope only where contracted; deployment_mode=not specified; region=Vendor currency and applicable invoicing terms not established for the platform; SEE guide separately quotes indicative CHF consumption; os=not specified. Limitations: - The SEE cost finding is scoped only to that Single-Tenant integration. It does not price the platform subscription or all modules. - The 2023 sales-conversation ToS is excluded as evidence of current Unique AI commercial terms; no sales quote or private contract was requested. - pricing_unit — What is the pricing unit? [unknown]: No applicable current platform MSA/order form or tariff establishing seat, active-user, platform or usage pricing units was retrieved. The public 18 October 2023 ToS defines a sales-conversation intelligence service, so its subscription/Order Form clauses are not applied to current Unique AI. - list_prices — What are list prices per plan, with date and currency? [unknown]: No applicable current platform list tariff, tier names or primary invoicing currency was retrieved from platform/contract documentation or targeted first-party search. - included_usage — What usage is included? [unknown]: No applicable current platform agreement specifying included model tokens, storage or module allowances was publicly retrieved. - add_ons — Which features cost extra? [partial]: Single-Tenant SEE passes through Azure consumption without markup; guide observes CHF20-50/month/environment, not a fixed quote, with initial engineering at agreed rates. Other module charges are unpublished. Sources: unique-ai:unique-ai:security-export. - overage — What do usage beyond limits and premium models cost? [unknown]: No applicable current platform overage or premium-model sales tariff was retrieved. Cost-management model estimates are not substituted for a customer sales tariff. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:security-export, unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### VEN-02: Scenario cost Judgment rule: Price three workloads for 12 months: 200, 1,000 and 5,000 users with a disclosed light/regular/power usage mix, in CHF and EUR excluding VAT. Include licences, platform fees, add-ons, model usage and, for self-hosted options, a stated operating assumption. Separate fixed, variable, included and unknown costs. No invented discounts. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21 apply; all three target seat counts require unpriced Enterprise terms. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - cost_200 — Year-one cost at 200 users? [unknown]: Year-one cost at 200 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_1000 — Year-one cost at 1,000 users? [unknown]: Year-one cost at 1,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - cost_5000 — Year-one cost at 5,000 users? [unknown]: Year-one cost at 5,000 users? For 200, 1,000 and 5,000 users over 12 months, the shared 60/30/10 message/token workload has no public applicable Enterprise seat quote or complete credit tariff. CHF/EUR ex-VAT totals remain unknown. ECB 2026-10-20 rates are recorded; the small-team Business price is not multiplied beyond its stated 100-person scope. - variable_share — Which part depends on usage? [supported]: Consumption adds token and action credits, including sub-agent work. Programmatic use and Enterprise PAYG draw from workspace pools separately from personal seat allocations. Sources: dust:dust:credits, dust:dust:credit-management. - unknown_parts — Which costs could not be priced? [supported]: Business is scoped to 100 people, so 200/1,000/5,000 seat Enterprise fees, committed pool and PAYG tariffs are unknown. The default Standard auto list is published, but a complete token-to-credit tariff is not, so no proxy replaces vendor-billed usage. Sources: dust:dust:pricing, dust:dust:models, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:credits, dust:dust:credit-management, dust:dust:pricing, dust:dust:models, dust:dust:fx-ecb #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial ALM-14 shared cost assumptions v1.4, 2026-10-21. Public enterprise pricing is insufficient for the required 200/1,000/5,000-user annual totals. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_200 — Year-one cost at 200 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_1000 — Year-one cost at 1,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - cost_5000 — Year-one cost at 5,000 users? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - variable_share — Which part depends on usage? [unknown]: ALM-14 shared cost assumptions v1.4, 2026-10-21. Horizon 12 months, list prices excluding VAT, no invented discounts. Mix 60% light at 100 messages/user/month, 30% regular at 400, 10% power at 1,500. Where model usage is separately billed, each message has 3,000 input and 600 output tokens, giving 990k input plus 198k output per user/month. At 200/1,000/5,000 users this is 198m/990m/4.95bn input and 39.6m/198m/990m output per month. All three seat counts require an unpublished enterprise/custom price; no quote was requested. CHF and EUR ex-VAT totals, fixed charges, variable charges and add-ons remain unknown. FX dated 2026-10-20: EUR 1 = CHF 0.9237 and USD 1.1215; CHF to EUR divide by 0.9237, USD to EUR divide by 1.1215, source ECB. No numeric conversion or proxy model tariff is applied because there is no applicable public enterprise base/usage rate. - unknown_parts — Which costs could not be priced? [supported]: Subscription/order pricing, usage billing, provider contracts, deployment operation, connectors, execution, training and support charges are not publicly priced. SEE consumption example alone cannot price the platform. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:platform, unique-ai:unique-ai:security-export, unique-ai:unique-ai:ecb-fx ### VEN-03: Evaluation access Judgment rule: Distinguish free tier, self-serve trial, sales-led pilot, paid proof of concept and open-source self-install. Record card requirement, duration, seat limit, and which features (SSO, connectors, admin) the trial includes. Map which shared scenarios can be run without sales approval. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial A limited Business free option enables self-serve evaluation; Enterprise features remain contract-scoped. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - free_tier — Is there a free tier for business use? [supported]: Business free supports up to five members with 500 lifetime credits per Free seat. Credits do not reset and a user cannot return to Free after upgrading. Sources: dust:dust:seats. - self_serve_trial — Is a self-serve business trial available? [partial]: The public site offers self-serve free workspace access, not a documented time-limited fully featured Enterprise trial. No card requirement was established. Sources: dust:dust:pricing, dust:dust:seats. - trial_scope — Do trials include SSO, connectors and admin features? [partial]: Business lists up to three connectors/five Spaces/five remote MCP servers and SSO at 5+ seats on demand. SCIM, audit and custom retention are Enterprise. Sources: dust:dust:pricing. - sales_gate — Does meaningful evaluation require sales contact? [supported]: Enterprise terms, pooled credits, advanced governance and support are sales-led; a small-team free evaluation is self-serve. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:seats, dust:dust:pricing #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public route is demo/evaluation by arrangement; self-service trial conditions were not established. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - free_tier — Is there a free tier for business use? [unknown]: Is there a free tier for business use? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - self_serve_trial — Is a self-serve business trial available? [unknown]: Is a self-serve business trial available? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - trial_scope — Do trials include SSO, connectors and admin features? [unknown]: Do trials include SSO, connectors and admin features? Unknown. No permanent business free tier or self-serve trial with duration/card/seat/SSO/connector/admin entitlements was located. No sales contact, login or fixture account was used. - sales_gate — Does meaningful evaluation require sales contact? [partial]: Current platform CTA requests a demo; public baseline ToS says Unique may offer evaluation at its discretion. This does not prove every meaningful evaluation is sales-gated. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:terms ### VEN-04: Contract terms and pricing transparency Judgment rule: Record minimum seats or commitment, contract length, monthly versus annual billing, price-change rules, cancellation and downgrade terms, and invoicing in CHF/EUR. Classify pricing as transparent, partially specified, quote-only or unknown, naming the missing fields. Quote-only pricing is a disclosed constraint. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business monthly and annual subscriptions are public; Enterprise seats are annual and prices contractual. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - minimum_commitment — What seat or spend minimum applies? [partial]: The free option has up to five members and Business targets up to 100 people; Enterprise numerical seat/spend minimum was not established. Sources: dust:dust:pricing, dust:dust:seats. - contract_length — What contract lengths are offered? [supported]: Business offers monthly and annual seats together; Enterprise seats are annual only. Sources: dust:dust:seats. - cancellation — How can the contract be cancelled or reduced? [supported]: Monthly seats unassign immediately with a prorated credit; annual seats return to stock for reassignment and are not refunded when someone leaves. Sources: dust:dust:seats. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [partial]: Prices are displayed in EUR and the privacy policy identifies a French entity; CHF invoicing and the actual invoicing entity/currency were not contract-verified. Sources: dust:dust:pricing, dust:dust:privacy. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [supported]: Partially specified: Business seat prices/credit allowances are public, while Enterprise pricing, complete usage conversion and negotiated terms require a quote. Sources: dust:dust:pricing, dust:dust:credits. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:seats, dust:dust:privacy, dust:dust:credits #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Current platform minimums, term, cancellation and local invoicing remain unknown because the applicable agreement was not publicly retrieved. Current documentation makes legal contracts available on request; legacy sales-conversation renewal clauses are excluded. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration, Unique API and Python SDK; version=not specified; plan=Contracted Unique AI platform; platform commercial agreement; actual agreement not inspected availability and deployment/provider configuration depend on the customer agreement; add_ons=none stated; deployment_mode=not specified; region=CHF/EUR invoicing and legal entity for a specific platform contract unverified; os=not specified. Limitations: - No current customer agreement or sales quote was requested. Contract availability on request does not establish price, term or cancellation conditions. - minimum_commitment — What seat or spend minimum applies? [unknown]: No current platform seat/spend minimum was established from the public contract-access and platform pages. - contract_length — What contract lengths are offered? [unknown]: No applicable current Unique AI agreement establishing subscription duration, renewal term or notice period was retrieved. The 2023 sales-conversation service term is not applied. - cancellation — How can the contract be cancelled or reduced? [unknown]: Current Unique AI cancellation, refund, seat-reduction and nonrenewal rules were not retrieved. The 30-day renewal notice and quantity restrictions from the sales-conversation ToS are excluded. - local_invoicing — Can it be invoiced in CHF or EUR from a European entity? [unknown]: CHF/EUR invoice currency, billing entity and local invoicing eligibility for a current platform contract were not established. - transparency_class — Is pricing transparent, partial, quote-only or unknown? [partial]: The current governance framework says legal contracts and end-user T&Cs are available on request. No applicable public platform list tariff or complete commercial agreement was retrieved. This records an access/transparency gap, not a price or a customer-specific commitment. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin ### VEN-05: Source licence Judgment rule: Record licence per component (client, server, connectors, hosted extensions) and revision. Distinguish OSI open source, source-available with restrictions (branding clauses, user caps), and closed. Repository visibility is not a licence classification. Licences change between releases: record the current terms, and never carry a fork's historical licence over to the upstream product or the reverse. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial The pinned public repository has an MIT root licence; hosted licensing and complete component coverage are separate. Availability: generally-available Delivery: native Scope: surfaces=Public dust-tt/dust repository root licence; version=dust-tt/dust commit2b1a4973af824f8ff970d585c5eb1f40ae76186c; root LICENSE only; plan=Public source component, not Business/Enterprise hosted-service rights; add_ons=none stated; deployment_mode=not specified; region=Repository licence has no deployment-region entitlement; os=not specified. Limitations: - MIT applies to the pinned repository root grant only; dependencies, supported self-host deployment, hosted terms and any closed Enterprise boundary remain unverified. - licence_type — Which licence applies to each component? [partial]: dust-tt/dust root LICENSE is MIT at commit 2b1a4973af824f8ff970d585c5eb1f40ae76186c. This does not classify every dependency or the contracted hosted service. Sources: dust:dust:licence. - branding_restrictions — Do licence terms restrict branding or user counts? [supported]: The MIT root grant requires preserving copyright and permission notices and does not itself impose branding or user-count caps. Sources: dust:dust:licence. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Are enterprise features in a separate closed edition? The pinned root LICENSE and README were retrieved; a complete nested-component licence inventory and separate closed Enterprise edition boundary were not established. Hosted terms were inaccessible. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:licence #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The public reference repository uses restricted Unique License v1, while the Python SDK has an explicit MIT exception. Hosted platform component terms and enterprise-edition boundaries remain unverified. Availability: source-only Delivery: native Scope: surfaces=Unique API and Python SDK, Unique AI Chat and administration; version=Unique-AG/ai commit afa596c9b4b0231895ff70f44029a9a525f746e9; plan=Public reference-code and Python SDK licences; current contracted Unique AI client/server/connector agreement remains unavailable; add_ons=none stated; deployment_mode=not specified; region=Public Unique License v1 specifies Swiss law and Zurich venue; this is not a hosted-service residency claim; os=not specified. Limitations: - The MIT exception applies to unique_sdk, not every directory or the hosted platform. - Root reference-code terms are not substituted for customer platform branding, seat or enterprise-edition conditions. - The 2023 sales-conversation service ToS remains excluded. - licence_type — Which licence applies to each component? [partial]: The public Unique-AG/ai repository at afa596c9b4b0231895ff70f44029a9a525f746e9 defaults to Unique License v1, which restricts commercial use, distribution and modification without written approval. The unique_sdk directory is an explicit MIT exception, confirmed by LICENSE and package metadata. This is a component-level source-available/MIT distinction; current hosted client/server/connector customer terms and a full dependency inventory remain unknown. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026. - branding_restrictions — Do licence terms restrict branding or user counts? [partial]: Unique License v1 requires written approval to modify or redistribute covered reference code; the MIT SDK exception requires retention of copyright/licence notices. A current hosted-platform white-label/logo-removal obligation or a numerical user cap is not established by these public component licences. Sources: unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026. - enterprise_features_closed — Are enterprise features in a separate closed edition? [unknown]: Current closed/open enterprise-edition boundaries were not established from an applicable component licence inventory. Public SDK/repository availability is not proof of the whole platform licence. Rechecked 2026-10-26 in Unique AI governance framework: contract access, Terms and Conditions Administration. No current customer MSA, quote, private schedule or gated contract was requested. The differently scoped 2023 sales-conversation ToS remains excluded. Checked 2026-10-26; agent cross-checked 2026-10-26; check again by 2026-12-25. Sources: unique-ai:unique-ai:review2-governance, unique-ai:unique-ai:review2-terms-admin, unique-ai:unique-ai:reference-licence-20261026, unique-ai:unique-ai:unique-licence-v1-20261026, unique-ai:unique-ai:sdk-licence-20261026, unique-ai:unique-ai:sdk-package-20261026, unique-ai:unique-ai:review2-governance-20261026, unique-ai:unique-ai:review2-terms-admin-20261026 ### VEN-06: Data export and exit Judgment rule: Record admin export of chats, assistants, knowledge bases, prompts and audit logs, formats, export completeness, user self-export, and what survives contract end. Run an admin export on a trial. Exported chats alone do not make assistants and knowledge portable. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business Conversation API and Enterprise Data Source API provide scoped data retrieval; agent export entitlement and complete tenant exit remain unknown. Availability: generally-available Delivery: native Scope: surfaces=Dust APIs and MCP server, Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business Conversation API and web analytics; Enterprise adds Data Source API. Agent-YAML endpoint entitlement is unverified.; add_ons=API keys with appropriate workspace/resource permissions; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Conversation and document retrieval require the corresponding plan and resource permissions. Complete organization coverage, agent-export entitlement and the post-termination retrieval window remain unknown. - chat_export — Can admins export all chats? [partial]: Business pricing includes Conversation API; authorized API users retrieve accessible conversation messages with pagination. This does not establish one-click all-tenant admin export. Sources: dust:dust:get-conversation, dust:dust:pricing. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: The agent-YAML endpoint and public pricing were checked on 2026-10-21. Neither establishes its Business or Enterprise entitlement. Reusable assistant/prompt export for a named plan remains unknown. - knowledge_export — Can knowledge bases and their sources be exported? [partial]: Enterprise pricing adds Data Source API; the documented endpoint retrieves accessible data-source documents as JSON. Complete source/credential/permission portability and an all-tenant export are unverified. Sources: dust:dust:get-document, dust:dust:pricing. - export_format — Are formats documented and machine-readable? [partial]: Business Conversation API and Enterprise Data Source API return JSON for accessible resources. Web analytics separately exports CSV. These formats do not establish complete tenant export; no plan-scoped agent-YAML export is claimed. Sources: dust:dust:get-conversation, dust:dust:get-document, dust:dust:analytics, dust:dust:pricing. - post_termination_window — How long can data be retrieved after termination? [unknown]: How long can data be retrieved after termination? No trial admin exit/export was run; complete tenant coverage and the post-termination retrieval window were not established from the accessible API docs or unreadable contract route. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:get-conversation, dust:dust:pricing, dust:dust:get-document, dust:dust:analytics #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Authorised content/report export exists, but full assistant/knowledge portability is unverified. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - chat_export — Can admins export all chats? [partial]: Detailed interaction export includes user prompts/answers over a chosen period with privacy settings. Completeness across files, agent state and all historical chats was not tested. Sources: unique-ai:unique-ai:analytics. - assistant_export — Can assistants and prompts be exported in a reusable format? [unknown]: Can assistants and prompts be exported in a reusable format? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - knowledge_export — Can knowledge bases and their sources be exported? [unknown]: Can knowledge bases and their sources be exported? Unknown. Reusable assistant/prompt and full knowledge/source exports, complete machine-readable state and current AI termination window remain unverified. No admin export fixture was run. - export_format — Are formats documented and machine-readable? [partial]: Model usage CSV and detailed analytics exports are documented. DPA promises return in existing format, not a universal reusable assistant/knowledge format. Sources: unique-ai:unique-ai:cost, unique-ai:unique-ai:analytics, unique-ai:unique-ai:dpa. - post_termination_window — How long can data be retrieved after termination? [partial]: Baseline ToS 11.4 offers recorded-call download/export on written request within 30 days; that does not establish a chat/assistant/KB exit window. DPA return is within reasonable time. Sources: unique-ai:unique-ai:terms, unique-ai:unique-ai:dpa. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:analytics, unique-ai:unique-ai:cost, unique-ai:unique-ai:dpa, unique-ai:unique-ai:terms ### VEN-07: Support and service levels Judgment rule: Record support channels, languages (German, French, Italian), hours and time zone, local or regional presence, documented response times, uptime SLA and credits, public status page and incident history. Popularity is not a reliability score. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Business email support and Enterprise priority/SLA service are advertised; credit terms and local-language support remain open. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Business credit-priced plan; Enterprise or legacy differences are named per answer; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - support_channels — Which support channels are available on each plan? [supported]: Pricing lists Business email and Enterprise priority support with dedicated CSM; public support/community resources are available. Sources: dust:dust:pricing, dust:dust:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Support/pricing/Enterprise pages and the official status URL were checked. German/French/Italian staffed support and detailed credited SLA terms were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [partial]: The public policy identifies a Paris, France entity. A DACH/Swiss support team or named regional partner was not established. Sources: dust:dust:privacy. - uptime_sla — Is there an uptime SLA with credits? [partial]: Enterprise marketing claims 99.9% uptime and pricing includes an SLA; service-credit amounts, exclusions and claim rules were not retrieved. Sources: dust:dust:enterprise, dust:dust:pricing. - status_page — Is there a public status page with history? [partial]: Model-selection docs link https://dust.statuspage.io for incidents. Direct retrieval timed out, so incident history was not verified. Sources: dust:dust:models. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:support, dust:dust:privacy, dust:dust:enterprise, dust:dust:models #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial Enterprise support and a public multitenant status page are available; response times are contracted. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - support_channels — Which support channels are available on each plan? [supported]: Enterprise email and three-layer dedicated support escalation through customer team, CS and engineering. Hours/responses depend on SLA; extended-hours contract is extra. Sources: unique-ai:unique-ai:support. - support_languages — Is support available in German, French or Italian? [unknown]: Is support available in German, French or Italian? Unknown. Guaranteed DE/FR/IT support, numeric hours/response times, dedicated uptime/credits and complete incident-history export were not established. - regional_presence — Is there a DACH or Swiss entity, team or partner? [supported]: Unique AI AG lists Zürich, Unique Germany GmbH Berlin, plus UK/US/Singapore entities. Sources: unique-ai:unique-ai:contact. - uptime_sla — Is there an uptime SLA with credits? [partial]: Support docs defer hours and response times to SLA contract; no public uptime/credit schedule was obtained. Baseline terms only promise commercially reasonable availability efforts. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:terms. - status_page — Is there a public status page with history? [supported]: status.prod.unique.app publicly shows component/uptime history. Support docs scope it to multitenant accounts, not every dedicated environment. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:status. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:support, unique-ai:unique-ai:contact, unique-ai:unique-ai:terms, unique-ai:unique-ai:status ### VEN-08: Onboarding, training and adoption Judgment rule: Record vendor-led onboarding, admin training, end-user training (live, e-learning, languages), use-case libraries, champion programmes, change-management materials and their cost. Distinguish included services from paid professional services and partner offerings. #### Dust Verification status: Agent cross-checked (agent-cross-checked) Support: partial Dust has rollout and training material, with hands-on support packaged for Enterprise. Availability: generally-available Delivery: native Scope: surfaces=Dust web workspace, Dust EU web workspace; version=Public source pass 2026-10-21; no logged-in deployment observed; plan=Public learning material (no paid entitlement required to read); contracted CSM/onboarding is Enterprise; add_ons=none stated; deployment_mode=multi-tenant-saas; region=US/global or EU workspace as named; EU-hosted-model restriction must be enabled separately; os=not specified. Limitations: - Documented findings only; unestablished atomic questions remain explicit gaps. - onboarding_service — Is guided onboarding included? [supported]: Enterprise pricing includes dedicated CSM and onboarding; exact hours and scope are contractual. Sources: dust:dust:pricing. - user_training — Is end-user training offered, in which languages? [partial]: Public team onboarding and education resources are available. Course/live-session language coverage was not established. Sources: dust:dust:training, dust:dust:rollout. - use_case_library — Are role-based use cases and templates provided? [supported]: The public Use Cases and Guides index lists departmental guides for Sales, Support, Marketing, Engineering, Data Analytics, Knowledge, People, Product and Collaboration; the Sales guide supplies concrete agent examples and build links. This establishes public role-based guidance, not a separately verified in-product template entitlement. Sources: dust:dust:r2-department-guides, dust:dust:r2-sales-guide. - adoption_programme — Is there a champion or adoption programme? [partial]: The rollout guide covers launch, builder community, education and expansion; a contracted champion programme entitlement was not established. Sources: dust:dust:rollout. - service_cost — Which services cost extra? [partial]: Hands-on CSM/onboarding is Enterprise packaging; a numerical professional-services tariff was not established. Sources: dust:dust:pricing. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: dust:dust:pricing, dust:dust:training, dust:dust:rollout, dust:dust:r2-department-guides, dust:dust:r2-sales-guide #### Unique AI Verification status: Agent cross-checked (agent-cross-checked) Support: partial The vendor markets forward-deployed delivery and structured training; inclusion and cost remain unpriced. Availability: generally-available Delivery: native Scope: surfaces=Unique AI Chat and administration; version=not specified; plan=Contracted Unique AI platform and enabled modules. No public named tariff tiers were established; deployment and provider entitlements vary by MSA.; add_ons=none stated; deployment_mode=not specified; region=CH/EU/US/UK/APAC per deployment; inference and external tools require separate region configuration; os=not specified. Limitations: - Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - onboarding_service — Is guided onboarding included? [partial]: Homepage markets embedded forward-deployed experts helping business/IT ship use cases; exact licence-included rollout scope is contracted. Sources: unique-ai:unique-ai:homepage. - user_training — Is end-user training offered, in which languages? [partial]: Vendor homepage describes structured programmes teaching users to use/build/scale; current languages and course entitlement are not specified. Sources: unique-ai:unique-ai:homepage. - use_case_library — Are role-based use cases and templates provided? [supported]: Public documentation has finance-role workflows, Chat/Conduct guidance, configurable Suggested Prompts and agent examples. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct. - adoption_programme — Is there a champion or adoption programme? [unknown]: Is there a champion or adoption programme? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. - service_cost — Which services cost extra? [unknown]: Which services cost extra? Unknown. Champion/adoption programme structure, training languages, included versus professional-service fees and onboarding hours are not published. Checked 2026-10-21; agent cross-checked 2026-10-21; check again by 2026-12-20. Sources: unique-ai:unique-ai:platform, unique-ai:unique-ai:homepage, unique-ai:unique-ai:agent, unique-ai:unique-ai:conduct ## Sources ### dust:dust:models Auto models and the model picker. Users select a model per message or agent; auto choices use maintained ordered lists rather than task-based routing. - URL: https://docs.dust.tt/docs/user-documentation/agents/model-selection - Locator: Auto model lists; availability; API overrides - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:eu-models EU-hosted models. EU credit-plan workspaces using Dust model hosting can restrict agents and auto choices to EU-hosted models; BYOK is excluded from this setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/eu-hosted-models - Locator: Availability; supported/excluded model table - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:changelog Dust changelog. Recent dated changes include German/French UI, Gemini 4 Argon and migration from File Generation to Computer. - URL: https://docs.dust.tt/docs/changelog - Locator: October 21, 16 and 14, 2026 entries - Evidence kind: documented - Source date: 2026-10-21 - Retrieved: 2026-10-21 ### dust:dust:files Conversation Files. Conversation uploads are scoped to one conversation and support documents, tabular data, images and audio. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/conversation-files/conversation-files - Locator: Formats; size table; generating files - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pricing Dust Pricing. Business supports up to 100 people with Free/Pro/Max seats; Enterprise pricing is sales-led and adds pooled credits, SCIM, audit, single tenancy and support. - URL: https://dust.tt/home/pricing - Locator: Business/Enterprise table and FAQ - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:models Unique LLM availability overview. Lists contract-dependent provider/model availability, region SKUs, dated additions and retirements; CH Phoeniqs remains QA-only. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Per-client availability; Azure/LiteLLM/Phoeniqs matrices; Recent changes - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:agent Unique AI space configuration. Documents admin instructions, configured model/tools, knowledge binding, prompts and people/group Can chat/Can manage access. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/unique-ai-space - Locator: Models; sources/tools; sharing; publishing - Evidence kind: documented - Source date: 2026-06-18 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:conduct Unique AI Conduct. Documents autonomous Python/Bash work, visible steps, approvals and stop, with per-chat files and restricted egress. - URL: https://docs.unique.ai/users/spaces/unique-ai-conduct - Locator: GA release 2026.40; execution UI; limitations - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:release42 Unique release 2026.42. Hosted release 14 October 2026 makes chat sharing and Context Memory GA, labels Scheduled Tasks experimental, changes protected-file ingestion and documents current model additions/migrations. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Release Overview; Chat Platform; RAG; Unique AI; Language Model - Evidence kind: documented - Source date: 2026-10-14 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:customllm Custom LXM connection. Documents operator-created external model endpoints, API/OAuth credentials and model groups. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/connect-custom-lxm-llm-with-unique-ai - Locator: Technical insight; Create and Connect; Security - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:code Code Execution. Documents Azure Responses API Python execution, downloadable outputs, no outbound internet and model/file restrictions. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Compatibility; output; limitations; governance - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:compliance Compliance Layer 3.0. Describes FINMA/bank-secrecy/CH-DPA Microsoft amendments and deployment-specific assurance limitations. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Legal framework; FSI amendments; deployment feature matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:embeddings Custom embedding models. Documents custom embedding endpoints, one model per organisation and mandatory re-embedding after model/dimension changes. - URL: https://docs.unique.ai/it-operators/custom-models-and-embeddings/usage-or-change-of-custom-embedding-model - Locator: Setup; configuration; re-embedding - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:onpremsecurity On-premises security architecture. Documents full customer control and possible operation without Unique access, with customer models/infrastructure. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/on-premise-tenant/security-architecture-on-premises - Locator: Overview; custom setup - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:operators IT operator documentation overview. Describes dedicated Unique-managed, customer-cloud and full air-gapped on-premise modes. - URL: https://docs.unique.ai/it-operators - Locator: Supported deployment models - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-code Code Execution. The page allows selected Knowledge Base files to be preloaded with additionalUploadedDocuments. Its compatibility list includes Azure and LiteLLM OpenAI Responses-capable IDs despite Azure-only introduction/limitations. Azure sandbox controls are not proof of the LiteLLM execution region. - URL: https://docs.unique.ai/administrators/space-management/tools/code-execution - Locator: Functionality; Limitations; All available models; Security & Governance; additionalUploadedDocuments - Evidence kind: documented - Source date: 2026-07-30 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-models Unique LLM availability overview. The model catalogue separates provider routes, region/SKU choices and QA-only Swiss Phoeniqs. It is a technical availability inventory, not a complete legal subprocessor schedule. - URL: https://docs.unique.ai/administrators/models-llm-management/how-we-evaluate-models/llm-availability-overview - Locator: Provider and region matrices; Phoeniqs Model Service; recent changes - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### dust:dust:tiers Model access tiers. Admins restrict models and reasoning efforts at workspace, group or member level, with a separate published-agent bypass setting. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/model-access-tiers - Locator: Workspace, group and individual ceilings - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:spaces Spaces management. Spaces control knowledge and agent access; Business allows five and Enterprise 100 spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/spaces-management - Locator: Open/restricted spaces; limits; visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credits Credits. Consumption adds token and tool credits; a 600-AWU checkpoint can pause user-started root tasks, with exceptions. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credits - Locator: Token/action credits; checkpoints - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:credit-management Credit management. Credit sources and block behavior vary by plan; beta Enterprise Pooled group budgets exclude programmatic consumption. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/credit-management - Locator: Personal caps; group budgets; programmatic use - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:cost Model usage and cost management. Documents off-by-default estimated usage dashboards and enforced daily company/group/user model-call limits. - URL: https://docs.unique.ai/administrators/models-llm-management/model-usage-and-cost-management - Locator: Beta flags; daily limits; cost calculation; CSV - Evidence kind: documented - Source date: 2026-07-21 - Retrieved: 2026-10-21 ### dust:dust:file-limits File size limits. The dedicated limits FAQ gives different image, audio and tabular caps than Conversation Files and excludes direct video uploads. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/file-size-limits - Locator: Upload caps; audio-only restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:computer Computer. Computer executes code in temporary workspaces, handles Office/PDF files, performs documented OCR and restricts network access by allowlist. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/computer - Locator: File work; OCR; network control; secrets - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:drive Google Drive. Drive sync follows a dedicated connection account and selected content; scanned documents need conversation upload for OCR and Excel table queries need conversion to Sheets. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/google-drive - Locator: Connection identity; refresh; OCR; spreadsheet limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:search Search data sources. Agents search selected knowledge sources and retrieve relevant document context. - URL: https://docs.dust.tt/docs/user-documentation/agents/knowledge/search-data-sources - Locator: Document selection; retrieval - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:files Upload and Chat limits. Specifies 512 MB/file, 30 files/batch, default forced retrieval for selected uploads and configurable expiry. - URL: https://docs.unique.ai/users/upload-chat-file-limits-how-large-documents-are-handled - Locator: Production limits; retrieval; expiry - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:filetypes Supported file types. Lists common Office/PDF/text formats and general ingestion limitations that differ from the newer chat-specific limits. - URL: https://docs.unique.ai/users/supported-file-types - Locator: Types; exceptions; ingestion quality - Evidence kind: documented - Source date: 2026-05-09 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:file-ingestion-20261026 Unique file ingestion administration. Base ingestion lacks scanned-PDF OCR. MDI supports image-based PDFs; Docling has partial support. MDI must be provisioned and enabled per folder or chat Space, and the guide distinguishes experimental image-content extraction and deprecated agentic ingestion. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/file-ingestion - Locator: Ingestion overview capability table; Enable MDI; Enable MDI for Upload in Chat - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:kbpermissions Knowledge scope permissions. Describes query filtering by user/group scopes, but older SharePoint permission statements differ from the newer connector guide. - URL: https://docs.unique.ai/administrators/knowledge-base-for-admins/folder-scope-access-permissions - Locator: Scopes; source integration limits - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### dust:dust:permissions Access Controls and Permissions. Knowledge access is organized through admin-selected connection content and membership of open/restricted Spaces. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/access-controls-and-permissions - Locator: Access policy; connection account; Spaces - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:microsoft Microsoft. Microsoft data is scoped to the connecting account and selected SharePoint sources; changes synchronize on a five-minute cycle. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/microsoft - Locator: Connection account; delegated and service-principal setup; sync - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:confluence Confluence. Confluence sync covers selected global spaces, excluding private spaces and pages with view restrictions. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/confluence - Locator: Scope; restricted pages; refresh - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:jira Beta: Import Jira issues. A separately documented beta route imports Jira issues as a custom connection. - URL: https://docs.dust.tt/docs/user-documentation/data-sources/custom-connections/beta-import-jira-issues - Locator: Import path - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:sources What data sources can be connected to Dust?. Official guides identify managed connections and custom API/import routes. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/general-questions/what-data-sources-can-be-connected-to-dust - Locator: Named sources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:tools Adding an MCP Server. Admins add remote MCP servers with OAuth or bearer credentials and can restrict tools to skills. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/adding-an-mcp-server - Locator: Remote/custom servers; auth; tool restriction - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-bigquery Dust BigQuery connection. Dust stores BigQuery metadata and runs table queries through a dedicated service account; dataset content is not synchronized into the index. - URL: https://docs.dust.tt/docs/user-documentation/admins/connections-management/bigquery.md - Locator: No content sync; service-account setup, one location and Space table selection - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sharepoint SharePoint connector. Documents periodic indexed sync, optional content-and-permissions mode, site selection and absent label-level detection. - URL: https://docs.unique.ai/it-operators/integrations-connectors/sharepoint-connector - Locator: Modes; permission sync; limitations - Evidence kind: documented - Source date: 2026-07-06 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:confluence Confluence connector. Documents Cloud/Data Center content sync without source-permission synchronisation. - URL: https://docs.unique.ai/it-operators/integrations-connectors/confluence-connector - Locator: Requirements; sync; limitations - Evidence kind: documented - Source date: 2026-06-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:platform-overview-20261026 Unique platform overview. The platform architecture names Google Drive and Salesforce among knowledge sources, alongside SharePoint/OneDrive, Confluence and Teams/Outlook. It does not provide per-connector consent, rollout or price entitlements. - URL: https://docs.unique.ai/administrators/platform-overview - Locator: Connectors and Knowledge Sources diagram - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:release40-20261026 Unique release 2026.40. GA HTML dashboards can list, enable and sign in to MCP connectors, with Salesforce and Yahoo Finance named examples. Contract/module enablement and personal connection state still apply. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-40 - Locator: Hosted September 30 2026; Chat Experience, GA HTML connector dashboards - Evidence kind: documented - Source date: 2026-09-30 - Retrieved: 2026-10-26 ### dust:dust:credentials Personal vs Shared Credentials for Tools & MCP Servers. Tools can use a shared account or each user OAuth identity; even personal auth needs initial admin setup. - URL: https://docs.dust.tt/docs/user-documentation/admins/tools-management/personal-vs-shared-credentials - Locator: Shared versus personal authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:permissioncache Permission cache timing. Describes usual subsecond internal permission propagation without a hard upper bound, and stale rules after a missed broadcast. - URL: https://docs.unique.ai/administrators/access-management-for-admins/cache-permission-sla - Locator: Expected timing; degraded scenarios - Evidence kind: documented - Source date: 2026-09-22 - Retrieved: 2026-10-21 ### dust:dust:security Dust Security. Dust claims EU/US hosting, AES-256/TLS, no model training, provider zero retention and SOC 2 Type II. - URL: https://dust.tt/home/security - Locator: Hosting, training, encryption and certification statements - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:keys Single-tenant key management. Explains why client-held keys are unavailable across all Single Tenant data stores and directs full key control to self-hosting. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Big picture; BYOK/CYOK/HYOK; storage locations - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:retention Retention and deletion at Unique. Documents no training, Azure abuse-monitoring opt-out, post-termination retention and backup exceptions. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Hosted-only scope; Azure provider retention; deletion; encryption - Evidence kind: documented - Source date: 2026-05-04 - Retrieved: 2026-10-21 ### dust:dust:deep Deep-dive Agent. Deep-dive plans, delegates and writes cited reports, using Company Data knowledge and selected tools; Table Query is excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/default-agents/deep-dive-agent - Locator: Research flow; citations; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:memory Agent Memory. Enabled agents retain user-private memory across conversations; users can view and delete it and it persists until deletion. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/agent-memory - Locator: Adding the tool; viewing/deleting; privacy - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:builder Create your first agent. Agents combine instructions, models, knowledge and tools with controlled sharing. - URL: https://docs.dust.tt/docs/user-documentation/agents/create-your-first-agent - Locator: Instructions; tools; sharing - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:memory Context Memory in Unique AI Chat. Documents private per-user cross-chat memory, edit/disable controls and an explicit warning that disabling does not delete the stored profile. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat/context-memory-in-unique-ai-chat - Locator: Private profile; edit and disable; web-search restriction - Evidence kind: documented - Source date: 2026-09-15 - Retrieved: 2026-10-21 ### dust:dust:governance Workspace Governance: Roles, Groups & Permissions. Admins delegate manager/group permissions for agents, skills, models, billing and security; grants are additive. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/workspace-governance-roles-groups-and-permissions - Locator: Roles; permission matrix; additive access - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:chat Unique AI Chat. Describes the user chat workspace and configurable tools. - URL: https://docs.unique.ai/users/spaces/unique-ai-chat - Locator: Features and access - Evidence kind: documented - Source date: 2026-09-03 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:roles Access role concept. Defines identity, application, space and knowledge-scope permissions, including delegated management roles. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/access-role-concept - Locator: Four access layers - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:mcp MCP tools for spaces. Describes feature-flagged beta MCP clients with organisation and per-space connector/tool controls. - URL: https://docs.unique.ai/administrators/space-management/tools/mcp-tools - Locator: Beta warning; flags; selective tool enablement - Evidence kind: documented - Source date: 2026-05-21 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:hub MCP Hub security governance. Documents per-user token routing, approved origin restrictions and tool-call correlation; some DLP/elicitation pipeline measures are planned. - URL: https://docs.unique.ai/administrators/mcp/the-mcp-hub/govern/security-governance - Locator: Authentication; governance; planned request pipeline - Evidence kind: documented - Source date: 2026-08-26 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:deepresearch Deep Research tool. Documents experimental research/report engine, with separate external OpenAI-engine data flows and limited current tools. - URL: https://docs.unique.ai/administrators/space-management/tools/deep-research - Locator: Experimental warning; engines; user flow - Evidence kind: documented - Source date: 2026-05-09 - Retrieved: 2026-10-21 ### dust:dust:web Web Search & Browse. The tool runs Google queries and browses results, with agent-level configuration and format options. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/web-search-and-browse - Locator: Search and browsing flow - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:websearch Web Search tool. Documents multiple search engines, source citations and experimental query review/screening; conversation context may leave through queries. - URL: https://docs.unique.ai/administrators/space-management/tools/web-search - Locator: Modes; engines; external-query warning - Evidence kind: documented - Source date: 2026-05-20 - Retrieved: 2026-10-21 ### dust:dust:triggers Triggers. Agents can run automatically from schedule or event triggers. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/index - Locator: Schedules and events - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:schedules Schedules. Agents can run on recurring schedules. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/schedules - Locator: Schedule setup - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:webhooks Webhooks. Admins configure webhook sources; members attach filtered triggers to agents, with optional signature verification for custom sources. - URL: https://docs.dust.tt/docs/user-documentation/agents/triggers/webhooks/index - Locator: Built-in and custom event sources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sdk Python SDK documentation. Documents SDK/public API access and customer-operated modules with event-driven webhook integration. - URL: https://docs.unique.ai/developers/software-development-kit-sdk - Locator: Public API; webhook verification; personal/app keys - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scheduled Scheduled Tasks. Documents off-by-default recurring tasks running with user permissions; unattended approvals/questions can stop a run. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: Beta warning; task settings; runs and limits - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### dust:dust:pods Pods overview. Pods combine shared conversations, tasks and files; open Pods are workspace-browsable and restricted Pods require invitation. - URL: https://docs.dust.tt/docs/user-documentation/pods/overview - Locator: Shared workspace and visibility - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-scheduled Scheduled Tasks. Scheduled Chat/Conduct tasks offer Automatic or Manual approval. The newer release labels scheduling Experimental and feature-flagged; unattended automatic approval is not mandatory human confirmation. - URL: https://docs.unique.ai/users/scheduled-tasks - Locator: At a glance; task Approval setting; unattended runs - Evidence kind: documented - Source date: 2026-10-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-release42 Unique release 2026.42. Release 2026.42 makes Shared Chats GA, on by default per company with a per-Space toggle and preservation of explicit settings. Scheduled Tasks remain Experimental and feature-flagged. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/release-notes-and-calendar/release-notes-2026/release-2026-42 - Locator: Highlights; Chat Platform; Conduct scheduling flag - Evidence kind: documented - Source date: 2026-10-14 - Retrieved: 2026-10-21 ### dust:dust:api-keys API keys. Dust API keys have read/admin scopes, data access and enforceable per-key monthly caps. - URL: https://docs.dust.tt/docs/user-documentation/admins/api-keys - Locator: Scopes; Space access; caps - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:mcp-server Dust MCP Server. Dust exposes workspace knowledge, agents, conversations, files and Pods to OAuth MCP clients under the authenticated user permissions. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-mcp-server - Locator: Region URLs; OAuth; user permissions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:upsert Upsert a document in a data source. The API loads or updates documents in a scoped data source. - URL: https://docs.dust.tt/api-reference/datasources/upsert-a-document-in-a-data-source - Locator: Endpoint and authentication - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:get-conversation Get a conversation. The API retrieves accessible conversation messages with pagination. - URL: https://docs.dust.tt/api-reference/conversations/get-a-conversation - Locator: Response schema - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:mcpkb Knowledge Base MCP user guide. Documents external-assistant search/read with user permissions, citations and optional KB scope restrictions. - URL: https://docs.unique.ai/it-operators/integrations-connectors/knowledge-base-mcp/knowledge-base-mcp-user-guide - Locator: Connecting; access; limitations - Evidence kind: documented - Source date: 2026-10-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:api-usage API model usage tracking. Documents public API/SDK model-call usage tracking; some other internal-service calls are outside scope and REST usage retrieval is planned. - URL: https://docs.unique.ai/it-operators/operations/api-model-usage-tracking - Locator: Coverage; flags; limitations - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:browser Browser Extension. An official extension supports Chrome, Firefox and Chromium-based browsers. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/browser-extension - Locator: Browsers and capabilities - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:teams Dust in Teams. An official Teams integration runs Dust agents within Microsoft Teams after admin setup. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/dust-in-teams - Locator: Setup and usage - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:translation Translator space. Documents beta Office-file/text translation with glossary pre/postprocessing and potential layout disruption. - URL: https://docs.unique.ai/administrators/space-management/create-spaces/translator-space - Locator: Beta; glossary; document types; limitations - Evidence kind: documented - Source date: 2026-05-06 - Retrieved: 2026-10-21 ### dust:dust:images Image Generation. Agents generate images from text or references, up to 14 reference images, with SynthID and content restrictions. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/image-generation - Locator: Reference images; parallel generation; safety - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:speech Voice and sound generation. The speech tool generates MP3 narration or multi-speaker dialogue with selectable languages and styles. - URL: https://docs.dust.tt/docs/user-documentation/agents/tools/voice-and-sound-generation - Locator: Speech Generator - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:meetings Meeting transcripts. Dust consumes transcripts from connected notetaker and sales tools; Gong private transcripts are excluded. - URL: https://docs.dust.tt/docs/user-documentation/agents/integrations/meeting-transcripts - Locator: Providers and scope - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:voice Voice administration. Requires Azure AI Speech Services and describes potential public/backbone audio routing. - URL: https://docs.unique.ai/administrators/space-management/voice-administration - Locator: Dependencies; networking; limitations - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:dpa Unique data processing addendum. Public DPA covers hosted chat/recordings, lists Microsoft, Swiss storage, return/deletion, confidentiality and ten-year audit-log retention. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 2-3, 6-7; Appendices A-B; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:voice-user Using Voice. Documents prompt dictation with EN/DE/FR/IT, immediate audio discard and dialect/recognition limitations. - URL: https://docs.unique.ai/users/spaces/using-voice - Locator: Prompt dictation; privacy note; supported languages - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:frames Frames overview. Frames provide persistent interactive agent output that can be refined and shared. - URL: https://docs.dust.tt/docs/user-documentation/agents/frames/overview - Locator: Creating and editing interactive content - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:pod-chats Pod conversations. All Pod members can read and contribute to Pod conversations, which are automatically indexed. - URL: https://docs.dust.tt/docs/user-documentation/pods/conversations - Locator: Visibility; indexing; participation - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:sso Single Sign-On. Admins configure and enforce SAML SSO, which disables other social sign-in paths for the workspace. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/single-sign-on-sso/single-sign-on-sso - Locator: Setup; enforcement - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:enterprise Dust for Enterprise. The Enterprise marketing page claims 365-day audit retention, 99.9% uptime and support for 10,000+ users. - URL: https://dust.tt/home/enterprise - Locator: Security and scale - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:sso Single sign-on setup. Documents Zitadel SSO across deployment types, group claims and automatic SAML account creation/update. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/how-to-setup-single-sign-on-sso - Locator: Entra ID OIDC; SAML; managed-tenant setup - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### dust:dust:provision Users and groups provisioning. Enterprise SCIM creates, updates and deactivates users and syncs groups; groups can grant Admin/Manager roles. - URL: https://docs.dust.tt/docs/user-documentation/admins/admin-governance/users-and-groups-provisioning - Locator: SCIM 2.0; group role mapping - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:seats Seat management. Admins assign independent roles and Free/Pro/Max seats; annual stock and already-allocated credits have specific reclaim rules. - URL: https://docs.dust.tt/docs/user-documentation/admins/usage-seats-and-credits/seat-management - Locator: Seat assignments; billing cycles; leaving - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:scim SCIM provisioning. Documents Unique SCIM endpoint/key for IdP user/group synchronisation. - URL: https://docs.unique.ai/it-operators/identity-and-access-management-iam/user-and-group-provisioning/scim-system-for-cross-domain-identity-management - Locator: Prerequisites and Entra setup - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### dust:dust:analytics Analytics. Consumption reports break down users, groups, models, tools, agents and Pods; exports omit message content and can double-attribute group usage. - URL: https://docs.dust.tt/analytics - Locator: Attribution; CSV; content exclusion - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:analytics Analytics interface. Documents adoption reports, detailed chat/model/tool exports and randomised or stable pseudonymous identifiers. - URL: https://docs.unique.ai/administrators/insights-measurement/analytics-interface/analytics - Locator: Reports; anonymisation; detailed interactions - Evidence kind: documented - Source date: 2026-09-03 - Retrieved: 2026-10-21 ### dust:dust:audit Audit Logs. Enterprise logs distinguish users, API keys and system actors with CSV and continuous SIEM delivery. - URL: https://docs.dust.tt/docs/user-documentation/admins/audit-logs/audit-logs - Locator: Enterprise scope; actor types; SIEM - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:audit Audit logs. Defines privileged API event logging with self-service exclusions, deployment-specific retention and request-based export. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: Scope; exclusions; default basic mode; retention and export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:security-export Security Events Export. Documents Single-Tenant-only Azure Activity/Defender Event Hub export with seven-day replay, client-region selection and consumption cost. - URL: https://docs.unique.ai/it-operators/integrations-connectors/security-events-export-see - Locator: Availability; delivered events; retention; cost - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-audit Audit logs. API audit-event guide specifies basic/verbose modes and MT 90-day/ST five-year operational retention. It does not reconcile those event classes to DPA audit logs or a customer-specific contractual override. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/audit-logs - Locator: About audit logs; modes; Single and Multi Tenant Clients - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-dpa Unique data processing addendum. The public July 2025 DPA specifies ten-year audit logs and CH storage, while Appendix A lists Microsoft and a client-chosen location. No signed current provider schedule, retention override or contract-precedence mapping was inspected. - URL: https://www.unique.ai/data-processing-addendum - Locator: Sections 3.15 and 6.1; Appendix A; July 2025 footer - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-retention Retention and deletion at Unique. Hosted-only policy separates ordinary post-termination content retention, recoverable files and backups and permits contract customisation. Its log/key statements are not reconciled to audit-event/DPA/key-management scopes. - URL: https://docs.unique.ai/security-and-compliance/data-protection/data-retention-and-data-deletion-at-unique - Locator: Purpose; Data retention; Deletion after termination; Backups; Encryption in Place - Evidence kind: documented - Source date: 2026-05-04 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:dlp Data leakage prevention integration. Describes customer-operated HTTPS/DLP proxy and post-chat analytics scanning rather than a default native PII-redaction feature. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-leakage-prevention-dlp - Locator: Proxy; analytics API; compatibility - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:single Single-tenant security architecture. Documents separate Azure landing zone, network restrictions, retention and Unique-managed infrastructure keys. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Azure resources; SSO; encryption; monitoring - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:policy Terms and conditions administration. Documents first-login acceptance, custom terms under an MSA and version/agreement export through GraphQL. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: First-login acceptance; MSA condition; API export - Evidence kind: documented - Source date: 2026-05-07 - Retrieved: 2026-10-21 ### dust:dust:privacy Dust Platform Privacy Policy. The policy identifies Permutation Labs in Paris and distinguishes its controller processing from customer processor processing, with non-EEA transfer safeguards. - URL: https://dust.tt/home/platform-privacy - Locator: About Us; sections 2, 6 and 7 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-keys Single-tenant key management. May 2026 key guide distinguishes imported customer-generated keys held by Unique from customer-exclusive key control via self-hosting. Its MT/ST CMK statement differs from the hosted retention page; actual MT configuration is unverified. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant/key-management - Locator: Infrastructure-only scope; PMK; BYOK/CYOK/HYOK; Summary - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-single Single-tenant security architecture. Single-tenant guide documents separate landing zone, WAF/IP controls and Unique-managed encryption. Its 2048-bit RSA-HSM description differs from the hosted retention page; this does not establish an exact current key design. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique/single-tenant/security-architecture-single-tenant - Locator: Overview; Encryption; Data classification - Evidence kind: documented - Source date: 2026-05-28 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-compliance Compliance Layer 3.0. The deployment matrix documents CH North multitenant hosting and selectable single/client-hosted regions, with deployment-specific controls. These are options, not proof of a particular customer contract or current key configuration. - URL: https://docs.unique.ai/security-and-compliance/compliance/compliance-layer-3-0 - Locator: Digital Sovereignty; Feature overview matrix - Evidence kind: documented - Source date: 2026-05-27 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:install Unique installation models. Enumerates multi-tenant, single-tenant, customer-managed and on-premise deployments. - URL: https://docs.unique.ai/it-operators/installing-and-upgrading-unique/install-unique - Locator: Overview - Evidence kind: documented - Source date: 2025-08-06 - Retrieved: 2026-10-21 ### dust:dust:training-policy Dust Platform Privacy Policy. The policy asserts listed providers do not train, retain or log Customer Content for human review; this source pass did not retrieve the customer DPA. - URL: https://dust.tt/home/platform-privacy - Locator: Section 6, Foundational Model Providers - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:terms Unique terms of service. Describes a sales-conversation service with Order Form subscription fees, nonrenewal notice, recording export and proprietary rights; applicability to the current AI MSA needs confirmation. - URL: https://www.unique.ai/terms-of-service - Locator: Sections 1-2, 4-6, 11, 17-18 - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:delete-chat Can I delete or rename a conversation?. Users can delete or rename their conversations. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/faq/managing-agents/can-i-delete-or-rename-a-conversation - Locator: Conversation actions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:redaction Chat data redaction and retention. Documents scheduled clearing of chat content and workspace records, with separate upload/KB retention rules. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/data-redaction - Locator: What is cleared; exclusions; administrator settings - Evidence kind: documented - Source date: 2026-10-18 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:contact Unique AI contact. Lists Unique AI AG in Zürich, Unique Germany GmbH in Berlin and other regional entities. - URL: https://www.unique.ai/contact-us - Locator: Office addresses - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:trust Unique AI trust centre. Describes CH Azure storage separately from globally routed inference and claims ISO/SOC assurances, with differing SOC types in the FAQ. - URL: https://www.unique.ai/trust-center - Locator: Enterprise security; compliance standards; FAQ - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:iso42001 Unique ISO/IEC 42001 certificate. TÜV SÜD certificate covers development/deployment SaaS for financial services using pretrained foundation models or client-provided models, valid to 6 March 2028. - URL: https://www.unique.ai/hubfs/ISO%2042001_Unique_EN_2025.pdf - Locator: One page; registration 99 420 00001; scope and dates - Evidence kind: certificate-verified - Source date: 2025-03-07 - Retrieved: 2026-10-21 - Issuer: TÜV SÜD South Asia Private Limited - Certificate scope: Unique AG, Stockerstr.34, Zurich. Development and deployment of SaaS for financial-services clients based on pretrained AI foundation models using Azure OpenAI or client-provided models, including client on-premise models. - Valid: 2025-03-07 to 2028-03-06 ### unique-ai:unique-ai:review2-iso-docs ISO Certifications and current downloads. The ISO documentation links 2026 English/German ATTESTA ISO27001 and ISO9001 renewals, plus the 2025 ISO42001 certificate; ISO27001 SoA requires an NDA. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/iso-certifications - Locator: Certificate ISO27001; ISO9001; ISO42001; Statement of Applicability - Evidence kind: documented - Source date: 2026-08-05 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-iso27001 Unique AG ISO27001 ATTESTA 2026 renewal. Inspected ATTESTA ISO27001:2022 renewal for Unique AG, registration 223-06-018.I, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750716/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO27001:2022 information security management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso9001 Unique AG ISO9001 ATTESTA 2026 renewal. Inspected ATTESTA ISO9001:2015 renewal for Unique AG, registration 223-06-017.Q, issued 10 June 2026 after 4 June surveillance, valid until 31 May 2029. The certificate-linked public register lists the same number and expiry. - URL: https://unique-ch.atlassian.net/wiki/rest/api/content/1384809423/child/attachment/att2423750710/download - Locator: One-page 2026 English certificate; scope, registration, surveillance, printed expiry - Evidence kind: certificate-verified - Source date: 2026-06-10 - Retrieved: 2026-10-21 - Issuer: ATTESTA Schweizer Zertifizierungsgesellschaft AG - Certificate scope: Unique AG, Stockerstrasse 34, 8002 Zürich: development, operation, trading and distribution of software and provision of IT/information-technology services; ISO9001:2015 quality management - Valid: start not stated to 2029-05-31 - Registry: https://www.ic-register.com/?qry=Unique&handler=Process ### unique-ai:unique-ai:review2-iso-register Certificate-linked public register: Unique AG. Public certificate-linked register lookup for Unique AG lists registrations 223-06-018.I and 223-06-017.Q, Zurich, software/IT scope and expiry 31 May 2029. Standard/status text fields are blank; certificate PDFs supply the standards. - URL: https://www.ic-register.com/?qry=Unique&handler=Process - Locator: Unique AG result rows; registration, scope, expiry - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-soc SOC2 Type2: chronology and report access. The dedicated SOC page explains Type1 in December 2023 followed by Type2 in January 2025; audit report and certificate are available only on request after NDA. Auditor, service scope and actual reporting period were not publicly inspected. - URL: https://docs.unique.ai/security-and-compliance/compliance/certifications/soc-2-type-2 - Locator: SOC2 Type2 timeline; Certificates/report access - Evidence kind: vendor-claimed - Source date: 2026-04-12 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-terms-admin Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-21 ### dust:dust:fx-ecb ECB historical euro reference rates. EUR 1 = USD 1.1215 = CHF 0.9237 on October 20, 2026. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time=2026-10-20, USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### unique-ai:unique-ai:platform Unique AI platform. Markets a modular finance platform with governed connectors, frontend, financial agents and APIs. - URL: https://www.unique.ai/en/platform - Locator: Frontend, financial agents, MCP Hub; deployment section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:ecb-fx ECB euro foreign exchange reference rates, 20 October 2026. ECB records EUR 1 = USD 1.1215 and CHF 0.9237 on 20 October 2026; derived USD to EUR is 1/1.1215 and CHF to EUR is 1/0.9237. - URL: https://www.ecb.europa.eu/stats/eurofxref/eurofxref-hist.xml - Locator: Cube time="2026-10-20": USD and CHF - Evidence kind: documented - Source date: 2026-10-20 - Retrieved: 2026-10-21 ### dust:dust:licence Dust repository LICENSE at pinned commit. The pinned public repository root licence is MIT; hosted service terms and third-party components are separate. - URL: https://github.com/dust-tt/dust/blob/2b1a4973af824f8ff970d585c5eb1f40ae76186c/LICENSE - Locator: Root LICENSE, MIT permission grant - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:review2-governance-20261026 Unique AI governance framework: contract access. The current governance framework says legal contracts and end-user T&Cs are available on request; the public page does not expose platform subscription or component licence clauses. - URL: https://docs.unique.ai/security-and-compliance/ai-governance-framework - Locator: Individual standards; Legal contracts; End-User Terms and Conditions - Evidence kind: documented - Source date: 2026-04-12 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:reference-licence-20261026 Unique public reference repository licence. The public repository defaults to Unique License v1 unless an explicit licence says otherwise; commercial use, distribution and modifications require prior approval. The default is restricted source-available, not an OSI open-source licence. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/LICENSE - Locator: LICENSE, repository-wide disclaimer and exceptions - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:unique-licence-v1-20261026 Unique License v1. The published full licence permits personal noncommercial use and requires prior written approval for commercial use, distribution and modification, with separate component-licence exceptions. Swiss law and Zurich venue are specified. - URL: https://github.com/Unique-AG/license/releases/tag/unique-license.v1 - Locator: Grant, Restrictions, Open Source Components, Governing Law - Evidence kind: documented - Source date: 2024-09-24 - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-licence-20261026 Unique Python SDK MIT licence. The Python SDK directory has an explicit MIT licence permitting commercial use and modification subject to notice requirements; this exception does not license the hosted platform. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/LICENSE - Locator: unique_sdk/LICENSE, explicit component exception - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:sdk-package-20261026 Unique SDK package metadata. At the pinned October 23 repository commit, unique_sdk package metadata declares MIT, consistent with its component licence. Repository/package version is not treated as the hosted release date. - URL: https://github.com/Unique-AG/ai/blob/afa596c9b4b0231895ff70f44029a9a525f746e9/unique_sdk/pyproject.toml - Locator: project name/version and licence - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-26 ### unique-ai:unique-ai:review2-terms-admin-20261026 Terms and Conditions Administration. Current platform T&C administration refers to a customer MSA and gated admin export; it does not publish the vendor platform agreement or determine subscription/IP/branding clauses. - URL: https://docs.unique.ai/it-operators/operations/security-and-data-privacy/terms-and-conditions-administration - Locator: Overview; MSA exceptions; Modifying/Exporting Terms and Conditions - Evidence kind: documented - Source date: 2026-05-08 - Retrieved: 2026-10-26 ### dust:dust:get-document Retrieve a document from a data source. The API retrieves a source document; this does not establish a complete one-click tenant export. - URL: https://docs.dust.tt/api-reference/datasources/retrieve-a-document-from-a-data-source - Locator: Endpoint and response - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:support Dust Support. The vendor provides public support entry points and community/documentation resources. - URL: https://dust.tt/home/support - Locator: Support channels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:support Enterprise support. Provides public multitenant status link, enterprise email and a contract-specific dedicated support model. - URL: https://docs.unique.ai/enterprise-support - Locator: Contact; dedicated support model; hours - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:status Unique public system status. Public status page displays service/API/collector components and historical uptime panels; dedicated environments are outside the documented status scope. - URL: https://status.prod.unique.app/ - Locator: Component and 90-day uptime panels - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:rollout Dust Rollout Guide. Public rollout guidance covers setup, launch, team education and measurement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/index - Locator: Rollout phases - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:training Team onboarding material. Dust provides reusable team-onboarding material. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/dust-rollout-guide/team-onboarding-material - Locator: Training resources - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-department-guides Dust Use Cases and Guides. Public guides are organized by Sales, Support, Marketing, Engineering, Data, Knowledge, People, Product and Collaboration. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/index.md - Locator: Use Cases by Department - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### dust:dust:r2-sales-guide Dust Sales use-case guide. The Sales guide provides concrete role-based agent examples; this is public learning material, not a contracted training entitlement. - URL: https://docs.dust.tt/docs/user-documentation/getting-started/use-cases-and-guides/sales.md - Locator: Sales agent examples and build links - Evidence kind: documented - Source date: Not stated - Retrieved: 2026-10-21 ### unique-ai:unique-ai:homepage Unique AI finance platform. Markets embedded experts and structured training programmes for finance users and IT. - URL: https://www.unique.ai/ - Locator: Forward-Deployed Engineers and training section - Evidence kind: vendor-claimed - Source date: Not stated - Retrieved: 2026-10-21