What we collect

Last updated 4 September 2026. Controller: Artbloom Labs.

Browsing the site

Every page here is generated at build time and served as static HTML. There is no ad network, no session recorder, and no third-party analytics of any kind; the only third-party code that can load is the error monitor described below, and only when a deployment switches it on. The one thing we put in your browser is your theme choice, which lives in local storage on your own device and is never sent anywhere.

Our host keeps ordinary server logs — IP address, user agent, the path requested — for a short window, to serve traffic and absorb abuse. We do not join those logs to anything else described on this page.

The CLI

When you run npx ui.artbloom add …, your machine fetches JSON from /r/<name>.json. That is an ordinary HTTP request, so it reaches the host with your IP address, exactly like loading a page.

Then, once the files are on disk, the CLI posts one short message per installed piece: the name of the piece, the CLI's version, and which package manager you use. Nothing else — not your project name, not a file path, not your username, not a machine id, and nothing that persists between runs to link two installs together. It is a single POST with a two-second timeout, and a failure is silent, so a counter can never break an install.

Three ways to send nothing at all:

• --no-telemetry on any command.
• DO_NOT_TRACK=1 in the environment.
• CI=1, which most build servers set for you — automated installs are not counted.

We keep none of it. The endpoint that once recorded these pings has been removed, so the request arrives at our origin and is dropped with nothing written down — no counter, no database, no hash of your address. The CLI still sends it because the same command works against any registry, and yours may run one that listens; ours does not. Sending nothing in the first place is still the cleaner option, so the opt-outs above continue to work.

Error monitoring

When a deployment is configured with a Sentry key, an uncaught error — in the browser or on the server — sends a report to Sentry so it can be fixed. A report is a stack trace and the technical context around the failure: the URL, the browser and operating system, and the error message. It is sent only when something breaks, never on an ordinary page view, and it carries no name because we have none to attach. We do not enable session replay, so your browsing is not recorded. When no key is configured — which is the default — the monitoring code never loads and nothing leaves your browser.

What we do not do

We do not sell or share any of this with anyone. There is no advertising, no cross-site tracking, no profiling, and no mailing list — outside of sign-in we never learn your address, so we could not email you if we wanted to. There is no payment processor and no card handling either, because everything in the catalogue is free.

Your rights

Under the GDPR and similar laws you can ask for a copy of anything we hold about you, ask for it corrected, or ask for it deleted. The honest answer is that we hold nothing we can tie to you: there is no account, and the one request your machine sends us is discarded unread. If a Sentry error report has captured something you believe identifies you, write to hello@shreyashmishra.in and we will remove it.

Other people's services

Our host serves the pages and keeps the ordinary server logs described above. Sentry receives an error report if — and only if — monitoring is switched on for a deployment, and then only when something breaks. That is the entire list.

Separately, a template you install may load fonts or images from a third party inside your project — that is your users' data and your privacy notice, not ours. Each item page lists what it fetches. See also the licence and terms.

Changes

If what we collect changes, the date at the top changes with it and the section that changed says what it now does. This page is meant to be checked against the code rather than believed: there are no cookies to find, and error monitoring lives in the two instrumentation files named above.

Children

This is a developer tool and not intended for anyone under 16.