can anyone from zeroqode answer?
@xtechaus Yes and yes to both questions. This is Bubble forum. You can go to to Zero forum of you need more info.
Bump! After extensive testing and back and fourth with Zero’s support, their plugin in fact IS NOT able to decode data that is encoded in a database.
STILL LOOKING, I WILL LITERALLY PAY LIKE $100 FOR THIS I AM GETTING SO FRUSTRATED.
How do big companies on bubble let their users know they can see all their data?
Sorry to chime in, but your claim is just NOT true. The Zero plugin does allow you to encrypt and decrypt data from your database. I’ve been using it in my app for nearly two years.
If you don’t know how to set this plugin up thats ok, but giving false statements about the app is not fair.
I suggest you start with the basics or find someone in Bubble to help you out. It isn’t very difficult to use or setup so you shouldn’t have a problem. I also recommend you look at the example Zero code have available in their forum so that you can look at how it was setup.
it’s not a false statement, bubble.io literally cannot decode something in a workflow that is in a repeating group. Yes you can get data from a repeating group and decode it in a text box in a normal group (maybe), but you CANNOT decode inside a repeating group and output the decoded info in that same group.
will pay $50-$100 if anyone can help me with this, serious issue.
You should decrypt iteratively Using the listshifter or orchestra plugin
I made this plugin for myself https://encrypt-decrypt-lists.bubbleapps.io/version-test
where the project required to encrypt lists of messages in the DB to go in a repeating group. (eg these were chat messages). It’s really no different to all the other Encryption/Decryption plugins except it takes lists - which is what you need for Repeating Groups.
Otherwise I’d have to do what @jared.gibb suggests which is totally viable.
The example page shows you how you might show a list of decrypted messages in a repeating group (using server side actions, custom states). All the other caveats and warnings folks are advising in this thread hold true. At the end of the day, your secret key is in Bubble itself, where you are also storing the data.
If you really want to understand Bubble security - read @petter security book.
The security architecture that is closest to providing good guarantees of data privacy on the Bubble database is to only ever process encryption and decryption on the client side. And even then you could still write your app to send clear text data back.
Unfortunately this architecture requires the user to carry a second secret, either a password, or key. If they loose or forget their secret Bubble password then there is no hope of recovery.
If you don’t want your Bubble devs or admins to see certain data in clear text then you CANNOT run encryption or decryption on the server as all action inputs are logged.
I would suggest requesting Bubble add a
private checkbox on fields that triggers the field to be encrypted with the user’s password. For this to function Bubble would need to automatically recycle the encryption of those fields on password change, and would have to never log those values. This would go a long way towards gaining HIPAA compliance.
Realizing that the user’s password is captured clear text on the client-side, it is possible to individually encrypt fields using the user’s password. Here is how on-boarding works:
- Capture the user created password on the client-side in the usual way
- On the client-side generate a public-private key pair with the private key encrypted by the user created password.
- Store both keys in the database.
- You can now safely encrypt and store private fields using the public key, making sure to run encryption on the client-side to avoid writing sensitive data to the logs.
- To decrypt, again capture the user’s password client-side, use the password to decrypt the private key, and then use the decrypted private key to decrypt the fields.
When a password is changed you will have to re-encrypt the private key on the client-side and then store the private key. The good part about this architecture is that you can always add encrypted information without a password, you just can’t retrieve it. As an added layer I would also recommend encrypting the private key using the users password salted with a random value that you also store in the database.
Again @xtechaus, that’s just not true. You can do this with the Zeroqode plugin. I do this on my app across many areas. You can see the oficial example for the plugin here,
There is an option in the plugin to automatically encrypt or decrypt several values in one go. Very useful for lists or dropdowns, etc.
Thanks for all the response guys, I will check this stuff out and hopefully make my data safer. Does bubble.io give refunds for plugins?
That login in as function is a nightmare when you start working on anything that requires encryption.
Hi, I am new to the forum. Are the privacy rules that are included in the data tab solving the problem here? (they are new arent they?)