# Session fields "cookies" stored on local device **URL:** \ **Category:** Feature Requests\ **Created:** [September 20, 2022, 1:12pm UTC](https://community.glideapps.com/t/session-fields-cookies-stored-on-local-device/49719 "2022-09-20T13:12:22Z")\ **Posts on this page:** 3\ **Page:** 1
**Author:** ![David\_Gabler](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/david_gabler/32/44332_2.png) [@David\_Gabler](https://community.glideapps.com/u/David_Gabler)\ **Post date:** [September 20, 2022, 1:12pm UTC](https://community.glideapps.com/t/session-fields-cookies-stored-on-local-device/49719/1 "2022-09-20T13:12:23Z")
With the change in update pricing, it has become imperative for Glide to find a way to store “session variables” – which would be User Specific Columns (USC) – on the local device, never to be synced with the databases. This is not just for swipes, though that is the scenario most frequently given. I have apps that use USC to track menus and “last field used” – to make data entry easier for the user. In addition to avoiding updates for what are essentially session cookies, it avoids the need of having to purge these types of fields as users drop off – delete the app from their device or whatever. I know a LOT of Gliders like to use session cookies for visibility conditions. For example, I have a custom form that “pops up” (all other tabs are hidden) to notify users of a special event on a day. Once the date is passed, or they “dismiss” the window, it does not show again. The “dismissed” is stored in a USC, but there is no reason for it to be stored in the database. Please implement “session cookies” that can be controlled and referenced by the App or Page. Even “favorited” columns “is favorite” should be able to be stored as session cookies. Think about an app that is used for a conference. Once the conference is over; most users will delete the app from their devices. But that app can be re-purposed for the next conference and not have the baggage of all the orphaned USC from conference to conference. It just makes sense. Here is another use case – custom advanced search filters… > [@How to build a custom advanced search filters?](https://community.glideapps.com/t/how-to-build-a-custom-advanced-search-filters/47061/10): > > But, USC columns actually are synced to the server. They are stored internally in Glide’s database. They are not stored locally on the device. There is a gray area if the user is not signed in, but it’s my understanding that even if a user is not signed in, the USC columns are still communicating with the database, so it still causes updates. Think of USC columns like an invisible table that contains a Row ID, Email, and the stored Value. When you create a USC column, glide is essentially … ---
**Author:** ![Jeff\_Hager](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/jeff_hager/32/43_2.png) [@Jeff\_Hager](https://community.glideapps.com/u/Jeff_Hager)\ **Post date:** [September 20, 2022, 5:27pm UTC](https://community.glideapps.com/t/session-fields-cookies-stored-on-local-device/49719/2 "2022-09-20T17:27:21Z")
> [@Session Variable Column](https://community.glideapps.com/t/session-variable-column/40260): > > I’ve always thought that it’s really useful how user specific columns only store values locally and for the duration of your session while you are not signed in. This allows for those column values to “reset” after you close the app, and the data does not need to be sent and synchronized with glide servers. However, once you sign in, then those values are sent to, and stored, on Glide’s servers. I think a new Session column type could be really useful. It would work just like user specific c… ---
**Author:** ![system](https://sea2.discourse-cdn.com/flex002/user_avatar/community.glideapps.com/system/32/53398_2.png) [@system](https://community.glideapps.com/u/system)\ **Post date:** [September 21, 2022, 5:27pm UTC](https://community.glideapps.com/t/session-fields-cookies-stored-on-local-device/49719/3 "2022-09-21T17:27:47Z")
This topic was automatically closed 24 hours after the last reply. New replies are no longer allowed.