Skip to content

Privacy Policy

Last updated: October 26, 2026

What Blaug cannot access

Blaug has zero access to your prompts, conversations, code, file contents, or anything you do inside Claude Code or Codex. We cannot read them, store them, or transmit them - the data simply never leaves your machine.

The CLI runs ccusage locally to aggregate your session logs into daily totals - token counts, cost, model names, and session count. Those totals are all that ever get sent. The raw logs, your project files, and every conversation stay on your device.

You can verify this yourself: running npx blaug-cli --dry-run shows you the exact payload before anything is sent.

1. Information We Collect

When you use Blaug, we collect:

  • Account information: email address, username, and profile details provided during signup. If you sign in with Google or Apple, we also receive the basic profile details that provider shares - your email address and, where provided, your name and profile picture. If you hide your email address when signing in with Apple, we receive an Apple-generated relay address instead. If you sign up with an email and password, your password is stored only in hashed form by our authentication provider - we never see it or store it in plain text
  • Session metadata: the start time, end time, duration, and surface (Chat, Artifact, Code, or Design) of work sessions you log - never the prompts, code, conversation content, or anything you do inside a session
  • Device information:if you use the CLI, the name of each machine you connect it from (its hostname, or a name you choose), its operating system, and whether it is a WSL distro, a container, or a cloud environment. This is shown only to you, on your Data Sources and Apps & Devices pages
  • Analytics: page views and basic interaction data via Vercel Analytics and PostHog. While you are signed in, PostHog links this activity to your account, including your account ID, email address, and profile picture

2. How We Use Your Information

We use your information to:

  • Provide and maintain the Service
  • Sign you in, keep your account secure, and send account emails such as password resets
  • Display sessions you make public on feeds and leaderboards
  • Send notifications about interactions with your content
  • Improve the Service based on usage patterns

Information we receive from Google or Apple is used only to create your account, sign you in, and fill in your profile. We do not use it for advertising, and we do not sell it.

3. Data Visibility

Accounts and sessions are private by default. New accounts are private: people must request to follow you, and only followers you approve can see your profile and activity. You can make your account public in Settings. Every session you log stays visible only to you until you change its visibility. You control this per session:

  • Private: the default - a personal log only you can see
  • Friends: shared with the people who follow you
  • Stealth: shows only the session title and statistics - not the description, images, or a link to the session itself
  • Public: posted to the feed for anyone to see (available once your account is public)

Nothing is shared until you choose to. Only sessions you set to Public appear on the feed and leaderboards.

4. Data Storage

Your data is stored securely on Supabase infrastructure. We use Row Level Security policies to ensure users can only access data they are authorized to see.

5. Third-Party Services

We use the following third-party services:

  • Supabase: authentication and database hosting
  • Vercel: application hosting and analytics
  • Google: sign-in (if you choose Sign in with Google). Google shares your email address, name, and profile picture with us. See Google's Privacy Policy
  • Apple: sign-in (if you choose Sign in with Apple). Apple shares your email address, and your name where you allow it. See Apple's Privacy Policy
  • Resend: delivery of account and notification emails, which requires sharing your email address and the message content with them
  • PostHog: product analytics, as described above

6. Data Retention

Your data is retained for as long as your account is active. You may request deletion of your account and associated data at any time.

7. Cookies

We use essential cookies for authentication and session management. We do not use third-party tracking cookies.

8. Your Rights

You have the right to:

  • Access the personal data we hold about you
  • Request correction of inaccurate data
  • Request deletion of your data
  • Export your data

9. Changes to This Policy

We may update this policy from time to time. We will notify users of significant changes via the Service.

10. Contact

Questions about this policy? Reach out at hello@blaug.app.