flutter3d
Showcase Changelog 38 packages API reference

Content Policy and Copyright Notices

Version 1.0, effective 16 September 2026.

1. Where this applies, and where it does not #

The Modeller is a tool that runs on your machine. We host nothing you make with it. Models you open, edit and export never reach us, and there is no gallery, marketplace, cloud folder or sharing feature in which we could store or publish your work. There is nothing for us to moderate and nothing for us to take down, because nothing arrives.

This policy therefore applies to the places where content does reach us or the public through something we operate:

2. What you are responsible for #

You are responsible for having the rights to the files you open, import, convert and export with the Modeller. A format converter is not a licence: a model you are not allowed to use does not become one you are allowed to use by passing through a GLB export.

The same holds for anything you post to our repository or send us: post only what you have the right to post.

3. What is not welcome in our spaces #

In issues, discussions and pull requests: content that infringes somebody's rights; material that is unlawful where we operate; sexual content involving minors, which will be reported to the authorities rather than merely deleted; harassment, threats and targeted abuse; malware, and code whose purpose is to attack somebody; spam.

We remove such content and may block the account that posted it. The repository's CODE_OF_CONDUCT governs conduct more broadly.

4. Reporting content you believe infringes your rights #

If you own rights in material that appears in our repository or on our website, write to [email protected] with the subject line "Copyright notice". This is our designated address for such notices, under the US Digital Millennium Copyright Act (17 U.S.C. § 512) and under the European Union's Directive 2000/31/EC and Regulation (EU) 2022/2065 (the Digital Services Act) alike.

Include:

  1. Your name, address, telephone number and email address.
  2. Identification of the work you claim is infringed: a URL, a registration, or enough detail to identify it.
  3. Identification of the material you say infringes it, with a URL or a path specific enough for us to find it.
  4. A statement that you have a good-faith belief that the use is not authorised by the rights owner, its agent, or the law.
  5. A statement that the information in your notice is accurate, and, under penalty of perjury, that you are the rights owner or authorised to act on their behalf.
  6. Your physical or electronic signature.

We aim to acknowledge a complete notice within five working days and to act on a well-founded one promptly. We will tell whoever posted the material what was removed and why, and pass your notice on to them unless the law says otherwise.

Counter-notice. If your material was removed and you believe that was a mistake or a misidentification, write to the same address with the subject line "Counter-notice", identifying the material and where it was, stating under penalty of perjury that you believe in good faith it was removed by mistake, and giving your name, address, telephone number and consent to the jurisdiction of the courts where you live. We will pass the counter-notice on to the complainant and may restore the material where the law allows.

Abuse of this process. A notice sent in bad faith, to silence criticism or over material you do not own, carries consequences under § 512(f) DMCA and under Article 23 of the Digital Services Act, and we treat repeat bad-faith notices as such.

5. Third-party assets we ship #

The repository and the demos include sample models from the Khronos glTF Sample Models set, under their own licences and attributions, together with the attribution files that came with them. They are there so that a performance measurement runs on the same mesh everywhere. They are not ours, and their own terms govern what you may do with them.

If you believe an asset we ship is misattributed or wrongly licensed, tell us at the same address above. We want those reports.

6. Contributions #

Contributions to the repository are accepted under the MIT Licence of the project. By opening a pull request you confirm that you wrote what you are contributing or have the right to contribute it, and that you license it under those terms. We do not require a separate contributor licence agreement.

Do not paste code into a contribution from a source whose licence you have not checked. This includes output from an AI coding assistant where the assistant reproduced somebody's code verbatim.

7. Contact #