あの頃の自作TCG拡張機能 is no longer in the Chrome Web Store: what it can access
あの頃の自作TCG拡張機能 is no longer in the Chrome Web Store: the listing disappeared on 2026-10-25. When it left, it had 19 users. あの頃の自作TCG拡張機能 asks for 3 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 · Lifestyle · Games · no longer in the store
What to use instead
Listings still in the store that are closest to it in what they say they do. Comparable, not endorsed.
-
Omegagu 13 users
-
BlitzGrab Companion 26 users
-
TCGGather 50 users
-
Decklist Auto-Filler 215 users
-
Master Collection for TCG Collector 47 users
If you still have it installed
A listing leaving the store does not by itself remove the extension from browsers that already have it. If you still have it, you can see what it can reach and remove it in a minute:
- Type chrome://extensions in the address bar and find the extension in the list.
- 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.
- To uninstall it, choose Remove on the same page.
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
- Upkeep
- Not updated for over a year
- Publisher
- No store badges
- Audience
- 19 users
- Store status
- No longer published in the Chrome Web Store
What data it declares
The developer declares that it collects these kinds of data:
- Authentication information such as passwords, credentials or PIN codes
- Personal communications such as emails, texts or chat messages
- User activity such as clicks, scrolling, keystrokes or network monitoring
- Website content such as text, images or links on the pages you open
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:
- Read and change your data on unityroom.com and omezi42.github.io
- Display notifications
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.
https://unityroom.com/games/anokorotcg*only unityroom.comhttps://omezi42.github.io/*only omezi42.github.io
Worth knowing
-
Run its own code on the pages it can access
scripting
Routine for an extension
-
Show you notifications
notifications -
Store data in your browser
storage
Pages it runs its code on
It runs its own code on specific pages only: 1 site pattern.
https://unityroom.com/games/anokorotcg*only unityroom.com
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 Lifestyle · Games, 2% of extensions ask for access to every site. This one: Access to specific sites only.
The typical extension there declares no 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
19 users
- 2026-08-3118
- 2026-09-0319
- 2026-09-0418
- 2026-09-0619
- 2026-09-0820
- 2026-09-1321
- 2026-09-1520
- 2026-09-1718
- 2026-09-2019
- 2026-09-2520
- 2026-09-2622
- 2026-09-2821
- 2026-10-0820
- 2026-10-0921
- 2026-10-1619
- 2026-10-1820
- 2026-10-1919
- 2026-10-2020
- 2026-10-2121
- 2026-10-2219
- 2026-10-2519removed from the store
- Not updated in the store for over a year: the last update was on 2025-07-30.
- No new version in the last 90 days.
What the store shows
The listing is no longer in the store, so none of the store's badges apply to it now.
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. This listing has been in the store since 2025-07-30 and was last updated on 2025-07-30.
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.
-
Fabtcg table 60 users
-
TCG Event to Google Calendar 8 users
-
Omegagu 13 users
Questions people ask
- What can あの頃の自作TCG拡張機能 access?
- Specific sites only: 2 match patterns. It declares 3 browser permissions.
- What data does あの頃の自作TCG拡張機能 collect?
- The developer declares that it collects these kinds of data: Authentication information, Personal communications, User activity, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
- Has あの頃の自作TCG拡張機能 asked for more permissions over time?
- The permissions this extension requests have not changed since we started watching it.
- Does あの頃の自作TCG拡張機能 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-25.
Back to あの頃の自作TCG拡張機能 · Alternatives to あの頃の自作TCG拡張機能
Where the data comes from: how the catalog is built