nele.ai

What happens to prompts, uploaded files, connected data and outputs: whether any of it trains a model (the vendor's or a model provider's), how long it is kept and where logs live, whether zero-retention is available, and whether a data processing agreement covers it.

0 — No statement on training or retention; the privacy policy is a website policy that does not cover the product.

3 — A general statement that business data is "not used for training", with no word on retention, on the model providers behind the product or on logs.

5 — Business data excluded from training by contract, retention periods stated for chats and files, and a DPA offered to business customers.

8 — No-training commitments stated for the vendor and every model provider it routes to, retention configurable by the admin (including deletion of chat history), zero-data-retention terms with the model providers named, and abuse-monitoring retention described.

10 — Data use fully accounted for: training, retention, logging and abuse monitoring stated per model provider, customer-controlled retention and deletion with an audit trail, outputs and connected data treated as customer data in the DPA, and an independent audit (SOC 2, ISO 27001 or ISO 42001) covering the product.

Which models sit behind the product and who runs them, where inference and storage happen, whether the customer can pin processing to the EU, choose or exclude model providers, bring its own model or key, or run the product in its own cloud or on premises.

0 — The models behind the product and the processing location are not stated.

3 — The model family is named, but where inference runs and through which provider (the model maker, a hyperscaler, the vendor) is unstated.

5 — Models and their providers named, with an EU processing option stated for storage and at least the default model.

8 — Each available model listed with provider and inference region, EU-only processing selectable by the admin and enforced across models, model providers excludable, and bring-your-own-key or own-cloud deployment documented.

10 — Processing fully under the customer's control and documented: EU-only or on-premises inference for every feature including agents and connectors, open-weight or self-hosted models supported, data flows per feature published, and a residency commitment in the contract rather than on a marketing page.

What the IT department controls: SSO and SCIM provisioning, roles and groups, which models, agents and connectors each group may use, retrieval that respects the permissions of the source system, audit logs, usage reporting, and policies such as data-loss prevention — and whether reporting on staff use is scoped and documented.

0 — No admin features documented; accounts are individual sign-ups.

3 — A team workspace with an owner and member invitations, but no SSO, no roles and no audit log.

5 — SSO, admin and member roles, user management, and an admin view of usage.

8 — SAML/OIDC SSO with SCIM provisioning, group-based permissions for models, agents and connectors, retrieval that inherits source-system permissions, exportable audit logs, and usage analytics with documented scope.

10 — Governance a regulated company can operate: fine-grained policies (DLP, content filters, prompt and output logging rules), audit logs streamed to a SIEM, per-agent ownership and approval, usage reporting that can be aggregated or pseudonymised for works-council agreements, and every admin action logged.

How the product reaches company knowledge and systems: connectors to file stores, wikis, mail, CRM, ticketing and ERP, how fast and how completely they sync, the API, support for open protocols such as MCP, and how the assistant cites the sources it answers from.

0 — No integrations; users paste text or upload files one at a time.

3 — File upload and one or two connectors (for example a drive), with no API and no statement on sync or citations.

5 — A connector library covering the common file stores, wikis and collaboration tools, answers citing sources, and a documented API.

8 — Connectors to file stores, wikis, mail, CRM and ticketing with incremental sync, custom connectors or MCP support, an API and webhooks for embedding assistants and agents in other tools, and source citations on every grounded answer.

10 — The product sits in the company's systems: read and write connectors with documented scopes, MCP servers and clients, contact-centre or telephony integration where relevant, a knowledge layer that can be audited and corrected, and the data, agents and configuration exportable when the customer leaves.

What an agent can actually do and where it stops: multi-step tasks, tool use and actions in other systems, scheduling and triggers, human approval before consequential actions, run logs, evaluation and testing before release, and the limits the vendor states rather than hides.

0 — No agents; the product is a chat window, whatever the marketing says.

3 — Saved prompts or custom assistants with instructions and files, but no actions in other systems and no run history.

5 — Agents that call tools or APIs and run multi-step tasks, built without code, with a log of each run.

8 — Agents that act in connected systems with scoped permissions, human approval configurable per action, triggers and schedules, test and evaluation tooling before release, and documented limits and failure handling.

10 — Agents a business can put in production and account for: versioning and staged rollout, evaluation against test sets, monitoring of quality and cost per agent, handover to a human with full context, every action attributable to the agent and the person who deployed it, and the vendor's own statement of what agents must not be trusted with.

Who the contracting entity and the parent company are, where customer data is hosted, and who the subprocessors are — model providers above all, then hosting, search, telephony and email. Independently sourced by the sovereignty pipeline; for an AI product the model provider is a subprocessor, so a European interface over a non-European model counts as such.

0 — Non-EU vendor and contracting entity, hosting unstated, subprocessors (including model providers) unnamed.

3 — A privacy policy exists, but hosting location is unstated or non-EU and the model providers behind the product are not named as subprocessors.

5 — EU hosting stated and an EU contracting entity, but prompts reach non-EU model providers or other subprocessors without a stated safeguard or EU region.

8 — EU hosting on named infrastructure, EU contracting entity, every subprocessor listed with its location including model providers, EU inference available, and a DPA offered.

10 — Sovereign end to end and evidenced: European ownership, entity, hosting and model processing, every subprocessor European or optional, data export and deletion documented, and a security or certification statement published rather than implied.

Whether a company can compute the real annual cost from public pages alone: price per seat, per agent, per conversation or per usage unit, what is included in each tier, usage limits and overage, which models, connectors or agents cost extra, minimum seats and term.

0 — No public prices at all; every customer is a sales call.

3 — A starting price or "from" figure exists, but usage limits, included models and what scales the cost are unclear.

5 — Prices per tier are public with the main inclusions, but usage limits, overage, agent runs or enterprise features (SSO, audit logs, EU processing) are unpriced or "on request".

8 — Every tier priced publicly with seat or usage units, usage limits and overage rates, add-ons listed, minimum seats and term stated.

10 — Complete price computability: annual cost derivable for a given number of seats, agents or conversations, with every usage rate, model surcharge, add-on and support tier and the cancellation and data-return terms published.