Acceptable use policy

This policy is part of the terms of service and it binds everybody who touches a workspace: the owner, every member invited into it, and anything calling the API with a key minted from it. A key acts for the whole workspace, so what it does is the workspace’s responsibility.

• Anything sexual involving a child, in a lyric, a title, a brief or an upload. There is no warning step for this one: the account is closed and the matter is reported.
• Content that harasses, threatens or incites violence against a person or a group, or that demeans people for who they are.
• Advertising you know to be false. A sung offer is still an offer. If the client has not stood behind the claim, do not have it sung.
• Anything designed to deceive about who is speaking or who paid. A spot that pretends to be a news item, an endorsement nobody gave, or a message from a public body.
• Content that breaks the law where it will be heard, including the advertising rules for regulated categories: alcohol, gambling, medicines, financial products, political messages. Those rules are stricter on air than anywhere else, and they follow the broadcast rather than the render.

The engine has no voice cloning in it, and this is not a limitation we are working around. A persona here is a saved style recipe, not a likeness, and there is no speaker model that could reproduce a particular singer. What the policy adds is that you must not try to obtain one anyway.

• Do not ask for audio “in the voice of” a named person, and do not use a person’s name as a style instruction to get close to their sound.
• Do not present a render as the performance, endorsement or work of a real artist, presenter or public figure.
• Do not upload a commercial recording as a reference in order to have something like it produced.
• Do not build imaging around another broadcaster’s call letters, dial position or positioning slogan. Yours is yours; theirs is a trademark complaint waiting to happen.

We render what you ask for. What goes out on a licensed signal is governed by rules that apply to you, not to us, and two of them come up often enough in imaging to be worth naming.

• Emergency alert tones, and anything meant to sound like one. Do not ask for them and do not build them into a sweeper or a news bed. Broadcast regulators in most countries prohibit transmitting an alert tone, or a simulation of one, outside a real alert or an authorised test, and a promo that imitates one puts a licence at risk.
• Sponsorship identification. If a piece of content is paid for, the obligation to say so on air is yours, and a jingle is not an exemption from it.

What is not permitted is reselling the engine itself:

• Do not offer a service that lets other people generate audio through your workspace, whether by proxying their prompts through your API key or by wrapping it in a product of your own.
• Do not share a key outside your workspace, and do not use one workspace to serve another business’s customers.
• Do not use the output as training data for a music model, or scrape the product to build one.

The distinction is finished work versus raw capacity. Deliver the jingle, keep the engine.

• Do not create accounts or workspaces to collect more free allowance, and do not spread work across workspaces for the same reason. The free plan is there so you can hear what the engine does with your call letters, not so a station group can render a season of imaging one workspace at a time.
• Do not do the same with promotional codes. A code can be redeemed once per person, and a workspace can redeem one promotional code in its lifetime, whichever code it is. The record of a redemption outlives the workspace precisely so that deleting one does not reset the count.
• Retry politely. A render can outlast a client’s timeout, so send the idempotency header and let a retry return the work the first attempt started, rather than hammering the endpoint and paying for the same job twice.
• Do not use the API to probe capacity, to benchmark us for a third party, or to queue work you have no intention of using.

• Do not attempt to reach another workspace’s content, keys, briefs or audio, and do not test for a way to. If you find one, tell us.
• Do not interfere with the service: no denial of service, no attempt to circumvent authentication, metering or the allowance gate, no reverse engineering of the engine or its interfaces.
• Report a vulnerability to support@workflowcorp.com with “security” in the subject line, which is what routes it. Report it before you publish it, and do not use somebody else’s data to demonstrate it. We acknowledge a report within two business days, business days being Monday to Friday, 8:00 AM to 6:00 PM Central. We do not pursue people who tell us in good faith and give us time to fix it. There is no bug bounty, and we would rather say so than have you assume one: if you need paying for the work, agree it with us before you start.

Worth knowing how this works, because it puts the responsibility where it actually sits: nothing screens a brief or a lyric before it renders. There is no moderation model and no keyword filter between what you type and the engine, so we find out about a breach when somebody tells us. The rules above are not a formality; they are most of what stands between this tool and a misuse of it.

In most cases we ask first. A brief that steps over the line usually got there by accident, and a warning with the offending line quoted back is more useful to everybody than a suspension.

Where that is not enough we can remove a track, reduce what a member is allowed to do, suspend a workspace or close an account. For the first item in the list above, and for anything with an immediate legal or safety consequence, we act first and explain afterwards.

Appeals. If you think we got a decision wrong, write to support@workflowcorp.com within 30 days of it, marked for the attention of the appeals team. Name the workspace and the decision and include whatever we did not have in front of us. A person will look at it again. Two things worth knowing before you start: a suspension normally stays in place while an appeal is open, and deletion is not reversible, so an appeal we uphold can restore your access but not a track that was already deleted.

Audio you rendered legitimately under a paid plan stays licensed to you even if your account is later closed. Enforcement is about what happens next, not about pulling a client’s spot off the air.

Acceptable use reports go to support@workflowcorp.com, marked for the attention of the abuse team, from any address, with or without an account. Tell us what you can: a link or a file, when you came across it, and how you are connected to it. Rights complaints, including copyright and trademark, are handled under the content and rights policy, which sets out what a notice needs to contain. Ordinary support questions go to the same address with nothing marked on them and get a faster answer there.

There is one published address on purpose. An abuse alias nobody has created bounces, and a bounced report about content made here is the worst failure this page could have; a shared inbox somebody reads beats a dedicated one nobody watches.

This policy is published by Workflow Corporation and forms part of the terms of service.