Does the OS X log notifications from the Notification Center? The helpful companion to the OSX notifications center Growl per default logs all received notifications. You can define how big the log may get or disable logging in the application.

Since the latest update Growl offers to forward all notifications to the OS X Notification Center.

Does OS X log Notifications Center messages as well? If yes, where can I find them?

Why I am asking this:

OS X logs all your downloads in a SQLite 3.x database. I want to know if something similar happens with notifications as well. This could be a privacy issue when thinking of private messages or e-mails if too much information is stored.
This is an old question, but just in case someone stumbles on it and is specifically worried about the privacy implications of Notification Center, the answer is YES, OS X does keep a log of notifications on disk.

The format is an sqlite database, and it can be found inside this folder:

~/Library/Application Support/NotificationCenter


Inside you'll find at least one .db file for your account, i've seen some that OS X apparently considered corrupt at one point, so they're called .db.corrupt.

Running the strings command on this file will show you a load of binary data, quite a few "NSSomething" class names, and yes, your iMessages, file paths, twitter and facebook notifications and anything else that was sent to Notification Center by an app or the system.

If you want to get rid of that file at a specific point in time, you can kill usernoted temporarily (it'll restart itself) and delete the file in one shot (run this as your user account, not with sudo):

killall usernoted &amp;&amp; rm ~/Library/Application\ Support/NotificationCenter/*.db


This will, 99% of the time, catch usernoted while it's temporarily not running, successfully delete the old database, and usernoted will make a new empty one when it starts again.

This isn't a good solution if you're really worried about privacy, but aside from encrypting your system or using a ramdisk for that folder, there really isn't a solution.