For a useful tool bug report

  1. Name the tool or guide where it happened.
  2. Include the browser and version, operating system and any WebGPU availability message.
  3. Describe the steps from opening the page to the problem.
  4. State the file format, approximate size and duration, and selected stem count. A private filename is unnecessary.
  5. Copy the visible error text and explain what you expected versus what happened.

Documentation corrections and suggestions

Include the page address and the relevant passage when reporting inaccurate instructions. For a feature suggestion, describe the task you want to complete; “I need a slower practice excerpt” is more useful than only naming a new button.

Privacy and previous orders

Use the same email for access, correction or deletion requests about previous account information, or questions about previous orders. The current tools do not require an account or payment. Do not include complete payment credentials in the initial message; any necessary record details can be discussed later.