Miruro RPC Privacy Policy

Last updated: November 4, 2026

Miruro RPC (“the extension”) is a browser add-on that shows your Miruro watching activity as Discord Rich Presence. This policy explains what information is handled and where it goes.

Summary

• We do not run an analytics service or sell your data.
• Discord OAuth access/refresh tokens (not your password; not a user account token) and preferences are stored locally in the browser.
• Watch/browse activity is sent only to Discord, to update your presence.
• The extension reads information from miruro.cx pages you open.

Data the extension uses

Discord account (authentication)

• When you tap Connect Discord, you sign in with Discord’s normal OAuth login (PKCE / public client). You never enter your Discord password into the extension itself.
• The extension stores Discord OAuth access and refresh tokens for this app only (scopes requested: openid and sdk.social_layer_presence), plus basic profile fields used to show that you are signed in (for example username / display name). These are not your Discord password and not a full Discord user “account token.”
• Those OAuth tokens are stored in the browser’s extension storage on your device and are used only to call Discord’s API: refresh the login and create/update/clear Rich Presence (headless sessions).
• Why Discord’s authorize screen may mention “relationships”: sdk.social_layer_presence is Discord’s Social SDK “default presence” umbrella scope. Discord bundles Rich Presence with related Social SDK capabilities (their docs list Friend System & Relationships alongside Presence). Miruro RPC does not read your friends list, send friend requests, block users, or otherwise manage relationships. We only use the authorized access to publish and clear your Miruro Rich Presence.

Miruro activity (website content / activity)

• On Miruro pages, the extension may read page content such as anime title, episode number, episode title, cover image URL, watch page URL, and playback position.
• That information is used to build your Discord Rich Presence (and optional “hide this anime” / presence on-off settings stored locally).

Presence session

• The extension creates or updates a Discord headless presence session so friends can see what you are watching or browsing.
• Clearing presence (for example leaving Miruro, turning presence off, or on Android minimizing Firefox) asks Discord to remove that session.

Where data is sent

• Discord (discord.com API) — OAuth token exchange and Rich Presence updates.
• OAuth callback page (https://d4rkov.github.io/miruro-rpc-oauth/) — used on Firefox for Android so Discord can redirect after login. The authorization code appears in the page URL briefly; the extension reads it locally to finish login. That page does not store your Discord password or tokens.

The extension does not send your Miruro activity or Discord OAuth tokens to a Miruro RPC backend or to the developer for analytics.

Data stored on your device

• Discord OAuth access token and OAuth refresh token for this extension (not your password; not a user account token)
• Signed-in Discord display info (e.g. username / global name) for the popup UI
• Presence preferences (enabled/disabled, muted anime titles)
• Temporary OAuth/PKCE values during login (code_verifier, state, redirect URI)
• Discord headless presence session token (used only to update or delete the Rich Presence session)

Disconnecting Discord in the extension removes stored auth data from extension storage (as far as the browser allows). Uninstalling the extension removes its local storage.

Permissions (why they exist)

• storage — save login and preferences on device
• identity / tabs — Discord login (desktop identity window; Android uses a tab + callback)
• alarms — keep presence reliable when the browser sleeps background scripts
• Host access to Miruro, Discord, and the OAuth callback host — required for the features above

Children

The extension is not directed at children. Use Discord and Miruro according to their own terms and age rules.

Third-party services

Discord’s and Miruro’s own privacy policies apply to their services. This policy only covers the Miruro RPC extension.

Changes

If this policy changes in a meaningful way, the “Last updated” date above will change. Continued use after an update means you accept the revised policy.

Contact

Questions about this policy: open an issue on the Miruro-RPC GitHub repository or contact the maintainer via that project.

Miruro RPC is not affiliated with Discord or Miruro.