Remove This Application Was Created By A Google Apps Script User Jun 2026

If the native scenarios above don't fit your needs, developers often use these technical methods to bypass the banner: Self-Hosted Iframe : Instead of sending users directly to the script.google.com

. This "wraps" the app in your own branding, though it may require specific X-Frame-Options settings in your script to allow embedding. Browser Extensions (Client-Side) If the native scenarios above don't fit your

and completing the OAuth verification process can sometimes help manage how warnings are displayed, though it is primarily for removing the "App not verified" screen rather than the footer banner. Google Groups Summary of Options Complexity Effectiveness Embed in Google Sites High (Best for internal/simple sites) Self-Hosted Iframe High (Provides custom domain feel) Workspace Domain High (Automatic for internal teams) Browser Extensions High (Only works for the person who installs it) Publish as Add-on Permanent (Official solution) : Attempting to hide this banner programmatically from the script's own HTML output using standard JavaScript ( document.getElementById If you are just prototyping, ignore the message

Before attempting to remove the message, you must understand its cause. The warning appears when a Google Apps Script application attempts to access sensitive user data (like Drive, Gmail, Sheets, or Contacts) or perform actions on behalf of a user without completing Google’s verification process. If you are just prototyping

Many developers assume removing the warning is free—it is not.

If you are just prototyping, ignore the message. But before you launch a tool for real users, invest the time to remove that warning. Your users will thank you.