Sign in

Privacy

Privacy Policy

Last updated: April 20, 2026

Back to Miru

1. Introduction

This Privacy Policy explains what information Miru Renderer processes, how we obtain it, how we use it and what choices you have.

This policy applies to the website, user accounts, guest rendering, uploads, saved presets, skins, rendered outputs, optional paid plans, one-time digital purchases and related support or billing flows.

Miru Renderer is operated from Ecuador under the Miru Renderer brand. Privacy questions can be sent to eie@miru.uno.

2. What information we process

We may process account data such as provider identifiers, username, email address when available, avatar, country, language, account role and basic account timestamps.

We may also process replays, beatmaps, mapsets, skins, presets, render configuration, render jobs, previews, rendered videos, download state, watch state and metadata related to those files or jobs.

We may process authentication cookies, session state, guest-render cookies, local browser state, worker registration data, worker tokens or token state, support messages and basic operational or security logs.

If you make a purchase, we may also receive limited commercial information such as product, subscription, order, gift, renewal, refund or dispute status.

3. How we collect information

We receive information directly from you when you create or use an account, connect login providers, upload files, save presets or skins, start a render, redeem a gift, add billing details or contact support.

If you sign in with osu!, Google or Discord, we also receive the information those providers return within the scope authorized by that login flow.

We collect technical information from your browser and device through cookies, session state and normal request handling. When a replay requires external metadata, we may also query external services related to beatmap lookups or downloads.

When you make a purchase, Lemon Squeezy may collect billing and transaction details directly as merchant of record and then share back the purchase information needed to provision access, reconcile the order, provide support and handle refunds or disputes.

4. How we use information

We use information to create accounts, authenticate users, keep sessions active and connect third-party providers.

We use uploaded data to prepare jobs, process renders, deliver outputs, show render history and provide temporary watch, stream or download functionality.

We also use information to save presets, manage gift or subscription access, provide support, investigate failures, prevent abuse, keep the service secure and operate the platform.

If you use paid features, we use the relevant transaction data to activate access, manage renewals, handle billing questions and respond to refunds, disputes or fraud checks.

5. Render workers and file processing

Miru Renderer may process render jobs on Miru-operated infrastructure and on authorized contributor render workers connected to the service.

When a worker is assigned a job, it may receive the files and temporary access needed to complete that render, including the replay, beatmap or mapset, selected skin, render configuration and rendered output.

Contributor workers are expected to process only assigned jobs and not retain, reuse, disclose or alter user files outside the render workflow.

6. Third-party services

Miru Renderer uses third-party services for specific product functions. These may include osu!, Google and Discord for authentication and account linking.

Uploaded and generated files may be stored through the S3-compatible object storage configured for the deployment. The service may also use Redis for sessions, temporary state, queue support and abuse controls.

Payment processing, tax handling, receipts, billing details, certain subscription-management tools and some dispute-related flows may be handled by Lemon Squeezy as merchant of record.

Transactional email, verification messages, purchase notices, gift delivery messages and support mail may be sent through Resend or another configured email provider.

When a replay or mapset requires external metadata, Miru Renderer may query the official osu! API or configured beatmap providers such as catboy.best, osu.direct, api.nerinyan.moe and api.rai.moe.

7. Cookies, sessions and local storage

Miru Renderer uses technical cookies and similar session mechanisms to sign you in, refresh sessions, protect private routes and associate temporary guest renders with the same browser when needed.

The frontend may also store limited state in your browser, including local interface preferences and some temporary render-related state.

This policy does not declare first-party advertising trackers or third-party behavioral advertising based on your Miru Renderer usage.

8. How information may be shared

We share information with service providers and infrastructure providers only as needed to run Miru Renderer, deliver purchases, store files, send emails, process payments, investigate abuse or comply with legal obligations.

We may disclose information when required by law, to enforce our terms, to protect the security of the service or to respond to fraud, chargebacks or other payment-related disputes.

Miru Renderer does not sell personal data and does not state that it shares personal data for third-party behavioral advertising.

10. Retention and deletion

We keep account and service data for as long as needed to operate the service and for reasonable periods needed for support, security, accounting, fraud prevention or legal compliance.

Input files are intended to be removed when they are no longer needed for the related job. Output videos may remain available for a limited period so history, watch and download functions can work.

Cleanup is not always instant across caches, logs, storage providers, backups or signed URLs.

Transaction, tax and billing records may also be retained by Lemon Squeezy according to its merchant of record and legal obligations.

11. Your rights and choices

Depending on applicable law, you may have rights to request access to, correction of or deletion of personal information, and in some cases to object to or restrict certain processing.

Miru Renderer does not currently provide a public self-service privacy portal. Requests can be sent to eie@miru.uno.

12. Children

Miru Renderer is not directed to children under 13 years old. If your jurisdiction requires a higher minimum age or additional consent, you must satisfy that requirement before using the service.

13. Security

Miru Renderer applies reasonable technical and operational measures designed to protect account data, sessions and service components.

No service can guarantee absolute security, so we cannot promise that incidents will never occur.

14. Changes to this policy

Miru Renderer may update this policy when the product, infrastructure, integrations or data-handling practices change.

The version currently in force is the one published on this page with its update date.

15. Contact

Privacy-related questions, requests or complaints can be sent to eie@miru.uno.

If you need formal operator details for a valid legal or privacy request, contact us at that address.