Sonorie

Terms of Service

Last updated 1 August 2026

These terms are the agreement between you and Sonorie. They cover what the service does, what you can do with what you make, how paying for it works, and what happens when something goes wrong. Please read them — particularly section 5, on who owns the plugins you generate, section 6, on the third-party code inside your exports, and section 12, which limits what we are liable for.

By creating an account or using Sonorie, you agree to them. If you do not, please don’t use the service.

1. What Sonorie is

You describe an audio effect or an instrument in plain language. A large language model writes C++ DSP code against our toolkit, we compile it to WebAssembly so you can play it in your browser, and the same source can be exported as a JUCE project or built into a VST3, AU or CLAP plugin.

Two consequences of that are worth stating plainly, because everything else follows from them:

  • The code is written by a model, so it can be wrong. We run every build through automated gates — it has to compile, stay numerically stable, and meet measured acceptance criteria — but those catch broken output, not bad taste and not every subtle defect. Nothing generated here should be assumed correct because it compiled.
  • You get the source. Every export contains the actual C++ and the project that builds it, so you can read it, change it, and take it elsewhere. That is deliberate: it is what stops a bad generation from being a dead end, and it is why we are comfortable being honest about the first point.

2. Who may use it

You must be at least 18, or the age of majority where you live, and legally able to enter into a contract. Sonorie is not directed at children and we do not knowingly collect their information.

Your account is for you. Don’t share credentials or let others generate on your subscription. You are responsible for what happens under your account, so keep your password to yourself, turn on two-factor authentication if you can, and tell us promptly if you think someone else has access. You can end a session on any device you no longer recognise from the security page in your account.

3. Plans, billing and how usage is measured

Sonorie is subscription-only; there is no free tier. Plans are billed monthly in advance through Stripe and renew automatically until you cancel. Prices are shown on the account page and exclude any tax we are required to add.

The usage budget

This is the part most worth understanding, because it is unusual. Your plan does not include a fixed number of builds. It includes a budget of real model usage, and each build consumes whatever it actually costs to produce. A simple tweak costs a fraction of an involved multi-stage build. We show the budget as a percentage rather than in dollars, and it resets at the start of each billing period.

  • Any “approximately N builds per month” figure in our marketing is an estimate derived from measured averages. It is not a guarantee or an entitlement.
  • Unused budget does not roll over into the next period.
  • A build that fails, is cancelled, or is repaired automatically still costs real model usage and still counts against your budget, even where it isn’t counted as a generation. We would rather say so here than have it surprise you.
  • Your plan sets how many builds you may run simultaneously. Extra requests wait rather than fail.
  • If usage looks automated, resold, or otherwise outside normal individual use, we may rate-limit or suspend the account.

Top-ups

You can buy additional usage as a one-off prepaid amount. Top-up credit does not expire, is consumed only after your included budget for the period is used up, and is not exchangeable for cash. Because it is consumed as you use it, it is non-refundable once spent, except where the law says otherwise.

Changing or cancelling

Upgrades take effect immediately and are charged pro rata. Downgrades take effect at the end of the current period, so you keep what you paid for. You can cancel at any time from the billing portal; your subscription then runs to the end of the period already paid and does not renew.

We may change prices with at least 30 days’ notice by email. If you don’t accept a change, cancel before it takes effect.

Refunds, and why they follow your usage

Every generation spends real money the moment you run it — we are billed by the model providers for the tokens your build consumes, and that cost is not recoverable by us afterwards. Your subscription fee is therefore consumed progressively as you use your budget, not held until the end of the month.

So refunds are calculated on the part of your budget you have not used:

  • If you have used none of your budget for the current period, we will refund that period in full on request.
  • If you have used part of it, we will refund the unused proportion. Your remaining percentage is shown on your account page and is the figure we use.
  • If you have used all of your budget, the service for that period has been delivered in full and there is nothing left to refund.

We keep a detailed, timestamped record of every generation run on your account — when it ran, what it produced and what it cost — and we will happily show it to you.

If you are a consumer in the EU or UK you have a statutory right to withdraw within 14 days of subscribing. By running your first generation inside that window, you expressly request that we begin supplying the service immediately and acknowledge that you lose the right of withdrawal once it has been fully supplied. If you withdraw while it has been partly supplied, you remain liable for a proportionate amount reflecting what you used, measured by the share of your budget consumed. Nothing in this section affects rights you have by law that cannot be waived, and if you believe you are entitled to more than the above, tell us and we will look at it properly.

Card disputes

If something has gone wrong, email us first — [email protected]. Nearly every billing problem is a misunderstanding we can resolve in a day, and we would rather refund you directly than have a bank do it slowly.

Raising a chargeback with your bank for usage you actually consumed is not a refund request; it is a claim that the charge was not legitimate. Where that happens:

  • Your subscription is cancelled and access to generation ends immediately, because the disputed period is no longer paid for.
  • We respond to the dispute with our usage records: the timestamped generations run on the account, the plugins produced, and any exports downloaded.
  • You may be asked to settle the disputed amount and any fee the bank charges us before subscribing again.

This is not meant to discourage anyone with a real problem from disputing a charge. It exists because a generation that has already run has already cost us money, and the cost of that has to sit somewhere.

4. Your content, and what we do with it

Your prompts, chat history, projects and any images you attach remain yours. You grant us only the licence we need to run the service: to store that content, transmit it to the model providers described in our Privacy Policy so a response can be generated, compile it, and display it back to you. If you publish a plugin to the marketplace, that licence extends to showing your listing publicly.

We do not train models on your content.We use aggregate, non-identifying telemetry — timings, costs, how often builds pass the gates — to improve the pipeline. Model providers process your prompts under their own terms in order to answer them; who they are and where they are is set out in the Privacy Policy. As a general matter, don’t put personal or confidential information into a prompt.

5. The plugins you make are yours

We claim no ownership of the DSP code, interfaces or plugins you generate. To the extent they can be owned, they are yours, and you may use, modify, distribute and sell them, including commercially, subject to section 6 and section 7. You do not owe us a royalty on anything you generate.

Two honest limits on that, which no service in this category can avoid:

  • We cannot promise the output is protectable. Several jurisdictions hold that material generated by a model without sufficient human authorship does not attract copyright. What that means for a given plugin is a question for your own lawyer, not something we can answer for you.
  • We cannot promise it is unique.Similar prompts produce similar code, and a model draws on patterns common to the whole field. Another user may receive output substantially similar to yours. You get no exclusivity, and we don’t warrant that output is original or that it doesn’t infringe someone else’s rights.

6. Third-party code inside your exports

This section has real financial consequences — please don’t skip it. An exported project is a CMake project that builds against JUCE and, for the CLAP format, clap-juce-extensions. Those are third-party frameworks with their own licences. We do not own them and we cannot license them to you.

JUCE in particular is dual-licensed: it is available under an open-source licence with conditions attached, and under paid commercial terms. Which one applies to you depends on how you distribute your plugin and how much revenue you make. Before you release or sell anything built from an export, check the current JUCE licence terms and obtain a commercial licence if your use requires one. The same goes for any other third-party dependency, sample, preset or artwork you add.

Complying with those terms is your responsibility, not ours, and it is not something our subscription covers.

7. Acceptable use

Don’t use Sonorie to:

  • break the law, or infringe anyone’s intellectual property or privacy;
  • pass off someone else’s brand as your own. Building something voiced likea classic unit is ordinary engineering practice; naming your plugin after a trademark you don’t own, copying another product’s branding, or implying an endorsement or affiliation you don’t have is not, and it is your problem if you do it;
  • attack the service — attempting to escape the compilation sandbox, reach other users’ data, extract our prompts or credentials, or use generated code as a vehicle for any of that;
  • resell or redistribute access to generation itself, scrape the service, or run it through automation on someone else’s behalf;
  • upload content you don’t have the rights to, or anything unlawful or harmful;
  • place a load on the service designed to degrade it for others, or circumvent budget, rate or plan limits.

We may remove content, and suspend or close accounts, for breaches of this section. Where it is reasonable and lawful to do so we will tell you why first.

8. The marketplace

The marketplace lets you sell plugins you have made. When you sell, you contract directly with the buyer. We operate the platform and handle payment; we are not the seller, and we are not party to that contract.

If you sell

  • You confirm you have the right to sell what you list, including any third-party components in it, and that your listing is accurate and not misleading.
  • Listings are reviewed before going live. We may decline or remove a listing, including for a breach of section 7 or a rights complaint.
  • Payouts run through Stripe Connect. You must complete Stripe’s onboarding, which is where identity, tax and bank details are collected — by Stripe, on their own pages, under their terms. Those details do not pass through Sonorie.
  • We take a platform fee of 10%of the sale price. Stripe’s own processing fees also apply. The rest is transferred to you on Stripe’s payout schedule.
  • You are responsible for your own taxes, and for any VAT or sales tax due on your sales.
  • If a buyer charges back or a refund is due, the amount plus any related fee may be deducted from your balance or future payouts.
  • You are responsible for supporting what you sell, and for honouring what your listing promised.

If you buy

  • You get a licence to use the plugin, not ownership of it. Unless the seller says otherwise, it is for your own use; you may not redistribute or resell it.
  • Paid plugins are unlocked with a licence key issued to your email address, so buy with an address you will keep.
  • Because plugins are delivered as an immediate download, sales are final once delivered, except where the law gives you a right of withdrawal or where the plugin does not work as described. If something is wrong, contact us — we can help resolve it with the seller.
  • Reviews must reflect genuine experience of the plugin.

9. Audio safety

Generated DSP can produce sudden loud output, feedback, oscillation or DC offset, particularly while you are iterating on it. Our gates reject the worst of it before you hear it, but they cannot catch everything.

Start with your monitoring level low, be careful with headphones, and take special care before putting a generated plugin anywhere loud. Sonorie is not intended for use in live sound reinforcement, broadcast, or any situation where a fault could cause injury, damage equipment, or otherwise result in harm.

10. Availability and changes

We are actively developing Sonorie, and features may change or be withdrawn. We don’t promise the service will be uninterrupted or error-free, and we may take it down for maintenance. Model providers, compilation and build workers are moving parts that can fail independently of us.

Keep your own copies of anything you care about. Export the plugins that matter to you rather than relying on us as your only storage.

11. Disclaimers

To the fullest extent the law allows, Sonorie is provided as is and as available, without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose and non-infringement.

Specifically, we do not warrant that generated code is correct, stable, efficient, original, non-infringing, or fit for professional or commercial release, nor that any measurement or fidelity score we report is accurate for your purpose. Those numbers are a tool for iterating, not a certification.

12. Limitation of liability

To the fullest extent the law allows, we are not liable for indirect, incidental, special or consequential loss, nor for lost profits, lost revenue, lost data, lost goodwill, or damage to equipment or hearing arising from your use of the service or of anything generated with it.

Our total liability for any claim relating to Sonorie is limited to the greater of the amount you paid us in the 12 months before the claim arose, or 50 USD.

Nothing here limits liability that cannot be limited by law — including for death or personal injury caused by negligence, for fraud, or any statutory rights you have as a consumer.

13. Indemnity

You will indemnify us against claims, losses and reasonable costs arising from content you submit, plugins you distribute or sell, your breach of these terms, or your infringement of anyone else’s rights.

14. Ending the agreement

You can stop using Sonorie at any time and ask us to delete your account — see your rights in the Privacy Policy. We may suspend or close an account for a material breach of these terms, for non-payment, or where we are required to by law.

When an account closes, access to the service and to projects stored in it ends, and we delete or anonymise your data as described in the Privacy Policy — though we keep billing records for as long as tax law requires. Exports you have already downloaded remain yours, and licences you sold or bought on the marketplace are unaffected. The sections that by their nature should survive — ownership, disclaimers, liability, indemnity — do.

15. Changes to these terms

We may update these terms. For material changes we will give notice by email or in the app before they take effect, and the date at the top always reflects the current version. Continuing to use Sonorie after a change means you accept it; if you don’t, cancel.

16. Contact

Questions about these terms: [email protected]. Anything else: [email protected].

See also our Privacy Policy, which explains what we collect and who processes it.