The problem
A website tool may use account connections and private search data. You need to understand what it can access and who can use it.
Security
Understand how your account and data are protected.
Your team permissions control who can see your data. Sensitive sign-in details are protected, scans have limits, and connecting Google requires your permission.
- Website checks do not edit your pages
- No automatic website changes
- See why each fix matters
What you get
Clear information about requested access, website changes, and how account data is kept separate.
How it works
A clear path from question to next step.
See what to expect, what you can learn, and how to use the results for your website.
01
Access
Your team permissions control access.
Access checks use your team membership, account role, and project permissions to keep you within the websites and data you are allowed to use.
- Team membership and account roles
- Email verification and sign-in protection
- Access controls for your projects and websites
02
Website scans
Website scans follow clear limits.
The scanner reads public pages, limits requests, and respects your website's scanning rules. It blocks private network addresses and unsafe destinations.
- Private network addresses and unsafe destinations blocked
- Limits on page moves, download sizes, and waiting time
- Website scanning rules and scan settings shown
03
Private connection details
Private sign-in details are kept out of support records.
Passwords and connection keys are stored in protected forms. Secure browser cookies protect sign-in sessions, and private values are removed from system records. Support will never ask for your password.
- Protected browser sign-in sessions
- Passwords and connection keys stored in protected forms
- Private values removed from system records
Trust is part of the product
What to know before you start.
See what you need, what the results can tell you, and where more information is needed. Measurements and estimates stay clearly labeled, and website changes need your approval.
See how scoring works →- 01
Available protections depend on how the live service is configured.
- 02
You control the Google connections and team access you grant.
- 03
No service can promise absolute security. Protection, monitoring, and response need ongoing attention.
Straight answers
Know how it works before you begin.
A little context makes it easier to get started.
Contact support →Does the platform automatically edit my website?
No. Scans check pages without editing them. Supported website changes need a separate connection, review, and your approval.
How is my data separated from other accounts?
Before showing data or allowing an action, we check your team membership, project access, and account role.
Should I send credentials to support?
No. Never send passwords, connection keys, sign-in codes, or payment details in a support message. Support will not ask for them.
Start with your website
Start with access you control.
Review how access works, then run a website scan when you are ready.