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
They state no training on customer data for their own models and publish a vendor table naming OpenAI and Anthropic with no training, no logging and a DPA; run logs have stated retention (30 days on free tier, until you delete otherwise) and an Enterprise data-retention control covers tool runs, agent conversations and versions in configurable day periods. It stops short of the higher bar because retention is Enterprise-only and must be enabled by their team, routing to any provider leaves providers beyond the two named unaccounted for, and the terms separately licence use of Client Data to improve the Solution. 5 6 7 9 13