Privacy Policy

Effective 30 October 2026

This policy explains how Umi processes information when you use the service. Umi is operated by the service owner, reachable at ashishbishnoi18@gmail.com.

Information Umi processes

• Google account information: a stable Google account identifier and your verified email address. Umi does not receive your Google password. The short-lived Google access token is used to retrieve this information during sign-in and is not stored.
• Workspace content: information you choose to add, including projects, chats, files, settings, and resource connection details.
• Connected resources: information needed to use browsers, model providers, and other services you choose to connect. Requests sent through a connected provider are also subject to that provider's privacy terms.
• Operational information: request, device, security, and diagnostic information needed to operate, protect, and troubleshoot the service.

How information is used

Umi uses this information to authenticate you, create and maintain your workspace, provide features you request, prevent abuse, secure the service, diagnose failures, and communicate about access or support.

Umi for Chrome

The side-panel chat is Umi's own page and uses your existing sign-in. When you turn on Use this page for a site, or explicitly ask to capture a page, the next message can include its address, title, selected words, readable text, a visible-area picture and facts about how the site is built. You can review or remove the page chip before sending. These new page and comment captures exclude form entries and passwords, and hide editable areas in pictures.

Website access is optional. After Umi explains, Chrome asks once for access to all websites so page and comment pictures work on websites you choose. Granting access alone captures or sends nothing. Capture requires an explicit action or your per-site Use this page preference; sending requires your action. This permission does not grant autonomous shared-tab control. Settings → This browser and the panel menu show access. Revoke it at chrome://extensions → Umi for Chrome → Site access.

Website comments include your words, the page address and title, the place you picked, nearby text, page labels and identifiers, screen position and pictures of the areas. Draft comments also identify the app. Comments stay in Chrome until you send them as a message with image attachments. Queued pictures are stored temporarily in the extension’s local IndexedDB, with small routing records in Chrome session storage. They expire after ten minutes and are removed by the next cleanup while Chrome runs. A new Chrome session, sign-out or account change clears earlier queues before reuse. Completed sends discard queued pictures and keep a small receipt briefly to prevent duplicate sends. Batches are scoped to their window and account; an interrupted send asks you to check the chat before sending again. Saving a page, selection or picture stores a file in the project you choose, where it remains until you remove it.

Browser sharing grants are bound to the verified Umi account. Signing out or changing accounts stops sharing and revokes the old connection; another account must choose its own tabs.

The extension shows the web app’s Needs you count for the workspace selected in that Chrome window. Finished results are separate optional notifications; they never increase the badge. An open Umi page supplies the account-bound count, which expires if it stops updating. The extension checks chat status for optional notifications. A notice may show a chat title on your device; turn notifications off in the panel's menu. Site choices, notification preferences and a small record of notices and viewed chats stay in this Chrome.

Send page in This Chrome captures the current page title, URL and selected text when you press it. Sharing is separate: shared-tab titles and URLs are sent to Umi, and requested reading operations may send page text, HTML, links, element descriptions and screenshots. Full control also permits clicks, typing, navigation and tab actions. Individual-tab and read-only sharing use bounded commands owned by the extension. Local grants and Chrome-issued tab-target identifiers preserve same-account extension reloads; browser restart clears individual grants and pauses remembered whole-Chrome sharing. Whole-Chrome sharing does not expose raw DevTools commands, cookies (including HttpOnly cookies), passwords or website storage. Acting requires a separate per-site and per-account choice, and follows the project’s Manual, Auto or Full access mode. Private password, card and sign-in-code fields are left to the person.

Browser content supplied to a conversation or agent may be included in model requests to your selected AI provider and retained with workspace conversations and tool results. A live-view image is carried through the Umi server to your signed-in page; the live-view route does not save an image archive. Relay tickets and live connection inventories are temporary server memory.

Umi works in a chat-owned tab group, with Stop in the panel and on the page. Person input pauses work until Hand back to Umi. Action history records the time, action, page, element, Chrome profile, chat and turn without entered values or URL query strings; Umi retains up to 10,000 records per account for up to 30 days. Project file transfers are bounded to 4 MB. The local panel keeps up to 200 action records and clears them on account change.

The extension stores sharing preferences locally. The older Send page queue stays in session storage, while account-bound grants and their browser-target proof also survive in local storage; tab grants are cleared on browser restart, and unconsumed Send captures expire after one minute. Remembered whole-Chrome sharing returns paused. Stop all, individual unshare controls and Chrome’s debugger Cancel revoke future extension access; they do not erase content already sent to a conversation. Uninstalling the extension removes its local data. For account or previously sent content deletion, use Umi’s deletion controls or contact the address below. No extension browsing data is sold or used for advertising. Umi’s use of information received through the extension follows the Chrome Web Store User Data Policy, including Limited Use. It is not used to determine creditworthiness or for lending.

Sharing

Umi does not sell personal information. Information may be processed by Google for sign-in, by infrastructure and network providers that deliver Umi, and by model, browser, or other providers you explicitly connect. Information may also be disclosed when required by law or necessary to protect users and the service.

Retention and your choices

Information is retained while needed to provide and secure the service, meet legal obligations, resolve disputes, and maintain legitimate operational records. You can disconnect resources in Umi. To request account access, correction, export, or deletion, email ashishbishnoi18@gmail.com. Some records may be retained where required for security, backup integrity, or legal compliance.

Security

Umi uses technical and organizational safeguards intended to protect information, but no online service can guarantee absolute security. Keep your Google account and connected-provider credentials secure and report suspected unauthorized access promptly.

Age and changes

Umi is not directed to children under 13. This policy may be updated as the service changes; the effective date above will be revised when material changes are published.