# Privacy rule based on Current User's email address not possible

**URL:** <https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299>\
**Category:** Need help\
**Created:** [October 23, 2024, 9:26am UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299 "2024-10-23T09:26:36Z")\
**Posts on this page:** 6\
**Page:** 2

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [October 24, 2024, 12:38pm UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/21 "2024-10-24T12:38:01Z")

</div>

> [@georgecollier](#):
>
> content may be hidden on page load even if no server side redirect

Hidden how? You mean not loaded yet from a search?

> [@georgecollier](#):
>
> sensitive data stored in option sets

Interesting, I’m guessing you’re running some sort of Claude or GPT analysis on this? It can be pretty subjective.

---

<div class="post-metadata">

**Author:** ![georgecollier](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/georgecollier/32/182327_2.png) [@georgecollier](https://forum.bubble.io/u/georgecollier)\
**Post date:** [October 24, 2024, 12:38pm UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/22 "2024-10-24T12:38:39Z")

</div>

> [@randomanon](#):
>
> Hidden how? You mean not loaded yet from a search?

You can securely have a client side redirect so long as the page’s content is invisible by default, and made visible by a server-side condition.

> [@randomanon](#):
>
> I’m guessing you’re running some sort of Claude or GPT analysis on this?

Yes, among other things

---

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [October 24, 2024, 12:42pm UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/23 "2024-10-24T12:42:36Z")

</div>

> [@georgecollier](#):
>
> You can securely have a client side redirect so long as the page’s content is invisible by default, and made visible by a server-side condition.

When you say “visible” do you mean literally the “is visible” condition? My understanding was that conditionals have no effect on what’s loaded since it’s purely clientside. Meaning if the group is invisible on load and the condition says “Visible if Current Users’s Role is Admin,” someone can still see the group using dev tools.

---

<div class="post-metadata">

**Author:** ![georgecollier](https://sea1.discourse-cdn.com/bubble/user_avatar/forum.bubble.io/georgecollier/32/182327_2.png) [@georgecollier](https://forum.bubble.io/u/georgecollier)\
**Post date:** [October 24, 2024, 12:53pm UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/24 "2024-10-24T12:53:41Z")

</div>

Basically, it’s complicated.

Hidden elements _can_ be downloaded, even if there is no condition to ever make them visible (or no show group / toggle group).

It’s not clear exactly when, but Bubble does this to pre-cache element loading. That’s why switching screens on SPAs is generally so fast.

Exactly how much is pre-cached I cannot work out or reliable replicate, so you have to search static.js to see if your element is being loaded on the page load and verify it’s secure that way.

Edit: That said, I have not worked out yet to what extent that permits users to take actions, even if they can see the elements (i.e it’s not necessarily problematic if they can see what elements are on an admin panel, so long as they cannot execute workflows inside of the groups that should be invisible)

---

<div class="post-metadata">

**Author:** ![randomanon](https://avatars.discourse-cdn.com/v4/letter/r/8491ac/32.png) [@randomanon](https://forum.bubble.io/u/randomanon)\
**Post date:** [October 24, 2024, 1:00pm UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/25 "2024-10-24T13:00:04Z")

</div>

Hmm… I think I’ll stick to server-side redirects and workflow conditions. Would love to see a list of known insecure plugins though, think that would be of great benefit to the community.

---

<div class="post-metadata">

**Author:** ![system](https://us1.discourse-cdn.com/bubble/original/3X/2/8/2847faa74692c2ffa5d939d3dc3724cdd060d247.png) [@system](https://forum.bubble.io/u/system)\
**Post date:** [January 1, 2025, 9:27am UTC](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299/26 "2025-01-01T09:27:09Z")

</div>

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

[Previous page](https://forum.bubble.io/t/privacy-rule-based-on-current-users-email-address-not-possible/345299.md?page=1)
