Review Rivya workflows by provider touchpoints, ownership framing, data sensitivity, upload rights, and pre-publication commercial checks.

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.

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:

what providers are likely touching this 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, GitHub, Discord, Resend, and other deployment-level providers when enabled	account access and product email can involve third-party services	who controls the account, which mailbox receives notices, and whether the right people can access billing and security events
Billing and checkout	Stripe and related billing flows	plans, packs, checkout, subscriptions, and invoice-linked records are handled through Stripe-connected flows	your own accounting, tax, approval, and billing-contact requirements
Chat and live tools	Rivya, third-party AI infrastructure, and the upstream chat or reasoning providers selected for the workflow	prompts, session history, usage records, and tool runs may be stored and processed to operate the service	whether the prompt contains confidential, regulated, or business-sensitive material
Image generation	Rivya, third-party AI infrastructure, and the selected image providers behind the run	outputs follow Rivya's ownership framing, and uploads plus task history are part of the workflow	rights in source assets, logos, likenesses, brand references, and the final visual review before publishing
Video generation	Rivya, third-party AI infrastructure, and the selected video providers behind the run	the same ownership framing applies, and async task handling plus uploads are part of the normal flow	footage rights, voice or music rights, platform ad rules, and whether the final cut is safe to ship
Voice, dialogue, and audio cleanup	Rivya, third-party AI infrastructure, and the selected audio providers behind the run	commercial workflows are supported, but provider terms and uploaded audio still matter	script rights, voice rights, localization review, and whether the uploaded audio is yours to use
Music and sound generation	Rivya, third-party AI infrastructure, and the selected music or sound providers behind the run	the current music branch and sound-generation paths are live, but still sit inside the same review model	lyrics rights, source-material rights, distribution rules, and any client clearance required before release

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
Ownership and Commercial Use in Rivya
Data and Provider Processing in Rivya
Terms of Service
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

Commercial Review Checklist

Use this matrix before treating an output as client-ready or public-ready:

Identify the workflow and provider touchpoints that touched the prompt, 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 Provider and Commercial-Use Matrix