Ext Ops Panel
Open dashboard
Permissions and history

Is Vibes.ai Automator safe to install?

Vibes.ai Automator asks for 6 browser permissions and 3 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.

Vibes.ai Automator

Chrome extension by neutronsamu · Productivity · Tools

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
1 kind of data declared
Publisher
No store badges
Audience
650 users · 5.0/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

Specific sites only: 3 match patterns.

Reaches your browsing data or every site

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.

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

650 users

Users
+298 since 01.09
352-650 · 39 readings
  1. 2026-09-01352
  2. 2026-09-02364
  3. 2026-09-04385
  4. 2026-09-05389
  5. 2026-09-06397
  6. 2026-09-07396
  7. 2026-09-08402
  8. 2026-09-09412
  9. 2026-09-13433
  10. 2026-09-15454
  11. 2026-09-17468
  12. 2026-09-20484
  13. 2026-09-21485
  14. 2026-09-25524
  15. 2026-09-26546
  16. 2026-09-28558
  17. 2026-10-04598
  18. 2026-10-08629
  19. 2026-10-09621
  20. 2026-10-10625
  21. 2026-10-13630
  22. 2026-10-16600
  23. 2026-10-17598
  24. 2026-10-18594
  25. 2026-10-19598
  26. 2026-10-20599
  27. 2026-10-21625
  28. 2026-10-22621
  29. 2026-10-23615
  30. 2026-10-24616
  31. 2026-10-25621
  32. 2026-10-26627
  33. 2026-10-28642
  34. 2026-10-29639
  35. 2026-10-30641
  36. 2026-11-01649
  37. 2026-11-02639
  38. 2026-11-04650
  39. 2026-11-05650

What the store shows

The store shows none of its badges on this listing. Most listings carry none.

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

neutronsamu, who publishes 5 listings we track. This listing has been in the store since 2026-07-12 and was last updated on 2026-08-17.

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. Meu Batch pro Vibes.ai Access to specific sites only · 5 permissions, 3 site patterns 4 users
  2. Scalable Creators - Veo Automation Access to specific sites only · 5 permissions, 1 site pattern 38 users ★ 1.0
  3. FlowPilot Studio Access to specific sites only · 5 permissions, 3 site patterns 84 users ★ 3.8

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

Back to Vibes.ai Automator · Alternatives to Vibes.ai Automator

Where the data comes from: how the catalog is built