Ext Ops Panel
Open dashboard
Permissions and history

Is Email Tracker for Gmail by EngageBay safe to install?

Email Tracker for Gmail by EngageBay asks for 7 browser permissions and 2 site patterns. We do not audit code and we do not judge intent; what we can show is what the listing declares and whether that has changed while we have been watching.

Email Tracker for Gmail by EngageBay

Chrome extension by EngageBay Inc · Productivity · Tools

Open in the Chrome Web Store
What the developer says, and 6 screenshots

Loading from the Chrome Web Store. Open the listing if it does not appear.

At a glance

Facts, not a score: an ad blocker needs every page and a theme needs nothing, so one number would be wrong about both. Each fact links to its detail.

Site access
Access to every site
Data collection
2 kinds of data declared
Audience
1k users · 3.9/5

What data it declares

The developer declares that it collects these kinds of data:

The developer also certifies that your data is not sold to third parties outside approved uses, not used for purposes unrelated to the extension's core function, and not used to decide creditworthiness or lending.

The listing links to a privacy policy.

This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.

What Chrome asks you to allow

When you add it, Chrome asks you to allow it to:

Derived from the manifest by Chrome's documented rules; the dialog's exact wording depends on your Chrome version and language. Chrome asks again if an update requests more.

What it can reach

Every site you visit. This extension can read and change the content of any page you open. What access to every site means

Reaches your browsing data or every site

Routine for an extension

Pages it runs its code on

It runs its own code on specific pages only: 16 site patterns.

Show the remaining 13
  • *://*.outlook.office365.com/* outlook.office365.com and all its subdomains
  • *://*.outlook.office.com/* outlook.office.com and all its subdomains
  • https://*.linkedin.com/* linkedin.com and all its subdomains
  • http://*.linkedin.com/* linkedin.com and all its subdomains
  • *://*.appspot.com/* appspot.com and all its subdomains
  • *://*.engagebay.com/* engagebay.com and all its subdomains
  • http://localhost:8888/* only localhost
  • https://*.google.co.in/search?num=100* google.co.in and all its subdomains
  • http://*.google.co.in/search?num=100* google.co.in and all its subdomains
  • https://*.google.com/search?num=100* google.com and all its subdomains
  • https://www.google.com/search?gws_rd=cr&as_qdr=all&q=* only www.google.com
  • https://www.google.co.in/search?gws_rd=cr&as_qdr=all&q=* only www.google.co.in
  • https://*.google.com/search?q=* google.com and all its subdomains

A content script is code the extension injects into pages matching these patterns. On those pages it can read and change what you see, whether or not a host permission is listed above.

Sites that can connect to it

Web pages matching these patterns can open a messaging channel to it: 2 site patterns.

Declared as externally connectable in the manifest: a page on these sites can exchange messages with the extension, for example to tell it you have signed in. It does not give the page access to your browser.

How usual this is for its category

In Productivity · Tools, 20% of extensions ask for access to every site. This one: Access to every site.

The typical extension there declares 3 browser permissions; this one declares 7 browser permissions.

Counted over the live extensions of the same category after our latest full pass of the store. A share is context, not a verdict: what is normal depends on what the extension is for.

Who uses it and how it is kept up

1k users

Users
unchanged since 31.08
1k · 2 readings
2026-10-12: released 2.1.3
  1. 2026-08-311k
  2. 2026-10-311k

What the store shows

Has it asked for more over time?

This is the question a permission list on its own cannot answer. An extension that shipped narrow and widened later is a different proposition from one that always asked for the same thing.

  1. Changed where it works (changed: sites that can connect to it)

Versions we have seen

  1. Version 2.1.3 · Changed where it works (changed: sites that can connect to it)

Who publishes it

EngageBay Inc. This listing has been in the store since 2018-10-01 and was last updated on 2026-10-12.

Similar extensions that ask for less

Listings close to this one in what they say they do, which declare less reach. Less reach is not a verdict on either: compare what each needs for the job.

  1. Email Eye - Email Tracker for Gmail Access to specific sites only · 2 permissions, 3 site patterns 57 users
  2. MailTraceX — Email Tracker & Read Receipts for Gmail Access to specific sites only · 2 permissions, 2 site patterns 55 users ★ 5.0
  3. Mail Tracker by Mailsumo • Email Tracker for Gmail Access to specific sites only · 3 permissions, 1 site pattern 1k users ★ 5.0

How to check or remove it in Chrome

  1. Type chrome://extensions in the address bar and find the extension in the list.
  2. Open its details. The site access setting shows where it can run; set it to run only on click and it reaches a page only after you press its icon.
  3. To uninstall it, choose Remove on the same page.

Questions people ask

What can Email Tracker for Gmail by EngageBay access?
Every site you visit. This extension can read and change the content of any page you open. It declares 7 browser permissions.
What data does Email Tracker for Gmail by EngageBay collect?
The developer declares that it collects these kinds of data: Authentication information, Personal communications. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Email Tracker for Gmail by EngageBay asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-12.
Does Email Tracker for Gmail by EngageBay publish a privacy policy?
Yes, the store listing links to a privacy policy.

We read the public store listing up to 2 times a day and keep what it declared. We do not install the extension, do not audit its code, do not judge its intent and publish no contact details for its developer. Last read on 2026-10-31.

Back to Email Tracker for Gmail by EngageBay · Alternatives to Email Tracker for Gmail by EngageBay

Where the data comes from: how the catalog is built