Is InstaBee for FlexBee.io safe to install?
InstaBee for FlexBee.io asks for 2 browser permissions and declares no blanket site access. 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 ju · Productivity · Communication
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
- No site access
- Data collection
- 2 kinds of data declared
- Upkeep
- Not updated for over a year
- Publisher
- Established publisher
- Audience
- 6 users (last published figure)
What data it declares
The developer declares that it collects these kinds of data:
- Authentication information such as passwords, credentials or PIN codes
- 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 a number of websites
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
No site access is declared in the manifest, so it cannot read the pages you open on its own.
Routine for an extension
Pages it runs its code on
It runs its own code on specific pages only: 4 site patterns.
*://www.instagram.com/*only www.instagram.com*://instagram.com/*only instagram.com*://api.flixbee.io/*only api.flixbee.io
Show the remaining 1
*://flixbee.io/*only flixbee.io
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.
*://api.flixbee.io/*only api.flixbee.io
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 · Communication, 14% of extensions ask for access to every site. This one: No site access.
The typical extension there declares 3 browser permissions; this one declares 2 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
6 users (last published figure)
- 2026-08-314
- 2026-09-035
- 2026-09-044
- 2026-09-055
- 2026-09-085
- 2026-09-136
- 2026-09-175
- 2026-09-214
- 2026-09-255
- 2026-09-284
- 2026-10-095
- 2026-10-104
- 2026-10-165
- 2026-10-186
- 2026-10-195
- 2026-10-216
- 2026-10-225
- 2026-10-236
- 2026-10-247
- 2026-10-256
- 2026-10-316
- Not updated in the store for over a year: the last update was on 2025-09-16.
- No new version in the last 90 days.
What the store shows
- Established publisher The store's badge for publishers with a good record and no history of violations.
The listing says it offers in-app purchases.
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
ju, who publishes 2 listings we track. This listing has been in the store since 2025-09-13 and was last updated on 2025-09-16.
How to check or remove it in Chrome
- 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.
Questions people ask
- What can InstaBee for FlexBee.io access?
- No site access is declared in the manifest, so it cannot read the pages you open on its own. It declares 2 browser permissions.
- What data does InstaBee for FlexBee.io collect?
- The developer declares that it collects these kinds of data: Authentication information, Website content. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
- Has InstaBee for FlexBee.io asked for more permissions over time?
- The permissions this extension requests have not changed since we started watching it.
- Does InstaBee for FlexBee.io 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-31.
Back to InstaBee for FlexBee.io · Alternatives to InstaBee for FlexBee.io
Where the data comes from: how the catalog is built