Privacy Policy

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.

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 replay files, user-selected rendering materials, skins, presets, render configuration, render jobs, previews, rendered videos, output-access state, watch state and metadata related to those files or jobs. If you use the HUD editor, we may also process HUD projects, layer settings, text content, font selections, custom images, GIFs, rendered thumbnails, asset manifests and preview cache metadata.

We may process authentication cookies, session state, guest-render cookies, local browser state, render-node registration data, render-node 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.

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 metadata services related to user-authorized render materials.

If you make a purchase through Polar Checkout, Polar may collect billing, tax, payment, receipt, subscription, refund and dispute information as merchant of record and authorized reseller. Miru Renderer may receive limited transaction information needed to provision access, manage subscriptions, provide support, prevent abuse and respond to refunds or disputes.

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 access to rendered outputs.

We use HUD editor data to save overlay projects, validate asset ownership, prepare exact previews, normalize uploaded media, create thumbnails, pass renderable manifests to automated render nodes and render the final video output selected by the user.

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.

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

When an automated render node is assigned a job, it may receive the files and temporary access needed to complete that render, including the replay file, user-selected rendering materials, HUD configuration, HUD assets, render configuration and rendered output.

Authorized automated render nodes are bound to process assigned jobs only and are restricted from retaining, reusing, accessing beyond job requirements, publishing, selling or redistributing user files. They may only access temporary job data required to complete the automated render workflow.

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

Uploaded files and rendered outputs 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 dispute-related flows may be handled by Polar Software, Inc. as merchant of record and authorized reseller.

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

Curated HUD fonts are self-hosted from the Miru Renderer deployment using open-source font packages. The HUD font catalog is not intended to load fonts from the Google Fonts CDN at runtime.

When a replay requires external metadata, Miru Renderer may query official APIs or configured metadata services needed to identify user-authorized render materials.

Miru Renderer is intended for authorized rendering workflows only. Do not upload content without rights, copyrighted audio or artwork without permission, malware, exploits, illegal content, fraudulent content, adult content, personal data of others without permission, or materials intended to support cheating, hacks, boosting, rule evasion or unauthorized access to another service.

Miru Renderer is not a marketplace and may not be used to sell third-party content, third-party services or customer data.

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.

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 customer files, uploaded assets, replay data, render data or personal data. Miru Renderer does not state that it shares personal data for third-party behavioral advertising.

Miru Renderer may create signed access links for rendered videos. Those links may be temporary and may stop working before the underlying file is deleted.

Access to outputs may depend on authentication, session state, signed-link validity, storage state and infrastructure availability.

The service may also link to external websites. Their privacy practices are governed by their own policies.

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 output-access functions can work.

Saved HUD projects, uploaded HUD assets and related thumbnails may be kept while your account needs them for presets, previews, render history, support, abuse prevention or paid-feature access. You can contact us to request deletion when those assets are no longer needed.

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

Transaction, tax and billing records may also be retained by Polar according to its merchant of record, reseller, tax, payment-network and legal obligations.

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.

Miru Renderer is not directed to children or minors. You must be at least 18 years old, or the age of majority in your jurisdiction if higher, to create an account, purchase paid access or use paid features.

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.

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.

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.