FAQ

The questions we get before install

Short answers, no hedging. If something here reads like a limitation, it is one — and we would rather say so on this page than in a support thread.

  • Why does Chrome warn me about developer mode?

    Because the package is loaded from a folder instead of the Web Store. The warning is Chrome being careful about unpacked code in general, not a verdict on Z-Manager. It goes away once the store listing is live.

  • Why don't you show CPU or memory per extension?

    There is no public browser API that exposes it. Chrome's task manager is internal, and Firefox's about:performance has no API either. Every manager that shows those numbers is either estimating or running a native helper.

  • When is the Firefox version coming?

    Firefox's management.setEnabled only works on themes, so a Firefox build cannot switch profiles — the entire point of Z-Manager. We are building a read-only inventory and permission auditor for Firefox instead, and it will be signed through Mozilla AMO.

  • What data leaves my browser?

    None. There is no account, no server and no analytics. Your groups, tags and ordering live in the browser's own extension storage, and the only network request Z-Manager can make is the one you trigger by clicking a store link.

  • Can Z-Manager see what my other extensions do?

    No, and neither can anything else. The management API returns names, versions, icons, declared permissions and enabled state. It cannot read another extension's data or watch it work.

  • Does uninstalling Z-Manager change my extensions?

    Whatever was enabled when you removed it stays enabled. Groups are just saved metadata; removing Z-Manager removes the metadata, not your extensions.

  • Is it free?

    Yes, and it works offline with no accounts. If paid features arrive later, everything described on this site stays in the free tier.