Privacy Policy | Muse AI Companion

1. Who we are / controller

Publisher / operator: Fitz.apps / FitzTools
Privacy & support contact: egor.besarabm@gmail.com
Website: https://getmuseai.app

For questions about this Policy, data access, deletion requests, or privacy complaints, email us at the address above. We aim to respond within a reasonable period.

By using the Site or installing Muse, you acknowledge this Policy. If you do not agree, please do not use the Site or the Extension.

2. Scope

This Policy applies to information processed when you:

visit or browse the Site;
install, enable, or use Muse AI Companion;
subscribe to, restore, or manage a Muse subscription;
contact us by email;
interact with Muse's listings on the Chrome Web Store, Microsoft Edge Add-ons, or Firefox Add-ons.

This Policy does not control how Google, Microsoft, or Mozilla process data as operators of their browsers, extension stores, or accounts. Their own policies apply separately.

3. Information we collect

3.1 Information you provide

Email and message content when you contact us (for example, support requests).
Content you choose to save locally inside Muse, such as notes, saved pages, and preferences.
The email address you enter when you ask to restore a purchase (see 3.4).

3.2 Information collected automatically on the Site

The Site is a static marketing site. We do not require accounts or logins on getmuseai.app. Standard web technologies and service providers may process:

Technical / server logs (for example IP address, date/time, requested URL, user-agent, referrer) through our hosting and CDN/DNS providers.
Language preference stored in your browser via localStorage, so the Site can remember the language you selected.

The Site does not currently load analytics or advertising pixels. If that changes, we will update this Policy first.

3.3 Information processed by Muse

Muse AI Companion is a side-panel companion that answers questions about the webpage you are looking at, drafts emails you ask it to write, and generates images from a prompt you submit. Muse only accesses data needed to provide the feature you request. Permissions are declared on each store listing and shown by your browser at install/update time. It processes the following:

Settings and on-device history (local). Theme, language, response style, page-context toggles, onboarding state, a single daily free-tier AI request counter (shared across chat, summaries, YouTube, email assist, and images), recent conversation titles and messages, and similar UI flags are stored in the browser's extension storage (chrome.storage.local, and short-lived pending selection/prompt state in chrome.storage.session) until you clear data, use in-product reset, or uninstall.

Current-page context (on device first). When the side panel is open, or when you use the "Ask AI" context menu, Muse may read the active tab's title, URL, headings, visible text excerpt, and selected text in your browser. This uses scripting plus host access to http://*/* and https://*/* so the companion can understand ordinary webpages you choose to view. It does not run on browser-internal pages (for example chrome://) and does not collect your browsing history as a list.

AI chat (remote, user-initiated only). When you send a message or use a quick action (Summarize, Explain, Rewrite, Extract, Ask AI), the prompt, recent chat turns, and, if those settings are on, the page excerpt and selected text are sent from your browser to our proxy at muse-companion-api-production.up.railway.app (hosted on Railway), which forwards the request to OpenRouter (model: typically OpenAI GPT-4o mini or a successor we configure) solely to generate the reply. We do not use these requests for advertising. Content is processed transiently for the requested answer and is not sold.

Email drafts (user-initiated only). On Gmail, Muse can show a reply control. It does not use the Gmail API and does not sign in to your Google Account. It does not list or download your inbox. When you choose a reply on that control, switch to Reply for the open message, or press "Use this page", Muse reads in your browser the open message's text, sender, and subject, or text you select or paste. A ready-made reply from the Gmail control sends that text immediately so the draft can be written. Otherwise the text stays on the device until you press generate. The handoff into the side panel uses chrome.storage.session and is removed as soon as the panel reads it. Email bodies are not stored in chrome.storage.local. When you generate, regenerate, or refine, the message, sender, subject, and your instructions go to the same Muse proxy and OpenRouter path as chat, only to produce the draft. If you insert the draft, Muse writes it into the compose field. It never clicks Send and never sends the email.

Image generation (user-initiated only). When you ask Muse to create or edit an image, the prompt, recent image requests from that chat, and any reference image you attach are sent from your browser to muse-companion-api-production.up.railway.app/v1/images on the same Railway proxy. The proxy forwards them to the configured image model through OpenRouter and returns the image to your browser. A copy may remain in on-device chat history until you clear history or uninstall. We do not use these requests for advertising, and we do not sell them.

Optional voice input (user-initiated only). If you tap the microphone button, the browser may ask for microphone access in a helper tab (side panels cannot show that system prompt). Speech is converted to text in your browser; only the resulting text is sent to our API when you send a message. Audio is not uploaded to FitzTools servers.

Browser permissions. Muse requests sidePanel, storage, activeTab, scripting, contextMenus, and tabs, plus host access to http://*/* and https://*/* (or the closest equivalents in other supported browsers). The tabs permission is used only to locate the active tab for page context, refresh context while the panel is open, open user-requested links (Privacy Policy, Terms, review page), and open/focus the optional microphone permission helper tab — not to monitor browsing history in the background.

On-device notes and page memory (local). Pages and notes you choose to save stay in chrome.storage.local on that device. They are added to a later question about the same site only when you ask. They are not a cloud account and are removed if you clear extension data or uninstall.

YouTube summaries (user-initiated only). If you ask Muse to summarize or transcribe a YouTube video while that watch page is open, Muse may send the video id and available caption-track addresses from that page to our transcript proxy at wps-ai-proxy-production.up.railway.app (hosted on Railway) to fetch the transcript. The transcript text is then used only for the summary or answer you requested and may be included in the chat request to the Muse proxy above. Muse does not upload the video file.

3.4 Install identifier, subscriptions and billing

Install identifier (local and billing). On first use Muse creates a random UUID (install_id) with crypto.randomUUID() and stores it in chrome.storage.local. There is no Muse account and no password. This id is how the billing server knows which browser installation a subscription belongs to. It is sent only to our billing service when you open checkout, check subscription status, or ask to restore a purchase. Clearing site data or uninstalling creates a new id on the next install; it does not by itself cancel a paid subscription.

Subscriptions and payments. On the free tier, Muse includes one shared AI request per calendar day across chat, page summaries, YouTube summaries, email assist, and image generation. Any completed AI action counts as that daily request. You receive the full result for your first AI action each day; starting another AI action the same day requires a subscription. The counter resets each day. Plans shown in the Extension, in USD, are Weekly $4.99 after a 3-day free trial (a payment method is required to start the trial), Monthly $9.99, and Yearly $39.99. Checkout is hosted by Dodo Payments. Muse opens that checkout page in a new tab and sends only the selected plan and your install_id to our billing service at muse-billing-production.up.railway.app (hosted on Railway). Card numbers, CVC codes, and full payment credentials are entered on Dodo's page. They are not collected by the Extension and are not stored by FitzTools.

Billing records (our server). When you start checkout or when Dodo notifies us that a subscription changed, we store on that billing server the install_id, Dodo customer id, the email and name you entered at checkout, subscription id, product id, plan, status, current period end, and webhook delivery ids. We keep these records to decide whether that installation has an active subscription, to prevent duplicate webhook processing, and to support restore and billing disputes. A typed email alone does not turn Pro on. Pro is set only after Dodo reports an entitled subscription and our server links it to the install_id. Changing extension storage on the device does not grant Pro.

Restore. If you type the email used at checkout, we look up a real Dodo subscription for that email. If one is entitled, Dodo emails a customer-portal link. The subscription is attached to this browser only after that check succeeds. The email is not saved in the Extension.

3.5 What Muse does not do

Muse does not connect to the Gmail API or your Google Account, does not list or download your mailbox, and does not access calendars or passwords. It does not send email and does not take autonomous actions on websites. It does not monitor clicks, scroll position, or keystrokes. No model API key, Dodo API key, or webhook secret is stored in the Extension. Page content is transmitted to the AI proxy only when you ask. An open email is read and sent only when you ask for a draft, as described above. An image prompt is sent only when you ask to create or edit an image. Dodo's practices are described at dodopayments.com. OpenRouter's practices are described in its own privacy policy at openrouter.ai/privacy.

We do not sell personal data. We do not use Extension page content to build advertising profiles for third-party ad networks.

4. How we use information

to operate, maintain, and improve the Site and Muse;
to provide features you request (summarize, explain, translate, store preferences, draft an email, or generate an image);
to grant, restore, and remove subscription access;
to respond to support and product inquiries;
to protect security, prevent abuse, and comply with law.

5. Legal bases (where applicable)

If you are in the EEA/UK or a similar jurisdiction, we process personal data where appropriate on bases such as: performance of a contract / requested service; legitimate interests (Site and service security, abuse prevention, product improvement); consent (where required, for example microphone access); and legal obligations (for example accounting).

We may share information with:

Service providers that help us run the Site, such as hosting and CDN/DNS providers;
Railway, which hosts our Muse proxies (muse-companion-api-production.up.railway.app for chat, email drafts, and image generation; wps-ai-proxy-production.up.railway.app for YouTube transcripts) and our billing service (muse-billing-production.up.railway.app);
OpenRouter and the AI model providers it routes to, when you use AI features;
Dodo Payments when you subscribe — Dodo is the merchant of record for the checkout, charges, invoices, taxes, and the customer portal. We send Dodo the selected product and install_id as checkout metadata. Dodo sends us subscription and customer events so we can grant or remove access;
Google, Microsoft, and Mozilla as operators of the browsers and extension stores where Muse is distributed (installs, reviews, policy enforcement);
authorities or other parties when required by law, legal process, or to protect rights, safety, and security;
a successor entity if we undergo a merger, acquisition, or asset transfer (with appropriate notice where required).

We do not sell your personal information for money.

7. International transfers

Our providers may process data in the United States or other countries. Where required, we rely on appropriate transfer mechanisms made available by those providers (for example standard contractual clauses) or other lawful grounds.

8. Retention

Extension local storage remains on your device until you clear it, uninstall Muse, or use in-product reset/clear options.
AI proxy requests are processed transiently for the user-requested action; we do not maintain a long-term database of your prompts, page content, email text, image prompts, reference images, or summaries on FitzTools servers.
Muse billing records (install id, Dodo customer and subscription status, checkout session ids, and webhook ids) are kept for as long as needed to provide access, prevent abuse, and meet accounting or dispute obligations. You may email us to ask about deletion. Deleting local extension data or uninstalling Muse does not automatically delete the server record and does not cancel a paid subscription.
Support emails are retained as needed to resolve requests and for legitimate records.
Server logs are retained according to hosting/CDN/Railway provider practices.

9. Security

We use reasonable technical and organizational measures appropriate to a small software publisher (HTTPS for the Site, least-privilege permissions for the Extension, no API keys or secrets stored in the Extension, limited access to the support inbox and billing records). No method of transmission or storage is 100% secure.

10. Your choices and rights

Uninstall Muse at any time from your browser's extensions page. Uninstalling Muse AI Companion does not cancel a Dodo Payments subscription; cancel that subscription in the Dodo receipt or customer portal.
Clear Muse's conversation history and saved notes with in-product options, or clear extension data.
Turn page-context settings off, and allow or block microphone access in your browser.
Clear the Site's localStorage in your browser to reset the remembered language.
Request access, correction, deletion, or restriction of personal data we hold about you (for example support emails or billing records) by contacting egor.besarabm@gmail.com.

Depending on your location (EEA/UK/California/other), you may have additional rights (access, deletion, portability, objection, appeal). We will not discriminate against you for exercising privacy rights. If we cannot verify a request, we may ask for limited additional information, such as the email used at checkout.

11. Children's privacy

The Site and Muse are not directed to children under 13 (or the equivalent minimum age in your jurisdiction). We do not knowingly collect personal information from children. If you believe a child provided personal data, contact us and we will take appropriate steps to delete it.

12. Third-party sites and services

The Site and Muse may link to or integrate with third-party services (extension stores, Dodo Payments, OpenRouter and AI providers, YouTube, Gmail, and the websites you visit). Their privacy practices are governed by their own policies. We are not responsible for third-party practices.

13. Store single purpose, permissions & Limited Use

Muse is designed for the single purpose disclosed in its store listings: an AI companion in the browser side panel for the page you are viewing. We request only permissions needed for disclosed functionality. If permissions or data practices change materially, we will update the listings and this Policy as required.

Our use of information received from browser APIs and permissions adheres to the Chrome Web Store User Data Policy, including the Limited Use requirements, and to the equivalent policies of Microsoft Edge Add-ons and Firefox Add-ons. We do not use browser user data for advertising, sell it, or transfer it to data brokers. We use it only to provide and improve the user-requested features described in this Policy.

For Muse AI Companion, the Chrome Web Store privacy practices declare Website content (the page you are viewing: title, URL, headings, visible text excerpt, and selected text, and, if you ask, a YouTube transcript fetched for that video) and Personal communications (the text, sender, and subject of an email you ask Muse to answer or improve, text you paste for a draft, and the draft returned to you). Website content is read locally only while the side panel is open or when you use Ask AI, and is transmitted to Railway → OpenRouter only when you send a message or use a quick action. Personal communications are read in the browser only when you request an email draft and are transmitted to the same proxy only to write that draft. They are not saved as a mailbox in the Extension. Image prompts and any reference image you attach are sent to the Muse proxy's image endpoint only when you ask to generate or edit an image. Optional voice input uses the microphone only when you tap the mic button; audio is not uploaded to FitzTools. A random install id and subscription status are used only to bill and unlock the features you choose. Payment card data is collected by Dodo Payments on their checkout page, not by the Extension. Muse does not connect to the Gmail API, does not list or download your mailbox, does not send email, does not monitor clicks, scroll, or keystrokes, does not collect browsing history as a list, does not access calendars, passwords, or your Google Account, and does not store an API key in the Extension. We do not use this data for advertising, do not sell it, and do not use it to train generalized ML models.

14. Changes to this Policy

We may update this Policy from time to time. The "Last updated" date at the top will change when we publish revisions. Continued use of the Site or Muse after an update means you accept the revised Policy, except where consent is required by law.

15. Language

The Site interface is available in several languages. This Policy is published in English, and the English version controls.

16. Contact

Privacy requests: egor.besarabm@gmail.com

Site: https://getmuseai.app