Privacy Policy

Effective: October 24, 2026 · Last updated: October 24, 2026 · ChipCraftX LLC

ChipCraftX LLC ("ChipCraftX", "we", "us", "our") builds tools that turn hardware specifications into verified RTL. This policy explains what personal information we collect, how we use it, who else receives it, how long we keep it, and the choices and rights you have. It applies to all of the following, together the "Services":

• our website, chipcraftx.io
• our web application, chipcraftx.app
• the ChipCraftX API
• the ChipCraftVS extension for Visual Studio Code
• the ChipCraftX app for iPhone and iPad

The short version

• We collect what we need to run your account and your design work: your contact and sign-in details, the specifications and prompts you write, and the RTL, testbenches and tool results the Services produce.
• Your specification is processed on hardware we operate (the ChipCraftX fleet) by default. It is sent to a third-party AI provider (Anthropic) only if you choose a Claude option and confirm that choice. We show you which tier handled each request.
• We do not sell or rent your personal information, we do not show ads, and we use no advertising or cross-site tracking cookies.
• We do not use your specifications or designs to train or fine-tune AI models, and we do not share them with anyone for that purpose.
• Generation records are deleted about 30 days after a run finishes. Your chat sessions stay until you delete them, and your Generate RTL jobs stay in your account until you ask us to delete them or close your account.
• You can ask for a copy of your data, a correction, or deletion of your account by emailing us. See "Your choices and rights."

Contents

1. Who we are and how to contact us
2. Information we collect
3. How we use information
4. Legal bases (EEA, UK and Switzerland)
5. AI model processing
6. How we share information
7. How long we keep information
8. Your choices and rights
9. US state privacy rights
10. Security
11. Notes for each product
12. Cookies and local storage
13. Children
14. International transfers
15. Changes to this policy

1. Who we are and how to contact us

ChipCraftX LLC is the controller of the personal information described in this policy. We are organized in Delaware, United States. You can reach us about privacy at info@chipcraftx.io. We will provide our postal address on request.

2. Information we collect

2.1 Information you give us

• Account details: your email address, username, first and last name, and a password (stored only as a one-way hash, never in readable form). You may optionally add your institution, course and expected graduation year. Your account also records a role (for example, student or instructor) and the time you last signed in.
• Sign-in with Google or GitHub: if you choose this, the provider sends us your account identifier, email address and basic profile information. We do not receive your Google or GitHub password, and we do not store the provider's access tokens.
• Access requests: ChipCraftX is invite-only. The access-request form in the web app asks for details such as your name, email, organization, a professional profile link, your role and your use case. The form on chipcraftx.io asks only for your email address.
• Your content: the specifications, prompts and chat messages you write; files and project context you attach; and the projects and studies you create.
• Feedback and support: ratings, comments, and anything you send us for support, including attachments.

2.2 Information the Services create

• Results: generated RTL, testbenches, simulation and verification results, error messages, and short summaries such as a session title taken from the opening of your first message.
• Generate RTL job records: when you run a Generate RTL job, we store the job's request (your specification and any context you attached), its result (RTL, testbench and the verification record), a progress log, and the amount billed, so you can reopen and reuse the job.
• Model interaction records: for each generation we keep the instructions and context sent to the model, the model's response, and token counts. We use these to investigate a result you report as wrong and to bill accurately. Only ChipCraftX administrators can view them, and they are deleted on the schedule in section 7.
• Billing records: your balance, purchases, usage charges and plan, and the identifiers our payment processor assigns to your customer record and payments.
• API keys: when you create a ChipCraftX API key, we store a one-way hash of it plus its first few characters so you can recognize it. We cannot recover the full key.
• Email records: which messages we sent you: the address, subject, type and delivery status.

2.3 Information collected automatically

• Server logs: when your browser, editor or app contacts our servers, we record your IP address, the browser or app identifier, the account making the request, the endpoint requested (without query parameters), and the time. We use this for security, rate limiting and troubleshooting.
• Website analytics: chipcraftx.io and chipcraftx.app use Plausible Analytics, which counts page views and referring sites in aggregate, sets no cookies, and does not track you across other sites.
• Device details for run alerts (iOS): if you turn on alerts, we store the push token Apple assigns to your device, the app identifier, and whether the build is a development or production build.

2.4 What we do not collect

• We never see or store your full payment card number. Our payment processor handles card details.
• If you turn on "bring your own key" in ChipCraftVS, those requests go directly from your computer to Anthropic under your own agreement with Anthropic. We do not receive or store that key or that traffic.
• The iOS app contains no analytics or advertising software.

3. How we use information

We use personal information to:

• provide the Services and keep your history in sync across the web app, the extension and the iOS app;
• create and secure your account, including sign-in, password reset, and preventing fraud and abuse;
• process payments and keep accurate billing records;
• investigate and fix problems, including reproducing a result you tell us is wrong;
• send you service messages, such as a password reset or an access invitation;
• send occasional product-feedback surveys, which you can unsubscribe from;
• understand in aggregate how the Services are used, so we can improve them;
• comply with the law and enforce our terms.

We do not sell your personal information, we do not use it for advertising or cross-context behavioral advertising, and we do not use your specifications, prompts, chat messages or generated designs to train or fine-tune AI models. We do not make decisions that produce legal or similarly significant effects about you based solely on automated processing.

Our use of information received from Google sign-in complies with the Google API Services User Data Policy, including its Limited Use requirements. We use that information only to authenticate you, and we do not transfer or sell it.

4. Legal bases (EEA, UK and Switzerland)

Where data-protection law requires a legal basis, we rely on:

• contract, to provide the Services you signed up for;
• legitimate interests, to secure the Services, prevent abuse, improve the product and respond to access requests, balanced against your rights;
• consent, where we ask for it (for example, push notifications), which you can withdraw at any time;
• legal obligation, for example keeping tax records.

You do not have to provide personal information, but we cannot create an account or provide the Services without at least your email address.

5. AI model processing

Generating RTL means processing your specification and related context, which can include earlier turns, generated code, tool output and knowledge-base excerpts.

• ChipCraftX fleet (CCM-1), the default. Your request is processed on hardware we operate and is not sent to any third-party model provider.
• Anthropic (Claude), optional. If you choose a Claude option and confirm it, your request and the context you attach are sent to Anthropic, PBC (United States) to generate the result. The Services show you which tier handled each request.

When we send content to Anthropic, we use Anthropic's commercial API, under terms that do not permit Anthropic to train its models on the content we send. If you use your own Anthropic key in ChipCraftVS, your use is governed by your own agreement with Anthropic.

6. How we share information

We share personal information only as described here. We do not sell or rent it.

Service providers. They process information on our behalf, under contracts that limit their use of it.

Internal team notifications. When you start a new chat session, our team receives an automated notification that includes your email address. It does not include what you wrote.

Other sharing:

• People you share with. If you share a project, the collaborators you choose can see it, in the role you give them. If you mark a simulation session as "shared," other signed-in ChipCraftX users can view it.
• Legal requirements. When we believe in good faith that disclosure is required to comply with law or valid legal process, or to protect the rights, property or safety of our users, the public or ChipCraftX.
• Business transfers. In a merger, acquisition or asset sale, personal information may transfer to the successor, which will remain bound by this policy.
• With your permission, in any other case.

Each third party with which we share user data is required to protect it consistently with this policy.

7. How long we keep information

8. Your choices and rights

Things you can do yourself:

• delete chat sessions, simulation sessions, projects and API keys;
• disconnect a Google or GitHub sign-in;
• turn off iOS run alerts, or sign out to remove the device registration;
• unsubscribe from non-essential email;
• in ChipCraftVS, turn off or clear local usage statistics.

Things you can ask us for. Email info@chipcraftx.io from your account address to request:

• a copy of your personal information;
• a correction;
• deletion of your account and data, including your Generate RTL jobs;
• restriction of, or objection to, a use of your information;
• data portability;
• withdrawal of a consent you gave.

We may verify your identity before acting, and we respond within the time the law requires (generally 30 to 45 days). You may use an authorized agent; we will ask for proof of authorization. Exercising these rights will not cause us to treat you differently.

EEA, UK and Switzerland. You also have the right to lodge a complaint with your local supervisory authority (in the UK, the ICO).

9. US state privacy rights

California. In the preceding 12 months we collected these categories of personal information (Cal. Civ. Code §1798.140):

• identifiers: name, email address, IP address, account ID;
• commercial information: purchases;
• internet or network activity: server logs and aggregate analytics;
• professional information: organization, role and job title, from access requests;
• education information: institution, course and graduation year, if you provide them;
• other content you create.

We collect it from you, from your device, and from any sign-in provider you choose, for the business purposes in section 3, and we disclose it to the service providers in section 6 for those business purposes.

We have not sold personal information and have not shared it for cross-context behavioral advertising in the preceding 12 months, and we do not do so. The only sensitive personal information we handle is your account log-in credentials, which we use only to provide the Services; we do not use or disclose sensitive personal information for purposes that would trigger a right to limit it. You have the rights to know, access, delete and correct your information and to opt out of sale or sharing (there is nothing to opt out of), and the right not to be discriminated against for exercising them. You may use an authorized agent as described in section 8.

Other US states (including Virginia, Colorado, Connecticut, Utah, Texas, Nebraska, Oregon and Montana). If you live in a state with a comprehensive privacy law, you have similar rights to access, correct, delete and obtain a copy of your personal information, and to opt out of targeted advertising, sale and certain profiling (we do none of these). Contact us the same way. If we deny your request, you may appeal by replying to our decision; if your appeal is denied, you may contact your state attorney general.

10. Security

We protect information with measures appropriate to its sensitivity, including encryption in transit (TLS), hashed passwords and API keys, administrator-only access to model interaction records, rate limiting, and per-account access controls. No method of transmission or storage is perfectly secure. If a breach affects your personal information, we will notify you and the authorities as the law requires. Report security concerns to info@chipcraftx.io.

11. Notes for each product

Web app (chipcraftx.app). Essential cookies keep you signed in (section 12). Drafts, recent chat state and layout are saved in your browser's local storage until you clear them.

ChipCraftVS for Visual Studio Code. In the default hosted mode, your specifications, chat messages and generated code are sent to ChipCraftX, and your chat history syncs with your account. When the assistant needs context, it can read files in the folder you have open and send their contents to ChipCraftX; each read is size-limited, and paths outside the open folder are refused. Do not open a folder that contains secrets you would not want processed. Your API key is stored in VS Code's encrypted secret storage. Local usage statistics stay on your computer and are not uploaded. If you turn on bring-your-own-key, some local features (such as inline edit) send code directly from your computer to Anthropic using your key; ChipCraftX does not receive that traffic.

ChipCraftX for iPhone and iPad. Drafts stay on your device unless you submit them. Sign-in tokens are stored in the iOS Keychain. The app connects to the ChipCraftX server and sends a specification only when you submit it. Dictation uses on-device speech recognition only; the audio is not sent to ChipCraftX or Apple. An optional on-device assistant is downloaded from Hugging Face, which receives the download request, including your IP address; after that it runs entirely on your device. If you turn on run alerts, we store your device's push token and Apple delivers the alerts. An alert says your run finished and whether its checks passed, and does not include your specification or code. The app does not create accounts; to delete your account, email us and we will delete it within 30 days.

Website (chipcraftx.io). The site uses Plausible Analytics (section 2.3). The access-request form sends your email address to our servers. Password-protected pages set a cookie to remember that you are authorized.

12. Cookies and local storage

We use only cookies that are necessary for the Services to work. We use no advertising or analytics cookies.

13. Children

The Services are not directed to children under 16, and we do not knowingly collect personal information from children under 16 without appropriate authorization, such as through an educational institution. If you believe a child has given us personal information without authorization, contact us and we will delete it. If you use ChipCraftX through a school or course, your institution may have additional terms.

14. International transfers

ChipCraftX is based in the United States, and information is stored and processed in the United States and wherever our service providers operate. When we transfer personal information from the EEA, the UK or Switzerland, we rely on appropriate safeguards recognized by law, such as the European Commission's Standard Contractual Clauses and the UK Addendum.

15. Changes to this policy

When we change this policy, we will post the new version here and update the "Last updated" date. If a change is significant, we will also tell you by email or within the Services before it takes effect.

Contact: ChipCraftX LLC, Delaware, USA · info@chipcraftx.io