Privacy Policy

What stays on your device

Mirsah keeps your workspace data and settings on your device so the extension can work quickly and reliably. Some information stays local and is not included in cloud sync, including custom wallpaper files, Focus timer state, local link-open counts, and Privacy Lock verification data.

Your account and sign-in

An account is required to use Mirsah. You can sign in with email and password or with Google. Google sign-in gives Mirsah only the basic account information needed to sign you in, such as your email and profile details. Mirsah does not use Google sign-in to access Gmail, Drive, contacts, calendars, or your browsing history.

Cloud sync

If your account includes cloud sync, it starts enabled. Mirsah may create or update a cloud copy of supported workspace data and settings after you sign in so they can be synchronized and recovered across devices. You can turn cloud sync off at any time from Settings. Custom wallpaper files, Focus timer state, local link-open counts, and Privacy Lock verification data are not uploaded by cloud sync.

Quick Save

Quick Save only uses the current tab when you trigger the Quick Save shortcut. Mirsah temporarily reads the tab title and URL so it can prepare the bookmark you asked to save. It does not continuously monitor the sites you visit.

Privacy Lock

If you use Privacy Lock, Mirsah does not store or sync your actual PIN. The information needed to verify the PIN stays on your device and is not included in cloud sync.

Pro trial eligibility

Eligible verified accounts may receive one 30-day Pro trial. To prevent repeated trial abuse, Mirsah keeps a privacy-preserving record that helps determine whether a trial has already been used. This record does not contain your email address and may remain after account deletion only to enforce the one-trial rule.

Payments and subscriptions

Lemon Squeezy handles payments, invoices, and subscription management. Mirsah does not receive or store your card number. Mirsah receives the subscription information needed to know whether Pro features should be available on your account.

Support requests

If you contact support, Mirsah stores the information you submit so we can respond and manage your request. This can include your name, email, request type, subject, message, optional Mirsah version, language, and request reference. Please do not send passwords, PINs, card details, verification links, or other sensitive information.

Services we use

Mirsah uses Google and Firebase for account services, hosting, cloud features, and support requests, and Lemon Squeezy for payments and subscriptions. Mirsah does not sell your personal data, use it for personalized advertising, or share it with data brokers.

Your choices and data retention

You can export a local backup, turn cloud sync off when available, sign out, and delete your Mirsah account and cloud workspace data. Data stored on your device remains there until you remove or reset it, uninstall Mirsah, or clear the extension data. The trial-eligibility record may remain after account deletion to enforce the one-trial rule. Some support, billing, or security records may also be kept when reasonably needed for support, accounting, abuse prevention, or legal obligations.

Chrome Web Store policy

Mirsah handles information received from Google APIs in line with the Chrome Web Store User Data Policy, including its Limited Use requirements.

Browser access and permissions

Mirsah asks only for browser capabilities used by specific features. Here is what each one does and what it does not do.

• Browsing history: Mirsah does not request your browser’s browsing-history permission and does not continuously monitor the sites you visit.
• Bookmark import: Browser bookmark access is optional. Mirsah asks for the bookmarks permission only when you choose browser bookmark import, then reads the bookmark tree to prepare the import you requested.
• Quick Save and the current tab: When you trigger Quick Save, Mirsah reads the active tab’s title and URL, accepts only normal http/https pages, keeps the pending save briefly in extension session storage, and opens Mirsah so you can finish saving it. It does not read tabs continuously.
• Sign-in: Authentication access supports Mirsah account sign-in. Google sign-in requests only OpenID, email, and basic profile scopes; it is not used to access Gmail, Drive, contacts, calendars, or browsing history.
• Search: Searching your saved Mirsah links happens locally in the extension. If you explicitly choose web search, Mirsah passes the query text to the browser’s search API, which opens a new tab using your browser’s search provider.
• Extension operation and cloud sync: Local storage keeps Mirsah workspace and settings state; alarms support Focus timer completion; favicon access displays site icons; Chromium offscreen access supports Focus completion audio. When cloud sync is available and enabled, supported workspace data and settings may be stored with Firebase as described in this Privacy Policy. Custom wallpaper files, Focus timer state, local link-open counts, and Privacy Lock verification data remain on your device and are not included in cloud sync.

Questions?

If you have a privacy question, send it through the contact form.