How can this happen?

The "archive" and the source / main database are two different files.  It appears that local databases are kept here

/Users/<user name>/Library/Containers/de.ninoxdb.ninox-mac.Ninox/Data/Documents/data

So.. if you are not sharing user accounts.. you "might" be ok.. If you are really worried about it.. Hmm.. look for a plan B.. ;) 

The new version 2.5 supports a database password. 

Awesome!  Will have to scope it out! 

Here is a snapshot from the BETA test...   I am not sure if this is a "feature" ... So, it appears that you can "protect" the database.. but logging out.. then back in.. at least as the same user.. I can simply open the database again.  When I want to configure the database.. then it prompted me for the password. 

You’re right. Seems like this is a sort of protection for the code. not the whole database. should it be possible to insert a dialog box with a pasword in the trigger after open code? 

I thought there was going to be a "default" form on open.. I will have to puruse the beta and support site to see if that made it into the version.   

In the "trigger after open" maybe open the form could be a solution?

As the creator of your db you are automatically the admin, thus you are allowed to open and work on your database. The new password feature is meant to protect the data model of your database. If several users work on your database you are able to create several rights and roles in the Ninox Cloud. Is it what are you looking for? You are also able to hide tables, which can be unlocked just by the admin mode, which can be now protected by the new password feature. 

I’ve made a workaround this problem. See 60_Protected_With_Password in webinar_EN.

Also made use of default form on open with trigger after open in the option menu of the database.