Privacy Policy

Account and profile information

You can use the analyzer without an account. If you create an account with email and password, Foo Guard stores that email address and a password hash in its authentication database. A Foo Guard profile record stores your user id and, when you subscribe, billing status fields described below. Foo Guard does not ask you for a legal name, postal address, or phone number.

Google user data

This Privacy Policy applies to Foo Guard. Foo Guard uses Google Sign-In only for authentication and account association. Google verifies your identity and returns the sign-in result to Foo Guard.

Foo Guard receives standard identity information: your Google account email address, and basic profile information such as your name and profile image when Google provides it. The sign-in uses only the standard identity scopes openid, email (userinfo.email), and profile (userinfo.profile). Foo Guard does not request access to Gmail, Google Drive, Google Calendar, Google Contacts, or other Google product data.

Foo Guard uses that identity information to create your Foo Guard account or sign you in, and to associate saved analyses, team memberships, and billing with that account. It is not used to read your Google content.

Foo Guard stores your account identity and profile information. The authentication service may store provider tokens on the server to manage the connected sign-in account.

Google identity data is not sold. Google identity data is not used for advertising. Google identity data is not sent to Anthropic. If you start checkout, Foo Guard may send your account email address and Foo Guard user id to Stripe so Stripe can create a billing customer.

If Foo Guard requests additional Google data in the future, this policy and the Google consent configuration will be updated accordingly.

You can stop using Google sign-in by signing out of Foo Guard. Foo Guard does not offer a self-serve delete-account control. To delete your Foo Guard account and the Foo Guard data associated with it, contact feedback@fooguard.com or use the support page. Deleting your Foo Guard account does not delete your Google account.

Sign-in and account emails

Foo Guard manages accounts and sessions using its authentication service. Session cookies keep you signed in. Resend delivers email verification, password reset, and invitation messages. Company SSO uses the identity provider configured by your workspace. We also store email delivery events, preferences, and unsubscribe records for onboarding messages and optional workspace digests. Foo Guard’s operators also receive an internal email, sent through Resend, when a new account is verified. It contains the account email address and sign-up time.

Analyses and agent configurations

An analysis you run without saving is processed for that request and is not written to your account. When you save an analysis, Foo Guard stores a sanitized configuration snapshot, deterministic findings, and metadata such as score, grade, and finding counts. Values that look like secrets or credentials are redacted before that snapshot is stored.

Optional AI remediation is available only after you sign in. Foo Guard sends a sanitized configuration and server-generated findings to Anthropic (Claude) to draft remediation guidance. Raw secrets are not included in that request. Completed remediation guidance and suggested configurations are retained so you can reopen them without spending another generation credit. Follow-up checks retain their results for comparison with the original scan. Scores, severities, and pass/fail results come from Foo Guard's rules engine, not from the model.

Pro users can create a public share link for a safe assessment view. Shared payloads omit user identifiers, the sanitized configuration, and sensitive evidence values.

GitHub App data

Team workspaces can connect a GitHub App installation. Foo Guard stores installation and repository metadata needed to scan and enforce policy: GitHub installation id, GitHub account id, login, and account type, repository selection, repository id, owner, name, full name, whether the repository is private or archived, default branch, and GitHub HTML URL. Scan records store summaries, policy results, and structural finding locations.

Foo Guard reads policy and agent configuration files from the repository at a specific commit in order to analyze them. It does not persist the raw repository configuration or credential values in scan records. GitHub installation tokens are created when a scan needs them and are not stored in the browser or in those scan records.

Team workspaces

A team workspace stores the organization name, slug, membership, roles, invitations, and policy settings. Audit records for workspace actions store the action and related identifiers so members can review who changed workspace settings.

Gateway connections

Gateway processes supported requests sent through it and forwards permitted requests to the connected provider. Foo Guard stores server definitions, connection settings, encrypted upstream credentials or member grants, and request metadata such as the agent, capability, decision, and outcome. Request history does not store tool arguments or returned tool content. The connected provider receives the requests you route to it and handles them under its own policies.

Payments

Stripe processes card payments and subscriptions. Foo Guard stores Stripe customer, subscription, and price identifiers, subscription status, billing period end, and, for team plans, seat quantity and billing interval. Foo Guard does not store card numbers. Stripe Checkout and the Stripe billing portal collect payment details directly from you.

Analytics, logs, and security records

Foo Guard records first-party product events such as analysis completed, checkout started, and GitHub scan completed. Those events include safe metadata such as event name, plan, rule ids, scores, grades, and success or failure. They do not include raw configuration, prompts, evidence text, secrets, or share tokens.

Unauthenticated requests may be rate-limited using the caller IP address from request headers. That address is used to enforce limits. Feedback records do not store IP addresses. Operational logs are not written with request bodies. Feedback and rule requests store ratings, rule ids, categories, and optional comments; comments are rejected when they appear to contain secrets.

Cookies and local storage

Foo Guard uses cookies for sign-in and browser session storage for interface state, such as workspace navigation. A first-party measurement cookie contains a random identifier and expires after 30 days. It helps connect a campaign visit and Library item view with account creation and a first successful scan. We store campaign labels, the traffic source, medium, and search keyword from campaign links, the domain of the referring site (for example, github.com), the public page where the visit started, Library item identifiers, Library downloads and setup copies, event times, and scan identifiers; authenticated events can be associated with your account id. These journey records do not contain email addresses, configuration contents, IP addresses, or full referring URLs. Do Not Track and Global Privacy Control signals disable this journey measurement. It does not set third-party advertising cookies.

Retention and deletion

Account records, saved analyses, team workspace data, GitHub installation and scan metadata, billing identifiers, and product analytics events are kept while the account or workspace exists. The product does not automatically delete them after a fixed number of days.

To ask Foo Guard to delete your account and associated Foo Guard data, email feedback@fooguard.com. Disconnecting the GitHub App stops new scans. Stripe retains its own payment records under Stripe's policies.

Processors

• Supabase — hosted database storage
• Resend — account emails, onboarding messages, optional digests, and delivery events
• Stripe — payments, subscriptions, and billing customer email
• Anthropic — optional remediation requests that contain sanitized configuration and findings
• GitHub — repository contents read for Team scans, and installation metadata returned by the GitHub App
• Google — identity only, when you choose Google sign-in, limited to openid, email, and profile

Security

Foo Guard checks account and workspace permissions on the server and uses database access controls to restrict stored data. Secrets are redacted before configurations are stored. API keys and Stripe secrets are kept on the server.

Your choices

You can analyze a configuration without an account, skip Google sign-in and use email and password, skip saving an analysis, skip AI remediation, and disconnect a GitHub installation. You can request access to or deletion of your Foo Guard account data by contacting us. Foo Guard does not provide an in-product data export or delete button.

Children

Foo Guard is a professional security tool. It is not directed at children under 13, and we do not knowingly create accounts for them. If you believe a child has created an account, contact us and we will delete it.

Changes

If these practices change, Foo Guard will update this page and the date above. Continued use of the site after an update means the updated policy applies to new activity.

Contact

Questions about this policy or a deletion request: feedback@fooguard.com. You can also use the support page.