瀏覽器擴充功能隱私權政策

1. Scope and shared principles

This policy applies to mi-screenshot, mi-right, mi-cookie, mi-volume, mi-check-gmail and the legacy “超簡單 Gmail 未讀顯示” (easy_check_gmail). Only the products you install and use apply to you. The versions below identify the behavior reviewed for this policy. It does not automatically cover future products, development templates or another publisher’s extensions. The publisher and privacy contact for all listed products appear in the contact block above.

Data is used to provide the functions described below. There is no publisher server endpoint receiving screenshots, email feeds, media content or website settings. The extensions do not transmit that content to the publisher, sell it, use it for advertising, analytics, profiling, creditworthiness, lending or model training, or load remotely hosted executable code.

This does not mean every product is offline, stores no data or uses no cookies. Gmail tools connect directly to Google; the legacy Gmail tool uses Chrome Sync; the volume tool stores website preferences locally. Screen pixels and audio are also processed on the device. Apart from signing in to a suitable Google account for Gmail, no publisher-operated account is required.

2. mi-screenshot

After you choose a capture action or assigned shortcut, the extension captures vertical page content, the visible viewport or a rectangular selection and downloads a PNG. It processes pixels, selection coordinates, DOM geometry and visibility styles, scroll positions, window and scale information, tab/window identifiers and the page hostname. A visible bitmap is obtained locally before selection cropping; pixels outside the selection are therefore processed as input.

Cropping and stitching take place in device memory, without uploads to the publisher or third-party services or an extension screenshot database. Downloaded filenames include the hostname, capture mode and time. PNG files remain until you delete them. If you choose a synchronized folder, subsequent synchronization is controlled by your storage service and settings.

Captured pages may contain personal, financial, health, account or confidential information. There is no OCR, sensitive-data classification or automatic redaction. The required permissions are activeTab and scripting. You can cancel selection or full-page capture; refreshing the page removes the code injected into that document. Uninstalling does not delete downloaded PNGs.

3. mi-right

After you click the toolbar icon, activeTab and scripting allow the extension to handle common right-button events in currently accessible page frames to restore the native context menu. It uses the current tab identifier, event type, mouse-button information and an enabled flag held in the document. It does not extract page text or form values, log mouse activity or keyboard input, persist data or transmit data over the network. Refreshing or leaving the document ends its injected behavior.

4. mi-cookie

When you click the icon, the extension uses the current tab URL, origin and hostname with activeTab and browsingData to ask Chrome to delete cookies. It does not read cookie names or values, retain browsing history, persist data or upload data.

Chrome clears cookies at the registrable-domain scope, not only the exact subdomain shown in the tab. Other subdomains may be signed out; clearing Google account cookies may pause Chrome Sync. The extension does not select other data types such as history, passwords or cache, although Chrome may also reset associated authentication or network state. The extension cannot undo deletion. Websites can create new cookies afterward. This version does not run in incognito mode.

5. mi-volume

After activation, the ordinary page mode reads the current website origin, top-level media elements, playback/mute state, current media URLs and compatibility information to adjust audio locally. Media URLs are used temporarily for compatibility checks, not stored as a viewing-history record.

Chrome storage.local holds at most 100 website-origin/gain pairs. An HTTP(S) origin includes the scheme, hostname and non-default port, but not a page path, query or fragment. Preferences have no automatic expiry; 100% is not retained as a default, reset removes the current site’s default, and exceeding the limit removes the earliest retained entry. Temporary mute is not saved. These preferences do not use Chrome Sync.

If you separately enable the experimental mode and grant optional tabCapture/offscreen permissions, the extension processes that tab’s output audio in real time and plays it on the local device. This is not microphone or camera capture and does not capture video, record, encode, download, save or upload audio. Stream/session identifiers and live state remain in local memory.

Processing can continue after the popup closes. Stop, full navigation, reload, tab closure, permission removal or capture failure ends tab capture and releases its resources. In ordinary page mode, reset can leave a neutral audio path; reload ends the document’s controller. Required permissions are activeTab, scripting and storage. There is no host permission or upload service; the original website remains responsible for loading its media.

6. mi-check-gmail

Installation, browser startup, account-setting changes, manual refresh and an approximately one-minute Chrome alarm can trigger an unread check. Browser suspension or closure can delay checks. HTTPS requests go directly to Google Gmail at mail.google.com/mail/u/{account-position}/feed/atom; the extension can also open the corresponding inbox.

The browser includes applicable existing Gmail session cookies. The extension does not read their values, collect passwords, store login tokens or implement an OAuth sign-in flow. Google receives the request and ordinary connection information under its own service policies; requests do not pass through a publisher server.

The full Feed text can include senders, names, email addresses, subjects, summaries and links. It is received in memory and parsed for the fullcount unread count. The extension does not persist the Feed or those content fields or forward them to the publisher.

Only gmailSlot and the latest lastUnreadCheck are saved in Chrome storage.local. The latest status contains success/failure, account position, unread count, check time and an error code. Updates overwrite the previous status; there is no accumulated history, automatic expiry or Chrome Sync. Required access is alarms, storage and the Gmail website.

Options allow account-position changes and immediate checks. The position is a Gmail URL index rather than a permanent identity and can refer to another account after sign-in order changes. Feed availability depends on the Google account; universal personal-Gmail support is not promised. This version rejects Feed redirects and has a request timeout. Disable or uninstall the extension to stop future checks.

7. Legacy Gmail tool: easy_check_gmail

The legacy tool also requests Gmail Feed data using the existing session, receives Feed text that may contain email information, and extracts an unread count. It does not persist the Feed or send it to the publisher. Installation, startup, account-position changes, manual refresh and an approximately one-minute alarm trigger checks. Unlike the newer version, it does not explicitly reject Fetch redirects; subsequent requests are subject to browser permissions and Google responses.

The legacy tool stores gmailSlot in Chrome storage.sync. Depending on your Chrome/Google sync settings, Google may synchronize this numeric account-position setting between devices. The latest check result stays in storage.local and includes success/failure, position, unread count, time and an error message. Each result replaces the previous result; no email-content database is created.

Settings and status have no automatic expiry. Change the account position in options, or disable/uninstall to stop checks. Local data can be removed through the browser. Retention and deletion of synchronized copies are governed by Chrome Sync/Google; uninstalling is not a promise of immediate deletion from all devices or cloud copies. The newer and legacy extensions are independent and do not automatically migrate settings.

8. Retention, controls and limited use

Temporary memory is reclaimed by the browser when no longer needed or referenced, without a promise of fixed reclamation time or secure erasure. Local preferences/latest status remain until overwritten, reset, cleared through the browser or removed with the extension. Disabling does not delete settings. Legacy synchronized copies are subject to the Sync rules above. You manage downloaded files and any sharing, uploads or storage synchronization you initiate.

You can disable/uninstall extensions and manage website access and optional permissions in the browser. Available cancel, reset, stop and configuration controls differ by product as described above. The publisher does not maintain a database of extension user content to retrieve or delete on your behalf.

Data is used only for disclosed functionality in accordance with the Chrome Web Store User Data Policy, including Limited Use requirements, and applicable Google API Services User Data Policy/Limited Use requirements for Google service data. Data is not sold or used for advertising, profiling, creditworthiness or lending. The extensions do not give publisher staff access to read emails, screenshots or audio content. Contact the publisher listed above with privacy questions.

9. Hosting website, other services and updates

This policy covers the listed extensions, not the hosting website’s accounts, orders, payments, advertising or other business operations. This standalone HTML file has no JavaScript, analytics, external fonts, cookies or forms. The actual hosting server, CDN, security services or added code may process IP addresses, requests or logs according to their configuration; the website operator must disclose that separately.

Google, Chrome, your operating system and visited websites process data under their own policies. This policy does not make commitments on their behalf. See the Google Privacy Policy. The publisher will update this policy and its date when products or data uses change, update store disclosures, and obtain authorization where applicable. The contact block above applies to every product in this policy.