Privacy Policy

This policy explains what data Open3DAI collects, why it is collected, how long it is kept and what you can do about it. It covers the website, the Studio, the converters, the browser-side tools and the REST API.

It does not cover the third-party generation engines that this deployment may route to — Tripo3D, Meshy, Rodin and Hitem3D. When a request goes to one of them, that provider's own privacy policy applies to the data it receives.

The short version: we collect what is needed to run an account, generate and store your models, charge credits correctly, secure the service and answer your support requests. We do not run advertising trackers and we do not sell personal data.

Account data: your email address, display name, a hashed password, your locale preference and the date the account was created. Passwords are stored only as a hash and cannot be read back.

Creation data: the mode, engine, style preset, texture options, speed or quality setting, status and timestamps of each task; the credit cost of each task and the ledger rows that record every balance change; the files you upload and the meshes the system produces; asset names and whether an asset is public or private.

API and integration data: API key names, their scopes, the stored hash, the last-used time; webhook URLs and delivery attempts including response codes. Operational data: IP address, user agent and request timestamps in server logs, used for rate limiting, abuse prevention and debugging.

To run a generation: your prompt or uploaded image is the input to the engine, and the produced mesh and its maps are the output that gets stored for you to download. Without this use there is no service to provide.

To account for credits: every balance change writes a ledger row with the reason and the related task, which is how a refund or a billing question can be resolved accurately.

To secure the service and comply with the law: rate limiting, abuse detection, retention of records required for tax and accounting, and responding to lawful requests. We do not use your uploads or outputs for advertising, and we do not train models on them.

Uploaded files and generated meshes are stored on the server so they can be downloaded and converted later. Assets are Private by default, which means they appear only in your account. Making an asset public is an explicit action, and reversing it removes the asset from public galleries.

When you use the browser-side viewers or the STL editor, the file is parsed locally in the tab and is not uploaded at all. Converting between formats, generating a model or publishing an asset does involve the server and is stored as described above.

When you select a third-party engine, the prompt or image needed for that request is transmitted to that provider so it can perform the generation. If you would rather nothing left this server, use the built-in local engine, which performs the whole job here.

We set a session cookie that keeps you signed in, a locale cookie that remembers English or Chinese, and a CSRF token that protects forms against cross-site request forgery. None of these are advertising cookies and none are shared with third parties.

Browser-side tools may keep small preferences — viewport shading mode, camera settings — in your browser's local storage so the tool opens the way you left it. Clearing site data removes them; nothing in local storage is uploaded.

We do not embed third-party analytics or advertising scripts on this site. If that changes, this section will be updated before any such script is loaded, and the change will be announced on this page.

We share data only where it is necessary to run the service. Two categories exist: the third-party generation engine you explicitly selected, which receives the prompt or image for that one request; and infrastructure providers that host the application, the database and the stored files on our behalf.

Those providers act on our instructions and are bound to use the data only to deliver their service to us. We do not sell personal data, we do not share it with advertising networks, and we do not disclose it to anyone else except where the law requires it or where it is necessary to investigate abuse.

Server logs that contain IP addresses are kept separate from generation content and are retained for the short period described in the next section.

Account data is kept while the account is open. Uploaded files and generated outputs are kept until you delete the asset or close the account, after which the stored files are removed in the normal deletion cycle.

Server logs containing IP addresses and user agents are kept for 30 days and then deleted. Credit ledger rows are retained after account closure because they are accounting records; they contain the amount, the reason and the task reference, not the content of your uploads.

To delete an asset, use the assets page. To close an account and request deletion of the associated data, email /contact from the address on the account. Requests are handled within 30 days, and we will confirm when the deletion is complete.

Passwords are stored as hashes. API keys are shown once at creation and stored only as a hash, so a lost key must be revoked and replaced rather than recovered. Sessions use signed cookies, and form submissions carry a CSRF token.

Access to stored files is scoped to the account that owns them, and every generation task records which account and which engine it belonged to. Servers are kept patched, and administrative access is limited to the people who need it to operate the service.

No system is perfectly secure. If you find a vulnerability, report it to /contact and we will investigate; please do not test against other users' accounts or data.

You can access and correct your account details from the account page, export or delete individual assets from the assets page, revoke API keys, change your locale, and close the account entirely.

Depending on where you live, you may also have the right to request a copy of your personal data, to ask for correction or deletion, to object to certain processing, and to lodge a complaint with your local data protection authority. Requests go to /contact and are answered within 30 days.

The choices that affect what leaves this server are in your hands: use the local engine to keep generation entirely here, use the browser-side viewers and editor to avoid uploading a file at all, and keep assets Private unless you want them shown publicly.

This service runs on infrastructure that may be located in a different country from you, and a third-party engine you select may process a request in another jurisdiction. Where personal data is transferred, we rely on the safeguards offered by the hosting and engine providers, or on your explicit choice to use that engine for that request.

The service is not intended for children. Accounts are for adults, and we do not knowingly collect personal data from anyone under the age required to consent to data processing in their jurisdiction. If such an account comes to our attention, it will be closed and its data deleted.

We will update this policy when the service changes in a way that affects data handling, and we will change the date at the top of this page. Material changes will be announced on the site before they take effect; continued use after that date means you accept the updated policy.