$5 · 100 credits Up to 4 Fast · 2 Balanced · 1 Careful

$25 · 650 credits Up to 26 Fast · 13 Balanced · 7 Careful

$100 · 3,000 credits Up to 120 Fast · 60 Balanced · 35 Careful

Generation counts are estimates, not per-generation spending caps. Actual provider spend can increase the final credit debit above the selected tier price and initial reservation.

What a credit buys

Credits pay for AI model requests, geometry generation, validation checks and related compute. A successful request costs at least the selected tier price. When actual provider spend is higher than that tier's allowance, the final debit increases at the live rate shown next to Make it and may exceed the reservation or available balance.

Public package

Current packs are $5 for 100 credits (up to 4 Fast, 2 Balanced or 1 Careful generation), $25 for 650 credits (up to 26, 13 or 7), and $100 for 3,000 credits (up to 120, 60 or 35). A high provider cost can reduce the actual count.

Deliverables

A paid request can produce editable project versions, visible assumptions, validation warnings and downloadable STEP, STL, OBJ or 3MF artifacts when export checks pass.

Taxes and currency

Displayed prices are shown before any tax unless checkout states otherwise. Paddle calculates applicable taxes, supported payment methods and final currency at checkout.

Merchant of record

Paddle acts as merchant of record for paid checkout, processes payment details and issues buyer-facing receipts. PurCad receives checkout status and credit fulfillment events.

Custom pricing

Custom or enterprise pricing is not currently self-serve. If it is offered later, a downloadable pricing sheet or written quote should be provided before Paddle domain review.

Local project data

Projects, prompts, generated versions, parameters, assumptions, validation records, export metadata and usage records are stored by the studio server configured for this build.

Uploaded assets

Photos, scans, meshes, CAD files and print packages you attach are stored as project assets. Export artifacts such as STEP, STL, OBJ and 3MF files are kept with the project until removed from the configured storage.

External model calls

When a live AI model call is allowed, PurCad sends the minimum request context needed to create or revise the part, which can include prompt text, selected dimensions, assumptions and relevant attachment summaries.

API keys

Provider keys are read from runtime environment configuration. They are not saved into project records, generated CAD files or exported artifacts.

Data we collect

Depending on how the app is deployed, records may include project names, prompts, uploaded filenames and metadata, generated geometry, validation warnings, credit balance, cost estimates, live-call counts, timestamps and checkout status.

Usage analytics

Before consent, usage events are anonymous and do not contain prompts, files, email addresses or project IDs. If you allow analytics and sign in, later events may be grouped by your account identifier to understand the product journey. You can change this preference at any time.

How data is used

Data is used to operate the editor, generate editable CAD, preserve version history, show assumptions, run validation checks, prepare downloads, account for credit usage and troubleshoot failed jobs.

Third-party providers

PurCad may share request data with configured AI, geometry, storage, hosting, logging or billing providers only to provide the product. Those providers are expected to protect data under their own terms and applicable data-processing commitments.

Payments

Credit checkout is handled by the configured payment provider. PurCad stores checkout identifiers, package size, status and credit balance; it does not need to store full card numbers in project records.

Retention

Project data and artifacts remain available until deleted by the workspace operator, removed through app controls, or cleared from the configured storage. Operational logs and billing records may be kept longer when needed for security, accounting or dispute handling.

Access and deletion

A user or workspace operator can delete local projects and assets from the configured store. If a hosted deployment adds accounts, support must provide a way to request access, correction, export or deletion of personal data.

Security

PurCad limits stored secrets, separates provider keys from project records and keeps artifacts in configured storage paths. No system is perfectly secure, so sensitive uploads should be reviewed before sending them to external model providers.

Children

PurCad is not designed for children and does not intentionally request children's personal information. A deployment intended for minors needs additional consent, review and data-protection controls before release.

Changes

This policy should be updated when data types, providers, payment flows, retention practices or hosted account features change. The live policy URL should remain reachable from the app and public listings.

Seller identity

PurCad is the product and seller brand for this website. For paid checkout, Paddle acts as merchant of record and displays the buyer-facing merchant, tax and receipt information in checkout and transactional emails.

Editable drafts

PurCad produces editable CAD drafts and supporting metadata. Generated parts should be inspected, dimensioned, revised and validated by the user before export, printing, machining or installation.

Validation limits

Validation checks can flag missing dimensions, thin walls, risk categories, assumptions and export readiness. They are not certified engineering analysis, finite-element verification, code compliance or a substitute for professional review.

User responsibility

The user is responsible for final use, fit testing, load testing, material choice, fasteners, print settings, manufacturing tolerances, safety factors and compliance with laws or standards that apply to the part.

Exports

STEP, STL, OBJ and 3MF downloads are available from project versions when export checks allow them. Export availability can depend on project state, validation results, worker availability and configured storage.

Accounts and local builds

This build can run without a hosted account. If a hosted deployment adds accounts, users are responsible for keeping credentials secure and for activity performed in their workspace.

Credits and payment

Credits are prepaid balance for model calls, checks and higher-quality compute paths. The selected tier price is a minimum charge, not a maximum. PurCad reserves credits before a request, then settles successful work from actual provider spend under the rate shown next to Make it. The final debit can exceed both the initial reservation and available balance, leaving a negative balance that blocks later generation until credits are added.

User content

You retain responsibility for prompts, uploaded files, reference photos, scans, meshes and CAD files you provide. You must have the rights and permissions needed to use that material with PurCad and any configured providers.

AI output

AI output can be incomplete, approximate, duplicated, unsafe or wrong. PurCad does not guarantee that generated geometry is unique, patent-clear, manufacturable, structurally sound or fit for a specific purpose.

Acceptable use

Do not use PurCad to design weapons, illegal devices, unsafe products, surveillance tools, infringing products or parts meant to bypass safety controls. Do not attempt to overload, reverse engineer or abuse the service.

Intellectual property

PurCad's software, interface, copy and brand assets remain owned by their respective owners. Generated project files belong to the workspace subject to any rights in uploaded references, provider terms and applicable law.

Third-party services

AI providers, payment processors, hosting services and geometry workers may have their own terms, availability and data practices. PurCad is not responsible for third-party outages, policy changes or provider-side processing beyond its control.

Availability

The service may change, pause, fail or be discontinued. Features that rely on live model providers, payment systems, workers or local configuration are not guaranteed to be available at all times.

Liability

To the maximum extent allowed by law, PurCad is provided as a design-assistance tool without warranties. Users remain responsible for review, manufacturing, installation, damage, injury or loss arising from use of generated parts.

Changes to terms

These terms should be updated when pricing, credit behavior, provider use, hosted accounts, export capabilities or safety limits change. Continued use after changes means the updated terms apply.

Failed jobs

If a paid request fails before meaningful provider spend or compute work occurs, reserved credits should be released back to the workspace balance. If credits were charged incorrectly, contact support with the project and checkout details.

Used credits

Credits already spent on completed model calls, validation work or export preparation are generally not refundable because the compute and provider costs have already been incurred.

Unused credits

Unused prepaid credits may be reviewed for refund when required by law, when a duplicate purchase happened, or when the product cannot provide the purchased service. Approved refunds may reduce the workspace credit balance.

Duplicate or incorrect charges

Duplicate charges, checkout errors or incorrect package fulfillment should be reported promptly. Include the Paddle receipt, checkout email, amount, date and workspace details so the transaction can be traced.

How to request a refund

Use the contact page or reply to the Paddle receipt email with the purchase details and a short explanation. Paddle may also provide buyer support and payment dispute handling as merchant of record.

Statutory rights

Nothing in this policy limits mandatory consumer rights, chargeback rights or refund rights that apply in your jurisdiction. If local law requires a different outcome, that law controls.

Project history

Prompts, versions, assumptions, validation results and artifact metadata are tracked per project.

Cost ledger

Model usage records estimated dollar spend, reserved budget cap, tokens and live call count.

Budget gates

Expensive model paths are blocked unless the selected budget class and policy allow them.

No training claim

This local build does not add a training-data pipeline; it uses stored project data to run the current workspace.

Create or edit

Use the editor to generate a part, adjust sizes, review warnings and export files.

Continue work

Use the library to reopen saved models and continue from existing project versions.

Local configuration

Provider keys, asset directories and worker settings are configured in the local runtime environment.

Account access

Firebase sign-in protects project history, uploaded files, credits and export links for each user.

Design the part you wish existed.

From request to editable model without leaving the studio.

Describe or attach

Review the editable part

Export when it is ready

The supported paths are the ones in the editor.

Text to CAD parts

Photos, measurements, and files

Editable versions

Checked exports

Functional parts need honest limits.

Make a real part, then keep editing it.