Dear Bubble forum community
I have a very specific data privacy issue on a client’s bubble app. I will pay 100USD to the first person to help me find a solution.
About my issue:
When doing do a search for workflows, the found data is downloaded to the users’ browser which means that even if they can’t visually see it they can find the matches if they know how to use their browser.
Normally, one would just make privacy rules in a way that the database doesn’t give these users that should see the data access to it using privacy rules. But since unregistered users have to be able to start a Twilio in browser phone call Plugin call, that needs to be activated by the user using a button to do a search. This needs to happen in some way, since the plugin otherwise doesn’t have the phone number it is supposed to call.
TL:RD the Twilio plugin has to be able to start a call without the data being downloaded and visible to the user starting the call.
Use a different plugin or build a new one, or pay someone to build a new one.
I’d be surprised if you can’t generate whatever connection info you need in the backend and then pass it to a plugin action in the front-end but I’ve never used said plugin.
I have reached out to the plugin developer and hoping it can somehow be done.
As the Twilio API is quite complex, I think development will be difficult but definitely a possible solution.
So @georgecollier gets the 100USD?
1 Like
Sadly I think doing backend actions with the Twilio API doesn’t work. But as I have said I really need a solution so if his is the one he will get it!
Backend API and returning the data will be the primary way to do what you’re asking if you’re trying to protect the rest of the data.
So this would mean making a Twilio plugin that supports starting calls from the backend? Is this even possible? As just sending the data from the API doesn’t work I am guessing as the Twilio Plugin still has to get the user data right?
Can you not just create an API connector call to Twilio get the info you need and return the relevant response fields using return data from API, and call that backend workflow from the front-end?
Thanks for all the help! I have just figured it out myself. I thought that the twilio call action was revealing the data when in reality it was the do a search action used to show or hide a button. So I think there should be a rather simple fix. I will get back to you once I have tested it!
How can I return data from the backend to the frontend? I know how to do it the other way around
Hmm. So now who gets the 100? 
