Privacy Policy

Last updated: 25 August 2026

This Privacy Policy explains how L.N.H., trading as Small Labs ("we", "us", or "our") handles information in connection with our Chrome extensions — Hue Shift, 1Click Auto Refresh and Refresh n Click — and this website at small-labs.com.

1. Our Extensions

No personal data collection

Hue Shift, 1Click Auto Refresh and Refresh n Click do not collect, transmit, or share any personally identifiable information. We have no servers that receive your data, and we do not track your browsing activity.

Local storage only

To make the extensions work, a small amount of configuration is saved locally using the browser's local storage — for Hue Shift, whether recoloring is on, the type and strength you chose, and the popup language if you picked one; for the reload pair, your chosen refresh interval, the button text to search for, the match mode, and similar preferences. This information stays on the device it was entered on and is never uploaded or synced to us. It is kept between sessions so you do not have to type it again; to remove the text you entered, use the clear button inside the text field, or uninstall the extension — either erases it from the device.

Permissions

The extensions request only the permissions required to function. Hue Shift asks for access to the tab you turn it on from, granted by your click; for script access used solely to apply and remove the recoloring; and for storage to keep your on/off state, type, strength and popup language, so that every tab and session agrees. Access to all sites is optional and is requested only when you press “Apply on all sites”, so recoloring can follow you to every tab and new page until you turn it off — nothing is granted up front. The reload pair ask for access to the tab you are on so it can be reloaded, and for Refresh n Click the ability to look for the text you typed and click the matching element — the same access also reads the page's own HTTP response code, solely for the red error mark below. Refresh n Click can also be granted optional per-site host access: it is requested only when you press the popup's “Allow this site” button, so a run that has been paused by a redirect to a different domain can carry on from where it stopped, and nothing is granted up front. 1Click Auto Refresh additionally asks for permission to schedule its next reload, so that a long wait survives the extension going idle, for browsing data access purely to clear the cache of the site being refreshed, only when you enable that option — the cache of every other site is left alone — and for script access used solely to read the page's own HTTP response code, which drives the red error mark on the tab and the optional “Stop when OK” setting; nothing else on the page is read. Both reload extensions also ask for tab group access, used only to mark the tab a run is working on so you can tell it apart in the tab strip (the mark also turns red while the site is returning errors, and back once it recovers; for Refresh n Click it turns amber while a run is waiting for you to allow a site it was redirected to); the mark is removed when the run stops — except that a run ending in success (Refresh n Click's click landing, or 1Click Auto Refresh stopping because the page is OK again) turns it green as the success signal, removed when you next open the popup on that tab or close the tab — and a tab you have already grouped yourself is left exactly where it is. Page contents are examined in your browser — for Hue Shift, to read the page's colors and compute the recoloring; for Refresh n Click, to find your button — and are never stored, harvested, or exported.

No remote code

Our extensions do not download or execute any remote scripts. All code that runs is contained within the published extension package and reviewed by the Chrome Web Store.

2. This Website

Unlike our extensions, this website uses a small number of third-party services to understand traffic and support the project. These may set cookies or process limited technical data such as your IP address, browser type, and pages viewed:

• Google Tag Manager / Google Analytics — anonymous, aggregated website analytics.
• Cookie Script — manages your cookie consent preferences.
• Buy Me a Coffee — used only if you choose to visit our support/donation link.

Where required, non-essential cookies are only set after you provide consent through the cookie banner. You can change or withdraw your consent at any time.

3. Children's Privacy

Our extensions and website are not directed at children under the age of 13, and we do not knowingly collect personal information from children.

4. Data Sharing & Selling

We do not sell, rent, or trade your data. Our extensions do not transfer any user data to third parties. The website services listed above process data only on our behalf to provide their respective functions.

5. Your Rights

Because our extensions store data only on your own device, you are always in control: you can clear the extension's stored preferences at any time, or uninstall the extension to remove them entirely. For any website-related data handled by the third-party services above, you may exercise the rights granted to you under applicable laws (such as the GDPR or CCPA) by contacting us.

6. Changes to This Policy

We may update this Privacy Policy from time to time. When we do, we will revise the "Last updated" date at the top of this page. Continued use of our extensions or website after changes take effect constitutes acceptance of the updated policy.

7. Contact Us

If you have any questions about this Privacy Policy or our data practices, please contact us at privacy@small-labs.com.

If you write to us

Our extensions send us nothing, but an email is different: the addresses on this site and in our Terms of Use reach a person. If you write to privacy@small-labs.com or legal@small-labs.com, we hold your message and your address for as long as it takes to deal with what you raised, and we use them for nothing else — no mailing list, no profile, and no sharing beyond what answering you requires. This applies to anyone who writes in, including a website operator reporting how an extension is being used on their site.