# Online Ordering System **URL:** https://community.glideapps.com/t/online-ordering-system/21754 **Category:** Project Showcase **Created:** [January 26, 2021, 1:10pm UTC](https://community.glideapps.com/t/online-ordering-system/21754 "2021-01-26T13:10:30Z") **Posts on this page:** 1 **Showing post:** 30
### 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: [February 3, 2021, 4:31am UTC](https://community.glideapps.com/t/online-ordering-system/21754/30 "2021-02-03T04:31:26Z")
Well, that’s not true security. Someone could always connect the dots and figure out if a unique ID in one sheet matches a unique ID in a user sheet that contains Personally Identifiable Information (PII) of the user. Plus, that prevents you from being able to use row owners if you ever need it, since you would no longer have an email in the sheets. There’s nothing wrong with using IDs to link data, but don’t rely on it as a security feature. > **[Database Keys in Relational DBMS | Studytonight](https://www.studytonight.com/dbms/database-key.php#:~:text=Keys%20are%20very%20important%20part,may%20act%20as%20a%20key)** > > Database Keys are used to establish and identify relationships between tables and within a table. Primary key, Foriegn Key, Composite Key, Candidate Key and Super Key are all Database Keys. I use keys to link all of my tables together, but I only do that as a way to properly link database relations through keys since the unique keys will never change. I do not use that method as a way of securing data, as it only slightly masks the data. It does not make it secure. Once somebody figures out your methods of hiding data, then you can’t stop them from exploiting it. [https://securitytrails.com/blog/security-through-obscurity](https://securitytrails.com/blog/security-through-obscurity) > **[Security through obscurity](https://en.m.wikipedia.org/wiki/Security_through_obscurity)** > > Security through obscurity (or security by obscurity) is the reliance on secrecy as the main method of providing security to a system or component, specifically in security engineering, whether on design or implementation. > An early opponent of security through obscurity was the locksmith Alfred Charles Hobbs, who in 1851 demonstrated to the public how state-of-the-art locks could be picked. In response to concerns that exposing security flaws in the design of locks could make them more vulnerabl... As always, follow Glide’s recommended practices for security. Not only for your sake, but for the sake of your users. You would never want to have to explain that you exposed all of their personal data because you took shortcuts to save a buck or make something easier. Even large companies make this mistake. If there is ANY data that you have in your app that you do not want exposed to any potential other users of the app…please remove that particular data or properly secure it as recommended. This user found out the hard way that there is always someone out there that could potentially cause harm. > [@How can I protect my app’s user profiles?](https://community.glideapps.com/t/how-can-i-protect-my-app-s-user-profiles/19980): > > A random person online has downloaded my full user database right after receiving access to my app. He sent me the list of my users in a txt file - I was literally shocked. Thank God it doesn’t seem to appear “ransomware” but more of a lead gen tactic - he wants to sell me cyber security services. After a bit of research and chatting with a technical friend, he told me that he might have performed UserEnum tactics to reverse engineer all my sign-ups. He has also told me that this issue could… --- _[View the full topic](https://community.glideapps.com/t/online-ordering-system/21754)._