Privacy and compliance
Content rights and visibility
Decide what others can access and review the permissions behind your audio, source and assets.
You keep ownership of what you make, subject to the permissions for any material you include. Uploading work also grants Maru the permissions described in the Terms. Before sharing, decide whether people should be able to hear the result, read its source or redistribute its files; those are different permissions.
Identify what you are sharing
| Action | Material to consider |
|---|---|
| Share an audio example | The recording and any material audible within it |
| Publish a bank or sound pack | Downloadable recordings, mappings and included metadata |
| Publish an instrument | Its interface, playable behavior, required assets and any supplied binaries |
| Share editable source | Code, presets, assets, attribution and dependency information |
| Offer a connected service | Account permissions and information sent to the service |
For example, permission to use a drum sample in a song may not let you include it in a downloadable sample pack. Read the asset's license for the use you intend. Making a player public does not itself give listeners permission to redistribute its content.
Check project visibility
New Studio module projects, including remixes, start public. Before uploading private recordings or editing confidential source, open Share, open the current access setting and choose Private. Wait for Private to appear before continuing. This setting does not require a paid plan. Public or unlisted modules let anyone who can open them play, read the latest saved source, fork and embed them. An unlisted link is not a private-access restriction.
Making the original private or deleting it does not remove forks people already made. Those copies remain in their accounts. Your unsaved edits, agent conversations and private revision history are not shown to other users. The Privacy Policy explains staff and service-provider access to private work.
Your signed-in view of your own profile may include private work and activity. Use each item's access settings to decide what other people can see. Your profile and community explains the public profile and follower connections.
Review dependencies
Keep provenance for recordings, samples, impulse responses, models, code and artwork. Confirm that the intended use includes distribution when those materials will reach customers.
Generation does not remove this review. Check the applicable model, service and source-material terms before including generated output in a commercial product. Generation in your products explains where content can enter the workflow.
Understand public playback
A playable browser experience must deliver enough data to play. Do not assume that an embed, public link or hidden download button protects those bytes from retrieval.
Use private access controls for material that should be restricted, and a product delivery flow for paid files. Confirm the delivery path with Maru before relying on it for protected content, particularly during marketplace beta.
Share or sell with clear terms
State what recipients may do with the result, and retain required attribution. For remixable source, consult the Maru Remix License guide; for framework distribution, consult licensing.
Selling on Maru covers the commercial preparation. If a permission or organizational data requirement is unclear, contact Maru before publishing or sending confidential material.