# Security issues with filtered data

**URL:** <https://community.glideapps.com/t/security-issues-with-filtered-data/43118>\
**Category:** Ask for Help\
**Created:** [June 15, 2022, 8:33pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118 "2022-06-15T20:33:42Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![lawsonk](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lawsonk/32/43869_2.png) [@lawsonk](https://community.glideapps.com/u/lawsonk)\
**Post date:** [June 15, 2022, 8:33pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118/1 "2022-06-15T20:33:42Z")

</div>

Hi! In the Glide library on the page about “filters” it says this below – and I don’t really understand – what exactly is the security concern with filtered data?

> Please note that filtering is not a security feature. If you use it, the app can still download filtered data. If your app has private or sensitive data then you should use Row Owners.

---

<div class="post-metadata">

**Author:** ![david](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david/32/62831_2.png) [@david](https://community.glideapps.com/u/david)\
**Post date:** [June 15, 2022, 8:37pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118/2 "2022-06-15T20:37:18Z")

</div>

With filtering, the information is only hidden in the app user interface. For example:

My secret password is hidden below:

> **Summary**
>
> `hunter1`

You can’t see it, but the data is still there. Clever people can figure out how to view any data your app downloads. If you use Row Owners, the data isn’t even downloaded, so nobody can see it no matter how clever they are.

---

<div class="post-metadata">

**Author:** ![lawsonk](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lawsonk/32/43869_2.png) [@lawsonk](https://community.glideapps.com/u/lawsonk)\
**Post date:** [June 15, 2022, 8:56pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118/3 "2022-06-15T20:56:08Z")

</div>

Got it! I’d certainly rather use ‘row owners’ if it’s safer… but it seems more complicated. So I was kind of wondering how unsafe the filter option is… seems like it’s still pretty safe overall just maybe not something you want to use for highly sensitive data.

---

<div class="post-metadata">

**Author:** ![nathanaelb](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/nathanaelb/32/43079_2.png) [@nathanaelb](https://community.glideapps.com/u/nathanaelb)\
**Post date:** [June 15, 2022, 10:10pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118/4 "2022-06-15T22:10:47Z")

</div>

You could approach it as follows.

“_If_ there were to be a data breach, or if the hidden data became unhidden and therefore viewable to unintended users, then would it be okay?”

- Yes, it would be okay. Annoying or a shame from a user experience standpoint, but it would be okay. → Filtering could be used

- No, it would definitely _not_ be okay. Huge no-no. → Filtering cannot be used. Row owners must be used.

---

<div class="post-metadata">

**Author:** ![lawsonk](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/lawsonk/32/43869_2.png) [@lawsonk](https://community.glideapps.com/u/lawsonk)\
**Post date:** [June 16, 2022, 2:16pm UTC](https://community.glideapps.com/t/security-issues-with-filtered-data/43118/5 "2022-06-16T14:16:49Z")

</div>

Thanks! That’s a helpful rubric.