Privacy Rules & Chrome Dev Tools

Hello - a couple questions regarding privacy rules & dev tools.

I am trying to hide data from dev tools but still make it accessible within my Bubble workflows…

Does anybody know if this is possible? Essentially I want to hide data when inspecting via dev tools but still have it accessible within Bubble workflows… Are there any privacy rule configurations that enable this? Alternatively, maybe there is some DB setup/links that would make this doable? Let me know.

Thanks

Hi @Bennn,

What you are looking for is Backend Workflows. You can schedule these API workflows to run immediately from the frontend or use the Bubble API connector if you need to return values from the API workflows.

There are no privacy rules that hide data from dev tools; dev tools can inspect any data that is retrieved by the frontend.

1 Like

Hi -

I’m not sure how this solves the problem. If I schedule a BE workflow, the parameters sent to the workflow would still be discoverable via dev tools, right?

Is all data retrieved from the server accessible to the user no matter what?

Yes, the parameters will be visible in dev tools, but you shouldn’t have parameters that expose private data. Private data should be hidden by privacy rules, and only available to the backend workflows where appropriate.

Within the backend workflow itself, you can manipulate the private data without exposing any of it to dev tools.

This topic was automatically closed after 70 days. New replies are no longer allowed.