Getting started
- Get access — private beta via hello@sprintaiapp.com. Public Marketplace listing ships soon.
- Run archaeology — open SprintAI on a Scrum or Kanban project and let Pulse read ~5 closed cycles into the brain (with claim gates on thin data).
- Complete setup — guided wizard for team profile, DNA, velocity, and Data Quality.
- Run the week from Pulse — Overview (Pulse Brief), Health & Risks, Plan Sprint (Scrum), Reports + share links, Brain.
Frequently asked questions
What data does SprintAI store?
SprintAI stores delivery intelligence only: sprint metadata, ticket titles, assignees, story points, velocity history, and AI-generated pattern memories. We do not store full issue descriptions, comments, or attachments. See our Privacy Policy for full details.
How do I delete my data?
Uninstall SprintAI from your Jira site — all data is automatically scheduled for deletion within 30 days. For immediate deletion, email support@sprintaiapp.com with your Jira cloud ID and project key.
Why does Pulse need sprint history?
Pulse builds a persistent brain from your team's actual delivery patterns — who completes what, which ticket types slip, and how velocity trends over time. Without history, Pulse can only give generic advice. With archaeology, it learns patterns specific to your team in minutes instead of months.
What AI model powers Pulse?
Pulse uses Anthropic Claude(Claude Haiku) for delivery intelligence inference. Your data is sent to Anthropic's API for processing and is not used to train AI models.
Is my data used to train AI?
No. SprintAI uses the Anthropic API under terms that prohibit using API inputs for model training. We also do not use your data to train any SprintAI models. Anonymised aggregated delivery patterns may be used to improve prediction accuracy across the platform — never in a way that identifies your team.
Contact us
Email support@sprintaiapp.com for help with installation, setup, bugs, or feature questions.
Response time: within 2 business days.