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

Method 3: Switching to Google Cloud Run (The Professional Path)

for your script to make it look even more official.

While the banner technically still exists inside the execution environment, embedding it inside a styled container on your own domain masks the default Google wrapping interface, making it look like an integrated part of your website.

Note: This process can be technical and may take several weeks to complete. 3. Use within a Workspace Domain Method 3: Switching to Google Cloud Run (The

Even after verification, many developers fail to remove the warning because of these errors:

Disclaimer: Some of these methods involve browser modifications and should be handled with care, particularly when dealing with data privacy. If you're interested, I can also show you how to:

: Perform a search across your project files for any references to "long review" or similar notices to ensure it's not hardcoded somewhere. Add the your script uses (e

Add the your script uses (e.g., https://googleapis.com ). Phase 3: Verification (The Critical Step)

As one developer noted on a support forum, "I cannot have this warning message displayed to them" because it ruins the user experience and trust in their custom Google Sheets feature. The verified status directly addresses this pain point.

: You can host a simple HTML file on your own domain (e.g., via GitHub Pages) and embed the Apps Script URL within an . While the banner may still technically exist within the frame, it is isolated from your main site's branding. The warning is mainly for external

If you are developing a tool exclusively for internal business use, the warning banner can be entirely disabled by .

If you are a developer writing a Google Apps Script to programmatically remove an application, you typically cannot remove "Third Party App" authorization tokens via a standard script function for security reasons. Users must manually revoke access via the Security settings mentioned in Scenario 1.

If you are part of an organization with a Google Workspace account, internal applications created by your domain will generally not show this warning to other members of the same domain. The warning is mainly for external, public-facing, or personal account scripts. 2. Bypass via Chrome Extensions (The Workaround)

Verifying your app connects your script to a verified billing account or domain name, ensuring compliance with Google's Terms of Service.

You cannot hide the Google permissions page, but you can embed your web app in an iframe on your own website. Then users see your domain, not Google’s warning screen — though Google may still show a small permissions popup.