Privacy policy

Local records. Clear connections.

Last revised September 9, 2026. Storybloq keeps core project records in local files. Connected AI clients, companion access, feedback, and diagnostics have separate data flows, described below.

Local project records

Storybloq is available as a Mac app and the@storybloq/storybloq CLI, MCP server, and Story skill for Claude Code and Codex. Core project records are JSON and Markdown files in your .story/ directory. The CLI and Mac dashboard read and update these files on your machine. No Storybloq account is required for that workflow.

You control the files and what you commit to Git. If you push them to a remote repository or place them in a synced folder, that service also receives them. Local storage is not a guarantee that every connected workflow stays on your device.

AI clients and review providers

Claude Code, Codex, and configured review backends can read project context and code through Storybloq or directly from your files. Depending on the client and configuration, that information is sent to the AI provider to process the request. Its privacy, retention, and account settings apply.

Choose your client and review providers with the needs of your project in mind. Storybloq does not make a cloud AI service operate offline.

Companion devices and remote access

Paired companion devices can receive project board and session information over a local connection. Optional remote access uses Apple CloudKit in your private iCloud database to relay project names, board contents, session status, commands, and permission requests between your devices. Permission requests may include tool names, descriptions, and input previews.

Remote access is off by default. Enabling it sends this information through Apple's service. It is separate from the Mac analytics preference. See Apple's privacy policy for Apple's handling of service data.

Feedback and support

Submitting community feedback sends the title, description, category, app and platform information, and any screenshot you choose to attach. App feedback uses Apple CloudKit's public database; comments and votes also use account-associated record identifiers. Community feedback is intended to be visible to other users. Include only information you want to share.

GitHub issues are governed by GitHub's visibility and privacy settings. When you contact support by email, we receive your address and the message and attachments you send. Use email for private support requests rather than posting sensitive details in public feedback.

Optional Mac analytics and crash reports

Mac analytics and crash reporting are off by default. You can choose to enable them on first launch or change your preference in Settings. This preference controls diagnostics, separately from companion access and feedback you submit.

  • TelemetryDeck receives usage events such as features opened, error categories, and project sizes grouped into ranges. These events are designed to describe app usage without ticket text or project names. See the TelemetryDeck privacy policy.
  • Sentry receives crash diagnostics and sampled performance traces, with app version, build, operating system, and feature-setting information. The app disables default personal information collection and replaces home-directory paths before upload. See the Sentry privacy policy.

Website analytics

This website uses Vercel Web Analytics to understand site usage. It can collect page URLs, referrers, approximate location, and browser and device information for aggregate reporting. This is separate from the Mac app's diagnostics preference. See Vercel's analytics privacy documentation for the data collected and how it is handled.

Your choices and retention

You manage the retention of your local project files and Git history. Copies sent to AI providers, Apple, GitHub, diagnostics providers, or other services are subject to their settings and retention policies. Turning a feature off does not by itself delete information already sent.

For privacy questions or access and deletion requests relating to data handled by Storybloq, email shayegh@me.com. We may need enough information to identify the relevant records. For data controlled by another provider, use that provider's account and privacy controls as well.

Changes to this policy

We update this page as the product and its data flows change. The revision date above identifies the latest version.