Privacy

How we handle data

• Saving or sharing a build stores the configuration and the generated estimate needed to reproduce its permalink. A saved build may also include the reason notes and interview answers submitted through the build flow.
• A saved build has a randomized share ID and no account — there is no list of your builds and no owner lookup. Anyone who has the permalink can open that saved build. The randomized share ID is the only access barrier; there is no login or owner authentication.
• There are no user accounts tied to saved builds, and builds are not managed through an account dashboard.
• The current product does not accept bill, invoice, or document uploads, and performs no automatic redaction — there is no upload workflow.
• The app runs on third-party hosting and database providers, which necessarily handle operational and network metadata to serve requests. The application itself does not write your IP address or request headers into a saved build.
• Privacy-light analytics is optional and is not loaded in production unless its domain is configured; it is currently not enabled.

For privacy questions, or to ask about or request deletion of a saved build, email hello@aistackpicker.com. Include the build’s permalink or share id so the record can be found. Please do not email full bills, invoices, passwords, or API keys.