1

Currently, I am using custom state to store data before displaying it to the front end. The data that I’m storing has a privacy setting.

So is it safe to do this? Also where can I see the custom state set on page while using Google inspect?

2

See Bubble’s warning:
While custom states are not visible to the users of your app directly, they are still not a secure way to store sensitive data. Keep in mind that any information you place in a custom state, including its default value, can be read by the user of that device.

Others may be able to point to precisely where you can see a value using the browser’s developer functions. As your question implies, if it’s possible for you to see custom state values via a browser function, then it’s possible for any user to do so.

3

Thank you for the reply.

But I wanted to know where and how I can see the state storage from google inspect.

1 Like
4

If this is even possible, it’s because your privacy rules aren’t secure enough.

Privacy rules are all that protect your user data in Bubble - if you are worried about them being able to see it in a custom state, then they can see it anyway with a bit of technical knowledge if privacy rules have granted them permission.

So, for any data that is private, use privacy rules, or put it in the backend. It’s visible even if you don’t display it on the page in a state/search/group/repeating group…

1 Like
5

Well most of my data can be accessed by the user who created it. Others can’t access it.

All i wanted to know is in google inspect where can i see the page custom state stored.

6

If it’s protected by privacy rules, it won’t be visible in the custom state :slight_smile:

1 Like