Ext Ops Panel
Open dashboard
Permissions and history

Is Zoēs Beta - AI Email Security safe to install?

Zoēs Beta - AI Email Security asks for 3 browser permissions and 11 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.

Zoēs Beta - AI Email Security

Chrome extension by Zoes Security Inc. · Make Chrome Yours · Privacy

Open in the Chrome Web Store
What the developer says, and 5 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 specific sites only
Data collection
2 kinds of data declared
Upkeep
Updated 234 days ago
Audience
6 users

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

Specific sites only: 11 match patterns.

Worth knowing

Routine for an extension

Pages it runs its code on

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

Show the remaining 8
  • https://outlook.office.com/* only outlook.office.com
  • https://outlook.office365.com/* only outlook.office365.com
  • https://zoes.one/auth/extension* only zoes.one
  • https://auth.zoes.one/extension* only auth.zoes.one
  • https://*.zoes.one/auth/extension* zoes.one and all its subdomains
  • https://*.zoes.one/extension* zoes.one and all its subdomains
  • https://zoes.one/* only zoes.one
  • https://*.zoes.one/* zoes.one 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 Make Chrome Yours · Privacy, 42% of extensions ask for access to every site. This one: Access to specific sites only.

The typical extension there declares 3 browser permissions; this one declares 3 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

6 users

Users
+1 since 01.09
4-6 · 24 readings
  1. 2026-09-015
  2. 2026-09-026
  3. 2026-09-045
  4. 2026-09-066
  5. 2026-09-075
  6. 2026-09-086
  7. 2026-09-095
  8. 2026-09-156
  9. 2026-09-165
  10. 2026-09-206
  11. 2026-09-215
  12. 2026-09-276
  13. 2026-09-284
  14. 2026-10-085
  15. 2026-10-096
  16. 2026-10-105
  17. 2026-10-176
  18. 2026-10-185
  19. 2026-10-216
  20. 2026-10-225
  21. 2026-10-236
  22. 2026-10-245
  23. 2026-10-296
  24. 2026-10-316

What the store shows

The listing says it offers in-app purchases.

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.

The permissions this extension requests have not changed since we started watching it.

Who publishes it

Zoes Security Inc.. This listing has been in the store since 2025-12-23 and was last updated on 2026-03-11.

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. PhishSignal No site access · 1 permission 13 users ★ 5.0
  2. PhishGuard AI Access to specific sites only · 1 permission, 2 site patterns 2 users
  3. Email Security Analyzer Access to specific sites only · 1 permission, 7 site patterns 7 users

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 Zoēs Beta - AI Email Security access?
Specific sites only: 11 match patterns. It declares 3 browser permissions.
What data does Zoēs Beta - AI Email Security collect?
The developer declares that it collects these kinds of data: Personally identifiable information, User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Zoēs Beta - AI Email Security asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does Zoēs Beta - AI Email Security 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 Zoēs Beta - AI Email Security · Alternatives to Zoēs Beta - AI Email Security

Where the data comes from: how the catalog is built