Data processing agreement
How TensorPass handles personal data for a site owner who uses AI Connect or orders our AI native website service.
Updated on 9 November 2026
What this agreement covers
This agreement applies between TensorPass and a site owner, the customer, that uses the AI Connect SDK or orders the AI native website service. It forms part of the terms of use and applies under the GDPR (Regulation (EU) 2016/679) and the UK GDPR where they apply.
The SDK and AI Wallet
With AI Connect, the conversation goes from the visitor's browser to the provider of the visitor's account, through AI Wallet on the visitor's computer, and each tool call goes from the visitor's page to the customer's MCP server. TensorPass receives none of this data, so running the SDK makes TensorPass neither a processor of the customer's visitor data nor a recipient of it.
The provider that answers acts under its own terms with the visitor, who chose the account.
The AI native website service
When we build or maintain a customer's AI native site, our team may access the customer's systems and the personal data they hold. For that work TensorPass acts as the customer's processor, on these terms:
- subject matter: the audit, the MCP server, the AI mode and their maintenance, as ordered
- duration: the time of the work and of any maintenance ordered, then deletion as described below
- nature and purpose: reading the site's data to design its tools, then building and testing them
- data: what the customer's systems hold and the work needs, such as names, contact details, bookings and orders
- data subjects: the customer's visitors, clients and staff
How we handle it as processor
For the data of the AI native service, TensorPass does its best to:
- process it only on the customer's documented instructions, including for any transfer outside the EU
- give access only to people who need it for the work and are bound to confidentiality
- work in the customer's own systems with the accounts the customer grants, over encrypted connections, and keep a working copy only when the work needs one
- help the customer answer the requests of data subjects and meet its duties on security, breaches and impact assessments
- tell the customer of a personal data breach as soon as it can once aware of it
- delete or return the data at the end of the work, as the customer chooses, unless the law requires keeping it
- give the customer the information needed to show compliance with this agreement, and arrange audits by the customer or an auditor it appoints when asked
Subprocessors
TensorPass engages no subprocessor for the customer's personal data: the work runs in the customer's own systems. Before engaging one, we try to name it on this page and tell the customer ahead of time, so the customer can object.
The customer's part
The customer is the controller of its visitors' data. It decides why and how that data is processed, has a legal basis for it, and tells its visitors, including that the site's AI answers on the visitor's own AI account through AI Wallet.
Signing and contact
This agreement applies from the start of the work. A customer that needs a signed copy, or terms its own rules require, writes to [email protected].