This seems like the end result of one of those "chatgpt - make me a business" online courses. There's no information about who's behind it, AI generated content everywhere, etc.
But standardized and verified digital encryption routines are available in modern operating systems to make strong cryptography experience available and accessible to the average developer.
A strong password and strong encryption is enough. The presence of 'blindlock' on a device is a clear indication that one of your files is a wallet. Phoning home to do a licence check is EVERY time you use it is obnoxious and defeats the purpose of having local software.
The question is, have you done something so unique and challenging that your website itself wouldn't serve as a prompt to rebuild the whole thing? Would I spend less than $49 doing so?
I built something similar years ago to use for a password vault --- data hidden locally in plain sight.
Instead of steganography, I simply appended the encrypted data/payload to the end of a JPG file in my photo library. The file opens and displays normally.
Part of the photo/carrier file is used as salt for decryption. The part that is used changes randomly based on the last modification time/attribute of the file. The file creation time (displayed in a normal directory list) is maintained/doesn't change with payload modifications.
Encryption is also tied to disk parameters so a simple file copy makes the data unreadable. The access utility can be used to move the file and re-encrypt the data on a different disk.
A labeled section of the payload data/vault holds TOTP keys so the access utility can also function as a 2FA authenticator.
>A vibe-coded password manager? Sign me up!
What's your security/cryptography background?
But standardized and verified digital encryption routines are available in modern operating systems to make strong cryptography experience available and accessible to the average developer.
A strong password and strong encryption is enough. The presence of 'blindlock' on a device is a clear indication that one of your files is a wallet. Phoning home to do a licence check is EVERY time you use it is obnoxious and defeats the purpose of having local software.
Instead of steganography, I simply appended the encrypted data/payload to the end of a JPG file in my photo library. The file opens and displays normally.
Part of the photo/carrier file is used as salt for decryption. The part that is used changes randomly based on the last modification time/attribute of the file. The file creation time (displayed in a normal directory list) is maintained/doesn't change with payload modifications.
Encryption is also tied to disk parameters so a simple file copy makes the data unreadable. The access utility can be used to move the file and re-encrypt the data on a different disk.
A labeled section of the payload data/vault holds TOTP keys so the access utility can also function as a 2FA authenticator.