Current website status
The current `gowebscope.com` site is static and informational. It does not create accounts, process payments, store reports, accept subscriptions, run hosted audits, or expose a live audit endpoint.
Pre-launch terms draft
Terms draft
These terms describe the current static WebScope website and the intended boundaries for future public audit features. They are a content draft for review, not final legal advice and not final launch approval.
Legal review is required before public launch.
Draft terms coverage
These sections describe the current static website state and future acceptable-use boundaries without activating accounts, subscriptions, payment terms, or hosted audit service terms.
Not implemented yet
Account creation, paid subscriptions, purchase checkout, billing, quota storage, report storage, hosted jobs, license activation, and device binding are not implemented yet.
No promised outcomes
WebScope must not promise rankings, traffic, revenue, conversions, availability, or business results. SEO checks are diagnostic aids and do not replace professional judgment.
Future public audit scope
Future hosted audits should be limited to public URL-only signals such as HTML, metadata, headings, links, public robots.txt, sitemap discovery, visible media tags, and structured data.
Acceptable use principles
Future audits should be used for sites the user owns, manages, or is authorized to assess. Public scanning should remain rate-limited, respectful, and limited to normal public web pages.
Prohibited future use
WebScope should not be used to attack services, bypass access controls, scrape private or internal systems, target localhost or intranet hosts, submit forms, or test systems without authorization.
Content reliability
Public audit observations can vary because websites, redirects, robots.txt, sitemaps, CDN behavior, locale handling, and JavaScript rendering can change over time.
Payments and subscriptions
Purchase, subscription, payment, refund, cancellation, invoice, and tax terms are not implemented yet. They must be written and reviewed before any paid flow is launched.
Review before launch
These terms need review for the final owner identity, hosting details, jurisdiction, consumer terms, acceptable use, privacy references, and any future commercial features.