Your data is incredibly sensitive and we don't take your trust lightly. eesel is purpose built to work totally locally. Everything lives in your local storage never to be accessed by anyone other than you and your local installation of eesel. Don't just believe us, see it for yourself.


In this exercise we're going to dissect the network requests eesel makes and verify that no network requests are made with your personal data. This should take 10mins. At the end of this you'll feel confident that we don't pass on any information like:

  • your name, email or company
  • the products you've installed
  • any work data at all

You'll also know the anonymised events and attributes we do pass on to Intercom like:

  • your anonymous user id
  • events when eesel is opened or closed

We'll look at what happens across the extension - in your new tab, in a doc, in spotlight and in your extension's background page (translation: it's the hidden brain of the extension).

Steps to verify

1. Open a new tab

Let's hack into the mainframe. 

2. Open your DevTools network tab

Press Command+Option+J (Mac) or Control+Shift+J  (Windows, Linux, Chrome OS) to go to your DevTools and switch to the network tab. This shows all the network requests that your browser makes.

3. Refresh the page and snoop around

Click into each resource and see exactly what your browser is sending and receiving. 

You'll notice:

  • the newtab HTML  and JS  files that are used to render eesel
  • image files used for product filters
  • Intercom scripts to load Intercom, so you can talk to us if you have an issue or a feedback
  • 'ping' which is an Intercom object that is used for anonymous Intercom events (more on that below)

You'll notice that there's no personal information in any of the preview objects. 

4. Investigate 'ping' and see your anonymous user id :)

eesel stores an anonymous, unique id for you (and every user) to, well, know how many users are there :). We also associate some basic events with this id to help us improve things. In order to investigate these events, we'll need to go the background page from where events are sent.

5. Go to your local background page

Almost every chrome extension uses a background page. This is basically the brain behind eesel and you can find it here.

It's beautiful, isn't it?

6. Open the networks tab

Let's investigate network requests in the background page.

7. Start browsing around in another tab

Go to your eesel new tab, go to a doc, open spotlight and so on. Investigate the network requests that the background page makes. eesel sends events when:

  • eesel is opened or closed - to know how many active users we have
  • a doc is viewed and when eesel is used to open a doc - to know if we're actually helping you open a doc
  • when a product filter is used - to know if filters are useful and need to be improved
  • when search is used - to know if search is used and needs to be improved

Every time an event is fired, you get this handy events object to poke into :)

Once again, you'll see that no personal work data leaves your local machine.


That's it! Notice that we don’t send any information about which doc you opened, which product filters you used, or the keywords you searched. You've hacked into the mainframe and shown how your personal data never leaves your browser. If you get stuck at any point or have more follow up questions, let us know :)

Did this answer your question?