Privacy

What we collect

• Your agent description — the freeform text you paste on Step 1 of the audit, plus any architecture diagram you upload.
• Your wizard inputs — model, tools, system prompt, call volume, conversation length, monthly spend (if entered), workload type, and the inferred archetype. Stored alongside the report so you can re-open it later.
• Your account email, when you sign in. Used for the magic-link auth and to attach reports to your account.
• A session cookie (`pc_session` for anonymous flows, plus a Supabase auth cookie when signed in). Both expire and rotate on a normal schedule.
• Calibration deltas — when you submit an audit, we log whether (not what) each parser-suggested field was edited, with a coarse direction and magnitude bucket. This lets us tighten the parser’s suggestions over time. The raw values you typed never enter the calibration log; only the fact that an edit happened, e.g. "callsPerDay was edited upward, medium magnitude."

What we don’t collect

• Live usage data. PitCrew is a pre-deploy forecasting tool. We don’t take provider API keys, don’t ingest your production traffic, don’t analyze deployed agents.
• Your end-users’ data. The agent description you paste should be about your agent, not about your users. We don’t want their messages, prompts, or PII.
• Browser fingerprints or cross-site tracking. No ad-network pixels, no fingerprinting libraries, no third-party advertising tags.
• Marketing cookies. See the cookies section.

We do use one privacy-friendly product-analytics service — PostHog — to understand how PitCrew is used (page views, sign-ups, audit volume, feature engagement). It’s opt-in: when you first visit, you can Accept or Reject in the banner. Reject means no analytics cookies are set and no events are sent. Details in the analytics section.

Where the data goes

• Supabase — stores the report row (your description, wizard inputs, computed analysis) and your account. US region.
• Anthropic API — when you click Continue on Step 1, your description gets sent to Claude to parse out the wizard fields. The request includes the description and a system prompt; nothing else from your account. Anthropic’s data-handling terms apply to that request.
• Vercel — hosts the app. Standard request logs apply (IP, path, user-agent), retained ~30 days.
• PostHog — product analytics, US region. Only reached when you’ve accepted the analytics banner. We transmit page paths, event names (e.g. audit_started,pro_purchased), and your Supabase user ID once you’re signed in. Your IP is NOT sent (we set their ip: false option). Session recording is disabled.
• Stripe — payment processing for PitCrew Pro. Only reached when you initiate a $9.99 purchase. Stripe handles your card details directly; PitCrew never sees them. We store only your Stripe Customer ID after a successful purchase.

That’s the full list. No advertising networks, no email-marketing providers, no data brokers.

Analytics — what we collect when you accept

When you click Accept on the cookie banner, PitCrew loads PostHog, a privacy-friendly product-analytics service. PostHog helps us answer questions like “where do users get stuck in the wizard?” and “which features drive Pro upgrades?”

What we track

• Page views (the URL path you visited, no query strings with sensitive data)
• Named product events: signup_completed, audit_started, audit_completed, audit_quota_blocked, pro_cta_clicked, pro_purchased, setup_guide_generated, report_shared
• Lightweight properties on those events (e.g. which AI archetype you picked, which IDE you generated a Setup Guide for) — never the contents of your audit
• Your Supabase user ID once signed in, so we can attribute events to the same person across sessions

What we DO NOT track

• Your IP address (we explicitly disable it)
• Session recordings or mouse-movement playback
• The contents of your agent description, system prompt, or audit results
• Anything when you click Reject

If you change your mind

Clear the pitcrew:analytics-consent-v1 entry from localStorage (Browser dev tools → Application → Local Storage → usepitcrew.com → delete the entry), refresh the page, and the banner will reappear so you can re-choose. We’ll add a one- click toggle to Settings in a future release.

Cookies

Strictly necessary (always set):

• `pc_session` — a random UUID used to scope your anonymous reports before sign-in. Without it, returning to a report you ran before signing in would 404.
• Supabase auth cookies — set when you sign in via magic link or OAuth. Used to keep you signed in.

Optional, set only after you click Accept on the analytics banner:

• `ph_*` — PostHog session and user-identification cookies. Used to stitch your events together into a coherent session for product analytics. Not used for ad targeting.

None of our cookies are used for advertising or shared with third-party ad networks.

Your rights

• See your data — every report you’ve run is on the Reports page when you’re signed in.
• Delete your data — Settings → Delete my data permanently removes your account and every report attached to it. There’s no soft-delete; the rows are gone.
• Export your data — email us and we’ll send your reports back as JSON.
• Ask questions or file complaints — same email.

Changes

If we change how data is handled, we’ll update the last-updated date at the top of this page. Material changes (new third-party recipients, new data categories) will be flagged in-app before they take effect.

Contact

See the contact page for the email address and what to expect.