Keystrokes don’t have to be in a text field or input. That’s my point.
If I’m on say google. And I type anything into the field it’s definitely capturing it. You know this for no other reason then it would have to be with autocomplete as an option.
Keystroke capturing is the same as keylogging, aka anything typed even if it’s not into a place where you would assume it’s being seen by the app. Aka, if I had an app open in the background and was typing in my password, it would see and capture that.
They’re completely different things. While the privacy issues of US large tech companies are abundant and awful, there is a large difference between keystroke capturing and capturing input via fields. Especially when you’re agreeing to allow them to process and transfer or even sell that information.
But that’s not what the terms on both Google/Meta and Deepseek say.
Google/Meta has no obligation to restrict the data collection to forms, if the ToS allowd them to collect them from forms (and as you admited, we do know for a fact that they do), then there’s no reason it also does not allow them to collect them outside of forms (which we don’t, for a fact, know).
In the same way, Deepseek terms don’t say the logging happens for “anything typed” like you are assuming without evidence. For all we know the only place they might be capturing it is exclusively in very specific forms, or they might even only added that to the terms so that they can add suggestions in the future. You can only make assumptions, since the terms are not specific on exactly what’s being captured and in which way, it only says keystrokes in the case of Deepseek and even more generic (and thus allowing more possible vectors) in Google/Meta’s terms.
Keystrokes don’t have to be in a text field or input. That’s my point.
If I’m on say google. And I type anything into the field it’s definitely capturing it. You know this for no other reason then it would have to be with autocomplete as an option.
Keystroke capturing is the same as keylogging, aka anything typed even if it’s not into a place where you would assume it’s being seen by the app. Aka, if I had an app open in the background and was typing in my password, it would see and capture that.
They’re completely different things. While the privacy issues of US large tech companies are abundant and awful, there is a large difference between keystroke capturing and capturing input via fields. Especially when you’re agreeing to allow them to process and transfer or even sell that information.
But that’s not what the terms on both Google/Meta and Deepseek say.
Google/Meta has no obligation to restrict the data collection to forms, if the ToS allowd them to collect them from forms (and as you admited, we do know for a fact that they do), then there’s no reason it also does not allow them to collect them outside of forms (which we don’t, for a fact, know).
In the same way, Deepseek terms don’t say the logging happens for “anything typed” like you are assuming without evidence. For all we know the only place they might be capturing it is exclusively in very specific forms, or they might even only added that to the terms so that they can add suggestions in the future. You can only make assumptions, since the terms are not specific on exactly what’s being captured and in which way, it only says keystrokes in the case of Deepseek and even more generic (and thus allowing more possible vectors) in Google/Meta’s terms.