Creating a windows 10 clock in / clock out app -- 2

Hello. I am looking to have a simple clock in / clock out application that will run in windows 10. It would be set to always run in the background and would be used to help a employee visualize their hours of when they work and when they don't. Here are the specs for the app so far: 1: As soon as a machine is logged in to you are greeted with a popup that can't be dismissed or minimized and it is on top of everything. The popup will say: "Good morning/afternoon/evening WindowsUserName" and present you with a big clock-in button and another small button in the bottom left corner that says "off the record". Clicking these buttons is the only way to make the popup go away. 2: Whenever there is no movement or keyboard usage for 15 minutes (this is a variable we can change in settings) the window will pop up and say: "you have been away for xx minutes, what was your primary activity?". And then it will display something like away.png. These button options would all be definable in a centralized settings file. 3: Whenever you are not using the computer for 3+ hours (definable in settings) it will assume you clocked out at the beginning of the period of no computer usage. Next time you log in or start using the mouse it will show the clock-in popup again. 4: At any point you can click on the application on the system tray and see the past 30 days. Each day will have a couple stats and will show something like [login to view URL] to show you when you were working and when you were away. The stats would be "hours working: xx" and then also list the other other things like the amount of time using the bathroom or the amount of time in meetings and whatever we have defined in away.png. 5: In this last view showing past history you should also be able to customize the range shown with two calendar selections at the top of the screen. Employees can see stats about themselves but not any stats about other employees. We would need a admin interface where someone can view anyone's stats from a different computer. So maybe we need a centralized database to store all of this employee information so that admins can also view the data from anywhere else. The admin interface would basically look just like the interface we want to show in #4, but there would be a dropdown up top to let you select what employee you want to view. This app will need to be extremely stable because it will be running 24/7 on at least 70 computers. The code will be reviewed by in-house developers here.