SEON published data handling and security terms for its MCP connector, which lets AI assistants query a SEON account. SEON says it keeps no copy of data passing through the connector and does not train on it, and that the connected AI provider is the customer's own recipient rather than a SEON sub processor. Each connection signs in as a specific user with OAuth 2.1 and inherits that user's permissions, every AI query is written to the Activity Log, and controls to withhold specific data points are not yet available.
Our readBanks and fintechs assessing the connector as a third party risk now have written terms on retention, training and sub processor status to cite. They also learn that customer data can reach the AI provider they choose, so the transfer terms with that provider fall on the institution.