Keron collects nothing.

To replace a system banner, Keron has to know what was in it. Using the Accessibility permission you grant, Keron observes the macOS Notification Center process and reads the banner's app name, title, message text and app icon at the moment it appears.

That content is held in memory only, for exactly as long as the banner is on screen. It is used for one thing — drawing the replacement banner — and it is discarded when the banner dismisses. Keron never writes your notification content to disk, never keeps a history of it, and has no mechanism to transmit it.

Keron saves your configuration locally, and nothing else:

• Your settings and designs — banner designs, placements, app groups, presets and preferences, in the standard macOS preferences store under com.nimaigoswami.Keron.
• App names — the names of apps you've added to a group, so Keron can match their banners. These are app names, not their contents.
• Custom sounds — audio files you import are copied to ~/Library/Application Support/Keron/Sounds so a design keeps working if you move or delete the original.
• Custom background images — likewise copied to ~/Library/Application Support/Keron/Images.

All of it is yours, on your disk, readable by you, and removable at any time — see the uninstall instructions.

Keron keeps a short diagnostic log — at most the last thousand entries — describing what the notification engine is doing. It lives in memory and disappears when you quit.

Nothing is written to disk unless you explicitly choose Save Log… and pick a location yourself, which exists so you can attach a log to a bug report. It is never uploaded, and there is nowhere for it to be uploaded to.

If you turn on Pause during Focus, Keron needs to know whether a Focus mode is currently active. macOS exposes no public API for this, so Keron reads your own Focus configuration on your Mac, read-only, and caches the answer for about a second.

It checks one thing: whether a Focus mode is on right now. It does not read which one, your schedules, or anything else in that store, and nothing about it is saved or sent.

Keron runs outside the macOS App Sandbox. It has to: observing the Notification Center process through the Accessibility API and checking Focus state are both things the sandbox forbids, and there is no sandbox-compatible way to build this app.

That's a meaningful amount of trust to ask for. Keron is built with the hardened runtime enabled, which prevents runtime code injection and restricts the process to only the entitlements it explicitly declares.

When you export a theme, Keron writes a self-contained .json file that embeds the design along with the actual bytes of any custom sound and background image you used — that's what makes it work on someone else's Mac without extra steps.

A settings backup likewise contains your designs, placements, app groups and the names of apps in them. These files are created only when you ask for them, saved where you choose, and shared only by you. Keron doesn't upload them anywhere. Bear in mind that anyone you send one to can see what's inside it.

keron.app is a set of static files. There are no cookies, no trackers, no analytics, and no third-party resources — every font, style and image on this page comes from this domain. Your light/dark preference, if you set one with the switch in the header, is stored in your own browser and never sent anywhere.