Privacy Policy

This Privacy Policy explains how Chromble handles personal data when you use the website, including when you choose to contact Chromble.

Chromble is currently designed so that core color tools and the Code Editor run primarily in your browser. Image-color extraction and pixel picking are intended to be processed locally in the browser rather than uploading the image to a Chromble server. The Code Editor uses browser storage to protect the active scratch session from reloads while you work, while editor preferences and console-layout preferences can remain stored locally between visits.

The Code Editor is designed as a temporary scratch playground rather than a local project library. While a browser-tab session is active, Chromble autosaves the current scratch primarily to IndexedDB and keeps a small session pointer in sessionStorage. Reloading the page, or leaving and returning to the Code Editor in that same tab, can therefore restore the scratch. When that tab/browser session ends, the session pointer ends with it and a later fresh visit starts with a new blank scratch instead of presenting old work as a saved project. Chromble can keep a small bounded number of abandoned scratch records in IndexedDB temporarily so browser storage stays robust and can be pruned as newer sessions are created; they are not surfaced as a recent-project library. To intentionally keep work for later, use the Code Editor export options. Uploaded editor assets are part of the active scratch. Editor preferences such as font size, tab size, word wrapping, minimap, auto-run, and console layout can remain stored locally between visits.

Live Web, React and Vue previews execute inside an isolated browser iframe. Chromble currently blocks project code from making arbitrary outbound network connections and blocks top-level navigation, forms, frames, and sensitive browser permissions from that preview environment. React and Vue previews may load the fixed runtime/compiler files and project packages described below. Code exported from Chromble is no longer inside that preview sandbox and runs according to the environment where you choose to execute it.

When you use the Packages panel in Web, React, Vue, or React Native projects, package names and search terms are sent directly from your browser to the public npm Registry so Chromble can search packages and resolve versions. This package lookup does not send your project source code to npm. Packages you add remain listed in the project's locally stored package.json.

Browser project packages are delivered from esm.sh as ES modules inside the isolated preview. Chromble may also request package TypeScript declaration metadata and declaration files from esm.sh in the editor so Monaco can provide package autocomplete, parameter information, and type checking; declaration follow-up requests are restricted to Chromble’s approved esm.sh declaration hosts and are sent without credentials or a referrer, and your project source code is not sent with those type requests. When you run a TypeScript, React or Vue browser project, or a Web JavaScript project that uses local modules or needs Chromble's long-running-loop guard, Chromble also loads Babel Standalone from UNPKG and loads the fixed framework runtime plus packages you have added from esm.sh. Vue projects additionally load Vue's Single-File Component compiler from esm.sh inside the isolated preview. Tailwind projects additionally load the fixed @tailwindcss/browser runtime from jsDelivr inside that same isolated preview. Chromble does not send your project source code to these CDNs for preview compilation, but package/runtime names, versions, IP address, browser information, and other ordinary request data may be visible to the CDN when those files are requested.

React Native projects remain local in the Code Editor until you explicitly choose Connect device. When you do, Chromble uses Expo's Snack service to make the project available to Expo Go. Project source files, declared package dependencies, and information needed to operate the live session are transmitted to Expo infrastructure. Console messages and basic connected-client information can be returned to Chromble while the session is active.

The device QR code is generated in your browser. Chromble currently loads the Snack SDK and QR-code library from esm.sh only when the device feature is used; that request can expose ordinary technical request data such as IP address and browser information to the CDN. Expo and any CDN used to deliver these libraries process information under their own privacy terms.

Disconnecting the device or closing the editor ends Chromble's live Snack session. This feature is for temporary testing and does not require Chromble to create an app-store build.

The website is hosted through Cloudflare. As with normal web hosting and security services, technical request information such as IP address, browser information, timestamps, and security-related metadata may be processed to deliver and protect the site. Cloudflare's own privacy terms may also apply to its role as a service provider.

You can contact Chromble by email at pgdevelopmentstudio@gmail.com. If you send an email, your email address, message, and related email metadata will be processed by your email provider and the email services used to deliver and receive the message.

At the time of this notice, Chromble does not require a user account for the browser-based Code Editor and does not describe itself as using advertising trackers or optional analytics cookies. If accounts, cloud project storage, analytics, advertising, or similar features are added, this policy and any required consent controls should be updated before those technologies are used.

Where personal data is processed, Chromble will rely on an appropriate legal basis under applicable data-protection law, depending on the purpose of the processing.

If the GDPR applies to processing of your personal data, you may have rights including access, correction, deletion, restriction, objection, portability, and the right to lodge a complaint with a supervisory authority, subject to the conditions in applicable law.

Personal data should be kept only for as long as necessary for the purpose for which it is processed, unless a longer period is required by law.

This policy may be updated as Chromble gains new features such as accounts, saved palettes, analytics, newsletters, or payments.

For privacy questions, contact Chromble at pgdevelopmentstudio@gmail.com.