Lean by default
Most editing work happens in the browser.
Core rigging, viewing, and animation adjustments run client-side when possible. Server-side handling is mainly used for accounts, billing, and AI-backed features.
Data Handling
Privacy Policy
This policy explains what AnimateMesh collects, including essential browser storage and optional analytics choices, how that data is used, when it is shared with infrastructure or AI providers, and what controls users keep over their account data, uploads, and generated assets.
Effective Date
April 30, 2026
If you deploy your own copy of AnimateMesh, the operator of that deployment is responsible for adding the correct legal entity, contact details, and jurisdiction-specific privacy notices.
Processors
Some requests are sent to infrastructure and AI providers.
That can include Supabase, Stripe, Meshy, and OpenAI depending on which features you actually use.
Your Control
You stay responsible for what you upload and choose to generate.
You can avoid specific third-party processing simply by not using the related feature paths.
01 What We Collect
AnimateMesh collects the data needed to run the features you use.
- Account data such as email address, auth provider, public profile metadata, and internal user id.
- Essential browser storage used for sign-in state, saved preferences, and workflow continuity.
- Uploaded files, prompts, images, textures, generation settings, and saved workflow metadata when you use those features.
- Billing-related identifiers and checkout records when you use paid plans or credit packs.
- Analytics data, such as page visits and broad usage patterns, when Google Analytics is enabled for a deployment.
- Operational logs, error records, and basic request metadata needed to keep the service secure and functioning.
02 How We Use It
Data is used to operate the app, not to invent unrelated uses.
We use collected information to authenticate users, deliver editing and export workflows, save dashboard history, process purchases, prevent abuse, troubleshoot failures, and maintain the service.
If Google Analytics is enabled for a deployment, aggregated visit and page usage data may also be used to understand which pages are reached, which tools are used most, and where product improvements are needed.
When you explicitly trigger AI-assisted features, the relevant prompt or asset data is used to generate the requested output. We do not need to collect unrelated personal profile details to provide the core tool.
03 Sharing
Data is shared only when the workflow requires it.
AnimateMesh may share data with service providers that support authentication, hosting, payments, analytics, or feature execution. That includes vendors such as Supabase for auth and stored records, Stripe for checkout and subscription handling, Google Analytics for optional visit measurement, and AI providers for model generation or texture workflows.
We may also disclose information when required by law, to enforce platform terms, or to protect the security of the service, users, or infrastructure.
04 AI Feature Routing
Generation features send only the content needed for that request.
If you use Text to 3D, Image to 3D, or AI texture workflows, the relevant prompt text, uploaded image, or texture data may be transmitted to the configured model provider so the feature can run.
Output quality and data handling may vary by provider. If you do not want data sent to a third-party model service, do not use that specific AI-driven feature path.
05 Retention
We keep records for as long as the workflow or account needs them.
Account and billing metadata may be retained as needed for security, compliance, fraud prevention, and subscription support. Saved workflow artifacts and model metadata may remain in your account history until deleted, expired, or removed by service policy.
Because this project can be self-hosted or customized, exact retention windows may differ by deployment and infrastructure settings.
06 Security
Reasonable safeguards are used, but no system is perfect.
We use reasonable administrative and technical measures to protect account and workflow data, including authenticated sessions, provider-managed infrastructure, and access controls appropriate to the current deployment.
No internet service can promise absolute security. You should avoid uploading highly sensitive materials unless you are comfortable with the provider and deployment handling them.
07 Choices
You can choose which features you use and what data they receive.
You can control whether to create an account, whether to purchase credits, and whether to use AI-powered workflows that transmit prompts or assets to external processors.
If a deployment offers account deletion, export, or support-based data access requests, those requests should be handled through the contact channel published by that deployment operator.
08 Updates
Policies can change as the platform changes.
We may update this Privacy Policy to reflect new features, new processors, legal requirements, or operating practices. The effective date on this page should be updated when material changes are published.
If a legal entity or support email needs to appear here, add it before production launch so users have a clear path for privacy questions and rights requests.