This Privacy Policy explains what Pixite Inc. (“Pixite”, “we”, “us”) collects when you use PartForge, the service at www.partforge.ai (the “Service”), how we use it, who processes it for us, and the choices you have. It applies to PartForge only; Pixite’s other apps have their own policy at pixiteapps.com/privacy-policy.
1. What we collect
Account. Your email address, which is your sign-in. We do not collect a password unless you use the password fallback; sign-in links and codes are single-use and expire on their own.
Your forges. The parts you create, the chats you have with the assistant, sketches, reference images, uploaded files (STL, STEP, 3MF, fonts), the images you add to a forge’s gallery, and every saved revision. A forge is private until you publish it.
Public profile. A username, an avatar, and an optional bio, if you set them, plus likes and comments you post on public forges.
Billing. Your plan, subscription status, and Stripe customer and subscription identifiers. Card numbers never reach us; Stripe collects and stores them.
Usage metering. For every assistant request: the model used, token counts, and the cost we compute from them. The metering ledger never stores your prompts, part source, or screenshots.
Feedback reports. If you file a report: its title and body, the route you were on, the app version, your browser’s user-agent string, and, only if you grant it, support access to the forge and chats the report is about. Every read under such a grant is recorded.
Connected API keys. If you connect your own Anthropic, OpenAI, or OpenRouter key, we store it encrypted and use it only to make requests on your behalf. It is never shown again and never logged.
Contact form. Your name if you give one, your email address, and your message.
Waitlist. If you ask to join the waitlist, your email address and which page you asked from, so we can tell you when a spot opens.
Technical. Our hosting provider logs the IP address and request metadata of each request for security and operations. We also collect anonymous, aggregated usage statistics through Vercel Web Analytics and Speed Insights: the page or route, the referring site, campaign parameters, country and region, device type, browser and operating system, page-load performance, and a few named product events, such as a sign-in link being requested or a forge being published. Each visit is counted under a short-lived hash of the request that is discarded within 24 hours; nothing is stored in your browser, no identifier follows you across sites, and the data cannot be tied back to you or your account. Public forge pages are recorded by their public address; inside the editor, paths are recorded without the forge’s identifier. We keep no analytics profile of you.
Advertising attribution. When you arrive from one of our ads, the ad network adds a click identifier to the address. For 90 days your browser keeps it, with your browser’s user-agent string (its name, operating system and versions), and sends both to us when you do things on PartForge, such as signing up, creating, publishing or downloading a forge, or buying a plan, whether or not you have an account. We store them with what happened and when, and tell the network that ran the ad. The network receives no more than the click identifier, the user-agent string, what happened, when, and for a purchase its price; never your email, name, IP address, or anything you make. We delete these records 90 days after the click. We record Meta’s identifier only from links marked as our paid ads, since Facebook and Instagram also add one to shared links. Global Privacy Control turns all of this off, and Do Not Sell or Share stops it and deletes what we hold. Today this reporting goes to Google Ads, Reddit Ads and Meta (section 3).
Where you first came from. On your first visit we note, in your browser, the website that linked you here (its name only, such as reddit.com, never the page), any campaign tags in the link (utm_source, utm_medium, utm_campaign), which public page you landed on, and when. We keep it there for 90 days and, if you create an account in that time, store it with the account so we can count which sources bring people who sign up. It is never shared with anyone. A browser sending a Global Privacy Control signal, or one opted out on Do Not Sell or Share, records none of it.
Library searches. When you search the public library we record the search text, how many forges it found, and the same daily-rotating hash the view counts use, so we can see what people look for and whether they found it. Anything that looks like an email address or a long number is not recorded at all. The hash cannot be reversed to identify you, no account identifier is stored with a search, and a browser sending a Global Privacy Control signal records no searches.
Page tests. Sometimes we show different versions of a public page to see which works better. Your browser is assigned one version at random and keeps that choice, in your browser, for 90 days. We count how many browsers saw each version, and whether the video was played, under the same daily-rotating hash the view counts use, with no account identifier. If you create an account in that time, we store which version you saw with the account, so we can compare how many people from each version signed up and started using PartForge. This is never shared with anyone. A browser sending a Global Privacy Control signal, or one opted out on Do Not Sell or Share, records none of it.
2. How we use it
To run the Service: signing you in, storing and building your forges, sending your prompts and attachments to the AI models that draft parts, serving public forges, metering usage against your plan’s limits, billing paid plans, answering feedback and contact messages, and sending the emails the Service needs (sign-in links and codes, a welcome message, replies to reports, and a note when a waitlist spot opens). We do not sell your personal information. The only advertising use is the click attribution described in section 1, which tells an ad network which of its ads led to sign-ups, use of the Service, and paid plans.
Product email. Unless you turn it off, we also email account holders about PartForge itself: a short series of lessons on getting the most out of it, one a week starting a week after you sign up, and a note when we publish something new on our blog. You get at most one of these a week. Each one has a one-click unsubscribe link, and you can turn either kind off at any time in Settings → Email. We keep a record of which of these emails we sent you, so nobody gets the same one twice, and we do not track whether you open them or click their links.
Improving and supporting the Service. We also use what you create and how you use the Service, including your prompts and chats, to understand how PartForge is used, to improve it, and to diagnose problems. This work is done by Pixite staff whose role requires it and by our own internal tools. Where we can, we work from aggregated or de-identified information, and we look at an individual forge or chat only when that is needed to fix a problem or to understand how a feature is working. For example, we keep a de-identified copy of the first request you make in each new forge, with email addresses, links, and long numbers removed and no link back to you or the forge, so we can see what people are asking PartForge to build. We never sell this information, publish it, or use it to advertise to you. We don’t share it with anyone outside Pixite, except the service providers in section 3 who process it only on our instructions and may not use it for their own purposes. We do not use your private forges or chats to train AI models.
3. Who processes it for us
- Supabase hosts our database, authentication, and file storage.
- Vercel hosts the Service, collects the anonymous usage statistics described in section 1, and its AI Gateway routes assistant requests to the model providers below. Both operate in the United States.
- Model providers. Your prompts, chats, attached images, and the relevant part source are sent to the provider of the model behind your assistant: Anthropic, OpenAI, Google, xAI, DeepSeek, Moonshot (served directly or through Fireworks), Alibaba, or Z.ai, depending on the model you pick. DeepSeek, Moonshot, Alibaba, and Z.ai are companies based in China; your data goes to them only when you choose one of their models. Some features use a fixed provider whatever model you pick: Anthropic for drafting a forge’s library listing, Google for outlining reference photos, and OpenAI for generated gallery images and for search over the public library. If you connect your own key, requests go to that provider, or through OpenRouter, under your own agreement with them.
- Exa runs web searches the assistant makes; it receives the search query only.
- Google Fonts supplies fonts the assistant fetches for a part; it receives the font name only.
- Resend delivers our email.
- Stripe handles payments and subscriptions.
- Google Ads, Reddit Ads and Meta (Facebook and Instagram ads) each receive the click attribution described in section 1 for their own ads, and nothing else.
Each processor receives only what its task needs, and each is bound by its own privacy terms. Wherever you live, your information is processed in the United States, and by each model provider wherever that provider processes requests.
4. Cookies and browser storage
PartForge sets no cookies. Everything the Service keeps in your browser lives in local storage or IndexedDB: your session, your theme choice, a cached model list, recent selections, which version of a public page you were shown (90 days), and, for 90 days after you arrive from an ad, its click identifier and your browser’s user-agent string. During an OpenRouter connection a one-time verifier is held in session storage until the connection completes. Files you attach on the home page before signing in are kept only in your browser (IndexedDB) for at most 30 minutes, and are uploaded only once you have signed in.
We use no advertising cookies and no cross-site tracking. Our usage statistics (section 1) run without cookies or browser storage and cannot identify you, and view counts on public forges are computed from a daily-rotating hash that cannot be reversed to identify a person. Everything in that list except the ad click identifier is needed to run the Service, and the statistics identify no one, so we show no consent banner for them. The ad click identifier is the exception: it is not needed to run the Service, it is kept only for the advertising attribution described in section 1, a browser sending a Global Privacy Control signal records none and has any stored one discarded, and you can have it and what we recorded under it deleted at any time on Do Not Sell or Share. If your browser sends a Global Privacy Control signal, we also do not collect usage statistics from it.
5. What is public
When you publish a forge, its name, description, tags, license, gallery images, and full revision history become public, including through a git clone. Revisions carry your display name, never your email address. Your username, avatar, and bio are public, as are likes and comments you post. Private forges are never shown to other users. Pixite staff can access them only for the purposes in section 2, and when support looks at a forge to answer a feedback report, it does so under a grant you give for that report.
6. Retention and deletion
Forges you trash can be restored until you purge them; a purged forge is deleted from storage. You can ask us to delete your account and its data through the contact form. We keep records the law requires us to keep, such as billing records, and the metering ledger keeps request-level usage without any content. Waitlist entries are kept until the address signs up or asks to be removed; ask through the contact form and we will remove it by hand. Individual library-search entries are deleted after 90 days; daily counts per search term are kept. Page-test visitor counts (section 1) are kept as anonymous daily totals; the raw per-visitor rows, which carry only the daily hash, are deleted after 90 days, and the version you were shown is kept with your account until the account is deleted. The de-identified copies of new forges’ first requests (section 2) are deleted after 90 days. The log of tool calls a connected AI assistant makes on your account (section 10) is deleted after 90 days. Ad attribution records, with or without an account, are deleted 90 days after the click, or with the account; the copy your browser keeps is discarded on your next visit after that. A copy also stays in your account’s sign-up record until the account is deleted. The note of where you first came from is kept with your account until the account is deleted; the copy in your browser is discarded after 90 days.
7. Your rights
Depending on where you live, you may have the right to access, correct, delete, or export your personal information, and to object to or restrict some processing. Everything you create in a forge is exportable at any time through its download options and its git clone URL. To exercise any other right, email privacy@pixiteapps.com or use the contact form; we will verify the request against your account email.
California residents. Under the CCPA you have the right to know what personal information we collect and how we use it, to delete it, to correct it, and not to be discriminated against for exercising these rights. We do not sell personal information, and the only disclosure that may count as “sharing” under the CCPA is described in section 1: telling an ad network what one of its clicks led to, as described in section 1. We honor Global Privacy Control signals as an opt-out where they apply — a signal opts you out of that attribution before anything is recorded — and you can ask us to remove a stored click identifier through the contact form. You can also opt out directly, with a self-service control, at Do Not Sell or Share My Personal Information, which every page links in its footer as “Your Privacy Choices”.
8. Children
The Service is for adults. You must be at least 18 to create an account, and we do not knowingly collect personal information from anyone under 18. If you believe a minor has an account, tell us through the contact form and we will remove it.
9. Security
We protect your information with access controls, encryption in transit, encryption at rest for connected API keys, and row-level security in our database. No method of transmission or storage is completely secure, and we cannot guarantee absolute security.
10. Connecting an AI assistant
If you connect Claude, ChatGPT, or another AI assistant to your PartForge account, the connection gives that assistant the same access to your account as you have when you’re signed in, and the assistant’s own app decides which of PartForge’s tools it calls. Through them it can see your forges, create and edit them, build and render them, and publish or unpublish them, and it can search and read the public forge library on your behalf. Whatever a tool call returns is delivered to that assistant — a forge’s name and code, its listing text, renders of it, build and verification results, and any public library content it searched or read. The sign-in token the assistant uses also carries your account email, so its platform learns that address. We don’t receive the conversation you have with your assistant, only the tool calls it makes against your account. The assistant decides what goes into each call, so a call can carry something from your conversation, such as a description you asked it to write; we handle that like anything else you add to your account. We log those tool calls only as metadata — which app, which tool, which forge, when, and its outcome, with no code, images, or other arguments — and keep that log for 90 days. What the assistant’s own provider does with what it receives from a tool call is governed by Anthropic’s or OpenAI’s privacy policy, not this one, depending on which assistant you connected. You can disconnect an assistant at any time from Settings → Connected apps; a disconnected app stops renewing its access at once, though a token it already holds can keep working for up to an hour.
11. Changes to this policy
When we change this policy we post the new version here with a new “Last updated” date, and we email account holders about material changes.
12. Contact
Privacy questions and requests: privacy@pixiteapps.com. Everything else: the contact form.