Generate a secure encryption key for your self-hosted Password Pusher instance.
Password Pusher encrypts all sensitive data in the database using a master encryption key. While a default key is provided for convenience, using your own unique key provides the highest level of security for your private instance.
A default key is used if none is provided. This works but is less secure than a custom key.
Using short push expirations (e.g., 1 day/1 view) reduces risk even with the default key.
Once a push expires, all encrypted data is permanently deleted from the database.
Changing keys makes existing pushes unreadable. New pushes will work normally.
You can also generate keys from the command line in the application source:
For detailed configuration options and deployment strategies, see the Configuration Documentation .