Privacy policy

Your project data stays with you.

Effective April 26, 2026. Tickets, issues, handovers, source code – none of it leaves your machine. Here is exactly what the app does and does not collect.

About storybloq

storybloq is an independent project distributed as-is under the terms of its license. It is available as a Mac app (listed on the App Store as .story), a CLI/MCP server (the npm package storybloq), and a Claude Code plugin. For privacy questions, open an issue on GitHub.

CLI, MCP server, and Claude Code plugin

The storybloq CLI, MCP server, and Claude Code plugin operate entirely locally. They read and write .story/ files on your machine and communicate only with the local Claude Code process. They do not include analytics, telemetry, or crash reporting. No data is sent anywhere.

What the Mac app does with your data

The Mac app (.story on the App Store, storybloq elsewhere) stores all project data locally in a .story/ directory inside your project folder. Tickets, issues, handovers, and roadmap files never leave your machine. The app reads these files directly from disk.

Mac app: optional analytics and crash reporting

The Mac app includes optional anonymous analytics and crash reporting. They are off by default. On first launch you’ll see a one-time prompt asking whether to enable them; you can also change your choice any time in Settings.

When enabled, we use two services.

  • Sentry GmbH (Frankfurt, EU) for crash reports and performance traces. Crash stack traces are collected with home directory paths replaced by ~ before upload. Each report includes app version, macOS version, build number, and whether experimental features are enabled. Session health data (app launch/close, session duration, crash-free rate) is tracked anonymously. Performance traces are sampled at 10%. No personal information is sent (sendDefaultPii = false). Sentry privacy policy.
  • TelemetryDeck GmbH (EU) for usage analytics. We track which features are used (e.g., notes panel opened, terminal launched), error categories (e.g., file load failure), and bucketed project sizes (ticket and issue counts grouped into ranges like 0, 1-5, 6-20, 21-50, 50+). No exact counts, no project names, no ticket content. TelemetryDeck privacy policy.

What we do NOT collect

  • Project names or directory paths
  • Ticket titles, descriptions, or content
  • Issue details or handover text
  • Source code
  • Personal information (name, email, IP address)
  • Keystrokes or screen content

How to opt in

Storybloq does not collect analytics or crash reports unless you opt in. On first launch you’ll see a consent prompt with Don’t Allow and Allow Analytics & Crash Reports buttons; choose either. To change your choice later, open Settings (gear icon) → Privacy and toggle “Send anonymous usage data and crash reports” on or off. The toggle takes effect immediately. Your preference is stored locally on your device and persists across launches.

Legal basis

We process analytics data based on your explicit consent, given by tapping Allow on the first-launch prompt or enabling the toggle in Settings. You can revoke consent at any time by toggling the setting off, which immediately stops all data collection.

Data retention

Crash reports and analytics are retained according to the default policies of Sentry and TelemetryDeck. We do not maintain a separate data store.

Your rights

You can request deletion of any data associated with your anonymous identifier by opening an issue on GitHub. Since we do not collect personal information, most data cannot be linked back to you.

Data transfers

Both Sentry and TelemetryDeck process data in the European Union. No data is transferred outside the EU.

Changes to this policy

We may update this policy to reflect changes in the app or applicable law. The effective date at the top of this page will be updated accordingly.