If your organization uses Google Workspace (Business, Enterprise, or Education), the message may appear differently or can be managed through admin settings, but it still cannot be fully removed.
It informs the end-user that the application is not an official Google product.
: Clearly state how you collect, process, and store user data.
. Google displays this message as a security feature to inform users that the app is not an official Google product and was created by a third party. Methods to Remove or Bypass the Warning
Submit for OAuth verification (if required) This ensures the script uses your credentials rather
When deploying, set Execute the app as to "Me" and Who has access to "Anyone" . This ensures the script uses your credentials rather than asking the end-user for permissions, which can sometimes bypass the warning.
The banner is not a bug — it's a deliberate security feature by Google. End users will always see a disclaimer when running unverified or user-created scripts.
For more complex applications, you might consider publishing your script as an (for Docs, Sheets, Slides, or Forms) or a Google Workspace add-on (for Gmail, Calendar, Drive, etc.). Publishing an add-on requires verification and a review by Google before it can be listed on the Google Workspace Marketplace. This is the ultimate sign of trust and legitimacy. The process is similar to the OAuth verification but includes additional steps for a full Marketplace listing. Once your add-on is published, the warning is entirely removed for all users.
For client-facing portals or public-facing dashboards, the "untrusted user" warning can alarm users and lower conversion rates. or other sensitive data.
: You can change your background runtime properties by binding your standalone script directly to a validated enterprise workspace project. To do this, open your Google Cloud Console, construct a customized workspace project identity, register an OAuth Consent Screen configuration, and map its unique project number directly inside your internal Project Settings hub. Comparative Analysis of Removal Options Optimization Strategy Implementation Difficulty Native Mobile Responsiveness Best Fit Case External Iframe Custom Code Variable (Requires viewport management) Public portfolios and standalone web tools Google Sites Embedding High (Automatic scaling adjustments) Intranet spaces, team wikis, and dashboard portals Google Workspace Domain Routing High (Native rendering) Corporate networks and private business workflows Why Does Google Enforce This Banner?
The most straightforward way to remove the banner for internal organizational tools is to use a paid Google Workspace account (formerly G Suite) rather than a free @gmail.com account.
While this method is highly effective for internal tools, it does not resolve the issue for external users outside your organization.
: Publishing your script as a Google Workspace Add-on often removes this specific web-app footer because the code runs within a sidebar or dialog inside a Google app (like Sheets or Gmail) rather than as a standalone webpage. 4. Client-Side Workarounds (Not Recommended for Users) embedding in Google Sites
The notice “This application was created by a Google Apps Script user” cannot be removed directly from a standard script.google.com deployment without violating terms. However, three legitimate architectural alternatives exist: proxying with HTML rewriting, embedding in Google Sites, or publishing as a Marketplace add-on. Organizations requiring white-label solutions should consider proxy-based masking or enterprise licensing options.
Before removing the warning, you must understand its origin. Google introduced this security measure to protect users from malicious or poorly configured third-party applications that request access to their Google Drive, Gmail, Sheets, or other sensitive data.
The best way to remove this message is to change how the script is deployed.