↓
Rivya AI Docs

Rivya Data Processing, Storage and Deletion

Learn what Rivya saves, when uploads reach external services, and what result expiry and account deletion mean for your data.

Last reviewed on November 5, 2026

Before you submit a prompt or upload a file, check what Rivya needs to run your request and which external services may receive it. This guide describes Rivya's behavior. The Privacy Policy and Terms of Service set out the applicable terms.

What does Rivya save?

Rivya may save the prompts, instructions and chat messages you submit, together with reference-file URLs and upload metadata, model and tool selections, generation settings, task status, output URLs and result details. Chat records can include messages, attachments and usage information. Records of credit reservations, settled usage and refunds are linked to the request.

These records help Rivya provide account access, generation, chat history, billing and support, and investigate errors or abuse. Technical information can include sessions, IP addresses, browser and device details, language preferences and security logs. Service and billing messages use the information needed to deliver them, as do newsletters when that feature is enabled.

Saved task or chat records do not mean every unfinished draft or setting is saved. An output URL in history is also different from a permanent copy of the file.

Which services may receive data?

The services involved depend on the feature you use and its enabled integrations. AI requests may pass through external AI infrastructure and the upstream model services selected for the request. A public model page does not mean the model is available to run or that it has received your data. Check model availability before planning a task.

Depending on the feature, data may also go to Stripe for checkout, subscriptions or payment management; the configured email service for authentication, account, support or newsletter messages; or the storage service handling an upload. Google is involved if you choose Google sign-in. Legacy GitHub or Discord sign-in applies only when it is offered and you select it. Hosting, security and monitoring services help operate Rivya. Analytics, captcha, affiliate and support integrations apply only when configured and active.

Stripe handles payment card details; Rivya does not store them directly. An optional integration's presence does not mean it handles every user or request. For a model's specific conditions, start with the provider and commercial-use table.

When is an uploaded file sent?

For supported models, reference files are sent through Rivya's upload endpoints to the external AI infrastructure used for the request. Uploading a reference is separate from starting generation or sending a chat message. Your file may therefore have reached an external service before you submit the request.

Review the file before uploading it. Removing a reference from the form does not confirm that a remote copy has been deleted. Avatar and other stored-file uploads use the storage service configured for that feature and may follow a different path from generation references.

Supported formats, sizes and reference counts vary by model. See references and uploads for the product limits. Acceptance of a file does not establish permission to use its contents.

Is there a no-training or no-retention guarantee?

Rivya's processing of data to provide the service does not establish a universal no-training or zero-retention guarantee. The Privacy Policy describes operational processing; it does not establish the same retention, review or secondary-use rules for every external provider.

If your project requires restrictions on training, review or retention, check the conditions for the services that will process your content before you send it. Resolve any unclear conditions first. Avoid sending sensitive personal information, confidential material or protected data unless you have assessed your requirements and can accept the external processing involved.

How do retention and account deletion work?

Rivya retains information for operational, billing, legal, security and support needs. For some successful media results, the application records a 14-day availability window. This does not guarantee that an external link will work for the full period or set a deletion deadline for prompts, billing records, backups or data held by providers. Follow output downloads to keep your own copies of files you need.

Deleting your account in Settings > Security generally removes account-linked records from Rivya's primary database through its deletion relationships. Limited records may remain for billing, fraud prevention, abuse handling, legal obligations, backups, security logs or provider-side processing. Account deletion does not mean immediate erasure across every service.

Review account settings before deleting your account, including how to manage a subscription. Deleting an account does not cancel subscription renewal. For a privacy request you cannot handle in settings, use Contact.

What should you check before sending content?

Identify personal, confidential, client-owned or third-party material before uploading. Send only what the task needs. A summary may let you avoid uploading an entire source file, but check the summary itself for sensitive details. Confirm both the right to upload and the right to use the result, as explained in ownership and commercial use.

Use the safe upload guidelines for practical checks. Reassess when you add real people, voices, unreleased product information or material that must stay within your organization. Permission to use a source, acceptance of the processing conditions and review of the finished result are separate decisions.