Privacy Policy

About Mimon

Mimon is a Chrome extension for raising a small 16x16 pixel pet that lives in the corner of your browser. Raising it is completed locally (inside the browser on this device) based on browser operations, and the Google Calendar connection and weather display are optional. For weather you can choose between the current-location method and manual region selection.

Where growth data and the album are stored

Currently, growth state and the album are stored per Chrome profile on the device where Mimon is installed. If several people use the same profile, they are not distinguished per person and share the same data.

Even with the same Google account, nothing is synced with another device or another Chrome profile. Google Calendar authorization is used to read events, and is not used to identify the owner of growth data or the album, or to transfer them. The individual ID in the album is an identifier for preventing duplicate records of Mimon and is not used to identify a person.

The public site (mimon.jp) never directly loads or changes growth state or the album inside the extension. Settings and viewing are done from the extension. With the optional share feature, the image information of that moment's look is sent only when you open the share page from the confirmation screen. Concrete examples for each storage location

Data that is stored

• Growth state (growth stage, growth counters, bond value and so on)
• Abstract operation counters (numbers only, such as click counts, scroll amounts and focused time)
• Display settings (display scale and so on)
• Mimon's album (the look at each growth stage of baby, child and adult, name, generation, growth stage, attribute, recording date and time, and an individual ID for preventing duplicates. A current look that has not been recorded is also saved when the album is viewed)
• If weather is enabled: the forecast area including a manually selected region, the day's forecast, announcement, fetch and attempt times, error state, and the dates already notified for morning, noon and night
• If Google Calendar connection is enabled: for the nearest events, summary (event name)start (start time)end (end time)id (event ID), the latest bubble notification text, and the sync time and error state are held temporarily in memory. The connection settings, and the one-way hashes and notification times for avoiding duplicate notifications, are stored on the device

Persistent data such as growth, the album, settings and forecasts is stored in the browser's chrome.storage.local. From v0.7.50, the event name, start/end times, event ID, notification text and sync information are not persisted to disk and are kept in memory in chrome.storage.session, which only trusted extension screens can access. Growth state, the album, operation counters and fetched events are never sent to the Mimon developer's servers. The album is kept separately from Google Calendar and weather records and is not deleted when you disconnect. There is no sync or backup feature between devices. For communication involved in the optional weather feature, see “About weather and location” below.

Data that is not stored

• URLs of pages you viewed
• Page titles
• Page text
• What you enter into forms and the like
• Browsing history
• Precise latitude and longitude, and location history
• Attendees of Google Calendar events
• Location of Google Calendar events
• Meeting URLs such as Google Meet
• Description text of Google Calendar events (description)

About the Google Calendar connection

• The Google Calendar connection is an optional feature. Mimon grows as usual without it.
• In v0.7.53 it requests only the scope for reading events of calendars you own (calendar.events.owned.readonly) and fetches only the primary calendar of the connected account. In v0.7.52 and earlier it requested calendar.events.readonly. No version ever creates, changes or deletes events. Permissions granted on the Google side for an older version are not revoked merely by updating the extension.
• Information obtained from the Google Calendar API is used only for the purpose of Mimon telling you in a speech bubble before an event (calendar reminders).
• At the time of the request to the API, the fetched fields are limited to event ID, cancellation status, event name, and start/end times. The dedicated fields for attendees, location, meeting links and description are not fetched. The cancellation status is used to decide which events to notify.
• The event name is shown in the actual bubble. Events and the latest notification text are kept in memory until the next update or disconnect, or until Chrome or the extension is closed, reloaded or updated. The event name is not embedded in the general watching history; only the fact that syncing or notification happened is recorded. Because events are fetched again after startup, event notifications cannot be used while there is no connection.
• To prevent duplicate notifications after a restart, it stores, for up to 7 days and 120 entries, values obtained by one-way hashing the event ID, start time and notification slot with SHA-256, together with the notification time. The event ID and event name themselves are not included in this record. This is not a mechanism for storing events in encrypted form.
• “Disconnect” stops fetching and notifying events and deletes the stored events, the latest notification text and sync information. It also removes event bubbles shown in other open tabs. So that event names from older versions do not remain, it erases the entire general watching history, including records unrelated to events, and leaves only the record of disconnecting. Growth state, the album and weather settings remain.
• In v0.7.49 and earlier, events and notification text were also stored in the device's persistent storage. After updating to v0.7.50, they are moved to memory at the first state load and deleted from the extension's current persistent data. The general watching history, which may contain past event names, is also cleaned up once. Growth state and the album are not affected. This does not guarantee erasure of backups separately made by the OS or the like, or of deleted areas on the disk.
• Authentication credentials for Google are handled through Chrome's authentication feature, and HTTPS is used for authentication and API communication. Mimon does not write access tokens into its own storage. “Disconnect” also clears the authentication cache inside Chrome, but this is separate from revoking the access permission on the Google account side. To revoke the permission as well, remove Mimon's access from your Google Account connections management.

Purpose of data use and Limited Use

Mimon handles data in accordance with the Chrome Web Store User Data Policy and the Limited Use requirements of the Google API Services User Data Policy. Abstract browser-operation counters are used only for growth, and information received from Google Calendar is used only for event notifications.

Google Calendar information is not sent to the developer's servers, sold or transferred to third parties, or used for advertising, credit evaluation or training general-purpose AI models. There is also no mechanism by which the developer can view the contents of events.

Explanation of the Chrome Web Store User Data Policy / Google API Services User Data Policy

About weather and location

• It is off by default. Google sign-in is not needed to use weather. If you agree to the explanation with “use weather at my current location”, your current location is obtained with the location features of Chrome and your OS.
• You can also set it manually with “choose a region”. While a region is chosen by hand, location is not obtained. It switches to the current-location method only if you agree to the explanation with “return to current location”.
• The obtained coordinates are converted into a forecast area in Japan on the device, and Mimon does not store precise coordinates or movement history. The forecast area, the latest forecast, the fetch time and the dates already notified are stored on the device.
• When fetching weather, it requests the data corresponding to the forecast area from the Japan Meteorological Agency. Ordinary communication information such as the connecting IP address reaches the destination. Mimon does not send precise coordinates to the Japan Meteorological Agency.
• Obtaining the current location may involve communication with the location service providers of Chrome and your OS. The privacy policy of each provider applies to that processing.
• Fetching is not constant tracking; it is done as needed at startup and periodic checks. While a valid forecast exists, the attempt interval is in principle 3 hours, and when there is no valid forecast the minimum interval is 30 minutes. With an explicit action such as the retry button, it tries to fetch immediately.
• “Stop” halts fetching and deletes the saved region (including a manually selected one) and forecast. So that turning it on and off does not cause repeated notifications, the dates already notified for morning, noon and night are kept. Growth and weather by manual selection can be used without allowing location.

Source: JMA weather forecast (Japan Meteorological Agency). Mimon displays the published forecast with Mimon's lines added. The region-determination data is created by processing the regional boundaries and names of the Japan Meteorological Agency. This is not an official service of the Japan Meteorological Agency.

Provision to third parties

Growth data and operation counters are not sold to third parties or provided for advertising purposes. The communication destinations and information needed for the optional features are described in the Google Calendar and weather sections above.

How to delete data

• If you remove Mimon on Chrome's extensions page (chrome://extensions), the stored data including the album is deleted as well and cannot be restored.
• If you delete the Chrome profile where it is stored, the growth state and album inside it are also lost. There is currently no transfer, export/import, backup or restore feature, and it cannot be restored by reinstalling or reconnecting to Google.
• To delete only the weather region and forecast, turn weather off.
• To delete event data, press “Disconnect” in the Google Calendar section. For what is deleted and for permissions on the Google side, see “About the Google Calendar connection” above.

About permissions

• storage: to store growth state and settings on this device.
• alarms: for periodic updates of growth state and for checking calendar reminders.
• identity: for OAuth authentication when connecting Google Calendar (used only when connecting).
• geolocation: to obtain the current location when the current-location method of weather is chosen. It is not used while a region is selected manually.
• offscreen: to convert the current location into a forecast area in a temporary hidden page. It is closed after processing.
• scripting: to show Mimon again in ordinary open tabs after an extension update.
• Host access (all sites): to display and raise Mimon in step with browser operations (clicks, scrolling, key presses and so on). The contents of pages themselves are not read.

The public site and inquiries

When viewing mimon.jp, ordinary communication information such as the connecting IP address and the page accessed reaches the site's delivery destination and may be recorded in logs for delivery and security. This does not send the growth state, album or events inside the extension.

If you inquire by email, we receive the sender's email address and the body and attachments, and use them to respond. You do not need to send event contents or authentication tokens. For screenshots that include personal information, please hide the parts that are not needed.

Changes to this policy

The content of this policy may be updated along with the addition of features or changes in specifications. When there is an important change, the last updated date of this page will be updated.

Operator information

Operated by: wwwn_lab

Contact

For inquiries about Mimon, contact youst519@gmail.com.