Ext Ops Panel
Open dashboard
Permissions and history

Is ビビカツ safe to install?

ビビカツ asks for 4 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.

ビビカツ

Chrome extension by general@axeler.jp · Productivity · Workflow

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
4 kinds of data declared
Audience
289 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: 2 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: 27 site patterns.

Show the remaining 24
  • https://*.disc-soft.com/* disc-soft.com and all its subdomains
  • https://job.rikunabi.com/* only job.rikunabi.com
  • https://*.rikunabi.com/* rikunabi.com and all its subdomains
  • https://*.mynavi.jp/* mynavi.jp and all its subdomains
  • https://*.sonar-ats.jp/* sonar-ats.jp and all its subdomains
  • https://*.snar.jp/* snar.jp and all its subdomains
  • https://axol.jp/* only axol.jp
  • https://*.axol.jp/* axol.jp and all its subdomains
  • https://job.axol.jp/* only job.axol.jp
  • https://hrmos.co/* only hrmos.co
  • https://*.talentio.com/* talentio.com and all its subdomains
  • https://*.talentio.co.jp/* talentio.co.jp and all its subdomains
  • https://*.jposting.net/* jposting.net and all its subdomains
  • https://*.jobsuite.jp/* jobsuite.jp and all its subdomains
  • https://app.offerbox.jp/* only app.offerbox.jp
  • https://*.kimisuka.com/* kimisuka.com and all its subdomains
  • https://*.career-tasu.jp/* career-tasu.jp and all its subdomains
  • https://*.onecareer.jp/* onecareer.jp and all its subdomains
  • https://*.syukatsu-kaigi.jp/* syukatsu-kaigi.jp and all its subdomains
  • https://campus.doda.jp/* only campus.doda.jp
  • https://*.br-campus.jp/* br-campus.jp and all its subdomains
  • https://*.ababa.co.jp/* ababa.co.jp and all its subdomains
  • https://*.goodfind.jp/* goodfind.jp and all its subdomains
  • https://*.factlogic.jp/* factlogic.jp 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.

What it may ask for later

Not granted when you add it: Chrome asks you the moment the extension requests one of these, and you can refuse. It may later ask for access to every site.

How usual this is for its category

In Productivity · Workflow, 19% 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 4 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

289 users

Users
+47 since 01.09
240-298 · 35 readings
2026-11-03: released 1.4.0
  1. 2026-09-01242
  2. 2026-09-02240
  3. 2026-09-05250
  4. 2026-09-06243
  5. 2026-09-08247
  6. 2026-09-09244
  7. 2026-09-10249
  8. 2026-09-13240
  9. 2026-09-15241
  10. 2026-09-16248
  11. 2026-09-21262
  12. 2026-09-22255
  13. 2026-09-25257
  14. 2026-09-26254
  15. 2026-09-28256
  16. 2026-10-04275
  17. 2026-10-08283
  18. 2026-10-09280
  19. 2026-10-10281
  20. 2026-10-11283
  21. 2026-10-13278
  22. 2026-10-16279
  23. 2026-10-18283
  24. 2026-10-19284
  25. 2026-10-20288
  26. 2026-10-21287
  27. 2026-10-22284
  28. 2026-10-23292
  29. 2026-10-24298
  30. 2026-10-25292
  31. 2026-10-28285
  32. 2026-10-29294
  33. 2026-11-01290
  34. 2026-11-04289
  35. 2026-11-05289

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.

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

Versions we have seen

  1. Version 1.4.0

Who publishes it

general@axeler.jp. This listing has been in the store since 2026-02-03 and was last updated on 2026-11-03.

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. 就活マイページ自動入力君 Runs its code on every site · 3 permissions 116 users
  2. 新卒就活マイページ自動入力ツール EntryBoost No site access · 3 permissions 43 users ★ 5.0
  3. 【採用応募】はじめてFill No site access · 3 permissions 6 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 ビビカツ access?
Specific sites only: 2 match patterns. It declares 4 browser permissions.
What data does ビビカツ collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Authentication information, Web history, User activity. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has ビビカツ asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does ビビカツ 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 ビビカツ · Alternatives to ビビカツ

Where the data comes from: how the catalog is built