Mishō

Mishō: security sheet and privacy policy

This page is Mishō's security sheet and its privacy policy.

This page is Mishō's security sheet, and also its privacy policy. It says what Mishō collects, what it asks Chrome for, what leaves your browser when you choose to share, where your data lives, how long it is kept, who else receives any of it, how to delete it, and how to stop Mishō. Last updated on 15 November 2026. The words in quotes are the panel's own.

Mishō runs in your browser, beside the web apps you already use.

On your own, nothing. Not your screens, not what you type, not a single request to us. You can check.

What Mishō collects

What Mishō asks Chrome for, and why

Chrome's documentation lists no install warning for any of these, and the install names no site.

Asks for What it lets Mishō do When Chrome asks
sidePanel Show Mishō's panel beside the page when you click its button in the toolbar. At install, with no warning
storage Keep your settings in this browser, such as the apps you allowed. Your sign-in and the counts waiting to be sent are kept in memory only, and are gone when the browser closes. At install, with no warning
activeTab See the tab you are on, and only that tab, when you use Mishō there yourself, until you leave the page. At install, with no warning
scripting Start Mishō's capture on each app you allowed, and on no other site. At install, with no warning
unlimitedStorage Keep your personal store from being deleted when the browser runs short of space, so it stays until you clear it. At install, with no warning
alarms Wake Mishō on a schedule: to find your repeats every two minutes, to carry on a run in your tab, and, while you are signed in, to read your company's switches, and whether it has stopped Mishō, every five minutes. At install, with no warning
https://*/* Let you allow an app that runs on https, one app at a time. Chrome asks you about each one, and Mishō sees no other. When you press Allow on that app
http://localhost/* The same for an app running on your own computer, such as a test copy. When you press Allow on that app
Mishō's own address Reach Mishō's server when you sign in. Without it nothing is sent. When you press Sign in

What leaves your browser

Until you sign in, Mishō sends nothing. The panel's header reads "Nothing sent", and the Network tab of Chrome's DevTools shows no request to Mishō's address. Mishō's tests check this before any change is merged.

Signing in, from the first screen or by turning a switch on, trades your browser's sign-in with your company for this browser's own. Mishō then reads your company's two switches, and whether it has stopped Mishō, every five minutes. Nothing about what you do is sent while Sharing is off.

When you sign in, Mishō records that you agree to be counted, and when you sign out it withdraws that first, if it can reach Mishō's server. Your company's team store keeps nothing from a member who has not agreed.

Both switches belong to your company and start off.

Cloud naming. Sends the labels of your steps, and what you type in Ask, to a model. Nothing else leaves.

With it on, Mishō's server sends a model the labels of the steps of a suggestion it made from what members shared, and reads back one name; and when a member asks for a task in Ask, it sends the model what they typed with the keys of the company's paths, and reads back one choice. When members share only counts, which carry no labels, only what a member types in Ask reaches the model.

Sharing. Publishes team counts and the templates you choose; your recordings and runs stay here.

The counts say which screens and controls followed which, by their names in the app, never their labels or anything you typed. The server counts each member once a day for each sequence, and uses a count only once at least five members share it. Publishing sends one approved version of a workflow: its name, its steps with each control's label, and the names of its inputs. Your own workflow stays in this browser, unchanged.

Sharing needs your company to know the app you allowed. If it has no record of it yet, the panel says Your company has not imported this app yet. and sends nothing until it does.

If a switch cannot change, it stays as it was, and the panel says why:

Where your data lives

In this browser. Your personal store holds what Mishō collected on the apps you allowed: the screens and controls with their labels, your map, your repeats, your recordings and drafts, the versions you approved, and your runs, each with a record of its steps that is only ever added to. It is as private as your browser profile: anyone who can use your computer account can read it, the same standing as your saved passwords and bookmarks. Mishō adds no encryption of its own. Export writes a copy to a file you choose.

In your company's team store. What members publish goes to one database for all companies, where the database itself keeps each company's rows apart from every other's. It holds the counts and templates members publish, the company's two switches, its members, and the record of who changed what. A member who connects an app's API, so runs can finish with the browser closed, leaves that app's refresh token there, sealed under Mishō's master key; the access token is never kept. Members join by invitation and sign in with their company's own Google, Microsoft or Okta account, and Mishō keeps no password and no token from it. Sharing publishes to the team store; it never copies your personal store.

How long it is kept

Who else receives any of it

How to delete it

How to stop it