GDPR and AI browsers: when does using one count as a transfer?
Short answer
Sending personal data to a hosted assistant is a disclosure to a processor and brings the usual obligations — lawful basis, a processing agreement, and transfer rules if the servers are outside the EEA. Local processing creates no recipient, so those obligations do not arise.
The structure of the question
GDPR cares who receives personal data and on what basis. A cloud assistant that receives a document containing personal data is a processor acting on your instructions, which needs an Article 28 agreement and, if it is outside the EEA, a transfer mechanism.
Special-category data under Article 9 — health, union membership, biometrics — raises the bar further, and employee files routinely contain it.
Why local changes the analysis
If the data never leaves the controller's own device, there is no processor and no transfer. The processing is still processing and still needs a lawful basis, but the vendor-diligence, DPA and international-transfer questions do not arise because there is no vendor in the data path.
This is a statement about the technical facts, not a legal opinion. Your DPO decides, and documenting it properly is part of the work.
What is unchanged
Data minimisation, retention limits, the rights of the people in the documents, and your security obligations for the device itself. Local processing makes the device the whole of the compliance surface, which is a narrower problem and not an absent one.
Other ways people ask this
- gdpr ai browser
- Does using an AI browser breach GDPR if I open customer records?
Related
- Up a levelGuides: local AI, browser privacy and the hardware to run it
- Closely relatedAI assistants and your banking pages
- Closely relatedWhat Brave Leo sends to Brave, and how to check
- Closely relatedChatGPT Atlas has been retired: what happened to your data
- Elsewhere on the siteAI browser alternatives, compared honestly
- Elsewhere on the siteAI browsers compared: where each one sends your pages