Rivya Providers and Commercial Use — Review by Task
Compare what to check before using Rivya chat, image, video, voice or music results commercially, including source rights, provider terms and data handling.
Last reviewed on September 13, 2026
Before publishing an ad or handing work to a client, review the task you actually ran. This guide compares the services that may be involved and the checks that differ between text, images, video and audio. It does not certify any provider's licence or approve your project for publication.
Start with the model and the material
Record the model, tool, inputs and intended use. A public model page does not prove that generation is available; check model availability and the settings offered by the selected model. Provider involvement depends on the enabled feature and the request you submit, not every integration that appears in the product's code.
The model developer and the infrastructure service handling a request may be different parties. A model name alone does not identify every service involved or prove that the terms of a provider's separate consumer subscription apply to your use through Rivya. If a project depends on a specific licence, retention rule or restriction, establish the applicable terms before sending material.
What Rivya's ownership terms cover
Under the Terms of Service, you retain rights you already hold in submitted material. Between you and Rivya, and to the extent allowed by applicable law, you own outputs generated through your account; Rivya assigns any rights in those outputs that vest in it. You grant Rivya the limited rights needed to run the service.
That allocation does not grant rights to a third party's photograph, logo, voice, music or other source material. Outputs are not guaranteed to be unique, non-infringing, error-free or suitable for every commercial use without review. See commercial use and rights for the distinction between input permission, output ownership and permission to publish.
Review each type of task
| Task | Services that may be involved | Check before use or delivery |
|---|---|---|
| Account access and service email | Google when selected; the configured email service for relevant messages; GitHub or Discord only if offered and selected | Confirm who controls the account and mailbox and who should receive account, billing and security notices. |
| Payment and subscription management | Stripe for the payment or subscription action used | Check the purchase, billing details and your own accounting or approval requirements. Payment is not clearance for source assets or generated content. |
| Chat and tools that use a chat model | Rivya, the selected AI infrastructure and model provider | Check whether the input may leave your organisation. Verify factual claims and calculations before relying on the answer; a fluent response is not evidence. |
| Image generation and editing | Rivya and services used by the selected image model; supported references may be uploaded | Check source-image rights, people, logos, product shape, visible text and any features the image appears to promise. A reference does not guarantee an exact product match. |
| Video generation | Rivya and services used by the selected video model; supported image, video or audio inputs may be involved | Review source footage, voice and music permissions. Watch the whole clip for changes between frames, inaccurate product details and suitability for the intended channel. |
| Speech and dialogue | Rivya and services used by the available speech or dialogue model | Check script rights, permissions for any person's voice or identity involved, pronunciation, language and the full recording. Availability of a voice does not establish consent for every portrayal or endorsement. |
| Music, lyrics and generated sounds | Rivya and services used by the selected available audio model | Review lyrics and other source material, the applicable provider terms, intended distribution and client requirements. A generated track is not automatically cleared for every release or rights-registration system. |
| ElevenLabs Audio Isolation and Sound Effect V2 | These two Rivya models are currently paused | Their pages do not provide a runnable cleanup or sound-effect task. Suno Sounds is a separate generated-sound option; it does not clean an uploaded recording or inherit another provider's terms. |
Use audio workflows for the available speech and sound operations, and music workflows for music, lyrics and related actions. Check the actual model's fields instead of assuming that every tool accepts the same source files.
Review data before uploading
Supported reference files can reach external infrastructure during upload, before you start generation or send a chat message. Removing a reference from the form does not confirm deletion from the external service. Inspect the material before uploading, not only before clicking Generate.
The data-processing guide explains saved records, external services and deletion limits. The Privacy Policy supplies the applicable policy. Do not infer a universal no-training or zero-retention guarantee from the fact that a service processes data to fulfil your request.
Check file types and limits in references and uploads. Technical acceptance of a file is separate from permission to send it. If a summary can replace a confidential document, review the summary too: it may still reveal protected information.
Keep a record for the intended release
For client work, keep the model and settings used, source permissions, the relevant provider terms you checked, intended channels and the final approved asset. These are project records you maintain; this guide does not create an approval workflow in Rivya. Download the result you intend to deliver and distinguish it from later edits or alternative generations.
Use the commercial review checklist to review the finished asset. Recheck when you change the script, language, person depicted, source media, client or distribution channel. Approval for one version or use does not automatically cover another.