Privacy
What this site collects, and what it does not.
Analytics
This site uses Google Analytics. It counts visits, pages read, a few interactions such as scrolling, outbound link clicks and file downloads, and these actions of the site's own: copying an install snippet, copying the agent starter, copying a component's markdown, opening a component's schema, and opening the chat. All of it sits under a random identifier, not your name. It sets cookies to tell one visit from the next. To opt out, install Google's opt-out add-on. Blocking cookies in your browser stops your visits being linked together, though each page view is still counted.
Your picks
The site remembers what you pick for it: light or dark, the theme, the background, and a template's shell and backdrop. They stay in your browser's local storage, on this device, and are never sent anywhere.
The site chat
The chat answers questions about this design system and its site. Messages go to Anthropic, whose model writes the replies. For each exchange the site keeps the question, the answer, the page it was asked from and any text you had highlighted on it, which model answered, timing and token counts, and a thumbs verdict if you leave one. Each entry carries a scrambled, one-way stand-in for your network address so abuse can be spotted; it is not your name, and it cannot be turned back into an address. Everything is deleted after 30 days. Do not type anything private into it.
The table command on the merchant sales template and the labs bench works the same way, with less kept: what you type and the table's current setup go to Anthropic, whose model picks the new setup. Its rate limit and budget share the chat's, and the commands themselves are not stored. The assistant on the merchant sales template is the same: your messages in that conversation, the table's setup, the changes you make to its demo orders, and the text you highlight or the orders you tick on that page go to Anthropic, and none of it is stored. Those changes live in the page until you reload it. While the assistant is open, a highlight or a tick is sent as you make it, before you type anything, so it can suggest questions about it.
The assistant in the raceway chat lab works the same way: your messages in that conversation, what its 3D model shows, and the names, kinds and sizes of any files you attach go to Anthropic, and none of it is stored. The files themselves never leave your browser. Its rate limit and budget share the chat's.
Registry downloads
When a tool fetches a component from the shadcn registry, the site adds one to that day's tally for that component, along with the kind of client that asked: the shadcn CLI, another script, a browser, or a crawler. Nothing else is recorded. No network address, no identifier and no cookie is kept with the count, so it cannot be traced to you, and it is kept without an end date.
What this site does not do
No accounts. No advertising. Nothing is sold or shared for marketing. The only data collected is the analytics, the chat logs and the registry tally above, and all three are used only to run and improve the site. The machine-readable endpoint at /api/mcp stores nothing: it reads published data and answers. An image or a DESIGN.md you drop on the playground never leaves your browser: it is read there to sample its colours or read its tokens, and nothing about it is uploaded or kept. The same goes for files you attach in a scripted chat, on the playground, the chat home template or the chat widget's own page: they are read in your browser to draw their previews, and are never uploaded or kept. The site’s own chat takes text only.
Questions
This site is designed, built and run by Robert Ritacca. Open an issue on the project's GitHub repository.