Of course – if the AI is supposed to give you an answer, they have to know what you are writing, so yes, logging your keystrokes is quintessential for every online service you interact with. You cannot get an answer without asking.
The wording is strange, though, and I’m not sure whether this ToS allows them to collect and process what you are typing while using their service, or all your typing.
logging your keystrokes is quintessential for every online service you interact with
No, it is not. Services expect the “complete” payload, whether a prompt, a text message, or whatever, it doesn’t matter if you typed it, if you copy-pasted it or something else. None of them need to analyze stuff you’ve typed, deleted and never sent.
Generally yes, but there is one use case where every key stroke is often recorded and analyzed, a search bar. If it’s trying to fill out suggestions as you type, every keystroke is recorded as you go.
They don’t need to read the keystrokes, they need to read what’s in the input box. In programming terms, you’re evaluating the field in real time, you’re not waiting for the “send request”, nor are you keylogging, otherwise the existence of the field would be irrelevant.
Keystroke patterns and rhythms is above and beyond, though. That’s not remotely necessary and the kind of thing that can only be used to track an individual across multiple platforms and attempts at anonymity. I don’t know how effective it is at that, but that is the sole purpose unless maybe they are training a better autocorrect tool and think that would be helpful.
At any rate, that’s the point where I noped out. They are completely honest about putting every effort into identifying users and associating them with real identity. Such a system would be quite capable of de-anonymizing marketing profiles, health data, etc. by correlating vast amounts of data.
Of course – if the AI is supposed to give you an answer, they have to know what you are writing, so yes, logging your keystrokes is quintessential for every online service you interact with. You cannot get an answer without asking.
The wording is strange, though, and I’m not sure whether this ToS allows them to collect and process what you are typing while using their service, or all your typing.
No, it is not. Services expect the “complete” payload, whether a prompt, a text message, or whatever, it doesn’t matter if you typed it, if you copy-pasted it or something else. None of them need to analyze stuff you’ve typed, deleted and never sent.
Generally yes, but there is one use case where every key stroke is often recorded and analyzed, a search bar. If it’s trying to fill out suggestions as you type, every keystroke is recorded as you go.
They don’t need to read the keystrokes, they need to read what’s in the input box. In programming terms, you’re evaluating the field in real time, you’re not waiting for the “send request”, nor are you keylogging, otherwise the existence of the field would be irrelevant.
Keystroke patterns and rhythms is above and beyond, though. That’s not remotely necessary and the kind of thing that can only be used to track an individual across multiple platforms and attempts at anonymity. I don’t know how effective it is at that, but that is the sole purpose unless maybe they are training a better autocorrect tool and think that would be helpful.
At any rate, that’s the point where I noped out. They are completely honest about putting every effort into identifying users and associating them with real identity. Such a system would be quite capable of de-anonymizing marketing profiles, health data, etc. by correlating vast amounts of data.
Quintessential does not mean “really essential”, and does not make sense in this context.
You can’t really be quintessential “for” something; only quintessential of something.
Ethymologically you are right, I wasn’t really aware of the alchemical background of five rounds of destillation when I wrote my comment.
Nonetheless, “quintessential for” is not unheard (or rather unread?) of:
It will take another generation or two until this usage becomes normalized, so thank you for pointing me to a better style.