Privacy Policy

Last updated: March 26, 2026

Who we are

This website (domscribe.com) is operated by Patch Orbit LLC. Domscribe is an open-source developer tool. This policy covers data practices for both the website and the Domscribe software.

Domscribe software

Domscribe is a development tool that runs entirely on your local machine. It is designed with privacy as a core principle.

Fully local architecture

All Domscribe components — the bundler plugin, relay server, overlay UI, and MCP server — run on localhost during development. No data is transmitted to Patch Orbit, Anthropic, or any external service. There are no cloud dependencies, no telemetry, and no phone-home behavior.

What data Domscribe processes

During development, Domscribe processes the following data locally:

• Source file locations— File paths, line numbers, and column numbers are recorded in the manifest (.domscribe/manifest.jsonl) to map DOM elements to source code.
• Component metadata— Component names, tag names, and element IDs are captured at build time.
• Runtime context— When queried by an agent, Domscribe captures live component props, state, and DOM snapshots from the running browser. This data is exchanged between the browser and your local agent via the localhost relay server.
• Annotations— When you use the UI-to-Code workflow, your instructions and element context are stored as JSON files in .domscribe/annotations/ within your project directory.

Built-in PII redaction

Domscribe automatically scrubs personally identifiable information before runtime context leaves the browser. The following patterns are redacted by default:

• Email addresses
• Phone numbers
• Credit card numbers
• Social Security numbers
• IP addresses
• API keys and tokens
• JWTs

Additionally, values in props or state with sensitive field names (e.g. password, secret, token, authorization, ssn, creditCard) are automatically replaced with redacted placeholders. PII redaction is enabled by default and can be configured via the redactPII runtime option.

Zero production impact

All Domscribe instrumentation — data-ds attributes, overlay scripts, relay connections, and runtime adapters — is automatically stripped from production builds. This is enforced by CI on every test fixture. No Domscribe code or data reaches your end users.

No data leaves your machine

To be explicit: Domscribe does not send any data to external servers. The relay server binds to 127.0.0.1. All communication between the browser, relay, and your coding agent happens over localhost. Your source code, component data, annotations, and manifest files remain on your machine and in your repository.

Website (domscribe.com)

Analytics

We use Vercel Analytics to understand how visitors use this website. Vercel Analytics collects anonymous, aggregated usage data including page views, referrers, browser type, and country. It does not use cookies, does not track individual users across sessions, and does not collect personal information. See Vercel's Analytics privacy policy for details.

Hosting

This site is hosted on Vercel. Vercel automatically collects standard server logs (IP address, request URL, timestamps) to operate the service. These logs are subject to Vercel's privacy policy.

No cookies

This website does not set any first-party cookies. We do not use advertising trackers, social media pixels, or third-party analytics services beyond Vercel Analytics.

No personal data collection

We do not collect names, email addresses, or any other personally identifiable information through this website. There are no sign-up forms, newsletters, or account systems.

Third-party services

This website loads resources from the following third parties:

• Google Fonts— Font files (DM Sans, Inter, JetBrains Mono). Subject to Google's privacy policy.
• cdnjs (Cloudflare)— highlight.js for syntax highlighting. Subject to Cloudflare's privacy policy.

GitHub

Links on this site may direct you to our GitHub repository. Your use of GitHub is subject to GitHub's privacy statement.

Changes

We may update this policy from time to time. Changes will be posted on this page with an updated date.

Contact

If you have questions about this privacy policy, you can open an issue on our GitHub repository.