4 ms·

See, the issue isn’t what Grammarly stores, that’s a sensibility defined policy. It’s what I would send to Grammarly that prevents me ever using it or any servi

See, the issue isn’t what Grammarly stores, that’s a sensibility defined policy. It’s what I would send to Grammarly that prevents me ever using it or any service like it. I don’t care how little data you’re storing. I type passwords into my browser and as a software developer I will never be sufficiently confident that you aren’t accidentally getting sent username and password box text even if you tried your damnedest to avoid it. The problem is you’re a keylogger. Ostensibly one with a positive reason your customers install you, but you fundamentally are a keylogger. I cannot trust such an application… ever.

gramhan 4y ago
Our product is blocked from accessing text fields like password and credit card number fields (you can see this because Grammarly clearly does not activate in those fields). You can see what Grammarly is processing by the presence of the Grammarly widget, and you can turn Grammarly off at any time if you don’t want it to check a particular piece of text. It works where you want it to work to provide writing suggestions to you, which I understand just may not be for you (and that's OK).
- techdragon 4y ago
  My point is more that since even my password manager occasionally has trouble identifying a password field to let me automatically fill in the passwords I have stored (this being representative of the challenge of correctly identifying such fields) … I can’t necessarily trust Grammarly to always correctly identify a text box as a username or password field or credit card field no matter how hard you’re trying to avoid this sort of thing, the only safe way would be manually activation and deactivation. Or explicit selection of text to be sent to Grammarly. But regardless of that, when my Operating System has a safe one I can trust is (for now at least) running locally (macOS) it’s hard to justify the risk of accidental exposure of sensitive information to Grammarly such as Personally Identifying Information about clients and other such business and legal risks which goes way beyond a simple matter of passwords. Grammarly is a security risk, and while I’m sure you’re all working hard to mitigate this as best as you can, you cannot eliminate certain fundamental security risks that are inherent in sending blocks of text to a third party, even manually sending a block of text contains a small level of risk that it could contain information you forgot (for a large block like a document) or included by accident without noticing (for a small block) and so it just cannot be eliminated.

gramhan 4y ago

Our product is blocked from accessing text fields like password and credit card number fields (you can see this because Grammarly clearly does not activate in those fields). You can see what Grammarly is processing by the presence of the Grammarly widget, and you can turn Grammarly off at any time if you don’t want it to check a particular piece of text. It works where you want it to work to provide writing suggestions to you, which I understand just may not be for you (and that's OK).

techdragon 4y ago
My point is more that since even my password manager occasionally has trouble identifying a password field to let me automatically fill in the passwords I have stored (this being representative of the challenge of correctly identifying such fields) … I can’t necessarily trust Grammarly to always correctly identify a text box as a username or password field or credit card field no matter how hard you’re trying to avoid this sort of thing, the only safe way would be manually activation and deactivation. Or explicit selection of text to be sent to Grammarly. But regardless of that, when my Operating System has a safe one I can trust is (for now at least) running locally (macOS) it’s hard to justify the risk of accidental exposure of sensitive information to Grammarly such as Personally Identifying Information about clients and other such business and legal risks which goes way beyond a simple matter of passwords. Grammarly is a security risk, and while I’m sure you’re all working hard to mitigate this as best as you can, you cannot eliminate certain fundamental security risks that are inherent in sending blocks of text to a third party, even manually sending a block of text contains a small level of risk that it could contain information you forgot (for a large block like a document) or included by accident without noticing (for a small block) and so it just cannot be eliminated.