Privacy Policy

This Privacy Policy explains what data Miru Renderer handles, how it gets that data, what it uses it for and what options you have as a user.

This policy applies to the website, user accounts, OAuth sign-ins, renders, uploaded files, presets, skins, gifts and the optional paid plans offered by the service.

Miru Renderer is operated by Ricardo Misael Silva Lara from Ecuadorunder the Miru Renderer brand. If you have privacy questions, you can write to eie@miru.uno.

Miru Renderer may handle account data such as identifiers associated with osu!, Google or Discord, plus username, email address when the provider shares it, avatar, country, language, account role and basic access or creation dates.

It may also handle replays, beatmaps, mapsets, skins, presets, configuration data, render jobs, history, previews, generated videos and metadata related to those files or to the rendered beatmap.

In addition, it may handle limited subscription and gift data, along with authentication cookies, session state, basic operational logs and part of the frontend state stored in your browser.

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

If you choose to sign in with osu!, Google or Discord, we also receive the data each provider returns within the scope authorized by that flow.

The service uses session cookies and may persist local state in your browser. If you purchase a plan, Paddle may send the information required to create, update or cancel the subscription. When the product needs to resolve beatmap metadata, it may also query external search services.

We use information to create your account, sign you in, link providers and keep sessions active.

We also use it to receive files, prepare the job, run renders, generate videos, display history and serve temporary downloads or streaming when needed.

In addition, we use it to save presets, skins and settings, manage subscriptions and gifts, handle support, prevent abuse, investigate failures and keep the service running.

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

Uploaded and generated files may be stored through infrastructure compatible with Backblaze B2. The service also uses Redis for sessions, OAuth state, counters and queue support.

Payments and part of subscription management may pass through Paddle. The service may also send limited operational events to Discord when that integration is enabled.

When a replay or mapset needs external metadata, Miru Renderer may query osu.direct, catboy.best, mino.pl and the official osu! API.

Miru Renderer does not sell personal data and does not currently describe advertising or behavioral marketing use of your data for its own ads.

Miru Renderer uses authentication cookies such as accessToken and refreshToken to sign you in, renew the session and protect private routes.

These cookies serve a technical and operational purpose. This page does not currently declare marketing cookies or first-party advertising trackers.

The frontend may also store state in localStorage, for example to remember visible session state in the interface and certain local preset or skin data. That storage stays on your device until you delete it, the browser clears it or the app replaces it.

Miru Renderer may generate signed download or streaming links for rendered videos. In general, those links have limited validity and are created to allow temporary access to the file.

A link stopping working does not by itself mean the underlying file was deleted at that same moment. A link may expire before the data disappears from the system.

If you share a valid link, someone else may use it while it remains active. For that reason, you should not treat a temporary link as private once it leaves your control.

The service may also include links to external sites. The privacy practices of those sites are governed by their own policies.

We keep account data while the account remains active and for the reasonable time needed for technical, operational, security, support or legal compliance purposes.

Files, renders, videos, presets, skins, subscriptions, gifts and related logs are kept according to the actual needs of the service. Some download or streaming URLs may expire before the data they point to.

If you request account deletion, Miru Renderer may remove the main records managed by the service. This page does not promise immediate or simultaneous deletion across every cache, log, integration or technical backup.

You may request access, correction or deletion of data when applicable law allows or requires it. You may also contact us if you need to review inaccurate information or resolve a privacy question.

Miru Renderer does not currently offer a public data export portal. If you need to make a request, write to eie@miru.uno.

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

Miru Renderer applies reasonable authentication, access control and operational separation measures across service components.

Even so, no system offers absolute security or a total absence of incidents. For that reason, we cannot guarantee complete invulnerability.

Miru Renderer may update this policy if the product changes, if its integrations change or if its data handling practices change.

The current version will be the one published on this page with its update date.

If you have privacy questions, requests or complaints, you can write to eie@miru.uno.

Declared service operator: Ricardo Misael Silva Lara. Declared operating country: Ecuador.