Senchan Company
JP

Privacy Policy

Last updated: September 17, 2026

Misete shows the keys you press on screen and keeps a record of your typing. Doing that needs Input Monitoring — permission to see every keystroke on this Mac — so this page says exactly what happens to what it sees.

Nothing Misete observes leaves your Mac. There is no account, no server, no analytics, no crash reporting, and no third-party SDK of any kind.

What is kept

What Misete writes to disk is counts.

  • How many times each physical key was pressed, by key code — so A and ⌘A are the same key, and no word you typed can be reconstructed from it.
  • How many presses happened on each day, and in each hour of each day. The hour and nothing finer: an hour is a rhythm, a timestamp is an order, and the order is what would make a sentence recoverable.
  • How many times each shortcut was used, recorded as a modifier-plus-key-code pair (for example ⌘:8), never as a sequence.
  • How many times each mouse button was clicked, and how far the cursor travelled, as a single distance.
  • How many minutes of each day had any input in them at all. The count, and not which minutes those were.
  • While 利用アプリを記録する is on, how many minutes, presses and clicks each app accounted for. Apps are recorded by bundle identifier — an id like com.apple.Safari. The switch is off until you turn it on, and nothing is recorded before you do. Those three numbers are all an app gets: not which keys you pressed in it, and not what time you were in it.

What is not kept

The following is not merely unsaved — it does not exist in the app at all.

  • The text you typed. Nothing that is typed is written down anywhere, and nothing assembles it into words. There is one exception worth describing: Japanese input is drawn as kana, so typing s, then h, then i has to hold those letters until they complete し. Those one or two pending letters live only in the code that draws the overlay, are never handed to the statistics, are never written to disk, and are discarded the moment the composition ends, a non-letter is pressed, or you switch apps. Nothing longer than a single kana’s worth of romaji exists at any point.
  • Where you pointed. The event tap turns two cursor positions into one distance before anything downstream sees them, and the type that carries pointer events has no way to express a coordinate.
  • Anything typed while a password field has the keyboard, or while an app you have excluded is frontmost. Both are dropped before they are displayed and before they are counted — and before the app record too, so an excluded app never appears in it either.

Where it is kept

Your records and your settings sit inside the app’s own sandbox container (~/Library/Containers/com.misete.app/Data/Library/Application Support/statistics.json). Nothing is written outside it, and no other app can read it.

Deleting it, and taking it with you

  • 設定 > 記録 > 消去 removes the record immediately. You choose what goes — the key record, the pointer record, time with your hands moving, the app record — and over which days. Deleting the app removes its container and everything in it.
  • What is erased is gone. A row saying when you erased, what you chose and over which days stays in the erase history, so 「消したっけ」 has an answer; what was in those days is not part of it. The history lives in Misete’s own settings, is never written into an export, and 履歴を消す removes it.
  • 設定 > 記録 > 書き出す writes your statistics out as a JSON file, and 読み込む reads one back. It is there for moving to another Mac, and for keeping a copy before erasing. The file holds the aggregates this page describes and nothing else — there is no shape in it that could carry what was typed, or the time of day to the minute. The file goes where you put it, and Misete never sends it anywhere.

Permissions

  • Input Monitoring is required. Misete’s event tap is listen-only: it can see keystrokes but cannot alter, delay, or swallow them. You can withdraw the permission at any time in System Settings.
  • Misete never connects to anything. It declares com.apple.security.network.client because macOS will not start WebKit’s helper processes without it, and the statistics window is drawn by WKWebView. The page it displays is inside the app bundle; every navigation away from it is cancelled, and the page’s content security policy blocks network requests outright.
  • No analytics, no tracking, no accounts. Misete contains no analytics SDKs or crash reporters, and never asks you to create an account.

This policy governs for Misete. For how information collected in connection with an app purchase or an enquiry is handled, see Senchan Company’s privacy policy.

If this policy changes, the updated version will be posted at this URL.

Contact

OperatorMasahiro Senda
Contactsenchan.company@gmail.com
© 2026 Senchan Company
ContactNotice Based on the Act on Specified Commercial TransactionsPrivacy Policy|NewsAbout Senchan Company