Allow users to easily check if a backup of their db is needed.

See -

But, in a nutshell, a backup of the db is really only needed if data such as passwords (ciphers) are altered. Data about users logging in and out does not really meet the threshold of a meaningful change to the db warranting a backup. Most days the tables "diesel_schema_migrations" "twofactor_incomplete" "event" and "devices" are altered as vw is used. While days or weeks can go by where the other tables don't change.

A new table could be added to the db that tracks meta data about the db. One of the columns could store a unixepoch value. When a change in a table worthy of making a backup occurs (most tables would meet this criteria) their triggers would update the unixepoch value.

A user could then know when they should perform a backup just by comparing the time of their last backup and the current value in the new column.