Privacy

Data & Telemetry

What BranchPy collects, what it does not collect, and why. Current for BranchPy Studio v2026.2.1.

Analysis stays on your machine

BranchPy's analysis engine runs locally on your device. Your scripts, images, project files, story content, and analysis outputs are not uploaded to BranchPy.

Limited operational data. BranchPy Studio v2026.2.1 sends product signals so we can understand usage frequency, errors, and feature reliability. These signals are designed to describe how BranchPy behaves, not what is inside your game.

Exception — Project Advisor (Pro, BYOK): when you configure and use Project Advisor, anonymized project evidence is sent to your chosen AI provider. BranchPy does not receive this data. See Privacy Policy §3.4.

Transparency

What we collect and what we do not collect

What we collect

  • Authentication and session events, such as login, logout, and account security activity.
  • Tool usage signals, such as which tool ran, its status, coarse duration bucket, and detected engine type.
  • Technical error categories, such as a broad error class, to measure reliability.
  • Version, operating system family, and license tier information when available.

What we never collect

  • Your scripts, dialogue, story text, or creative content.
  • Your images, audio, project files, full paths, or file names.
  • The detailed outputs of your local analyses.
  • Secret machine identifiers or authentication tokens inside event payloads.
  • Data for targeted advertising, resale, or personal profiling.

Two different systems

BranchPy separates product signals from diagnostic telemetry. They follow different rules.

Always-on product signals

These signals are emitted automatically when major actions start or finish. If Studio is offline, signals are held temporarily in BranchPy Studio local app data and retried during a later online use.

The local queue is capped, old events expire, and the queue is not stored inside your project folder.

Optional diagnostic telemetry

Local diagnostic telemetry is separate. It is stored on your device and sent only through the diagnostic or deferred upload flow when that flow is enabled.

It is not required to use BranchPy.

Why we collect it

  1. Product reliability: know which features fail and where fixes matter most.
  2. Update planning: understand which surfaces are actually used.
  3. Support: diagnose BranchPy problems without inspecting your game.
  4. Account security: protect logins, sessions, and licenses.

Retention

Raw operational data is kept for a limited period. Offline local queues are capped and old events expire. Aggregated statistics may be kept longer to understand reliability and usage trends.

What we will never do

  • Sell, share, or monetize your personal data or content.
  • Access your creative content or project files.
  • Use your data for targeted advertising.
  • Change this policy silently.

Questions?

If you have questions about our data practices, reach out via the Community page.