Apex 3D Studio
Trust · privacy · rights · safety

Know where your work goes.

This page describes the current standalone preview. It is not a substitute for legal advice or a final public service privacy policy.

Last reviewed October 17, 2026

Local preview data flow

Modeling and GLB export occur in your browser. The “Save in this browser” action stores a small scene description in this browser’s local storage. This preview has no sign-in, hosted project library, server-side model generation, or cloud asset upload. Clearing browser data can remove a locally saved scene.

Generation and AI providers

No generative AI model is called by the current editor. Text commands add simple geometric primitives locally. The application does not send those command strings or scene geometry to Meshy, Tripo, Rodin, or another provider.

Output and intellectual property

Basic geometric primitives are not a legal clearance or exclusive-rights service. Rights may depend on source material, human creative contribution, applicable law and the terms of any future provider. This preview does not screen every design for similarity, trademarks, character rights, likeness, patents or third-party restrictions.

Safety boundary

The standalone editor does not validate printability, mechanical properties, medical suitability or engineering performance. Do not rely on an unverified model for safety-critical applications. Consult a qualified professional and applicable regulations.

Accessibility and device controls

The page provides keyboard-operable buttons, text controls, labels and respects reduced-motion settings for decorative animation. The interactive viewport depends on browser WebGL support; the product displays a diagnostic if it cannot initialize. Assistive-technology and device coverage still needs broad validation before a production accessibility claim.

Production launch requirements

Before hosted accounts, cloud generation or embeds launch, publish and test a complete privacy notice, retention/deletion terms, subprocessor list, acceptable-use policy, rights reporting/takedown path, support contact, security process, incident response, billing/refund terms and provider contract disclosures. Nothing in a disclaimer makes a potentially infringing output automatically lawful.