Google explains what Magic Pointer processes locally and what goes to the cloud

Google detailed how Magic Pointer works on the Googlebook: identifying interactive elements on screen happens locally, while content is sent to a cloud model only after the user selects an item and asks Gemini to act on it. The feature stays inactive until deliberately triggered.

• On-screen element recognition runs locally on the device
• Content is sent to the cloud model only on a Gemini request
• Magic Pointer stays inactive until the user triggers it
• Internal Google test: employees moved the cursor about a mile a day