Privacy Policy

1. Service Operator

3D Print Pass is the registered New Jersey alternate name under which the company operating the Service does business. In this policy, “the Operator” means that company, which is responsible for the practices described here. This policy applies to the website, accounts, file and report workflows, Print Analysis, Community, customer review links, billing records, support, and configured product monitoring.

New accounts and restricted product workflows are currently limited to people who assert that they are at least 18, legally able to contract, and using the Service from the United States. The Service does not collect a date of birth for this gate. Public site availability outside the United States does not mean the Service is offered or represented as compliant in every country. A public privacy-request path is currently provided for former users, non-account data subjects, parents or guardians, and authorized agents regardless of the enrollment boundary.

2. Information Collected

• Account and profile: email address, account identifiers, authentication and external-login identifiers, public profile name, optional avatar and its review status, account settings, and security events.
• Eligibility and legal evidence: selected ISO country, presented locale, adult and contract-capacity assertion, market-policy version, Terms and Privacy versions and source hashes, acceptance method, and UTC acceptance time. A date of birth is not collected for this gate.
• Files and custody: uploaded content; original filename; file type, size, and cryptographic hash; quarantine and trusted-storage references; scan provider, status, and details; request IP address, user agent, and trace identifiers; model measurements; and generated previews.
• Reports and workflows: scores, findings, report text, quote inputs and estimates, internal notes, tags, due dates, source URLs, Print Analysis questions and evidence, selected printer/material context, AI-assisted output, and saved case history.
• Customer review: customer name and email entered by the account owner, bearer-link creation and access context, and the name, email, and time submitted with a review acknowledgment.
• Community, support, and rights reports: display name, public questions, answers, comments, selected report summaries, moderation status, support contact details and message content, plus the contact details, work and material descriptions, required statements, and electronic signature submitted through the copyright notice or counter-notice intake.
• Signed-in product feedback: the page or product surface, helpful/not-helpful selection, selected reason, and submission time. If a signed-in user chooses “Other,” detail is required and is stored separately as an access-restricted, internally resolved support case and a non-customer-visible support note linked through server-derived account identifiers. It does not appear in the user-facing customer support-case list. Other detail is limited to 1,000 characters; do not include model data or unnecessary personal or confidential information.
• Technical activity: IP address, user agent, request and audit records, sign-in and security events, fixed product-event names, coarse outcomes and reason codes, timing, pseudonymous account or session hashes when configured, and operational logs.

3. Purposes

The Operator uses information to enforce the supported U.S. adult market boundary; create accounts and apply account-security controls; receive and validate content in available workflows; scan model files and profile images when the configured workflow requires a scanner verdict; analyze submitted files, written troubleshooting details, and photos when offered; generate scores, reports, previews, troubleshooting output, source checklists, and customer-review records; provide Community and support; administer credits, subscriptions, and billing access; prevent abuse; investigate errors and security events; meet legal obligations; and improve Service reliability and usability.

4. Uploads & Optional AI

Model-file and profile-image intake may use configured safety scanning before trusted processing. Print Analysis photo submission is currently paused. 3D Print Pass should not be used as the only copy of a production file. Upload only content you trust, and avoid unnecessary personal or confidential information in filenames, notes, prompts, photos, or other evidence.

When an AI-assisted feature is enabled, bounded prompts, selected text, original filenames, model measurements, an image, or source-review material such as a public URL, page title, and bounded page excerpt may be sent to the configured AI provider. Direct Edit requires an unchecked, one-request acknowledgment before provider processing; it sends the typed prompt plus model-derived source hash, revision counters, object and boundary identifiers, node kind, selection state, and undo/redo counts. Studio does not add a filename, model bytes, vertices, or G-code to that provider request, although anything the user types into the prompt is sent. Provider/model identifiers and generated output may be saved with a report or case. Production AI deployment is release-gated to an approved U.S. data-zone or regional configuration, but provider networks, support, security, and contractual subprocessors may still transmit or process data elsewhere as their documented service requires. AI output can be inaccurate and must be reviewed.

5. Analytics, Cookies & Browser Storage

First-party product monitoring may record important product steps such as page and intake views, upload or analysis outcomes, sign-in or registration outcomes, and checkout or report-unlock actions. The allowlisted event schema uses fixed names, coarse outcomes and reason codes, duration, and pseudonymous identifiers when configured; it excludes uploaded content, filenames, Print Analysis text, photos, email addresses, card details, and free-form feedback.

Product feedback is stored separately from that fixed event stream and records the product surface, helpful/not-helpful selection, an allowlisted reason, and submission time. It does not store the free-form “Other” detail. For authenticated “Other” submissions, that required detail and its server-derived account linkage are stored separately as access-restricted support-operations records for product reliability and usability review.

Required cookies support authentication, antiforgery protection, security, metered previews, and core preferences. An optional analytics-session cookie is created only after optional cookies are allowed. The first-visit control presents equally available allow and reject choices, and the site-wide Cookie settings control currently permits a later preference change. Coarse first-party events may still be counted without an account or session identifier for operations and product improvement. Current configuration applies a short retention limit to unlinked product events; actual deletion depends on the configured cleanup process and may be affected by the backup and legal-hold conditions described below.

Device-only storage can include interface and tutorial preferences; Print Analysis drafts for up to 7 days; optional Studio source-file recovery for up to 24 hours; and Studio plans, repair completion, and up to 30 outcome records per printer/material, including an optional free-form note, for no more than 90 days after the last save. Plans are capped at eight per model-derived browser key. Expiring Studio records are purged on a later site visit after expiration. Legacy unversioned Studio records are deleted when that feature next reads them rather than silently receiving a new retention period.

The listed browser-only records are designed to remain local. The relevant workflow sends them to the server when the user invokes its submit or save action, as described for that workflow; the separate source-recovery control governs restoration of an enabled Studio source record. Anyone using the same browser profile may be able to access these records. Browser cleanup or clearing site data can remove them.

6. Billing Information

New checkout is currently paused. When provider-hosted billing is available, full payment-card numbers, security codes, billing name, email, and address are entered with Stripe. 3D Print Pass does not intentionally request or persist full card numbers or security codes. New webhook processing keeps billing contact and postal-address details at Stripe instead of copying them into the local customer snapshot. Local records retain provider customer, subscription, price, checkout-session, event, invoice, and payment-method identifiers when those objects are reconciled; transaction subtotal, tax amount, total and currency; tax and payment status; the verified two-letter billing country required for U.S. checkout enforcement; and card brand, last four digits, and expiration month/year for display, reconciliation, refunds, and support. Legacy local snapshot columns may still contain older billing email, name, country, postal code, funding type, or card-country values until an approved accounting/legal retention decision authorizes cleanup.

7. Disclosures & Public Features

Information may be disclosed to configured providers that perform hosting, storage, security scanning, email, billing, AI processing, monitoring, and support; to professional advisers and authorities when reasonably necessary to protect rights, investigate harm, complete a business transaction, or comply with law; and to recipients a user directs through Community publication or a tokenized report link.

Primary application, storage, database, communications, and configured AI resources are in United States locations or a U.S. data zone. Provider networks, support, backups, and subprocessors may process information elsewhere under their applicable terms. This is a description of the current setup, not a promise that all processing stays in one place.

Community content and deliberately published report summaries are public. A customer report link can be created either as a bearer link that anyone holding the token may open or as a confirmed-account link limited to the selected signed-in recipient. Both modes end at the selected expiry or earlier owner revocation. Shared reports exclude customer contact details, internal notes, and the original upload. Uploaded model files are not automatically published to Community or offered as public marketplace listings.

8. Retention & Deletion

No single retention period applies to every category. Account, report, case, billing, Community, share, custody, security, support, and copyright-dispute records serve different operational and legal purposes. Saved workflow data may remain while an account is active; audit and product-monitoring records use configurable retention controls; anonymous metering identifiers and rows are bounded to the configured cookie-and-abuse-prevention period; and provider and backup copies follow their applicable schedules.

The submitted “Other” detail and its server-derived account linkage are kept in restricted support records under the support-operations retention and privacy-request process, not the shorter product-monitoring event stream. Support records are retained for case handling and related operational or legal needs. No fixed deletion date is stated here. A legal hold, unresolved request, provider schedule, or backup cycle may delay deletion.

Signed-in users can track account-data access, export, correction, and deletion requests in the privacy-request area. Some records may remain where an applicable legal or operational reason requires it. Retention varies for uploads, reports, support, logs, billing, Community, and backups; the privacy-request paths below accept requests about specific records.

9. Choices & Requests

Account tools support selected profile, authentication, billing, and preference changes. Optional analytics-session cookies can be declined. Public Community content and bearer links should be used only after reviewing what will be disclosed; confidential report sharing should use the confirmed-account option. Signed-in users can use the authenticated, account-scoped tracked privacy-request area. Former users, non-account data subjects, parents or guardians, and authorized agents can use the public email-verified intake. After identity and authority verification, the versioned downloadable portability package includes projected responsive records for account identity, profile, onboarding, uploads, Print Score reports, subscriptions, usage, legal acceptance and market eligibility, Community contributions, support cases and eligible notes, privacy-request operations, and bounded operational telemetry. It omits credentials, tokens, protected verification values, storage paths, provider identifiers, internal-only notes, and unrelated people's records. Categories that cannot yet be safely or deterministically assembled, including provider-held copies and pseudonymous or indirect relationships, remain explicitly marked for manual or external review rather than reported as complete. The public response does not disclose whether an account exists. Email-channel verification does not by itself prove identity or authority, so additional proportionate verification may be required. Applicable law may provide additional rights or exceptions.

10. Security, Policy Changes & Contact

3D Print Pass uses administrative and technical controls intended to reduce risk, including access controls, secure-cookie and production HTTPS requirements, file quarantine and configured scanning, audit records, and role restrictions. Production configuration requires encrypted transport, while each release still needs a live deployment probe before that condition is treated as verified. No system, scan, storage provider, or transmission method is guaranteed secure.

The Operator may update this policy as the Service, providers, laws, or data practices change. When a document version is configured as requiring renewed acceptance, authenticated use is gated until the current version is accepted. Other notice obligations require an approved operational process. Route a privacy-policy question through the legal contact path; use the tracked privacy-request area for account-data requests.