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

<style> .footer-branding display: none; </style>

Return to the Google Cloud Console and search for .

We can explore any of these deployment architectures further depending on your specific needs. Please select one of the options below to continue:

. 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 you prefer to stay within the Google ecosystem without managing independent web hosting accounts, embedding the project inside Google Sites will automatically suppress the notification banner. Steps to Implement: Navigate to your Google Sites workspace. &lt;style&gt;

Ultimately, while browser extensions and iframe workarounds can hide the banner, they are temporary, client-side solutions. For developers and organizations serious about distributing Google Apps Script applications, investing the time to complete Google's OAuth verification process is the only professional path to a warning-free experience that respects both Google's policies and user security.

He spent forty-eight hours straight buried in documentation. He learned that the banner was a security feature, a permanent "badge of origin" for scripts running on Google’s infrastructure. It was there to protect users from phishing, ensuring they knew the app wasn't an official Google product.

The warning does not mean your app is dangerous. It simply means Google has not yet verified your identity and compliance with their API policies.

If you are building the application exclusively for your personal use or a tiny tech-savvy team, you can block the DOM element locally using content filters. This "wraps" the app in your own branding,

By decoupling the frontend from Google's hosting environment, your users will interact with a pristine, unbranded interface, eliminating the script user banner entirely. Summary of Options Technical Difficulty Internal business apps iFrame Embedding Public forms or simple dashboards GCP Linking Professional tools and branding Free / Variable API Decoupling Advanced web applications If you want to tailor this further, tell me:

Once verified and published as an add-on, your code executes natively inside Gmail, Calendar, or Drive sidebars, bypassing web app layout banners entirely. Summary of Deployment Options Banner Status Best Used For Requirements Visible ⚠️ Rapid debugging or developer testing Free Google Account HTML IFrame Embedding Hidden 🟢 Public MVPs, contact forms, client tools External host (e.g., GitHub Pages) Workspace Domain Lock Hidden 🟢 Internal enterprise tools & dashboards Google Workspace account Marketplace Add-on Hidden 🟢 Commercial SaaS distribution GCP Verification Process Local Workaround for Developers: Browser Extensions

If you do not want to manage external web servers or code repositories, you can use Google's ecosystem to swallow the banner natively. Open or build a page inside Google Sites. Click the tool from the right-hand panel.

Here is a helpful write-up on how to remove these applications and revoke their access to your Google account. CSS injection ( !important )

If the application is published as a (for Sheets, Docs, Forms, or Gmail), Google replaces the generic footer with an “Powered by Google Apps Script” notice that is less intrusive and can be accompanied by your logo. However, the attribution remains but is integrated into the add-on sidebar/menu rather than as a floating banner.

You cannot use internal JavaScript, CSS injection ( !important ), or Google Apps Script configuration properties to natively force the removal of the user disclaimer. Google explicitly prevents the script's HtmlOutput from accessing or modifying the outer parent frame holding the warning.

The message “This application was created by a Google Apps Script user” is Google’s way of enforcing security transparency. You cannot “hack” or “trick” the system into removing it. The only legitimate methods are: