Privacy rules: restrict built-in fields?

Questions
1

With respect to privacy rules, is it worth it to go the extra mile and case by case check or uncheck bubble’s built-in fields?

So I do not use bubble’s built-in fields in my app’s logic or UI for most of my tables.

This makes me wonder if it is worth unchecking these fields in the privacy rules.

On one hand this would follow the principle of least priviliege, but on the other hand it makes maintaining privacy rules more complex.

I believe exposing these fields shouldn’t be insecure if everything else is properly setup.

What is your recommendation?

2

If it doesn’t make much of a difference, why not have privacy rules in place for the built-in fields as well? It might not be that big of an effort unless I might be missing something. The reason I say this is that you never know, depending on the app or use-case, whether the data contained in the Created or Modified date/user fields would be relevant or not.

3

You’re right, if it isn’t that big of an effort, it is worth it to further protect your data.

Thanks!