Privacy policy

What Storyblast collects

• Account and access information needed to let you sign in, confirm a purchase, and verify plugin entitlement.
• Checkout and payment metadata processed through Stripe so Storyblast can confirm purchase status.
• Plugin-link state and short-lived plugin session metadata used to let the Figma plugin confirm that the linked account has access.
• Support emails and troubleshooting context you choose to send to support@storyblastai.com.

Plugin and local bridge data

The Storyblast plugin stores a small amount of configuration on your device through Figma client storage, including your Storyblast base URL, local bridge URL, and short-lived plugin session data. Generation in Storyblast v1 currently runs through a local Codex bridge on your machine rather than through Storyblast-hosted generation endpoints.

That means creative inputs you send for generation are handled by the local bridge and your configured Codex/OpenAI account. Storyblast’s web app uses your account and entitlement state to unlock the plugin, but does not need your generation prompts to grant access.

How Storyblast uses information

• To create and secure your account.
• To process purchases, refunds, and access recovery.
• To link the plugin to the correct Storyblast account.
• To respond to support and operational issues.
• To maintain service reliability and prevent abuse.

Sharing and retention

Storyblast relies on third-party providers including Clerk for authentication, Stripe for payments, Figma for plugin distribution, and OpenAI/Codex when you use the local generation flow. Storyblast keeps account, access, and support information only as long as reasonably needed for product operation, support, and compliance.

If you need to request deletion or have privacy questions, contact support@storyblastai.com.