Terms of service
Effective 8 August 2026
The short version: you keep what you type in, the audio the engine renders for you is yours, and on Creator, Station and Group you may put it on air and bill a client for it. You pay for seconds of rendered audio, the allowance is a ceiling rather than a meter, and there is no overage charge waiting for you at the end of the month.
Who you are agreeing with
These terms are an agreement between Workflow Corporation, which trades as Radio Workflow HQ and has its place of business at 210 Emerson Pl, Suite 300, Davenport, IA 52801, USA, called “we” here, and you, the person or the business using Jingle Buddy. They cover the website, the studio, the public API and everything the engine renders for you.
By opening an account you accept them. If you are accepting on behalf of a station, a group or an agency, you are confirming you can bind it, and “you” means that business.
The acceptable use policy and the content and rights policy form part of this agreement. The privacy notice is not part of the contract but describes how we perform it, and it is more specific than this document about what deletion deletes.
Accounts, workspaces and who is responsible
- You must be at least 18 to open an account. Not the age of digital consent where you live, 18 everywhere. This service takes payment by card and it grants a commercial licence a business will rely on in front of its own clients, and neither a subscription nor a licence is a contract a child can enter. If we learn an account holder is under 18 we will close the account.
- The details you give have to be true. The address on the account is the only way we have of reaching you: it is where a workspace invitation and a password reset go, and it is the address we will expect a request about the account to come from.
- Work lives in a workspace. A workspace has an owner, and the owner is responsible for what is in it, for who is invited into it, and for what those people do with it.
- Members hold a role. Owners and administrators manage the workspace, members can render, and viewers can listen and download but cannot spend the allowance. How many people may be in a workspace at once is set by the plan (see the table below).
- You are responsible for your credentials and for your API keys. A key is shown once when it is minted, it acts for the whole workspace, and anything done with it is charged to it. Revoke a key you cannot account for.
What you put in stays yours
Your prompts, your lyrics, your client briefs, your station profiles and anything you upload remain yours. We do not claim any ownership in them.
You give us only the permission we need to run the service: to store what you typed, to send it to the engine so it can be sung, to render, keep and serve back the audio, and to keep it safe. That permission ends when you delete the content, except where the privacy notice explains something outlives it, and it exists for no other purpose. In particular we do not train any model on it.
You confirm you are entitled to put it in. An advertiser’s name, phone number and offer, a legal line that has to be read word for word, another station’s call letters: those belong to somebody, and the content and rights policy sets out what that means in practice.
The audio, and your right to put it on air
As between you and us, the audio the engine renders for you is yours. On Creator, Station and Group you may use it commercially, including on air and in advertising you charge a client for. No per-play fee, no reporting to us, no further permission needed.
Spelled out, because this is the clause people need to be able to quote: we grant you a worldwide, perpetual, irrevocable, transferable and sub-licensable right to use, reproduce, edit, distribute, broadcast, stream and perform the audio you rendered, for any lawful purpose, on any medium. That includes handing the finished file to the advertiser it was made for, and charging them for the work.
The right survives the subscription. Audio you rendered while on a plan that carries commercial use stays licensed to you after you downgrade, cancel or close the account. A spot running for a client does not come off the air because a card expired.
The free tier is different. Free is for evaluation and personal use: rendering to hear what the engine does with your call letters or your client’s brief, not for putting to air and not for anything you are paid for. Upgrade and render it again before it goes out.
Worth knowing rather than discovering: nothing in the product stops you downloading a track you rendered on the free plan, and the file carries no marking to say which plan made it. The restriction above is a term of this agreement rather than a lock in the software, so putting a free render to air is a breach of it rather than something we will catch for you. The table is the whole of the rule, and it is generated from the same plan catalogue the service bills from.
| Plan | Commercial and broadcast use | People in a workspace |
|---|---|---|
| Free | Evaluation only | 1 |
| Creator | Permitted | 3 |
| Station | Permitted | 10 |
| Group | Permitted | 50 |
We do not licence audio rendered for your workspace to anybody else. There is a public switch on a track, a persona and a playlist, and turning it on is your permission for us to show that item to other people inside Jingle Buddy. It is off until you turn it on and you can turn it off again. Said plainly because a permission is not a feature: nothing acts on that switch today. No screen and no endpoint in the product shows one workspace’s public items to another, so what it records is a permission rather than a publication, and if we ever build the listing it belongs in, this clause says so before it opens.
What the licence does not promise
Everything above is what we can honestly grant. These are the edges of it, and they are here rather than in a footnote because a broadcaster needs to know them before the client meeting, not after.
- The style is not exclusive. We do not licence your renders to anyone else, but nobody owns a genre. Another customer asking for the same kind of bed can receive audio that sounds similar, and nothing here promises otherwise.
- Copyright in machine-generated audio is unsettled. In some countries, the United States among them, material produced by a machine without human authorship may not attract copyright protection at all. We grant you every right we hold. We cannot grant a right that nobody holds, and we do not promise the output is registrable. If you need an exclusive, registrable composition, that is a commission rather than this.
- Anything you add is yours to clear. A voice read over the bed, an advertiser’s trademark, a piece of music you licensed elsewhere and mixed underneath: this licence covers what our engine rendered, and nothing else in the file.
- No generative system can promise it will never resemble something. If somebody believes a render infringes their rights, the route to us is in the content and rights policy, and it does not require an account.
- Check the length before you traffic it. The engine renders to the length you asked for and does not always land on it to the frame. A :30 that runs long is a rejected spot, and the file is yours to verify against your own log.
How the service may be used
The acceptable use policy is part of these terms and binds everybody in your workspace. The short version: make jingles and imaging, for yourself and for your clients, and do not use the engine to imitate a real person, to deceive, to break broadcast rules, or to resell raw generation as a competing service.
Plans, the allowance and payment
- The unit is a second of rendered audio, not a song. A sung second and an instrumental second cost different amounts, and the rates and the allowances are published on the pricing page. That page is generated from the same figures the meter reads.
- The allowance is a ceiling, not a meter. Every render is priced and claimed against the allowance before the engine is asked to do anything, so when the allowance is spent, renders stop and you are invited to move up a plan. There is no overage line and no automatic charge for going over, because going over is not possible.
- Renewal. Subscriptions renew each period and are charged to the card on file through our payment gateway until you cancel. Cancelling stops the next renewal; the current period runs to its end.
- Changing plan. Both directions take effect at once. On an upgrade you are charged the difference between the two prices for the days left in the period, immediately, with any account credit applied first. On a downgrade nothing is charged and nothing is refunded, and the smaller allowance applies from that moment rather than from the end of the period. The seconds you have already spent this period stay spent, so if they are past what the new plan carries, that workspace cannot render again until the period rolls over. Nobody is removed from a workspace that drops below its headcount, but you cannot invite anybody new until it is back under the seats the new plan includes.
- If a payment fails. The service keeps running while we retry: a declined card is a payment problem, not a trust problem. The charge is retried a day after it fails, then three days after that, then five days after that: four attempts in all, spread across nine days. If every attempt fails, the workspace moves to the Free plan and its allowance moves with it. Nothing you have rendered is deleted, and the licence on audio you rendered while paying is not affected. We do not email you about any of this, because the product sends no billing mail at all: the state of a retry, the last error and the payment history are on the billing page, which is where to look.
- Account credit is money on the workspace that offsets the next invoice. It does not expire, it is not exchangeable for cash, it is not transferable between workspaces, and it is not seconds: a workspace with credit and no allowance left still cannot render. Promotional codes are limited to one redemption per code per person, and to one promotional code per workspace, ever. A workspace that has redeemed any code cannot redeem another, and the record of a redemption deliberately outlives both the workspace and the account.
- Tax. Prices are in US dollars and are exclusive of tax. The amount charged is the plan price as listed, with nothing added, because the service does not calculate a tax. Where a sales, use or similar tax is due on your purchase and we are not collecting it, accounting for it is yours to do. If we become required to collect one we will add it to the charge and tell you before the first charge that includes it.
- Refunds. There is no automatic refund and no self-serve refund path. A downgrade is not refunded, as above. If you were billed in error, or something went wrong that we should stand behind, write to support@workflowcorp.com and a person will decide; we can reverse a charge at the gateway when that is the right answer, and put back by hand any part of it that was settled from account credit. There is no cooling-off period, because US law does not give you one here and we are not inventing one. What you have instead is cancellation: you can stop the next renewal at any moment, from the console, without asking us, and you keep what you paid for until the period ends. If you are a consumer somewhere whose law does give you a withdrawal or refund right that cannot be contracted away, this paragraph does not take it away. Tell us and we will honour it.
Availability, and what we do not promise about it
We work to keep the service up and we do not offer a service level agreement on these plans. No plan carries an uptime commitment, a service credit or a support response time. Four specifics, because they are normal here and would look like faults anywhere else:
- The engine scales down when nobody is using it. A render that arrives while it is scaled down waits for the engine to start before it produces anything, which is why the product distinguishes “queued” from “rendering” rather than showing one spinner for both. We do not publish a figure for that wait: how many instances stay warm is a setting on the deployment rather than a property of the product, and a number here would be wrong the first time somebody changed it.
- We do not publish a render time and we do not commit to one. When we have measured it properly at every length we sell, we will say so.
- Plans list a concurrency figure, and we do not enforce it today. Nothing counts your in-flight renders and nothing refuses a render for being simultaneous, so that number is neither a cap we apply to you nor a throughput we promise you. Do not size a workflow around it in either direction. If we start enforcing it, that is a material change to a paid plan and gets the notice described below.
- Outbound email is worth knowing about before you rely on it. The service sends exactly two kinds of message, a workspace invitation and a password reset you asked for, and nothing else is emailed at all. Delivery goes through a third-party provider and we do not promise it: a message can be refused, delayed or filed as spam at the receiving end, and we will not know that it was. Where the send itself fails, the team screen hands you a copyable invitation link instead, so an invitation is never stuck behind the mail. A password reset gives you no such signal, because that page says the same thing whether or not the address belongs to an account, so if one does not turn up, ask us rather than assuming the account is gone.
Suspension, cancellation and closing an account
You can cancel a subscription at any time. Closing things down is self-serve and works at two levels: an owner deletes a whole workspace from workspace settings, and anybody closes their own account from account settings. Both are immediate and neither can be undone. Closing an account will not let you strand a workspace: if you are its last owner and other people are still in it, you have to make somebody else an owner first, because a workspace nobody owns cannot be billed, renamed or closed by anyone. What happens to your data then is set out in the privacy notice, and it is more specific than this clause. Export anything you want to keep first; we are not obliged to hold a copy for you. If something has gone wrong and you cannot reach either button, write to support@workflowcorp.com from the address on the account and we will do it.
We may suspend or close an account for a serious or repeated breach of these terms or the acceptable use policy, or where we are legally required to. Except where the breach makes it impossible, we will tell you first and give you a chance to put it right. A failed payment is not one of these: it is handled by the retry schedule above and ends in a move to the Free plan rather than a suspension. Suspension does not revoke the licence on audio you already rendered under a paid plan.
Warranties
The service is provided as it is. We do not warrant that it will be uninterrupted, that a particular render will please you, that the same request will produce the same audio twice (it will not, once the engine checkpoint changes), or that generated words and music will suit a purpose we know nothing about. Listen to the file before you air it. To the extent the law allows, all other warranties are excluded.
Limitation of liability
Neither of us is liable to the other for indirect or consequential loss, for lost profit, lost revenue, lost business or lost data, however it arises. Our total liability arising out of or connected with these terms, taken together across every claim, is limited to the greater of the fees you paid us in the twelve months before the claim arose, or USD 100.
That cap is small because the price is small: a workspace on the free plan has paid nothing, and the paid plans run from a few dollars a month upward. If what you are making carries risk out of proportion to what you pay us, a national campaign or a contract with penalties in it, the protection that fits is your own insurance and your own check of the audio before it airs, not a number in this document. We would rather tell you that than write a cap you would only discover was low at the moment you needed it.
Nothing here limits liability that cannot lawfully be limited, including for death or personal injury caused by negligence, or for fraud.
What you cover us for
You will cover us against claims arising from what you put into the service and what you did with what came out: an advertiser’s claim you asked to have sung, a must-say line you were given, a trademark or a set of call letters you were not entitled to use, or a broadcast that did not meet the rules that apply to your licence. You are the one who knows those things; we render what you ask for.
Changes to the service and to these terms
The product changes: features are added, and occasionally one is retired. Where a change materially reduces what you are paying for, or where these terms change materially, the new version goes up on this page with its new effective date at least 30 days before it takes effect, and you may cancel rather than accept it. A change that is not material, a clarification or a corrected cross-reference, takes effect when it is published.
Checking this page is the mechanism, and we would rather say so than promise a notification we have built no way to send. There is no announcement email, no mailing list and no policy banner in the product, so the date at the top of this page is the notice and it is the date that governs. Continuing to use the service after that date means you accept the new version.
Governing law and disputes
These terms are governed by the law of the State of Iowa, USA, without regard to its conflict-of-laws rules, and the state and federal courts located in Scott County, Iowa have exclusive jurisdiction over any dispute arising out of or relating to them. Each of us consents to personal jurisdiction there.
Iowa is simply where Workflow Corporation is, and Davenport is in Scott County. It is not a forum picked for its case law, and there is no reason for you to read it as one.
There is no mandatory arbitration clause and no class-action waiver in this agreement. We are not asking you to give up a court or a jury, and we would rather say that plainly than bury the opposite in a paragraph nobody finishes.
Before either of us files anything, tell the other side what is wrong. Write to support@workflowcorp.com with what happened and what you want, marked for the attention of the legal team; we will respond, and most of what reaches a filing could have been settled by somebody reading it first. If it is not resolved within 30 days of that message, either of us is free to go to court.
If you are a consumer resident somewhere whose law gives you the right to bring proceedings in your local courts, or applies consumer protections that cannot be contracted away, this clause does not take that away from you.
Contact
Everything reaches us at support@workflowcorp.com. A formal notice under this agreement, and anything else for the legal team, goes to the same address marked for their attention in the subject line, which is what routes it. There is one address on purpose: a legal@ or a notices@ that nobody watches is worse than a shared inbox that somebody reads, and a bounced notice under a contract helps neither of us.
Post reaches us at Workflow Corporation, 210 Emerson Pl, Suite 300, Davenport, IA 52801, USA, and the phone is +1 (563) 275-6409. Support is available at any hour, every day. The office is open Monday to Friday, 8:00 AM to 6:00 PM Central and closed at weekends, so anything needing a decision rather than an answer, a notice, a refund or an appeal, is dealt with on a business day.