unbrainrot streak · Last updated 23 July 2026
Everything stays on your own computer. There is no server, no account, no analytics, and no data is ever sold or shared.
All of the following is written to chrome.storage.local — storage
inside your own browser profile, on your own device.
These are shown back to you in the popup and on the "Your Reality" page.
yt:dQw4w9WgXcQ),
used only to detect when the same clip is served to you more than onceThe clip identifiers are derived from the address of pages you open on the four supported sites. Under Chrome Web Store definitions this counts as web history, and the scroll counting counts as user activity — which is why both categories are disclosed on the store listing.
The extension only has access to these four domains, because these are the sites that host the feeds it blocks:
youtube.cominstagram.comtiktok.comfacebook.comIt has no access to any other website you visit.
Nowhere. The extension contains no networking code, no analytics SDK, no crash reporting, and no server of any kind. The data described above never leaves your browser.
Specifically, the developer of this extension cannot see your streak, your statistics, or which clips you opened.
The extension does not sell, transfer, or share user data with anyone.
Web fonts: the extension's interface pages currently load their fonts from Google Fonts. When those pages open, your IP address and browser user-agent are visible to Google as part of that ordinary request, and are governed by Google's Privacy Policy. No extension data is included in the request.
Uninstalling the extension deletes everything it stored. You can also clear it
at any time from chrome://extensions by removing and re-adding the
extension.
The extension is not directed at children under 13 and collects no information that could identify anyone.
If this policy changes, the "Last updated" date above will change with it.
unbrainrot streak is designed and developed by lfillaz (GitHub @lfillaz, Bugcrowd @lfillaz). There is no company, no third-party processor, and no one else with access to anything described above.
Questions about this policy: open an issue on the project's GitHub page.