d2c_

Privacy Policy

Last updated: April 15, 2026

This Privacy Policy describes how d2c ("we", "us", or "our") handles information in connection with the d2c documentation website (this site) and the d2c tooling.

What we collect

We do not collect, store, or process any personal data directly.

This documentation website is a static site. We do not run user accounts, contact forms, analytics scripts, or any first-party data collection.

Hosting and infrastructure

This site is hosted on Vercel. Vercel may collect standard server-access logs (IP addresses, request paths, timestamps) as part of normal hosting operations. These logs are governed by Vercel's Privacy Policy and are not accessible to or controlled by d2c-ai.

Third-party services

GitHub

The d2c documentation fetches content (skill references, plugin manifests) directly from the d2c-ai/d2c public GitHub repository at build time. No user data is sent to GitHub. Public GitHub API requests may include your IP address per GitHub's Privacy Statement.

Fonts and assets

All fonts and static assets are self-hosted. No requests are made to Google Fonts, CDNs, or other external asset providers that could track users.

d2c skills

The d2c tooling runs as Claude Code skills entirely on your local machine. This section explains what data each skill reads, writes, and sends externally.

What the skills access locally

All four skills operate on files already present in your project:

  • d2c-init — reads package.json, framework config files (nuxt.config.ts, angular.json, etc.), and your src/ or app/ directory to detect your stack and extract design tokens. Writes .claude/d2c/design-tokens.json.
  • d2c-build — reads your design tokens and Figma design data to generate component files. Writes generated code into your repo and stores intermediate build state under .claude/d2c/runs/<timestamp>/.
  • d2c-guard — reads .claude/d2c/design-tokens.json and your component files when you edit them. Read-only; writes nothing.
  • d2c-audit — scans your codebase for design token drift and hardcoded values. With --fix, rewrites affected files in place.

Local files written

Skills write only to paths inside your project:

Path Purpose
.claude/d2c/design-tokens.json Extracted tokens and framework config
.claude/d2c/intake-history.json Last 5 build inputs (Figma URL, mode, target)
.claude/d2c/build-stats.json Per-build metrics (match %, rounds, timing)
.claude/d2c/runs/<timestamp>/ Intermediate IR files for in-progress builds
Your src/ or app/ files Generated component code

None of these files are transmitted anywhere. Build stats and history are stored locally to help you track iteration patterns.

External services

The only external call made by d2c skills is to the Figma API, via the Figma MCP you configure and authenticate yourself. d2c passes your Figma URLs to the MCP to fetch design metadata and screenshots — no Figma data is cached or forwarded beyond that request.

There is no telemetry, analytics, crash reporting, or any other remote data transmission built into the skills.

Cookies

This site does not set any cookies. A theme preference (light/dark mode) may be stored in your browser's localStorage — this data never leaves your device.

Children's privacy

This site is not directed at children under 13. We do not knowingly collect information from children.

Changes to this policy

We may update this policy occasionally. Changes will be reflected by the "Last updated" date at the top of this page.

Contact

For questions about this privacy policy, open an issue at github.com/d2c-ai/d2c/issues.