Request for Clarification on Definition of "On-Device Models" Based on TAG Feedback

Hi folks,

I am reaching out to the group to seek clarification on the definition of
"on-device models" in light of the recent feedback and
<https://github.com/w3ctag/design-reviews/issues/1038#:~:text=A.%20The%20sam
e,this%20category%20challenging> discussion from the TAG regarding the place
where models are run. Also, the
<https://github.com/w3ctag/design-reviews/issues/948#issuecomment-2256555364
> TAG review on the API mentions preference for on-device models (as "
<https://github.com/w3ctag/design-reviews/issues/948#:~:text=input%20support
..-,We%27re%20concerned%20about%20the%20use%20of%20the%20network.,-Specifical
ly%2C%20use%20of> We're concerned about the use of the network", may need
you press the "load more" button to be able to see the exact TAG review).

Reviewing TAG discussions, there are several scenarios that could be
considered as "on-device" processing, which include:

1. The same device that the UA (User Agent) is running on.
2. Encrypted connections to other devices that the same user owns, for
example, to allow a phone to offload work to the same person's desktop.
3. Various flavours of private computation on other people's computers,
ranging from homomorphic encryption to TEEs (Trusted Execution
Environments).
4. "Service providers" (in the GDPR sense) for the user, who have
committed not to use or expose the data outside that particular user's
context.
5. Distinct data controllers (again in the GDPR sense), who could use
the user's data for their own purposes.

Given these scenarios, I would like to understand how the group interprets
and applies the term "on-device models." Specifically:

* Scope of "On-Device": Does the group consider only scenario A
(processing on the same device) as "on-device," or does it extend to
scenarios B, C, and D as well?
* Implications for Privacy and Security: How do these different
scenarios impact privacy and security considerations for the models (we can
use the writing assistant API models as usecase, but it can be extended)?
* Alignment with TAG Recommendations: How does the group plan to align
its definition and implementation of "on-device models" with the TAG's
feedback and recommendations?

Clarifying these points can be stepping stone for further discussions on
security and privacy aspects of on-device processing.

Best Regards,
Ehsan