The approach described - allowing anonymous users to access the app by entering a shared password (not tied to an email or identity), with the password checked against a list in a table - violates the following specific section:
Section: 4. Applications and User Data
As further set forth in the User Data Rules and Restrictions, available at glideapps.com/legal/user-data, you are not permitted to Process certain types of User Data in connection with your use of the Services. … Any violation of the User Data Rules and Restrictions will be deemed a violation of this Agreement and is grounds for termination of your right to use or access the Services.
This section states that violating the User Data Rules and Restrictions (such as storing unencrypted passwords) is also a direct violation of the Terms of Service.
User Data Rules and Restrictions | Glide
Section: Prohibited Types of Data
- Unencrypted passwords and other login credentials, such as authentication tokens.
The post describes storing a list of passwords in a table and matching user input against this list. This means unencrypted passwords are being collected, stored, and processed within the Glide app. Glide’s User Data Rules and Restrictions explicitly prohibit collecting, uploading, storing, transmitting, displaying, modifying, or otherwise processing unencrypted passwords in any application created using Glide.