Last updated: 25 July 2026

FardinScripts sends nothing anywhere. There is no server, no analytics, and no
third party. Everything it stores stays in your own browser.


All data is kept in your browser's local extension storage
(browser.storage.local). It never leaves your device, and is not synced
between machines unless you export it yourself. Three things are stored: your
settings (which modules are on and how each is configured); for the X.com
module, a cache mapping an author's handle to their country, so the same author
is not looked up repeatedly; and the identifier of X's own "About this account"
API request, so region lookups keep working when X rotates it.

Nothing else is recorded — not your browsing history, the pages you visit, the
posts you read, form input, passwords, or cookies.


FardinScripts has no server of its own.

The X.com Region Blocker makes requests to x.com only, using the session you
are already logged into, to read the country X itself publishes for a post's
author ("Account based in", the value shown on x.com/<user>/about). It also
reads X's own JavaScript from abs.twimg.com to locate that API. These requests
go to X and nowhere else. Nothing about you, your browsing, or the accounts you
view is sent to the developer or any third party.

To avoid making more requests than necessary, the same module also reads the API
responses X's website already downloads as you browse, taking the country field
from them. This is passive: responses are copied, never altered, blocked, or
redirected, and nothing read this way is transmitted anywhere. It applies only
to x.com and twitter.com.


Storage saves your settings and the cache above. Access to all websites
is required by ScrollClick, which converts mouse-wheel gestures into a click or
back-navigation and so must work on whatever page you are on. Modules only run
on the sites they declare — YouTube Music Nonstop on music.youtube.com, the
Region Blocker on x.com and twitter.com — and disabling one stops it
entirely.


Each module can be turned off individually, and the master switch pauses all of
them. Clear X region cache deletes stored author regions; Reset
everything deletes all settings and caches; uninstalling removes everything.
Export settings writes your configuration to a file you choose — exports
contain settings only, never the region cache, and are sent nowhere.


If this policy changes in a way that affects what is stored or transmitted, the
updated version will accompany the release that introduces the change.


Questions or concerns: open an issue on the project's repository.