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
- On the apps you allow, one at a time: which screens you open, and which control you use on each screen, with the control's label.
- Never a value. The capture module never reads a typed value. Password and payment fields are skipped entirely, and a list is seen by its label, never by what you chose in it.
- Before a label is kept, Mishō removes anything that looks like an email address, any number of five or more digits, and angle brackets.
- Each app is allowed through Chrome's own prompt, and Mishō collects nothing on any other site.
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:
- "Could not read the switches. They show as off."
- "The change did not save, so the switch is back as it was."
- "Sign in with the link your admin sent, then come back here."
- "Sign-in did not finish, so the switch is back as it was."
- "Sign-in did not finish with your company, so the switch is back as it was."
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
- In this browser: until you clear it or remove Mishō.
- A member's own steps, in assisted mode: 90 days. The panel does not offer assisted mode yet, and the deletion after 90 days is not built yet either.
- Counts: kept by day. Each day the server forgets which members counted towards each sequence, and keeps only the number. The server sleeps while no one uses it, and a day it slept through is forgotten when it next wakes. A company's own setting that deletes counts on a schedule, 90 days unless it chooses otherwise, is not built yet, so until it is, counts are kept.
- Templates and the record of who changed what: kept, and never edited.
- A connected app's refresh token: until its grant is revoked.
Who else receives any of it
- Groq runs the model behind Cloud naming, only while your company has it on, and receives only what Cloud naming sends, above. Mishō's setup turns on Groq's zero data retention, under which Groq does not keep what it is sent for reliability and abuse monitoring, and records only usage figures that hold no input or output.
- Render runs the server, in the United States (Ohio). Signing in, and everything your company's two switches send, goes through it.
- Neon keeps the team store's database, in the United States (AWS, Ohio).
- Cloudflare stands in front of that server, so every request to it passes through Cloudflare. It also runs the browser of the hosted session, a way to try Mishō with nothing installed. The hosted session is not offered yet.
How to delete it
- In this browser: press Clear local data in Settings, as "How to stop it" below describes.
- In your company's team store: your company's admin has it deleted. There is no button for it yet, so the admin asks Mishō to delete it.
- A connected app's grant: revoking it ends it at the app and deletes it here. The panel has no button for it yet; until it does, removing Mishō from the app's own list of connected apps ends it at the app.
How to stop it
- Turn a switch off in Settings. What it sends stops from the next send.
- Stop watching an app in Settings, under Allowed apps. Mishō stops collecting on it at once and asks Chrome to forget the site access. "What Mishō already noticed about an app stays in your personal store until you clear it."
- Sign out in Settings. It clears this browser's sign-in, the batches waiting to be sent and your company's last answers, and keeps your personal store. It withdraws your agreement to be counted first. It then ends this browser's session on Mishō's server, if it can reach it; a session it cannot reach ends by itself within an hour unused. If it cannot finish, the panel says "Sign out did not finish. Try again."
- Your company can stop Mishō for all its members. Within five minutes every signed-in member's panel says "Mishō is stopped by your company. Nothing is sent and no workflow runs." with the time it last checked, such as "Checked at 09:30."
- Stop Mishō on one app by removing its site access in Chrome's settings for Mishō. Mishō stops seeing that app.
- Clear local data in Settings deletes your personal store from this browser. It first names what will go, such as "This deletes from this browser: 3 sources, 41 screens and actions, 2 workflows, 1 run. It cannot be undone. Export first to keep a copy." If it cannot read the store, the panel says "Could not read what this browser holds.", and if it cannot finish, "Clear did not finish. Nothing was deleted." If Export cannot finish, it says "Export did not finish."
- Remove Mishō from Chrome to stop everything in this browser. Chrome then deletes the storage Mishō keeps its settings in. To be sure your personal store goes too, press Clear local data first. A connected app's grant is not ended by removing Mishō: see "How to delete it" above.