Is Grammarly a keylogger? What can you do about it?

Is Grammarly a keylogger? What can you do about it?

Sometimes when I sit down and try to write, the words don’t flow. The sentences
are clumsy, the words bump into each other, and I always have the sneaking
suspicion that there is a more straightforward way to get my point across. I
just can’t always get there on my own.

Enter Grammarly.

YouTube video

Their pitch? Forget that D+ you got in 9th Grade English 20
years ago; we will make you sound compelling, concise, —and let’s face it— smarter.
Their cheerful videos provide persuasive examples of this value proposition in
action, as pithy phrases (which all too closely resemble my writing skills) are
transformed like Cinderella into glamourous ball-room dancing maxims for the

But just like Cinderella, there’s always a catch. The problem, it seems, is that
Grammarly is only willing to perform this magic trick on their cloud.
That means, every. single. bit. of. text. you want improved is sent to them.
As an individual, you may be all too willing to agree to that bargain. But
what about businesses and IT teams? How do they evaluate Grammarly? On the one
hand, it’s a tool potentially beloved by your users, but on the other, it’s a
potential nightmare for keeping your secrets, well… secret! Is this any
different than the same bargain offered by other cloud-based word processors or
chat tools?

Let’s figure it out.

No one wants their product to be called a keylogger. The term evokes images of
creeps installing malware on devices for the express purpose of surveillance
and password harvesting. Yet, by explicit definition, any tool that logs a user’s
keystrokes and sends them to a third party is technically a keylogger.

This must come up a lot for Grammarly because they have an official response
to the question right on their support page

Here is a direct quote (emphasis mine)

Grammarly does not record every keystroke you make on your device. Grammarly
accesses only the text you write when you are actively using a Grammarly
product offering
: The product checks only the text you want it to
and provides writing suggestions. Additionally, Grammarly’s product is blocked
from accessing text in fields marked “sensitive.”
This means that
Grammarly’s desktop applications and mobile keyboards do not see anything
typed in credit card forms, password fields, URL fields, email address
fields, or fields where similar private information is provided.

Sure, this is an answer, but as we will see later, it vastly
oversimplifies how Grammarly captures text in practice. Grammarly is
essentially saying that it is not a keylogger because the user
chooses when Grammarly can receive text, and Grammarly provides value. It’s an
answer carefully built around a technicality.

Sebastian breaks it down much better:

Grammarly *ISa keylogger. They try to dodge it by
saying “Grammarly accesses only the text you write while using our product”

— Sebastian (@sebmck) March 8, 2019

Here’s the problem: Grammarly’s framing of the question isn’t helpful.
When people ask, “Is Grammarly a keylogger?” they are really asking,
“Am I going to regret using this service?” To answer that question as a
security practitioner, here are some things I would want to know:

  1. What methods does Grammarly use to capture text I write?
  2. What sensitive data could be captured inadvertently?
  3. What is Grammarly allowed to do with the text that they capture?

Let’s find out.

Grammarly offers a variety of products under their
branding. If I want to use Grammarly, the options include:

  • A web-based document editor
  • A web-browser extension
  • An app-specific add-in (ex: Microsoft Word)
  • A custom installable keyboard (for mobile devices)
  • An app running on your OS

A graphic that displays Grammarly's apps.

Each one of these methods comes with different risks and tradeoffs. Today
I want to focus on what is likely the most popular method of utilizing
Grammarly, running it as an app on your device. Since I run macOS, let’s
dig into that one.

On macOS, when you install Grammarly, you are first presented with a screen
that looks like this:

A screenshot of the installation screen for the macOS version of the Grammarly app. The screenshot asks the user to add Grammarly to the list of apps with accessibility permissions and offers a button to kick off that process.

And then helpfully pops up the following screen:

A screenshot of the System Preferences app showing the Security pane. On the bottom of the app Grammarly has anchored its own window with arrows that direct the user to unlock the pane and check the box next to Grammarly which will instantly grant it the accessibility permissions.

Grammarly is briskly moving you through this process because their
app cannot function as designed unless it has these specific accessibility

But why would a grammar app need accessibility permissions? It turns out that
accessibility permissions are like the Holy Grail of permission entitlements.
Accessibility permissions allow approved apps to fully control the entire
computer as if they were sitting next to you, watching your screen, and holding
their hand on top of yours while you typed on the keyboard and moved the mouse.

Based on my brief usage of the app, in practice, this means:

  1. Capturing all of the text inside any application used by the user.
  2. Capturing new keystrokes entered into any other app.
  3. Augmenting/Manipulating the UI of other apps in focus.

Once this permission is granted, Grammarly can now capture text and send it
back to its servers without any further user interaction. No other permissions
or extensions are needed.

Grammarly Captures Text That You Already Typed Before You Installed It

Revisiting the keylogger answer
from earlier:

“…Grammarly accesses only the text you write when you are actively using a
Grammarly product offering.”

In my reading, Grammarly heavily implies that users have a fair degree of
control over what Grammarly can access. But in practice, this is very
. Let me show you why.

Below, I have composed a new note in riddled with grammatical errors.
I did not have Grammarly running while writing the document, so
there isn’t any possibility that keystrokes have been sent to them.

The with various grammatically incorrect sentences.

After running the Grammarly app, re-granting the accessibility permission,
and then putting the app in focus, the screen looks like the following:

The same with the various grammatically incorrect sentences now with the Grammarly widget activated and the text marked up by Grammarly.

Grammarly processes text that was already entered in the window

Grammarly parsed and marked up my document without me typing a single
keystroke. All I needed to do was bring the window into the foreground.
This makes sense; Grammarly would not be easy to use if it could only provide
grammar advice on the documents and words you typed when it was running. I’m
not even sure how much Grammarly even cares about the keystrokes you’re typing;
if it can read what was written previously, it does not need to.

That being said, I believe it is stretching credulity when they
say, “Grammarly accesses only the text you write when you are actively using a
Grammarly product offering.”

This is a big problem when it comes to claims that users have control. As a
user, I had no way to know that the instant I opened the Grammarly
would swoop in, scrape all the text, and send it to their servers. Now that I
know a document was scraped, I can tell Grammarly to stop doing that in the
future, but the cat is already out of the bag. As far as I can tell, there is
no easy way to preemptively block Grammarly from accessing apps without you
first allowing it to activate in the app and performing the block in-situ.

How do I know when and where Grammarly will even activate? It’s impracticable
(perhaps impossible?) to tell until it’s already happened. This lack of consent
is fundamentally dishonest.

Now that we know Grammarly can capture text by reading the content of the apps
in focus, how do we know it won’t collect sensitive information? From their
support page

…Grammarly is blocked from accessing anything you type in text fields marked
“sensitive,” such as credit card forms or password fields. You can deactivate
Grammarly at any time if you don’t want it to check a particular piece of text.

Sounds great on the surface, but let’s dig in. First, what in practice
constitutes a sensitive field? Their support only offers two obvious examples
password fields and credit cards, but what about Social Security Numbers?

Here I’ve constructed a simple form with the following markup:

class="input text optional marketing_sales_contact_request_ssn">

Here is what happens when I click into the resulting form in my browser
with the Grammarly app installed on macOS:

A cropped screenshot of a form-field that shows a social security number entered into a text-area with the Grammarly widget active.

See that Grammarly widget? That means despite the words “Social Security Number”
and “SSN” appearing multiple times in the markup, Grammarly instantly activates
as soon as I put focus into the text area. It seems as long as something is a
and not a single-line input field, Grammarly is all too eager to
activate and pull down something potentially sensitive.

The above example may be contrived
(unless you use many poorly programmed sites from local governments),
but it demonstrates a more significant point. There is no way to know
when and why Grammarly will activate
. And when it does, it’s already
too late.

Grammarly’s support page Q&A is helpful, but there are no guarantees (or likely even
consequences) if it’s inaccurate. That’s not true in the
Privacy Policy,
a legal document that they enter with each user of their service.
Because of this, we are far more likely to get an accurate picture.

Here are some salient excerpts (emphasis mine)

Yes, User Content Is Collected

User Content.
This consists of all text, documents, or other content or
information uploaded, entered, or otherwise transmitted by you in connection
with your use of the Services and/or Software. For more information about
how we care for and protect your User Content, please see our User Trust

Yes, User Content Can Be Accessed And Reviewed By Humans At Grammarly

As a rule, Grammarly employees do not monitor or view your User Content
stored in or transferred through our Site, Software, and/or Services, but it
may be viewed if we believe the Terms of Service have been violated

and confirmation is required, if we need to do so to respond to your requests
for support, if we otherwise determine that we have an obligation to
review it as described in the Terms of Service, or to improve our algorithms
as described in the User Content section of our Terms of Service


Finally, your Information may be viewed where necessary to protect the
rights, property, or personal safety of Grammarly and its users, or to
comply with our legal obligations
, such as responding to warrants,
court orders, or other legal processes

Data Is Retained for an Undisclosed Amount of Time Even After Account Deletion

How long is Personal Data retained?
You can remove your Personal Data from Grammarly at any time by deleting
your account as described above. However, we may keep some of your Personal
Data for as long as reasonably necessary for our legitimate business
, including fraud detection and prevention and to comply with our
legal obligations including tax, legal reporting, and auditing obligations.

It’s clear that once Grammarly has its hands-on “User Content,” it stores it,
makes it accessible to certain privileged employees, and can share that
information with others (like law enforcement) if compelled via legal means.
Also, interestingly, since they claim they may need to access “User Content”
during support interactions, it heavily implies that this data is associated
with your account.

Putting my Corporate Governance cap on, imagine a competitor suing you. They
ask the judge to subpoena all available information related to
conversations about them and your resulting strategy. Even if you only
retain logs/emails for a short period, if the opposing counsel believed a few
key employees had Grammarly, they could produce copies of documents
(conversations, emails, papers) that were not accessible through any other
means. That’s a huge deal.

There are many ways to use Grammarly, the browser extension, the app, and
even a web-based tool. Except for the web-based tool, they all
suffer from the same underlying problem, lack of ongoing consent to collect
the data they need to perform their service. As a result, any company with
users who use Grammarly should react swiftly to educate users about the above

Use The Web Editor

A screenshot of Grammarly's web-based word processor.

The web-editor is the safest bet because you can control what is entered.

If users don’t want to lose the benefit, the web editor is your safest bet
because they can ensure that the program can’t access any data or content
except what the user types or pastes onto the web pages. This method gives you
the most control over what the application can record.

Use an Open-Source Alternative

After initial publication of this article, a few folks reached out to me to
let me know about a company called LanguageTool.
They provide a similar experience to Grammarly, but with one key difference. If
you wish, you can run your own server.

In theory, a concerned IT team could setup a server to ensure data isn’t
being sent to a third-party and direct their team to make the switch. That said,
in practice, the perceived impact of this change on users could be extreme,
especially if the quality of the suggestions isn’t as good. Therefore the
other alternatives above might be a better compromise.

Is the Browser Extension Any Safer?

One commenter on Hackernews

“This article misses the way I use it, which is much safer. I am security
minded but also a terrible writer. I have Grammarly as a browser extension
that is OFF BY DEFAULT, except, when I am writing on Medium, and a few times
when I click to enable it temporarily. Problem solved! […]”

So while we didn’t do a deep-dive into the extension, this comment piqued my
interest. When we looking briefly at the privacy information in the
Google Chrome Web Store, we certainly are not off to a promising start.

A screenshot of the Grammarly privacy disclosure page on the Google Web Store. It shows that Grammarly collects and sends a lot of personal information including the contents of webpages, the location of the user, user activity, and personal communications

The red boxes (added by me) show how much data Grammarly potentially collects

After installing the extension and viewing its permissions, you can see the

A screenshot of Google Chrome's extension configuration screen showing the various permissions that Grammarly asks for. Several items are highlighted, specifically that Grammarly has the ability to

While I expected the extension to be able to modify webpages, the need to read
my browser history was a surprise. The key question though is, can Grammarly
see any web browsing history that Chrome recorded prior to a user activating
the extension?

To answer this, I found the extension on my device and looked at the
manifest.json file. This file contains a lot of important metadata about the
extension, but the section we care about is the permissio

Read More



Hey! look, i give tutorials to all my users and i help them!