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.
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.
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 and we do not use it for advertising.
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 model behind your assistant: Anthropic, OpenAI, Google, Moonshot, or Z.ai (served directly, or through Novita or Crusoe), depending on the model in use. 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.
Each processor receives only what its task needs, and each is bound by its own privacy terms.
4. Cookies and browser storage
partforge sets no cookies. Everything the Service keeps in your browser lives in local storage: your session, your theme choice, a cached model list, and recent selections. During an OpenRouter connection a one-time verifier is held in session storage until the connection completes.
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. Because none of the storage above is optional to running the Service, and the statistics identify no one, we do not show a consent banner. If your browser sends a Global Privacy Control signal, we 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 visible only to you, and to support staff only under a grant you give while a feedback report is open.
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.
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 or share personal information as those terms are defined in the CCPA, and we honor Global Privacy Control signals as an opt-out where they apply.
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. 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.
11. Contact
Privacy questions and requests: privacy@pixiteapps.com. Everything else: the contact form.