Google authorization
Connect with Google's authorization flow instead of giving Novaon your Google password.
Connect only the accounts you choose through Google authorization, review access at any time and keep meaningful changes deliberate.
Connect with Google's authorization flow instead of giving Novaon your Google password.
Permission requests are tied to product functions and presented during connection.
Review or revoke access granted to external services from the security controls in your Google Account.
Bulk workflows and AI-assisted workflows retain an explicit review and approval checkpoint.
Access and audit workflows help teams understand who is responsible for operational actions.
Product workflows are designed to request and handle only the account data needed for their purpose.
Bring landing page quality, advertiser verification, billing consistency and policy history into one preventive review. Novaon prioritizes evidence and recommended checks, while Google remains the sole decision maker for policy enforcement and account status.
Two accounts require an immediate owner review.
Review connected access, permission scopes, assigned roles and recent account actions from one security workspace.

Security begins with clear authorization and ownership. Novaon uses Google sign-in and consent so users do not provide their Google password to Novaon, and the account owner can review or revoke granted access through Google Account controls.
| Control | What the user should see | User responsibility |
|---|---|---|
| Google sign-in | Google identifies the user and presents the authorization flow | Use the correct Google account and protect it with strong authentication |
| Permission consent | The requested access is shown before connection | Read the consent screen and approve only the access you understand |
| Account selection | Only the accounts selected for the workflow are brought into operating context | Confirm the advertiser and manager account relationship before acting |
| Review checkpoint | Meaningful campaign, budget and AI-assisted actions remain visible before approval | Verify the commercial and technical impact before moving forward |
| Team accountability | Roles, ownership and recent activity help identify who is responsible | Remove unnecessary team access and keep user accounts individual |
| Revocation | Connected access can be reviewed and revoked from Google Account security controls | Revoke access when the service is no longer used or access is in doubt |
| Security reporting | A direct support channel accepts responsible reports | Share only the details needed to investigate and never email live credentials |
No. The score organizes warning signals for preventive review. Google independently interprets policy, verification, billing and account history, and only Google decides whether an account remains eligible.
No. Sign-in and authorization are handled through Google's flow. Never send a Google password, authorization code or access token to Novaon by email or chat.
Review third-party connections in your Google Account security settings and revoke Novaon when access is no longer required. You should also review workspace team access.
No. Access depends on the granted Google permissions and the user's Google Ads role. Novaon also keeps review checkpoints around meaningful operational actions.
Stop the workflow, revoke or disconnect the unintended access, then reconnect with the correct Google account and verify the selected advertiser accounts.
Include the affected page, date and time, a concise description, reproduction steps and non-sensitive screenshots if useful. Do not include passwords, tokens, billing details or unnecessary personal data.
Keep your Google Account protected with strong authentication, review teammate access, verify campaign changes before publishing and never share passwords or authorization tokens by email. Novaon security does not replace the security of your Google Account, device, website, analytics platform or CRM.
Email support@novaon-partners.io with a concise description, affected page and reproduction details. Do not include live credentials, access tokens, payment details or personal data that is not necessary for the report.
Review the Privacy Policy for information about data handling and user choices. Review the Terms of Service for account responsibilities, acceptable use and product conditions.
Review Google's consent screen before granting access.