Safe Uploads in Rivya: Privacy and File Preparation
Prepare reference files for Rivya, remove unnecessary private information, check permission and model support, and understand what uploading or removing a file does.
Last reviewed on September 9, 2026
Prepare a copy containing only what the task needs before you upload it. A reference upload leaves your browser and passes through Rivya to the third-party AI infrastructure used for that workflow. You do not need to start a generation for that file transfer to happen.
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
First confirm the selected model is currently runnable and accepts the file for your chosen operation. A visible model page is not proof of availability. Check type, size, count, dimensions, and duration in reference files and upload limits; do not assume every image, video, audio, or chat model accepts the same inputs.
If a short description is enough, start with that. For a reference-based task, choose the one asset or small set of assets that actually guides the result. Upload is not a general file archive. 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; do not upload a whole folder just because it is available |
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
Signing in gives access to supported uploads; it does not make processing browser-only. See data and provider processing for the distinction between Rivya records and third-party processing. Do not infer a universal no-training or zero-retention guarantee from this upload guide. If your work depends on such a condition, clarify the specific processing requirements before sharing the material.
Removing a reference thumbnail from the form removes it from the current 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, wait for upload completion, and check the displayed files and their roles. 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.
Do not upload a recording expecting an unavailable cleanup feature to fix it: ElevenLabs Audio Isolation is paused, and Suno Sounds creates new sounds rather than cleaning your recording. See audio uploads before preparing audio input.
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. Provide the model name, approximate upload time, a brief description of the issue, and the task identifier if one exists; an upload alone may not have a task identifier. Do not include passwords, API keys, verification codes, or another copy of the sensitive material in the initial message. Explain what help you need without creating another unnecessary disclosure.