Glide

Overview

Glide is a no-code application platform that transforms spreadsheets and databases into functional web applications. Organizations use Glide to build internal tools, customer portals, inventory management systems, and other data-driven applications without writing traditional code. When a Glide-built application is deployed and accessed by users, Glide's scripts handle the entire application runtime — from rendering the user interface to synchronizing data with the underlying data source.

Website operators encounter Glide's scripts when they deploy Glide apps on custom domains or embed them within existing web properties. The scripts are not optional add-ons; they are the application itself. Without Glide's runtime scripts, the app simply does not function.

What This Script Does

Glide's scripts constitute the full runtime environment for applications built on its platform:

• UI rendering: Generates and renders the application's user interface, including navigation, forms, lists, detail views, and custom layouts configured by the app builder.
• Data synchronization: Maintains real-time connections to the underlying data sources (Google Sheets, Airtable, Glide Tables, or other connected databases), fetching and pushing data as users interact with the application.
• User authentication: Handles sign-in flows, session management, and access control when the app is configured with user authentication, including email-based login and role-based permissions.
• Offline support: Caches application data and state locally to enable offline functionality, syncing changes when connectivity is restored.
• Media handling: Loads and displays images, files, and other media assets stored in or linked from the application's data source.
• Action execution: Processes user-triggered actions such as form submissions, row additions, email sends, and workflow triggers configured within the app builder.

Glide's scripts do not perform cross-site advertising tracking or share user data with ad networks. Data processing is scoped to the application's configured data sources and the Glide platform itself.

Consent & Compliance

Glide applications are functional software — they are the product the user is interacting with, not a supplementary tracking or marketing layer. This places Glide's scripts firmly in the "strictly necessary" category for the purposes of the application they power. Without these scripts, the application ceases to exist.

Under GDPR and ePrivacy regulations, scripts that are strictly necessary for providing a service explicitly requested by the user are exempt from consent requirements. A user accessing a Glide-built app has intentionally navigated to that application, and the scripts are required to deliver the requested service.

However, if a Glide app is embedded as a supplementary widget on a larger website (for example, an embedded feedback form or directory), the consent classification may depend on whether the embed is considered essential to the page's primary function. Website operators should evaluate each embed's role individually.

Data processed within Glide apps — particularly personal data entered by users — must be handled according to applicable privacy regulations, but this is a data processing concern rather than a cookie consent issue.

Should You Block This Without Consent?

Glide's scripts are the application runtime itself. Blocking them renders the entire Glide-built application non-functional. If visitors are navigating to a Glide app, they are requesting that service, and the scripts are strictly necessary to deliver it. For embedded Glide apps that serve a supplementary function on a larger page, evaluate whether the embed is essential to the page. In most cases, blocking is not appropriate. No.