Submit your app for OAuth verification through the Google Cloud Console . This process can take several weeks and may require identifying yourself (which often requires a paid Workspace account) . 2. The Browser-Side "Fix" (For Personal Use)
I can provide the exact customized template code for your setup!
If you are part of a Google Workspace organization and you deploy the web app to be accessed only by users within your domain , the banner is usually hidden.
| Method | Removes “free user” text? | Effort | |--------|----------------------------|--------| | Google verification | ✅ Yes | Medium–High | | Keep users <100 | ❌ No | None | | Avoid sensitive scopes | ⚠️ Sometimes | Low |
I can provide the exact code snippets or step-by-step setup guide for the path you choose. Share public link Submit your app for OAuth verification through the
Set "Who has access" to . Click Deploy .
While this message helps protect users from malicious scripts, it can make professional applications look unprofessional, particularly on mobile devices where the banner causes scaling issues.
Note: Google occasionally updates its internal class names to prevent this. If the banner reappears, right-click it in your browser, select , find its exact class or ID, and update your CSS accordingly. Method 2: Embed via an iFrame on Your Own Website
In this setup, you host your HTML, CSS, and JavaScript files on a free hosting provider (like GitHub Pages, Netlify, or Vercel) and use standard JavaScript fetch() requests to send and receive data from your Apps Script. Step 1: Configure Your Apps Script as an API The Browser-Side "Fix" (For Personal Use) I can
OAuth verification is not required for Google Apps Script projects "whose owner and users belong to the same domain or Google Workspace organization". This means if everyone using your script is within the same Google Workspace account, you won't see the warning regardless of verification status.
// Important: Pass parameters to the IFrame if needed htmltemplate.params = JSON.stringify(e.parameter);
Are you using a or a paid Google Workspace domain ?
Google Apps Script is a powerful tool for automating tasks across Google services. However, when you deploy a web app or script for use by others—especially outside your organization—Google displays a security banner. The most common message reads: serves legitimate business functions
Use code with caution.
Inside your GitHub index.html , add an iframe tag that points to your deployed Apps Script URL.
The most effective, official, and to remove the disclaimer banner is by shifting the script's execution context. Google applies this banner dynamically to standard web app deployments ( /exec URLs) to protect users from unverified external scripts. However, Google provides a specific exception for developers building internal tools or publishing to a controlled environment.
Only hide the banner using these methods if your application is safe, serves legitimate business functions, and handles user data responsibly. If you want to fine-tune your setup, let me know:
If you build web applications, custom forms, or client portals using Google Apps Script , you are likely familiar with the prominent warning banner at the top of your deployed web apps. The banner reads: