Review privacy, rights, sensitive data, people, voice, brand assets, provider processing, and file necessity before uploading to Rivya.

Use this guide before uploading images, video, audio, product files, brand materials, or reference assets into a Rivya workflow.

Uploads can make Rivya workflows more useful, but files may include sensitive data, third-party rights, private people, confidential business material, or content that should not be sent to providers.

What To Review Before Uploading

Before uploading, check:

whether the file is yours to use
whether it contains private people
whether it includes confidential business data
whether there are visible addresses, IDs, emails, or account details
whether client approval is required
whether the upload is necessary for the task

If a file is not needed, do not upload it.

Upload Only Where It Helps

Uploads should support a specific workflow, not act as general storage.

Use uploads when a model or Studio can use the file as a reference, source material, or analysis input. Check the relevant workflow page before upload, because not every public page, model, or task supports files.

If the task can be solved with a written description, start there and add files only when they change the result.

Product And Brand Assets

Product and brand assets can be useful references.

Review:

logos
packaging
unreleased product details
client-owned images
campaign materials
licensed photography

Make sure the intended workflow is appropriate for the asset.

People And Voice

Be especially careful with files that include people or voices.

Consider:

consent
likeness rights
voice rights
private settings
minors
sensitive contexts

If you are not sure you have permission, do not use the file.

Sensitive Information

Avoid uploading files that include:

passwords
API keys
financial records
medical records
identity documents
private customer data
confidential contracts

If sensitive information is not required for the task, remove it first.

Safe Upload Checklist

Before a task depends on a file, reference, or provider handoff, check:

Check file type, size, source quality, and whether the workflow actually supports uploads.
Decide whether the file is a reference, a source to transform, or material for analysis.
Remove sensitive or unnecessary data before upload.
Check provider-processing expectations if the file leaves the browser as part of generation.
Keep the original file available until the generated result has been reviewed.

The goal is to make the input safe and useful before generation starts.

Common Upload Mistakes

Avoid uploading a file just because it is available.

Common mistakes include uploading a whole client folder instead of the one useful asset, sending raw recordings that need cleanup first, using brand assets without approval, or adding a reference file without saying what it should control.

If the file is too broad, simplify it before spending credits on a generation attempt.

When File Inputs Need Rework

Rework the input when the upload is too large, too noisy, too sensitive, unsupported by the chosen workflow, or unclear about what it should control.

In those cases, fix the file or choose a better workflow before spending credits on a generation attempt.

Rivya Safe Upload Guidelines