Privacy Policy
This English text is a reference translation. The Japanese version is the official version. If the two differ, the Japanese version prevails.
MICHISE ("we") sets out below how the MICHISE browser extension ("the Extension") handles information.
This policy describes what the Extension actually does. In particular, it states explicitly which information read from a business screen is not sent to our server.
1. Scope
This policy applies to:
- the MICHISE browser extension distributed through the Chrome Web Store;
- the MICHISE server that the Extension connects to.
The Extension is intended to be deployed by a company to its employees. In this policy, "user" means a person operating the business system, and "administrator" means a person who creates and publishes guidance in the Extension's admin screen.
2. Information the Extension handles
2-1. Information entered by an administrator
- Email address (entered when an administrator signs in)
- Password (same)
- Authentication token (received from our server on successful sign-in)
- The guidance content an administrator creates (text, button labels, the element to attach guidance to, display conditions, and so on)
2-2. Information received at deployment
- A one-time enrollment token. A company administrator places this on each device using the MICHISE installer, and the Extension reads it. It is used once only, to determine which company's settings the device should receive.
2-3. Information processed on the business screen
To place guidance correctly and to judge whether a step has been completed, the Extension processes the following on the business screen. None of it is sent to our server.
- Page elements and their text (to locate where guidance should appear)
- Values in input fields. Read only when an administrator has configured a step that fills one field by referring to another. Password fields, file inputs and hidden fields are never read.
- The address (URL) of the page currently displayed, to evaluate the display conditions an administrator configured
- Clicks, key presses, focus changes and scrolling, used solely to judge whether the current step of the guidance has been completed
- A screenshot of the business screen. Taken once, immediately after an administrator uses "select on screen" in the admin screen to designate where guidance should appear, so that the administrator can later confirm which location was chosen.
About screenshots. A screenshot is taken only when an administrator performs the location-selection action in the admin screen. It is never taken during ordinary use, when a user is simply viewing guidance. The image is stored only in that device's browser (IndexedDB) and is not sent to our server.
2-4. Information the Extension does not handle
- Health information
- The contents of personal communications such as email or chat
- Location (no location API is used)
- Browsing history (no list of visited pages is recorded or stored)
- Cookies (never read or written)
3. Purposes
| Information | Purpose |
|---|---|
| Email address and password | To verify the administrator's identity |
| Authentication token | To keep the administrator signed in |
| Enrollment token | To determine which company the device belongs to |
| Guidance content | To display guidance on the user's business screen |
| Page elements and text | To locate where guidance should appear |
| Input field values | To perform the "fill by reference" step an administrator configured |
| Page address | To evaluate the display conditions an administrator configured |
| Clicks and similar actions | To judge whether a guidance step has been completed |
| Screenshot of the business screen | So an administrator can confirm the location they designated |
| Guidance progress | So guidance can continue after the page changes |
We do not use this information for advertising, behavioural analysis or web analytics, and we do not send it to any external analytics service.
4. Information processed and stored on the device
| Where | What | When it is removed |
|---|---|---|
| Extension storage (chrome.storage.local) |
A cached copy of the company's published settings, synchronisation state, guidance progress, the company binding, and the list an administrator uses to preview drafts on their own device only | Guidance progress expires after 30 minutes. The rest is removed when the company settings are cleared or the Extension is uninstalled |
| Extension session storage (chrome.storage.session) |
The administrator's authentication token | When the browser is closed, on sign-out, or when the token expires |
| Managed configuration (chrome.storage.managed) |
The one-time enrollment token (read only; the Extension cannot write to this area) | When the company administrator removes the deployed configuration |
| In-browser database (IndexedDB) |
Screenshots of the business screen, and images an administrator inserted in the admin screen | When the Extension is uninstalled, or when deleted from the admin screen |
An administrator's password is sent for authentication immediately after entry and is not stored on the device. The authentication token is stored only in an area that is cleared when the browser closes; it is never written to disk-backed storage.
Guidance progress consists only of the guide identifier, flags for completed steps, the branch taken, the starting step and a timestamp. It contains no screen content and no entered values.
5. Information sent to our server
The Extension sends information to our server only in the following cases.
- When an administrator signs in: the email address and password are sent.
- When a device is bound to a company: the one-time enrollment token is sent once, and the device receives its own connection information in return.
- When an administrator selects "Publish changes": the guidance content they created (guides, buttons, popups, hints and the default button appearance) is sent.
- When receiving published settings: the server decides which company's settings to return; the Extension never sends a company or environment identifier.
6. Information that is not sent to our server
The following is processed on the device only and is never sent to our server.
- Screenshots of the business screen
- Text displayed on the business screen
- Values entered in input fields
- The address of the page currently displayed
- Clicks, key presses and scrolling
- Guidance progress
The part of the Extension that runs inside the business screen performs no external communication at all. Communication occurs only in the four cases listed in section 5.
Relationship to the Chrome Web Store declaration. The Chrome Web Store requires disclosure even for information that is processed only on the device. We declare five categories: "Personally identifiable information", "Authentication information", "Website content", "User activity" and "Financial and payment information". Of these, the only things sent to our server are the items listed in section 5 — the administrator's email address, password, authentication token and enrollment token, and the guidance content the administrator created. The remaining three — "Website content", "User activity" and "Financial and payment information" — are processed on the device to the extent needed to display guidance; that does not mean we collect them, send them to our server, or use them for advertising or analytics. "Financial and payment information" is declared because a screenshot taken by an administrator may happen to capture whatever is shown on that screen, not because the Extension seeks out such information.
7. Retention
On the device
- Guidance progress: expires after 30 minutes
- Administrator authentication token: removed when the browser is closed, on sign-out, or when it expires
- Cached settings and company binding: removed when the company settings are cleared or the Extension is uninstalled
- Screenshots: removed when the Extension is uninstalled
On our server
We retain the necessary data for as long as MICHISE is in use, and delete it within 30 days after use ends.
Enrollment tokens are issued with an expiry (90 days at most) and a maximum number of devices; they stop working once expired, exhausted or revoked.
8. Deleting data
- On the device: "Clear company settings" in the admin screen removes the company binding and the cached settings. Uninstalling the Extension removes all data it holds.
- Authentication token: removed on sign-out, and when the browser is closed.
- On our server: deletion requests are accepted at michise.support@gmail.com.
9. Sharing with third parties
We do not sell the information we handle, and we do not provide it to advertising platforms, data brokers or similar third parties.
The Extension communicates with a single server that we operate. No code is implemented to send information to any external analytics or advertising service.
We may disclose information to the extent required by applicable law.
10. Advertising and analytics
We do not use the information for delivering or measuring advertising, nor for analysing user behaviour. The Extension displays no advertising and contains no analytics mechanism.
11. Security
- Secrets used for connection are never held in plain text on our server; only an irreversible hash is stored.
- The administrator's authentication token is stored only in an area cleared when the browser closes, never in disk-backed storage.
- The Extension's communication destination is fixed to a single location and cannot be changed from outside.
- The Extension requests only two permissions: access to its own storage, and the ability to capture the visible screen once, immediately after an administrator designates a location.
- No remotely hosted code is executed. The Extension runs only the code included in the package distributed through the Chrome Web Store.
- Which company's settings are returned is decided by the server from the device's connection information; the Extension cannot specify a company.
12. Limited Use disclosure
MICHISE's use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
Information handled by MICHISE is used only for MICHISE's single purpose — displaying administrator-authored guidance on the user's business screen — and for related operational purposes.
MICHISE does not:
- use, transfer or sell the information for personalized advertising;
- sell or transfer it to third parties such as advertising platforms or data brokers;
- use, transfer or sell it to determine credit-worthiness or for lending purposes.
13. Changes to this policy
When we change this policy, the updated text is published on this page. The text published here is the current version. The last updated date is shown at the top of this page.
14. Governing law
This policy is interpreted in accordance with the laws of Japan.
15. Contact
For questions about this policy, or to request deletion of data, please contact us.
Provider: MICHISE
Contact: michise.support@gmail.com