Rivya Provider and Commercial-Use Matrix
Review Rivya workflows by provider touchpoints, ownership framing, data sensitivity, upload rights, and pre-publication commercial checks.
Last reviewed on 2026/08/29
Use this provider and commercial-use matrix when you need a workflow-by-workflow view before publishing, client delivery, or internal approval.
This page reviews provider touchpoints, ownership framing, data sensitivity, upload rights, and pre-publication checks in Rivya. A provider category applies only when the related feature is enabled or the selected runnable workflow uses it.
It exists because "commercial use is supported" and "every workflow carries the same release risk" are not the same statement.
What This Page Is For
This matrix helps when the real question is not just:
can I generate this here?
but also:
which providers actually apply to the enabled feature or selected runnable workflow?
what does Rivya say about ownership here?
what do I still need to review before I publish, deliver, or bill a client?
This is a review matrix, not a warranty matrix.
The Working Rule Behind Commercial Use
Rivya's current public language is consistent on the main point:
you retain rights you already hold in prompts, uploads, and other submitted material
outputs generated through your account are yours as between you and Rivya, to the extent permitted by applicable law
Rivya needs limited rights to operate the service
release-readiness still depends on your input rights, provider terms, and applicable law
So the useful reading is: commercial workflows are supported, but human review and rights review are still part of the job.
Provider And Workflow Review Matrix
| Area | Typical provider touchpoints | What Rivya is telling you today | What you still need to review |
|---|---|---|---|
| Account, sign-in, and service email | Google and the configured email delivery provider when those methods are used; GitHub or Discord only when the legacy method is enabled and selected | account access and product email can involve the specific third-party service used for that action | who controls the account, which mailbox receives notices, and whether the right people can access billing and security events |
| Billing and checkout | Stripe when a billing, checkout, subscription, or payment-management flow is used | payment-related records are handled through the enabled Stripe-connected flow | your own accounting, tax, approval, and billing-contact requirements |
| Chat and live tools | Rivya and the AI infrastructure selected for the runnable model or tool used | prompts, session history, usage records, and tool runs may be stored and processed to operate the selected service | whether the prompt contains confidential, regulated, or business-sensitive material |
| Image generation | Rivya and the image infrastructure selected for the runnable model used | outputs follow Rivya's ownership framing, and supported uploads plus task history may be part of the workflow | rights in source assets, logos, likenesses, brand references, and the final visual review before publishing |
| Video generation | Rivya and the video infrastructure selected for the runnable model used | the same ownership framing applies, and async task handling plus supported uploads may be part of the selected flow | footage rights, voice or music rights, platform ad rules, and whether the final cut is safe to ship |
| Voice and dialogue | Rivya and the audio infrastructure selected for the currently available voice or dialogue model | commercial review still depends on provider terms, script rights, voice rights, and the final output | script rights, voice or likeness permissions, localization review, and final listening review |
| Music and generated sound | Rivya and the audio infrastructure selected for the currently available music or sound model | current runnable music and sound paths remain subject to provider terms and output review | lyrics rights, source-material rights, distribution rules, and any client clearance required before release |
| Audio cleanup and dedicated sound effects | no runnable Rivya workflow while Audio Isolation and ElevenLabs Sound Effect V2 are paused | their public pages are status references and cannot start tasks or consume credits | use an approved external process if the work cannot wait, and review that provider separately |
The Questions To Ask Before You Ship
do you have the rights to every upload, source file, logo, likeness, or brand element in the workflow?
does the workflow involve a provider whose terms you should review separately before client or public use?
is the output accurate, safe, and editorially ready enough for the context where it will be used?
are you accidentally sending confidential, personal, or regulated information into a workflow that should stay cleaner?
if the work is commercial, has a human reviewed the final asset before distribution?
What This Page Does Not Replace
This page does not replace:
the exact model page you plan to use
your own legal, compliance, or client-side review process
Where To Check The Exact Product Boundary
use Current Live Features in Rivya when you need the strict scope page
use Choosing Models in Rivya when you need the inventory view
use Model Fields and Parameters in Rivya when you need to understand the exact run shape
use References and Uploads in Rivya when uploaded files are part of the job
Read Next
Commercial Review Checklist
Use this matrix before treating an output as client-ready or public-ready:
Identify the enabled workflow and the provider touchpoints that actually handled the prompt, supported upload, or output.
Check whether uploaded references, voices, people, brands, and source files were authorized.
Review the output for product accuracy, claims, logos, people, text, and channel-specific restrictions.
Separate Rivya's product behavior from your own rights, contracts, and platform obligations.
Keep records for high-value client work before publishing or handing off.
Recheck Before Commercial Handoff
Recheck when the output will be used in paid ads, client delivery, ecommerce listings, voice work, real-person likeness, regulated industries, or any context where rights and claims matter more than speed.
Rivya Data and Provider Processing Guide
Understand what Rivya stores, when providers may process prompts, uploads, outputs, and metadata, and how to handle sensitive data.
Rivya Commercial Review Checklist
Review Rivya AI assets before publishing or client delivery: accuracy, claims, rights, uploads, logos, likeness, brand fit, and approval.