SECURITY & DATA HANDLING
Trust begins with
clear boundaries.
The public website, customer enquiries and authenticated SEO workspace have different responsibilities. Keep them separate and be precise about what has been verified.
- Separate systems
- Read-only Google connections
- No passwords by email
- PublicPublic websiteContent and enquiries only
- PrivateSEO workspaceIts own login, projects and integrations
- ScopedAI agentsThe approved endpoint and authorisation flow
SEPARATE RESPONSIBILITIES
The marketing site is not the SEO application.
Three systems, each with its own job and its own access.
Content and enquiries
WordPress publishes the public pages and handles configured enquiry forms. It does not read the application database or store the platform’s provider keys.
Authorised SEO data
The existing application controls its own authentication, projects and integrations. A WordPress login or enquiry does not grant application access.
Deliberate connections
Use only the endpoint and authorisation flow supplied by the approved deployment. Review tool scope, external providers and generated output.
FAQ
Security questions.
How data is separated, and how to raise a concern.
How do I report a security concern?
Contact the team through the published contact route with the affected URL, a clear description and non-sensitive reproduction steps. Do not send live credentials, another customer’s records or unnecessary personal data. Avoid destructive tests against production.
Does a WordPress login give access to the SEO workspace?
No. The application controls its own authentication, projects and integrations, separately from the public website.
Has the platform been independently audited?
This page explains the intended architecture and handling principles. It is not a claim of an independent security audit, certification, guaranteed uptime or completed multi-tenant isolation. Deployment-specific controls must be verified before public launch.
Need a deployment-specific answer?
Ask about the relevant integration, permission boundary or data-handling requirement.