Data use, training & retention
How this is scored
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.
The Automation Lead
No-training is stated for the vendor and for Microsoft behind the Azure OpenAI models, with an opt-out agreement, disabled abuse monitoring and in-memory-only processing described; retention is published per service for prompts, answers, documents and embedding vectors with deletion on request and hard deletion from the database, the DPA leaves all client data the client's property, and ISO 27001, ISO 42001 and SOC 2 Type 2 audits cover the product. It stops just short of the top because retention is not admin-configurable — deletion goes through an emailed request to the security team, and multi-tenant audit logs are capped at 90 days unless the contract is upsold. 3 4 6 7 11