Privacy
Last updated July 2026
Scout OS stores the Builds you create so you can return to them. This page explains what is stored, who can read it, and what we do not yet promise.
What we store
Your account email, an optional display name, and the content of each Build you create — intake answers, proposals, scores, decisions, plans, and any approved reports.
Purchase records (offer, amount, coupon code, status) are stored so entitlements can be verified. Card details are handled by Stripe and never reach Scout OS.
Who can read it
Build content is scoped to your account by database row-level security: other founders cannot read your Builds. Operators of Scout OS can access stored data for support and debugging.
AI processing
When you ask Scout to generate a proposal, the relevant Build content is sent to a third-party model provider through an AI gateway to produce that response. The seeded demonstration Build is never sent to a model.
What we do not claim
This is an early paid beta. Formal security certification, guaranteed retention or deletion windows, and audited confidentiality controls are not in place. Do not place regulated, or third-party confidential material into Scout OS.
Deletion
You can archive Builds in the app. To request account deletion, contact support and we will remove your account and Build content.
Questions about this page? Contact support.