Ext Ops Panel
Open dashboard
Permissions and history

Is AutoFillPro - 就活マイページ自動入力 safe to install?

AutoFillPro - 就活マイページ自動入力 asks for 4 browser permissions and 14 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.

What the developer says, and 1 screenshot

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
3 kinds of data declared
Upkeep
Updated 153 days ago
Publisher
No store badges
Audience
170 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: 14 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: 14 site patterns.

Show the remaining 11
  • *://job.axol.jp/bx/s/*/mypage/* only job.axol.jp
  • *://job.axol.jp/bx/s/*/entry/* only job.axol.jp
  • *://job.axol.jp/bx/s/*/*/* only job.axol.jp
  • *://www.e2r.jp/ja/*/career_edu/* only www.e2r.jp
  • *://www.e2r.jp/eARTH/* only www.e2r.jp
  • *://job.mynavi.jp/28/pc/* only job.mynavi.jp
  • *://*.i-webs.jp/* i-webs.jp and all its subdomains
  • *://*.i-web.jpn.com/* i-web.jpn.com and all its subdomains
  • *://*.snar.jp/* snar.jp and all its subdomains
  • *://suntory.saiyo.jp/2028/* only suntory.saiyo.jp
  • *://www.mypage.bk.mufg.jp/* only www.mypage.bk.mufg.jp

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

170 users

Users
+28 since 01.09
129-175 · 28 readings
  1. 2026-09-01142
  2. 2026-09-02143
  3. 2026-09-05145
  4. 2026-09-08141
  5. 2026-09-10143
  6. 2026-09-15145
  7. 2026-09-17151
  8. 2026-09-21146
  9. 2026-09-25139
  10. 2026-09-27129
  11. 2026-09-28133
  12. 2026-10-05155
  13. 2026-10-08157
  14. 2026-10-09163
  15. 2026-10-10161
  16. 2026-10-16168
  17. 2026-10-17165
  18. 2026-10-20168
  19. 2026-10-21169
  20. 2026-10-22167
  21. 2026-10-23163
  22. 2026-10-24165
  23. 2026-10-25171
  24. 2026-10-28174
  25. 2026-10-29175
  26. 2026-10-30174
  27. 2026-11-01170
  28. 2026-11-03170

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

The store lists no publisher name, who publishes 3 listings we track. This listing has been in the store since 2026-05-15 and was last updated on 2026-06-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 · 1 permission 6 users
  2. 就活マイページ自動入力君 Runs its code on every site · 3 permissions 116 users
  3. 新卒就活マイページ自動入力ツール EntryBoost No site access · 3 permissions 48 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 AutoFillPro - 就活マイページ自動入力 access?
Specific sites only: 14 match patterns. It declares 4 browser permissions.
What data does AutoFillPro - 就活マイページ自動入力 collect?
The developer declares that it collects these kinds of data: Personally identifiable information, Web history, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has AutoFillPro - 就活マイページ自動入力 asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does AutoFillPro - 就活マイページ自動入力 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-03.

Back to AutoFillPro - 就活マイページ自動入力 · Alternatives to AutoFillPro - 就活マイページ自動入力

Where the data comes from: how the catalog is built