Scout Beta Terms Placeholder

Beta use is limited, permission-based, and evidence-first.

This is not a final Terms of Service. It is a temporary beta boundary page so testers understand the responsible-use rules before a lawyer-reviewed agreement is published.

Beta boundaries

Use Scout only where you have the right to collect evidence.

Permission

Allowed access only

Use Scout only for websites and data you are allowed to access. You are responsible for site terms, robots guidance, rate limits, copyright, account boundaries, and applicable law.

No bypass promise

No guaranteed hard-site bypass.

Scout can record blocked evidence and use browser-assisted acquisition, but it does not guarantee access to sites that block crawlers, automation, or third-party capture.

No abuse

Restricted uses need separate review

Do not use Scout for login-walled pages, private account data, credentialed social networks, personal-data enrichment, regulated data, spam, evasion, or job auto-apply workflows unless separately reviewed and approved.

Hosted beta

Hosted beta is capped and metered.

Hosted beta access is for approved testers only. It may include finite run credits, rate limits, manual review, temporary downtime, and revoked access if usage creates security, legal, infrastructure, or abuse risk.

Do not submit secrets or regulated personal data to Scout. Keep API keys in environment files such as `.env.local`, never in prompts, public repos, screenshots, or artifacts.

Launch status

Controlled beta is ready with limits.

Security gate

Dependency audit must close

Scout is not a public self-serve production SaaS. Public registries, paid checkout, and security-clean claims remain deferred until their gates reopen and pass.

Legal gate

Final terms still required

These terms are a beta placeholder. Public or commercial launch still requires final license, terms, privacy, and support policy decisions.