# Client side encryption **URL:** \ **Category:** Ask for Help\ **Created:** [September 18, 2022, 1:58pm UTC](https://community.glideapps.com/t/client-side-encryption/49577 "2022-09-18T13:58:52Z")\ **Posts on this page:** 1\ **Showing post:** 3
**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:** [September 18, 2022, 10:36pm UTC](https://community.glideapps.com/t/client-side-encryption/49577/3 "2022-09-18T22:36:37Z")
The following thread could be of interest to you. > [@App Security Questions](https://community.glideapps.com/t/app-security-questions/47393/3): > > Key phase here is that data isn’t downloaded to the device…meaning that it can’t be used by the app. And really, there isn’t anything preventing the developer from turning off the protection and viewing the data. I think it’s more useful in cases where you have an existing table with columns that should not be used by an app, for example, like in the U.S. where we should never share an SSN or Tax ID. If you happen to have an existing table of data that contains a tax id, but is not needed by… --- _[View the full topic](https://community.glideapps.com/t/client-side-encryption/49577)._