What the app knows about you

macOS calls the permission Screen & System Audio Recording, and asks for it before any app may read what is on your display. Mika+ScreenSnap needs it for one thing: to take the screenshot you asked for. It records no video and no audio. Every capture is a single still image, taken at the moment you press a shortcut or choose a command in the menu bar — never in the background, never on a timer.

What is captured. The pixels of the region you chose: the whole display, an area you drag, or a window you click. Nothing else is read, and nothing about your other apps is recorded. Windows belonging to apps on your exclusion list are removed from the picture before the app ever sees it.

What it is used for. Showing you the capture, letting you annotate it, and saving or copying it — that is the whole purpose. Text recognition (OCR) and the colour picker work on those same pixels, on your Mac, using Apple's Vision framework. Screen data is never used for analytics, advertising, profiling, or training any model.

Who it is shared with. Nobody. There is no server, no third-party SDK and no analytics provider to share it with. Captures leave your Mac only if you send them somewhere yourself. Nothing is uploaded, and the app has no code that would be able to do so — you can verify this in the source.

Where it is stored. On your own Mac, in the folder you pick during setup, with a small preview image beside it in a .thumbnails subfolder so the history window has something to show. Pinned screenshots are held in the app's own Application Support folder until you close the pin. Recognised text and sampled colours go to your clipboard and are never written to disk. Your settings live in the app's preferences; they contain no image data.

How long it is kept. For as long as you keep the files, and no longer. The app expires nothing behind your back and keeps no second copy: the history window is a view of your save folder, so a screenshot exists until you delete it — in that window, or in the Finder. Delete all there removes every image in the folder along with the thumbnails. Closing a pinned screenshot deletes its stored image immediately. Captures you never save are held in memory only and are gone when you close the editor.

The app collects none. No usage statistics, no crash reporting, no identifiers, no cookies inside the app — whichever way you installed it.

One thing changes if you install from the Mac App Store: Apple then collects its own crash reports and usage figures for this app and shows them to the developer in aggregate. That happens only if you have allowed it under System Settings › Privacy & Security › Analytics & Improvements, it is Apple's collection rather than the app's, and the developer never sees anything that identifies you. The direct download has no equivalent. We mention it because “collects nothing” would otherwise be quietly untrue for App Store users.

To check for updates, the app asks GitHub for a small release feed at raw.githubusercontent.com. That request tells GitHub your IP address and the app version, in the same way visiting any web page would. Sparkle's optional system profiling is not enabled, so no hardware or usage details are attached. Downloading an update fetches a file from GitHub Releases.

The App Store version does not do this at all: it contains no updater, and makes no network connection of its own. Updates arrive through the App Store.

Only Screen & System Audio Recording, which macOS requires before any app may read the contents of your display. It is used solely to take the screenshot you asked for. Despite the name of the permission, the app captures no audio and no video — it has no code for either.

It asks for nothing else: no camera, no microphone, no location, no contacts, no accessibility access, and no account of any kind.

The site is a set of static pages hosted on Vercel. It sets no cookies and runs no analytics or tracking scripts. Vercel records standard server request logs, which include IP addresses, as part of operating the hosting service.

If any of this ever changes, it will change here first, and the commit history of the repository will show exactly when and why.