The current Sight disclosure says JML does not store the image or reply in this release. That is a useful, specific promise. It should be read exactly as written rather than expanded into a broader claim that no connected processing, service handling, logs, or network records can exist anywhere.
Separate processing from storage
A frame must be transmitted and processed to produce the connected reply. Non-storage by JML describes what happens after that processing in the current release; it does not make the feature on-device. Connected processing remains subject to the active service's controls, and technical security records may follow different rules than image or reply content.
Match the promise to the policy version
The consent text has a version and cryptographic reference so the service can record which disclosure applied. If a future feature needs history, personalization, or saved captures, it should not inherit today's non-storage language. The owner should receive a new explanation before materially different retention begins.
Minimize what enters the frame
Even with a strong non-storage commitment, data minimization is the safer habit. Move private documents, bystanders, screens, and location clues out of view. Capture only the object or text needed for the question, and avoid Sight entirely when the same answer is available without sending an image.
The short version
- JML's current promise covers storage of the Sight frame and reply by JML.
- Connected processing and service controls still apply.