Ext Ops Panel
Open dashboard
Permissions and history

Is AKA Profiles safe to install?

AKA Profiles 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.

AKA Profiles

Chrome extension by neil · Lifestyle · Social

Open in the Chrome Web Store
What the developer says, and 2 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.

Data collection
1 kind of data declared
Audience
354 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

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 every page you open: the manifest declares a content script for all sites.

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 · Social, 8% of extensions ask for access to every site. This one: Runs its code on every site.

The typical extension there declares 2 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

354 users

Users
-5 since 01.09
351-387 · 30 readings
  1. 2026-09-01359
  2. 2026-09-02358
  3. 2026-09-04355
  4. 2026-09-06363
  5. 2026-09-07372
  6. 2026-09-08373
  7. 2026-09-09387
  8. 2026-09-13384
  9. 2026-09-15378
  10. 2026-09-17367
  11. 2026-09-20379
  12. 2026-09-21385
  13. 2026-09-25376
  14. 2026-09-26372
  15. 2026-09-28375
  16. 2026-10-05354
  17. 2026-10-08352
  18. 2026-10-09355
  19. 2026-10-10351
  20. 2026-10-16364
  21. 2026-10-19366
  22. 2026-10-21361
  23. 2026-10-22355
  24. 2026-10-23355
  25. 2026-10-24354
  26. 2026-10-25358
  27. 2026-10-27355
  28. 2026-10-29358
  29. 2026-11-01354
  30. 2026-11-02354

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.

Who publishes it

neil. This listing has been in the store since 2023-05-19 and was last updated on 2025-04-01.

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 AKA Profiles 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 AKA Profiles collect?
The developer declares that it collects these kinds of data: Authentication information. This is the developer's own declaration in the Chrome Web Store. We cannot check it against what the extension does.
Has AKA Profiles asked for more permissions over time?
The permissions this extension requests have not changed since we started watching it.
Does AKA Profiles 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-02.

Back to AKA Profiles · Alternatives to AKA Profiles

Where the data comes from: how the catalog is built