Safe Uploads in Rivya: Privacy and File Preparation
Prepare reference files for Rivya with only the information the task needs. Check permissions, model inputs, processing conditions, and what file removal means.
Last reviewed on November 5, 2026
Review a separate copy containing only what the task needs before you upload it. Uploading a supported reference sends the file through Rivya to the external AI infrastructure for that workflow, even if you do not start generation.
This guide explains practical preparation. The Privacy Policy and Terms of Service contain the applicable policy and service terms.
Check That the File Is Needed and Supported
Before choosing a file, confirm that the selected model is currently runnable and accepts it for your chosen operation. A visible model page is not proof of availability. Check file type, size, count, dimensions, aspect ratio, duration, and allowed combinations in reference files and upload limits. These requirements depend on the selected model and operation; some operations take text only.
If a short description will do, use it and check it for private details too. For a reference-based task, choose only the assets needed to guide the result. Keep your file archive locally. For device and format issues, see browser and file requirements.
Prepare a Separate Copy
| Material | Preparation before upload |
|---|---|
| Product or brand photo | Crop out shipping labels, addresses, unreleased details, or unrelated client material; retain only what the task needs |
| Screenshot | Remove passwords, API keys, verification codes, account identifiers, private messages, and unrelated open tabs |
| Image or video with people | Check permission for the intended use and remove unrelated bystanders or private surroundings where possible |
| Recording | Check permission to use the voice and content; trim unrelated speech locally and confirm the chosen operation accepts audio |
| Customer or business material | Use a redacted copy or a non-sensitive example when it can serve the task; leave out unrelated files from the same folder |
Use your local editor to make the changes, export a separate file, then open that exported copy to check it. Make sure removed information is absent from the actual file you select, not merely hidden in an editing preview. Review the filename and any metadata you intend to share as well. Keep the original locally.
Check People, Voices, and Brand Permissions
Owning a copy of a file does not by itself establish permission for every use. Check client approval, licensed photography, logos, likenesses, voices, and the intended publication context before uploading. Be particularly careful with minors, private settings, and sensitive personal information. If permission is unclear, use a different asset or resolve it before upload.
A paid plan does not replace these checks. Review ownership and commercial use for Rivya's stated terms and use the commercial review checklist before publishing a result. A successful generation is not proof that the result is accurate or cleared for your use.
Understand Processing and Removal
Sign in before using a supported upload form; the file still leaves your browser. See data and provider processing for the distinction between Rivya records and third-party processing. This guide does not establish a universal no-training or zero-retention guarantee. If your project needs either condition, confirm it for the actual processing path before uploading.
Removing a reference thumbnail takes it out of the current form selection. It is not confirmation that a previously uploaded copy has been deleted from third-party storage. Closing the page or deciding not to generate also does not undo a completed upload. Retention and deletion are covered in the Privacy Policy; this guide does not promise immediate deletion across every system.
Upload the Reviewed Copy and Check the Result
Open the supported model form and sign in before uploading. Preserve any unsent text as described in the login and draft guide.
Select the prepared copy and wait for upload completion. Check the displayed files and the role each should play in the task. If the form has a prompt field, use it to explain what each reference should control. Uploading alone does not start generation.
Check settings and estimated credits, then submit once. Inspect the output for unintended private details, incorrect text, distorted logos, or unwanted people before sharing it. Download results you need and keep your original files locally.
ElevenLabs Audio Isolation is currently paused. Suno Sounds creates new audio from text; it does not clean up an uploaded recording. Read audio uploads to choose a supported operation before preparing a recording.
If You Uploaded the Wrong File
Stop before starting another task. Remove the file from the current form to avoid reusing it, but do not treat that action as a deletion receipt. Avoid uploading it again or posting its access link publicly.
Use Contact for a privacy or support request. Include the model name, approximate upload time, a brief description of the issue, and the task identifier if one exists. An upload problem can happen before a task identifier exists. Keep passwords, API keys, verification codes, and the sensitive file itself out of the initial message. Describe the help you need without sending more private material.
