If you want a native web application experience with a custom domain and zero Google branding, you should move your backend logic away from Apps Script web apps and host it on . Why This Works:
One common but approach attempts to hide the footer using injected CSS or DOM manipulation:
location / proxy_pass https://script.google.com/macros/s/AKfycb.../exec; proxy_set_header Host script.google.com; sub_filter '<div class="footer-branding">' '</div><!-- removed -->'; sub_filter_once off; proxy_ssl_server_name on;
The banner exists as a permanent security feature implemented by Google to prevent phishing and malware. Because it is rendered within an isolated top-level wrapper outside your project’s custom HTML payload, . If you want a native web application experience
Use a Google Cloud project with proper OAuth branding
The short answer is that the "This application was created by a Google Apps Script user" banner from a native Google Apps Script web app [1, 2]. Google deliberately hardcodes this warning banner at the top of the screen as a mandatory security feature to prevent phishing and protect users [1, 2].
: Some Google Workspace apps have settings that allow developers to add notices or disclaimers. Review the settings of the app in question. Use a Google Cloud project with proper OAuth
We can explore any of these deployment architectures further depending on your specific needs. Please select one of the options below to continue:
Sometimes the warning appears because of overly broad scopes. You can reduce or remove scopes to avoid triggering the warning altogether.
Method 2: Re-Routing the Web App as an API Endpoint (The Custom Frontend Approach) Review the settings of the app in question
Deploy your Google Apps Script as a and set the execution permissions to: Execute as: Me Who has access: Anyone Copy the deployment URL (which ends in /exec ).
Google displays these warnings in specific scenarios to ensure user safety. Understanding the "why" is the first step toward permanent removal. The banner appears on web apps under two primary conditions:
If you are building an app strictly for personal use and want to clean up your own screen real estate, you can use a browser extension like uBlock Origin. Use the extension's element picker tool to click on the blue banner and create a permanent local hide filter rule. This completely cleans up your personal view without altering the source code structure for others. Share public link
"I don't want to hide," Elias whispered to his glowing monitor, "I want to be independent."