Plain-language beta policy
Privacy
How WarmStart public resources, the manual Project Warmth Audit, content attribution, and the separate signed-in LiveOps beta handle data.
Public resources and audit tool
The public resource pages can store first-party content attribution in your browser so source, campaign, article, and CTA context can continue into the signed-in product. The manual Project Warmth Audit runs in your browser, does not fetch the domain you are assessing, and offers a local JSON download.
Do not enter secrets or customer personal information into the audit. Its answers are not submitted by the generated tool. Hosting, security, and standard web logs may still process technical request information according to the providers operating the site.
Signed-in LiveOps beta
The signed-in product may process account identity, project configuration, operating tasks, evidence, provider connection status, and product analytics needed to deliver and improve the service. Provider credentials and permissions should be handled through the controls documented in the product; never paste secrets into public content forms.
WarmStart uses analytics to understand content and product usage when configured. Content attribution may include site, slug, cluster, CTA, referrer, and UTM parameters. First-party product and payment records remain the authoritative source for activation and billing outcomes.
Requests and changes
Contact msanchezgrice@gmail.com for access, correction, deletion, or other privacy questions. Because the service is evolving, this policy should be reviewed again when data practices, providers, or product capabilities materially change.
Last reviewed July 13, 2026. Questions or correction requests: msanchezgrice@gmail.com.