Privacy & data handling

Anonymous analysis

When you analyze a configuration without signing in, the configuration is processed in memory for that request. It is not saved unless you explicitly save the analysis after creating an account.

Saved analyses

Saved analyses store a sanitized configuration snapshot, deterministic analysis results, and metadata such as score, grade, and finding counts. Raw secrets are redacted before storage.

AI remediation

Remediation requires authentication. Only sanitized configuration and server-generated findings are sent to the AI provider. Raw secrets are never included. AI responses are returned to your browser and are not stored as part of your saved analysis unless you choose to save a revised configuration separately.

Public share links

PRO users can create share links that expose a safe public assessment view. Shared payloads exclude user identifiers, sanitized configuration, and sensitive evidence values.

Analytics & telemetry

Foo Guard records aggregate product metadata such as event names, plan, rule IDs, scores, grades, finding counts, and success/failure indicators. Analytics events do not include raw configuration, prompts, evidence text, secrets, or share tokens.

Feedback

Finding feedback, assessment ratings, and rule requests store safe metadata such as rule IDs, categories, ratings, and optional comments. Comments are validated to reject values that appear to contain secrets.

Billing

Stripe stores payment and subscription metadata. Foo Guard stores plan status and Stripe customer/subscription identifiers server-side. Stripe secrets never reach the browser.

What we do not store in telemetry

• Raw or sanitized full configurations in analytics events
• Prompts or Claude responses in product analytics
• Request bodies in operational logs
• IP addresses in feedback records