Privacy policy

What this policy covers

This policy covers the Renderly website, workspace and API. Personal information includes information that identifies you or can reasonably be connected to you. Your prompts, uploads and results may contain personal information, including information about other people.

Read this policy alongside the Terms of service and Cookies policy. Websites you choose to open from Renderly have their own privacy practices.

Information used by the service

• Account information: email address, profile name, account identifier, sign-in records and account settings.
• Creation information: prompts, reference images, video and audio, selected model and settings, generated results, request identifiers, status and timestamps.
• Billing information: credit balances, reservations, usage charges, transaction identifiers and payment status. Payment card details are collected in hosted checkout rather than in the Renderly workspace.
• Technical information: network and browser information needed to deliver requests, diagnose failures, protect accounts and maintain service records.
• Communications: information you choose to send in a support, privacy, rights, security or safety report. A report prepared or copied on your device is not sent to Renderly merely by preparing it.

Why information is processed

We use information to authenticate accounts, run requested creations, deliver results, maintain your request history and balance, verify payments and help resolve service problems. We also use relevant records to prevent fraud and abuse, enforce service rules and meet legal obligations.

Where a legal basis is required, processing may be necessary to provide a service you request, meet a legal obligation or pursue a legitimate interest such as account security, subject to your rights. Processing that requires consent must have that consent.

The data protections applicable to a creation can vary with the model and feature. If your project requires specific confidentiality, training, retention or residency conditions, confirm those conditions before uploading the material.

Service processors and disclosures

Service processors may receive information needed for account authentication, hosting, computation, media handling, payment processing and service support. Processing a creation can require access to its prompt, reference media, selected settings and result. This policy describes those functions without changing your rights in the material.

Information may also be disclosed when you authorize a disclosure, when a valid legal requirement applies, to protect people or the service against serious abuse, or in a business transfer subject to applicable privacy protections. Access for support and safety purposes should be limited to the information relevant to the issue.

Processing may take place outside your country. Applicable requirements for international transfers, including any required contractual or other safeguards, depend on the transfer and jurisdiction. You can request information about the arrangements relevant to your use.

Storage, retention and security

Generated result files are kept for 7 days by default. You can choose a retention period from 1 hour to 30 days for your account or for an individual result. Uploaded input files are kept for 24 hours. When a retention period ends, the stored file is deleted and new download links can no longer be issued.

Account, request, ledger and transaction records are retained according to the needs of the service and applicable legal, accounting, security and dispute obligations. Deleting browser storage or allowing a download link to expire does not delete server records. Keep a copy of important results. Request deletion through the privacy contact options when you want server-held information reviewed for deletion.

Renderly does not use your prompts, uploads or results to train models. A model provider processes a request only to generate its result.

Private account records require authenticated access, and result files are delivered through signed download links that expire after 15 minutes. Protect your sign-in credentials and API keys, revoke unused keys and avoid sharing private download links. Security controls reduce risk but cannot eliminate every risk.

Your choices and privacy rights

You can update available profile settings, turn on two-factor authentication, revoke API keys and control browser storage. Settings → Security lets you download an export of your profile, preferences, API key and webhook details (without secrets), request history, balance ledger and payment records, and close your account. Closing revokes keys, turns off webhooks, deletes stored files and blocks sign-in; request, ledger and payment records are kept for the accounting and legal periods described above.

Depending on applicable law, you may have rights to access, correct, delete or receive personal information, restrict or object to processing, withdraw consent and complain to the relevant privacy authority. Mandatory privacy rights continue to apply even where a particular control is not available in the workspace.

Use the privacy contact options to prepare a request and provide enough information to identify your account and the requested action. Identity verification may be needed to protect your information. Do not include passwords, API keys, payment card details or unnecessary sensitive documents.

Adults only

Renderly is intended for people aged 18 or older who can enter into a binding agreement. If you believe a child has provided personal information or opened an account, use the privacy contact options. A safety concern involving a child can also be described through the content reporting page.

Changes and questions

The date above identifies this version. Updates should reflect changes to the service and its data practices. Where applicable law requires additional notice or consent for a change, those requirements apply.