Privacy Policy

Overview

StoryPulse is an Atlassian Forge app. This privacy policy explains what data StoryPulse accesses, how it is used, and what protections are in place.

Data We Access

From Jira:

• Project names and keys
• Sprint names, dates, goals, and status
• Issue summaries, statuses, priorities, assignee display names, story points, and descriptions
• Issue comments (last 2 comments per issue, used for context)
• Issue links (blocked-by and depends-on relationships)
• Epic names and parent relationships
• Board IDs

From Confluence:

• Space names and IDs (for the publish destination selector)
• Page names and IDs (for the parent page selector)

User-provided:

• Project context (text you type into the Project Context field)
• Sprint context and focus topic
• Report preferences (template, audience, narrative style) — stored in Forge KV Storage

How We Use Your Data

StoryPulse uses your Jira data solely to generate the narrative report you requested. Specifically:

• Issue data is assembled into a structured prompt and sent to the Anthropic Claude API to generate the report narrative.
• Confluence space and page data is used only to display the publish destination selector and to create or update the Confluence page you choose.
• User preferences are stored in Forge KV Storage and used to pre-populate your settings on future visits.
• Monthly usage counts are stored in Forge KV Storage to enforce tier limits.

Third-Party Services

Anthropic (Claude API) — Issue summaries, descriptions, assignee names, statuses, and user-provided context are sent to the Anthropic API to generate the report narrative. This is the only external data transfer StoryPulse performs.

Anthropic's privacy policy is available at: anthropic.com/privacy

We recommend reviewing Anthropic's data processing terms if your organisation has specific requirements around AI data handling. No other third-party services receive your data.

Data Storage

StoryPulse stores the following data in Atlassian Forge KV Storage (hosted on Atlassian infrastructure):

Data	Key format	Purpose
Monthly report usage count	usage:YYYY-MM	Enforce tier limits
Monthly refinement usage count	refine:YYYY-MM	Enforce refinement limits
User preferences	userPreferences	Remember template, audience, style settings
Project context	projectContext:KEY	Persist project background across sessions

All stored data remains on Atlassian infrastructure. We do not have access to your KV Storage data outside of the app's own resolver functions.

Data Retention

• Usage counts — stored monthly, automatically superseded each month. Old keys are not actively deleted but are never read after the month they belong to.
• User preferences — retained until you clear them or uninstall the app.
• Project context — retained per project key until you clear it within the app or uninstall.

Data Security

StoryPulse is built on Atlassian Forge, which means:

• The app runs entirely within Atlassian's infrastructure.
• There are no external servers operated by Akaneo Labs.
• All Jira and Confluence API calls are made as the authenticated user, respecting your existing Atlassian permissions.
• The Anthropic API key is stored as an encrypted Forge environment variable and is never exposed to the frontend or to users.

Your Rights

You may request deletion of any data StoryPulse stores about you by contacting us at support@storypulse-ai.com. We will respond within 30 days.

Uninstalling StoryPulse from your Atlassian instance will prevent any further data access. Forge KV Storage data associated with your instance will be retained by Atlassian per their data retention policies.

Changes to This Policy

We will update this policy if our data practices change. The "last updated" date at the top of this page reflects the most recent revision. Continued use of StoryPulse after a policy update constitutes acceptance of the updated policy.

Contact

Akaneo Labs
support@storypulse-ai.com