ReelMuse Chrome Extension — Privacy Policy

Last updated: May 1, 2026

1. Overview

This document describes the privacy practices of the ReelMuse Chrome browser extension (the "Extension"). The Extension is a companion to reelmuse.ai and is operated by ReelMuse ("we", "us"). The Extension's use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

For our website privacy policy, see reelmuse.ai/privacy.

2. Single purpose

The Extension exists for one purpose: to capture an image element from any web page and remix it into a new image or animated video using the ReelMuse AI generation API. All features, permissions, and data accesses serve this purpose.

3. What data the Extension collects

3.1 Account identity (only via Google sign-in)

When you click Sign in with Google, the Extension uses chrome.identity.getAuthToken to obtain a Google OAuth access token, then asks Google for your basic profile (email, name, and profile picture URL). This is forwarded once to the ReelMuse backend to look up or create your ReelMuse account, after which only your ReelMuse account JWT is retained.

3.2 Authentication token

The Extension stores your ReelMuse account JWT in chrome.storage.local so you stay signed in across browser sessions. The JWT is sent only to api.reelmuse.ai on requests you initiate.

3.3 Picked image elements

When you explicitly click Pick element on page (or use the right-click context menu on an image), the Extension captures that single element — either as the source image bytes or as a cropped screenshot of its bounding box. The captured image is uploaded to your private ReelMuse library and used as the input to whichever AI effect you trigger.

The Extension does not read, scan, or transmit any other page content. It does not track which sites you visit, your scroll position, your clicks, or the surrounding HTML.

3.4 One-time onboarding state

A boolean flag is written to chrome.storage.local so the onboarding card stops appearing after you dismiss it. No identifying information.

4. What the Extension does NOT collect

  • Browsing history or visited URLs (beyond the page URL of an image you explicitly pick).
  • Form input or keystrokes.
  • Cookies from third-party sites.
  • Mouse movement, scroll, or click telemetry.
  • Page HTML, scripts, or DOM contents.
  • Any data when you are not actively using the Extension.

5. How data is used

  • Account identity — to authenticate you with your ReelMuse account and display your name + credit balance inside the Extension.
  • JWT — to authorize requests to api.reelmuse.ai.
  • Picked images — stored in your private library and submitted as the input to the AI model you select. They are not used for training and are not shared with third parties beyond the model providers ReelMuse uses to fulfill your generation request.

6. Third-party services

To fulfill a generation request, your picked image and prompt are forwarded to the AI model provider you select. As of the date above, this can include: Google (Nano Banana / Gemini Image), Alibaba (Qwen Image Edit), Pixverse, Kling, Seedance, and other providers listed in the in-app model picker. Each provider's data practices are governed by their own privacy policies.

The Extension does not contain any third-party analytics, advertising, or tracking SDKs.

7. Data retention and deletion

Local storage data (JWT, last-picked image reference, onboarding flag) lives in your browser's Chrome profile. You can clear it at any time by signing out from the Extension, removing the Extension, or clearing the extension's site data from chrome://settings.

Picked images and generations stored in your ReelMuse account can be deleted at any time from reelmuse.ai/libraries. To delete your entire account, email support@reelmuse.ai.

8. Permissions explained

  • sidePanel — render the Remix interface in Chrome's side panel.
  • storage — persist your JWT and onboarding flag locally.
  • identity — sign you in via Google OAuth.
  • contextMenus — add the "Remix with ReelMuse" entry to the right-click menu on images.
  • activeTab + scripting + broad host permissions (http://*/*, https://*/*) — inject the element-picker overlay onto whichever tab you are looking at only after you explicitly click the picker button. The overlay is never injected proactively.
  • https://api.reelmuse.ai/* — call our generation, library, and auth APIs.
  • https://www.reelmuse.ai/* — reuse your existing session if you are already signed in on the website.
  • https://accounts.google.com/* — fallback OAuth flow when chrome.identity is unavailable.

9. Children's privacy

The Extension and ReelMuse are not directed to children under 13. We do not knowingly collect Personal Data from children.

10. Changes to this policy

We may update this policy as the Extension evolves. Material changes will be reflected by updating the "Last updated" date above and, where appropriate, by an in-Extension notice.

11. Contact

Questions or requests: support@reelmuse.ai.