Remove This Application Was Created By A Google Apps Script User Instant

Note: If your application is public and used by many people outside your organization, you may also need to submit the project for Google Verification to completely clear all OAuth warning screens.

If you are seeing a prompt stating and you want to remove the application (or your connection to it), you are likely dealing with a Google Workspace Add-on, a web app, or an authorization token you previously granted.

If you are building a professional application and want total branding control, moving away from the Google Apps Script Web App environment is the best long-term choice.

Imagine you built a script that reads data from Google Sheets and sends personalized emails via Gmail. You want your 50 clients to use it without seeing the warning.

You can host a completely independent frontend on free or premium static hosting providers such as GitHub Pages, Vercel, Netlify, or AWS S3. Step 3: Fetch Data via AJAX Note: If your application is public and used

Method 3: Reverse Proxy via a Node.js or Cloudflare Worker Server

There is no "off switch" in Google Apps Script settings to immediately remove this banner, but you can remove it through proper deployment and, in some cases, with third-party tools. 1. Authorized Deployment Options (The Official Fix)

The only way to remove the banner for users outside your domain is to verify your OAuth client .

When the application's access permissions match the exact domain infrastructure of the creator, Google recognizes it as a trusted internal tool and removes the notification banner for your employees. 3. Transition to a Verified Google Workspace Add-on Imagine you built a script that reads data

: The banner appears for scripts that have not undergone the formal Google Workspace Add-on verification process . Even with a verified brand, simple web apps may still trigger it if they are not published as official Add-ons. Limitations and Technical Challenges

Google displays this header as a . It ensures users know the application is custom-built and not an official Google product. This helps prevent phishing and data misuse by identifying the script's origin. ✅ Methods to Remove or Hide the Banner 1. Use a Google Workspace Account

While Google includes this for security and transparency—to ensure users know they aren't interacting with an official Google product—it can be a major eyesore for developers trying to create a professional, branded experience.

If you're a user who has authorized a script and now want to to your Google account, you can do so via Google's permissions page: Step 3: Fetch Data via AJAX Method 3:

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.

What if you cannot complete verification (e.g., you use a personal Gmail account or cannot afford the time/cost)?

To completely remove the banner from your web application, you must link your Apps Script project to a verified Google Cloud Platform (GCP) project and complete the OAuth consent screen verification process . Google automatically injects this disclaimer banner into standalone Google Apps Script web apps as a security safeguard. The warning alerts external, anonymous users that the application was written by an independent developer rather than by Google directly.

First, it’s crucial to understand what this message actually is. The exact text you're likely seeing is: