Local Scout keeps run artifacts on your machine.
Local runs write artifacts to the configured working directory: records, source pages, blocked pages, screenshots or DOM evidence when captured, validation files, logs, and reports.
Scout Beta Privacy Placeholder
Know where Scout stores evidence before you run it.
This is not a final Privacy Policy. It is a temporary beta notice that documents local and hosted data handling until lawyer-reviewed privacy terms are published.
Data handling
Local Scout and hosted Scout have different data footprints.
Hosted beta stores run metadata and artifacts for limited retention.
Hosted beta may store account email, payment references, API key status, run metadata, source URLs, extracted records, blocked evidence, logs, and artifacts long enough to operate, debug, meter, and support the beta.
Do not submit secrets or regulated personal data.
Do not place passwords, private keys, regulated personal data, private account pages, credentialed social content, or customer confidential information into Scout beta runs.
Browser evidence
Screenshots and DOM captures can contain visible page data.
Browser-assisted acquisition may capture screenshots, rendered DOM, markdown, links, network diagnostics, console errors, and source hashes. Review pages before capture and avoid private sessions unless you have explicit permission.
Retention and deletion are beta operations for now: delete local run folders when no longer needed, and request hosted artifact deletion through the beta support channel once that channel is confirmed.
Credentials
Keep keys out of artifacts.
Use `.env.local` for local keys
API keys and service tokens should stay in local environment files or deployment secret managers. Do not commit them, paste them into public prompts, or store them in run artifacts.
Secret handling is still a launch gate
Hosted API key generation and delivery still need final verification before hosted access expands beyond controlled private beta testing.