Privacy Policy — TaskRoket: Site Lock

TaskRoket

Last updated: 25 October 2026

Summary

Site Lock does not collect, transmit or sell any personal data. It has no account system, no analytics, no telemetry and no server of its own. The list of blocked sites, the schedule and the PIN hash stay in your browser profile.

What the extension processes

chrome.storage.local so the extension can build its blocking rules again after a browser restart.

The list of blocked domains. The site names you add are stored in

PIN is required are stored in the same place.

Settings. The on/off switch, the schedule (hours and weekdays) and whether a

and a random 16-byte salt. The PIN itself is never written to storage, never leaves the device and cannot be read back from the extension.

The PIN. Only a salted hash is kept: PBKDF2-SHA256 with 150,000 iterations

pauses for one minute. The counter is a timestamp in local storage.

A short lockout counter. After five wrong PIN attempts the entry dialog

Network requests

The extension makes no network requests at all.

configuration.

There is no update ping, no license check, no analytics endpoint and no remote

code is inside the package.

The service worker never calls fetch and never loads a script from a URL. All

from a server.

Interface translations are read from files that ship with the extension, not

How blocking works

Blocking is done by the browser itself. The extension registers rules with chrome.declarativeNetRequest that tell Chrome to refuse the request for a domain on your list before the page is loaded. The extension does not read the page, does not inject a script into it and does not see what you type or view. It has no content scripts and no host permissions.

What the extension does not do

location.

It does not collect or transmit your browsing history, your identity or your

pixels.

It does not read the content of the pages you visit.
It does not use cookies, fingerprinting, advertising identifiers or tracking

It does not sell, rent or share data with anyone.
It does not load remote code.

Permissions and why they are needed

PIN hash in your browser profile.

storage — keep the blocked list, the schedule, the setting switches and the

domains on your list. It is the only way to block a site without reading it.

declarativeNetRequest — register the blocking rules that Chrome applies to the

Data retention and deletion

Everything lives in chrome.storage.local inside your browser profile.

There is no backup and no recovery: after a reinstall you set a new PIN and add the sites again.

Removing a site from the list deletes it immediately.
"Unblock everything" clears the list.
Resetting the extension restores the defaults and removes the PIN hash.
Uninstalling the extension deletes all of its stored data, including the PIN.

of the computer and developer tools.

The PIN is a local speed bump, not encryption against someone with full control

Children

The extension is a general-purpose utility. It is not directed to children and does not knowingly collect data from anyone.

Changes

If this policy changes, the new version is published at the same address with a new "last updated" date.

Contact

Questions about privacy: the contact address published on the extension's Chrome Web Store listing page.