Ext Ops Panel
Open dashboard
Permissions and history

Is Email Signature Generator for Gmail — ProSignature safe to install?

Email Signature Generator for Gmail — ProSignature asks for 3 browser permissions and 1 site pattern. 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.

What the developer says, and 4 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
Declares it collects none
Audience
23 users · 5.0/5

What data it declares

The developer declares that it does not collect or use your 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: 1 match pattern.

Worth knowing

Routine for an extension

Pages it runs its code on

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

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: 1 site pattern.

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 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

23 users

Users
+18 since 31.08
5-26 · 28 readings
2026-09-18: released 0.2.32026-10-01: gained the good publisher record badge2026-10-09: released 0.2.52026-10-16: released 0.3.0
  1. 2026-08-315
  2. 2026-09-029
  3. 2026-09-058
  4. 2026-09-068
  5. 2026-09-0811
  6. 2026-09-0910
  7. 2026-09-1311
  8. 2026-09-1512
  9. 2026-09-1618
  10. 2026-09-2117
  11. 2026-09-2522
  12. 2026-09-2626
  13. 2026-09-2825
  14. 2026-10-0419
  15. 2026-10-0821
  16. 2026-10-0924released 0.2.5
  17. 2026-10-1023
  18. 2026-10-1122
  19. 2026-10-1322
  20. 2026-10-1723
  21. 2026-10-1922
  22. 2026-10-2021
  23. 2026-10-2220
  24. 2026-10-2422
  25. 2026-10-2521
  26. 2026-10-2824
  27. 2026-10-2923
  28. 2026-10-3023

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. Asked for more permissions (4, was 3) (changed: browser permissions, sites that can connect to it)

Versions we have seen

  1. Version 0.3.0 · Asked for more permissions (4, was 3) (changed: browser permissions, sites that can connect to it)
  2. Version 0.2.5
  3. Version 0.2.3

Who publishes it

The store lists no publisher name, who publishes 2 listings we track. This listing has been in the store since 2026-07-20 and was last updated on 2026-10-16.

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 Signature Maker No site access · 1 permission 12 users ★ 5.0
  2. SignedRise - Professional Email Signature No site access · 1 permission 148 users ★ 5.0
  3. Email Signature Maker Access to specific sites only · 1 permission, 6 site patterns 330 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 Signature Generator for Gmail — ProSignature access?
Specific sites only: 1 match pattern. It declares 3 browser permissions.
What data does Email Signature Generator for Gmail — ProSignature collect?
The developer declares that it does not collect or use your data. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has Email Signature Generator for Gmail — ProSignature asked for more permissions over time?
Its permissions changed once while we watched, on 2026-10-16.
Does Email Signature Generator for Gmail — ProSignature 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-30.

Back to Email Signature Generator for Gmail — ProSignature · Alternatives to Email Signature Generator for Gmail — ProSignature

Where the data comes from: how the catalog is built