Start with the exact official statement
Meta’s current Muse Code product page makes one direct distinction:
| Tier | Current Meta wording | What that establishes |
|---|---|---|
| Standard | Not used to improve our products | A current product-improvement label |
| Contributor | Used to improve our products | A different current product-improvement label |
That is meaningful evidence, but it is narrower than many questions developers naturally ask. “Improve products” is not automatically the same question as storage duration, human access, subprocessors, geographic processing, deletion, confidentiality, or a particular compliance control.
Separate three evidence layers
Current official product facts
The tier labels and rate rows are visible on Meta’s current Muse Code product page. The product is beta, so keep the Aug 9 verification date attached to any internal decision.
Launch context
The official research launch describes a local event log for model calls, tool runs, approvals, and edits. “Local event log” explains runtime recovery; it does not by itself establish the retention policy for every service-side request or account record.
Questions that still require current terms
- Exact retention and deletion behavior for each data category.
- Account-level controls and whether they differ by customer type.
- Contract terms for confidential or regulated code.
- Security review, incident response, subprocessors, and geographic requirements.
- Whether a specific enterprise or client policy permits the selected tier.
A lightweight review record
For a team trial, record the project classification, selected tier, official source URL, visible terms version or date, approving owner, and the date for re-review. That turns a one-time click into an auditable decision—especially useful while the product is beta.
If your decision is primarily economic, compare the two rows in the Contributor guide and run them through the cost calculator. If the code policy cannot support Contributor, use the Standard estimate rather than treating the cheaper row as the default.