Copyright & third parties

Your content and permissions

You keep ownership of your music, recordings, images, settings, logs and other customer content. You are responsible for having the permissions, licences, consents and account rights needed for anything you stream, upload, route, message or share.

Use third-party tools lawfully

RigWave is for lawful, authorised and ethical use. It must not be used to bypass or defeat copyright controls, DRM, licence checks, payment controls, account permissions, authentication, security protections, rate limits, anti-abuse systems, consent requirements, geographic restrictions, moderation safeguards or platform rules.

If RigWave guidance ever conflicts with the current rules of a third-party product or service, the provider's own terms, licence and platform rules govern your use of that provider. Stop, check the provider's current instructions and use the safer route.

RigWave intellectual property

RigWave software, brand, artwork, source code and proprietary methods are protected intellectual property of RigWave Streaming Systems / Gary Woodward, subject to third-party and open-source rights that cannot lawfully be restricted.

Open-source software

RigWave uses or may distribute open-source components. A public release must preserve the licence notices, source availability, corresponding source, written offers or other rights required by the applicable licences. The RigWave EULA does not override open-source rights. OBS Studio and Audacity are examples of third-party GPL software referenced by RigWave; their own licences remain in force.

Names, marks and logos

Product names, company names, service marks, trademarks and logos belong to their respective owners. RigWave currently uses text names where needed to identify compatibility or explain a workflow. No third-party logo is reproduced on this page, and no endorsement, certification, sponsorship, agency or partnership is implied unless the relevant owner expressly confirms it.

Official provider links

Checked for this pre-release review on 5 September 2026. Providers can update their rules. The version currently published by the provider is the one to check before use.

Third-party services can change

A provider can change an integration, driver, app, API, policy, licence or service. RigWave cannot guarantee permanent compatibility with every future version. A major provider change may temporarily move a feature to compatibility under verification while it is retested.

Before you go live

• Check that your third-party apps and accounts are properly licensed and authorised.
• Check current platform bitrate, content, messaging and acceptable-use rules.
• Confirm you have the rights to the music, artwork, messages and other content you use.
• Never paste passwords, stream keys, secret API keys or recovery codes into RigWave support material unless an approved secure process specifically requires it.
• If a provider changes its rules, follow the provider's current rules first and report the compatibility issue to RigWave.

Back to Legal hub

Hardware/device identifiers are descriptive only. Current RigWave source can recognise names from DJ hardware, audio interfaces, capture devices, microphones and GPU vendors. Detection does not grant RigWave rights to vendor drivers, firmware, manuals, logos or product artwork.

Final public third-party notices, the software component list (SBOM), Go licence notices, OBS/libobs source-availability obligations and the final Genre Master/Nyquist licence decision remain final checks. This pre-release package records the boundary; it does not turn those items still to prove into PASS.

LIVE SHARE · MUST READ

Lawful, responsible sharing is a condition of use

Before Live Share or connected-chat controls unlock, RigWave presents separate required tick boxes for: account and destination authority; copyright and other content rights; privacy and recipient permission; no bullying, harassment or harmful misuse; third-party app rules; checking before sending; and end-user responsibility. The accepted wording version and time are stored on that PC so the same checklist is not repeated on every launch. A material change to the requirements triggers a fresh acknowledgement.

The acknowledgement is not another person’s consent, does not grant access to an account or destination, and does not prove delivery. The operator must already have any permission, consent or lawful basis required for each recipient, purpose and channel; must check the actual message, link, account, audience and recipient; and must honour STOP, blocking, objections and withdrawal.

Never use RigWave for bullying, harassment, stalking, threats, discrimination, doxxing, impersonation, deception, spam, fraud, unlawful surveillance or exploitation. Misuse can harm people and damage the RigWave brand. Police.uk online harassment and threatening-message help ↗ · Report Harmful Content ↗.

If WhatsApp, Messenger, Facebook or another third-party desktop/web app is used, install or open its official app, sign in and authorise there, approve only the permissions needed, protect credentials, and comply with its current terms, policies, recipient controls, templates, moderation, rate limits and charges. RigWave does not control or guarantee the service. WhatsApp official app-link guidance ↗. If a message is direct marketing, review the ICO electronic-mail marketing guidance ↗ before use.