DATA & PRIVACY / UPDATED NOVEMBER 16, 2026
Your workspace.
Your provider choices.
This page describes how this version of the Forg3d website and studio handles data.
The public website
The website and release downloads are hosted on Cloudflare. Cloudflare processes technical request data, such as IP addresses, to serve and protect the site. We have not added advertising pixels, third-party analytics scripts, mailing-list forms, or visitor accounts to this website.
Cloudflare’s privacy policy describes its handling of data.
Projects and revisions
The studio stores named projects, thumbnails, up to 30 revisions, ten recovery checkpoints, components and binary mesh assets in IndexedDB on your device. Preferences use localStorage. Imported source files remain with their assets; embedded PNG/JPEG GLB textures are also decoded locally for display. Polygon reduction and its previews run locally, and accepted reduced geometry is stored as a separate asset. Trash retains data for restoration. Clearing site data removes this library; export project files for portable backups. The native app also keeps its library locally.
Printing checks, previews and 3MF packaging run on your device. Repaired copies are stored locally alongside their original projects. No printing geometry is uploaded to a repair service.
The public website does not offer cloud project accounts or upload your project history, thumbnails or imported model files to a Forg3d project server. Mesh imports do not fetch external resources. Current scene metadata is sent only when you request an AI operation.
Presentation and shared viewers
Images, videos, PNG frames and viewer files are generated on your device. Only the rendered canvas is recorded; no camera or microphone is used. Last-used presentation appearance is saved in localStorage. Shared snapshots include visible geometry and complete material texture maps, a public title and view settings, not hidden geometry, original source files, prompts or history.
Compact links carry compressed snapshot data after the URL fragment (#), which is not sent in ordinary HTTP requests to the website. Full links can still be retained by messaging services, recipients, browser history or extensions. They are not encrypted or revocable. Larger snapshots are sent as viewer files through the method you choose. The viewer validates them locally and does not write them into the recipient’s project library. No Forg3d model upload or share-index service is involved.
API keys
Keys manually entered in the browser stay in memory for that session and clear on reload. Native apps offer OS-protected credential storage. The public site does not include the developer’s API key. Keys are not part of saved project files.
AI requests and images
When you generate, apply an AI edit or compare providers, the studio sends the relevant prompt, scene data, and attached reference image to the selected providers. An edit sends the full current scene metadata, including part names, IDs, procedural parameters, transforms, lock flags and mesh asset references, along with the chosen scope and constraints. This lets the model account for ancestors and locked parts. Imported mesh file bytes and previous revisions are not sent. Accepted edits are saved locally; unaccepted previews are discarded when closed or reloaded. Comparisons send the input to each selected provider.
Reference images are not saved in project history. Providers have their own policies for retention, usage and billing. The OpenAI adapter requests store: false, which does not replace the provider’s broader data-handling policies.
Detailed mesh services
When you request detailed mesh generation, Forg3d sends the description or selected reference image directly to Meshy, or to Tripo through the native app. The service processes the input under its own retention and billing policies. Provider credentials are sent only to that service’s fixed API endpoint, never to a model-download CDN or Forg3d server.
Task IDs, the model description, status, output link and estimated-credit reservations are saved in a separate local job ledger. The reference image and API key are not saved there. Completed model files are downloaded from supported provider CDNs only when you choose Add generated model. Stopping local work does not delete or cancel work already held by the provider. Use its dashboard to manage that data.
Offline use and control
Demo presets and simple edits do not require an AI request. You can remove a reference image, clear browser site data, forget a saved native API key, or export and remove local project copies using your device’s tools.
For a walkthrough, see Getting started.