Hakarasenai — Google 애널리틱스 옵트아웃 제작자: omikuji
Google 애널리틱스가 나를 측정하지 못하게 합니다. 옵트아웃을 알리고, 그래도 나가려는 측정 데이터를 차단합니다.
Android™용 Firefox에서 사용 가능Android™용 Firefox에서 사용 가능
Android용 Firefox에서 이 확장 기능을 열려면 QR 코드를 스캔하세요
확장 메타 데이터
스크린샷
정보
Google publishes an official Google Analytics opt-out add-on, and there is a Firefox build of it. The trouble is how it works: it injects a script element into the page, and Firefox applies the page's own Content Security Policy to content scripts. On any site with a strict CSP the injection is blocked and the opt-out quietly does nothing — and nothing tells you it failed.
Hakarasenai uses the same official opt-out hook, but puts it where no CSP can reach it, and adds network blocking behind it as a second layer.
What it does
What it does not block
The Tag Manager loader (gtag.js, gtm.js) and the scripts served by google-analytics.com are left alone. Opting out means letting the code load and not letting it report; taking out the loader would break whatever else a site drives through Tag Manager. No page resource is blocked, so this practically never breaks a site.
What it cannot do
Server-side tagging that collects on a site's own domain cannot be told apart from ordinary traffic to that site, so the blocking layer cannot catch it — the opt-out flag still applies there. Analytics products other than Google Analytics are out of scope.
Privacy
It collects nothing, sends nothing anywhere, and makes no network requests of its own. The only stored value is the list of hostnames you excluded, and it never leaves the device.
No options page, no filter subscriptions, no counters, no Pro version. MIT licensed, source at https://github.com/omikuji/hakarasenai
Hakarasenai uses the same official opt-out hook, but puts it where no CSP can reach it, and adds network blocking behind it as a second layer.
What it does
- Tells the Google Analytics code on the page that you have opted out. The flag is the one Google Analytics reads itself (window._gaUserPrefs.ioo), set from a content script running in the page's own world at document start, so there is nothing in the DOM for a CSP to block.
- Blocks the measurement hits. Five static declarativeNetRequest rules cover the /collect and /batch endpoints on google-analytics.com and analytics.google.com, including the regional hosts, plus stats.g.doubleclick.net.
- Lets you exclude one site at a time from the toolbar button, if you actually want to be measured — verifying Analytics on your own site, for instance. Exclusions cover subdomains and turn off both layers.
What it does not block
The Tag Manager loader (gtag.js, gtm.js) and the scripts served by google-analytics.com are left alone. Opting out means letting the code load and not letting it report; taking out the loader would break whatever else a site drives through Tag Manager. No page resource is blocked, so this practically never breaks a site.
What it cannot do
Server-side tagging that collects on a site's own domain cannot be told apart from ordinary traffic to that site, so the blocking layer cannot catch it — the opt-out flag still applies there. Analytics products other than Google Analytics are out of scope.
Privacy
It collects nothing, sends nothing anywhere, and makes no network requests of its own. The only stored value is the list of hostnames you excluded, and it never leaves the device.
No options page, no filter subscriptions, no counters, no Pro version. MIT licensed, source at https://github.com/omikuji/hakarasenai
리뷰어 0명이 0점으로 평가함
권한 및 데이터
필수 권한:
- 모든 페이지의 콘텐츠 차단
선택적 권한:
- 모든 웹사이트에서 사용자의 데이터에 접근
데이터 수집:
- 개발자는 이 확장 기능이 데이터 수집을 요구하지 않는다고 밝히고 있습니다.
추가 정보
- 부가 기능 링크
- 버전
- 1.2.0
- 크기
- 44.35 KB
- 최근 업데이트
- 6일 전 (2026년 9월 4일)
- 관련 카테고리
- 라이선스
- MIT 라이선스
- 개인정보처리방침
- 이 부가 기능에 대한 개인정보처리방침 읽기
- 버전 목록
- 모음집에 추가