Home / All tools / Security Security
Understand how your account and data are protected. Only people on your team can see your data. Sensitive sign-in details are protected, scans have limits, and connecting Google requires your permission.
Example walkthrough example.com
Security · example steps
See who can access your website tools Fictional sample · no customer data 01
Choose your workspace Membership and role determine access
02
Allow access to a service Choose the website and supported service you want to connect
03
Review before making a change Website changes follow separate permission and approval checks
See what the website scanner can do
Target Public website pages using HTTP or HTTPS addresses
Limits The scan respects website scanning rules and limits on pages, moved links, and requests.
Access A scan reads public pages. It does not give permission to edit your website. This example explains the steps. It does not check your account security or show private sign-in details.
How it works (3)
Access. Website scans. Private connection details. 01 Access
Only your team can see your data. Team membership and account roles Email verification and sign-in protection Roles that limit who can change websites and fixes 02 Website scans
Website scans follow clear limits. 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. Protected browser sign-in sessions Passwords and connection keys stored in protected forms Private values removed from system records 01 Available protections depend on how the live service is configured.
02 You control the Google connections and team access you grant.
03 Everyone on your team can see every project and website in your workspace; each person's role decides what they can change.
04 No service can promise absolute security. Protection, monitoring, and response need ongoing attention.
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 that you belong to the workspace that owns it and that your role allows the action.
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 access you control. Review how access works, then run a website scan when you are ready.