Privacy policy
Effective July 15, 2026
Burn is designed to make aggregate AI-agent activity social without uploading the work itself. This policy explains the narrow data boundary, the controls you have, and how to contact us.
What Burn collects
- Daily aggregate token totals by supported agent and model: input, output, cache reads, cache writes, estimated cost, message counts, and session counts.
- Collector metadata needed for reliability: a random installation identifier, device name, operating-system family, collector version, sync and attempt times, scheduler and parser state, detected supported agents, and a bounded error category such as network or authorization. Full error messages and local paths stay on your machine.
- Your Burn account and profile data: handle, display name, sign-in identity if you secure the account, visibility setting, and account creation time.
- Product data you choose to create: follows, kudos, team memberships and roles, goals, check-ins, reports, blocks, in-app notification state, and your weekly-reminder preference.
- Bounded first-party product counters, such as whether onboarding instructions were copied or a dashboard was opened. Burn stores one aggregate count per account, day, and allowlisted event—never screen contents or advertising identifiers.
What stays on your machine
Burn does not collect prompts, responses, code, files, file paths, project names, repository names, terminal history, or raw agent-session content. The companion collector reads supported local usage records, reduces them to allowlisted numeric aggregates, and sends only those aggregates.
How Burn uses data
We use the data to sync your activity, calculate streaks and rankings, improve activation and reliability, show the visibility and social features you request, operate teams, prevent abuse, troubleshoot reliability, and secure the service. Burn does not sell personal data or use your prompts or code to train models because Burn never receives that material.
Visibility and sharing
Guest Burns start private. You can explicitly make a Burn public or private in Settings. Public profiles can show aggregate totals, streaks, agent mix, milestones, and goals you mark public. A followers-only goal is shown only to a current follower. Kudos are attached to a visible aggregate activity event; blocking removes kudos between both accounts. Teams change who can access a shared aggregate leaderboard and weekly Team Pulse; they do not change what the collector uploads. Team Pulse never shows last-active timestamps or per-person agent mix, and aggregate agent mix stays hidden until at least three team members are active that week.
Weekly reminders
Weekly recap reminders are off by default. If you enable one, Burn asks for notification permission after your confirmation and schedules a local Monday reminder on that device. Burn stores the last preference you set with your account; the notification schedule itself stays on that device. This setting does not enable marketing notifications.
Service providers and transfers
Burn uses hosting, database, authentication, and platform providers to operate the service. They process data for Burn under their service terms and only as needed to provide those functions. Data may be processed where those providers operate. We use reasonable technical and organizational safeguards, but no online service can promise absolute security.
Retention, export, and deletion
You can export your Burn data as JSON and delete your account from Settings. Account deletion removes the profile, aggregate usage, collectors, goals, check-ins, follows, kudos, blocks, notifications, notification preferences, and memberships associated with that account. A report may be retained where needed to investigate abuse, meet legal obligations, or protect the service. Revoking a collector stops future syncs; uninstalling its local daemon removes its scheduled job.
Children and changes
Burn is not directed to children under 13, or a higher minimum age where local law requires it. We may update this policy as the product changes and will post the effective date here. Material changes will be communicated in the app when appropriate.
Contact
Questions, privacy requests, and safety concerns can be sent to [email protected].