Privacy Policy

ColorLasso inspects colors and design information on the page you choose. That work happens in your browser, not on our servers.

Last updated October 26, 2026 · ColorLasso extension preview 2.0.0

1. Scope and publisher

This policy covers the ColorLasso Chrome extension and this ColorLasso website. The publisher and privacy contact is ColorLasso, reachable at contact@colorlasso.com. It describes the current build, not future services. If the extension's handling of data changes, this policy and the Chrome Web Store disclosures must be updated before the new behavior is released.

2. Information processed locally

When you activate an inspection tool, ColorLasso reads the selected page's pixels, computed styles, element structure, typography, colors, gradients and layout details. Contrast analysis may process visible text and its styling. Component extraction can include selected page text and markup in the code or prompt you ask it to produce. A temporary visible-tab screenshot can be used to read pixel colors; it is not uploaded to ColorLasso.

The Vault and history store the items you keep, such as colors, gradients, folders, extracted components and design-system results. Saved items may include their source domain, timestamps, element labels and generated HTML, React, SVG or prompt text. Settings include language, theme and color format. These are stored in the extension's local browser storage. Temporary inspector tab state uses session storage. A format preference can also be stored in the inspected site's localStorage.

This is data handling even though it stays local. ColorLasso does not maintain a general log of every site you visit. The current build does not upload inspected page content, sampled pixels, Vault items or generated code to the publisher or to AI services.

3. Permissions and why they are used

4. Network, accounts and planned licensing

The current extension code loads its translations and bundled fonts from the extension package. No remote analytics, cloud synchronization, Gumroad activation or license-verification request is implemented in the reviewed build. The extension's design tools do not need a design account.

A legacy account callback handler remains in the code for the trusted origin styleflow.getscrollflow.com. If that flow is used, a token, email address, handle and entitlement fields from the callback can be saved locally to display account state. This is not cloud synchronization, and the extension does not currently send that state to a verification API. The feature is not promoted as an active sign-in service on this site.

A paid plan and Gumroad licensing are planned but are not active here. This site does not currently accept payment or collect a license key. Before a paid activation flow is enabled, its actual transmitted fields, recipients, retention and provider policies will be documented. Do not send passwords, payment-card details or license keys by support email.

5. Copying, exporting and third-party tools

You decide when to copy or export material. If you paste a generated prompt or component into an AI coding tool, editor, Figma or another service, that service receives the content under its own terms and privacy policy. ColorLasso does not automatically send your inspected pages to those services. Review exported content before sharing it, particularly on private or client pages.

6. This website and support email

The ColorLasso site serves its page code, images and fonts locally from its own host. It does not include an advertising pixel or external font CDN. It uses self-hosted Umami audience measurement served from privastats.getscrollflow.com. The browser sends page views, the visited URL, referrer, page title, browser and device details, screen size and language to that service. The web server necessarily receives connection information, including an IP address. This notice does not promise complete anonymity or a consent exemption; server-side retention and privacy settings are still under review. Umami measurement is separate from the extension and does not read your Vault or inspected pages. You can block the statistics script with your browser or content blocker, or contact us about your privacy choices. Loading the site still sends ordinary HTTP information to its hosting infrastructure, such as an IP address, requested path, browser headers and request time. Web-server, reverse-proxy or hosting logs may retain that technical information for operation and security; it is not extension inspection data.

If you contact contact@colorlasso.com, your email address, message and any attachments are processed by the publisher and its email service to answer you. Send only what is needed. Support correspondence is separate from the local Vault.

Links to ScrollFlow, ColorZilla, Chrome Web Store and other sites have their own policies. Following a link opens that service; it does not upload your Vault.

7. Use, disclosure and Limited Use

ColorLasso uses inspected information only for the color, design-inspection, audit and export features you request. It does not sell inspection data, use it for personalized advertising, or transfer it to data brokers or AI training services. The publisher cannot read your local Vault remotely. Support material you choose to send may be read to help with your request. Information may also be processed or disclosed when legally required or necessary for security.

The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.

8. Retention and deletion

Local history and Vault items remain in your browser until you remove them or clear extension data. Removing the extension normally removes its chrome.storage data; files you exported or clipboard contents are not deleted by uninstalling. Any preference written to a site's localStorage can be removed by clearing that site's storage in Chrome. Session state is temporary.

For support correspondence or hosting data held by the publisher, contact us to request access, correction or deletion. Some records may need to be retained for security or legal obligations. We do not claim a fixed server-log or support-email deletion period that has not yet been configured.

9. Your choices and rights

You can stop the inspector, revoke site access, remove saved items and uninstall ColorLasso. Depending on applicable law, you may request access, correction, erasure, restriction, portability or object to processing of personal information held by the publisher. We may need to verify a request. You may also contact your local data protection authority. We cannot retrieve a Vault stored only on your device.

10. Security and changes

Local browser storage is not presented as a separate encrypted vault. Protect your device and Chrome profile. No system is perfectly secure. This policy will be revised when the product or its data handling changes; the date above identifies this version.