This topic includes unacceptable and prohibited usage of anonymous access to a Quickbase app. It is possible to design solutions that meet similar requirements, using intermediary middleware, such as custom code written by a Quickbase Solution Provider (QSP). Please note that all solutions built using EOTI, especially those involving personally-identifiable information (PII), must comply with all regulatory and legal requirements and governing controls such as (but not limited to) HIPAA, and GDPR.
By using these techniques with EOTI, you expose sensitive, confidential, or personal information or violate Quickbase’s Acceptable Use Policy. We reserve the right to cancel or suspend apps and/or accounts if we find that you are using EOTI to circumvent licensing costs or otherwise violating the unacceptable uses listed below.
|
Emulating user credentials |
This involves users locating personal information without signing in. This includes having search fields or reports that allow users to enter identifying information to access data. An example of this is an “ask the user” report where users type a last name or phone number to look up their contact record and make edits. |
|
Using Quickbase as a High Traffic Content Delivery Network (CDN) |
For uses such as high traffic requests for images embedded in websites, emails, and other services. Unacceptable use for these public resources is defined as more than 4 requests per second for all the combined resources in a given app. |
|
Credential spoofing |
Building a JavaScript page in Quickbase that provides authentication inputs, other than going directly to Quickbase for true authentication. For example, having a page query a list of data to determine what records someone accessing the page can see, when the information is not free to disclose to the public. |