Privacy First

Privacy & Data Protection

Effective Date: May 23, 2026

Overview

SprintBrief is designed with a privacy-first, minimal-retention architecture focused on reducing unnecessary data exposure.

The platform analyses Jira exports to generate delivery intelligence dashboards, forecasting insights, operational analytics, and stakeholder-ready project summaries. Wherever possible, processing is performed locally and deterministically before any AI narrative generation occurs.

SprintBrief does not permanently store uploaded CSV files, pasted ticket content, or generated operational text outputs.

Uploaded Jira exports are processed transiently in-memory to generate analytics and reports, after which the source data is discarded rather than retained as a long-term data store.

To further minimise exposure:

  • Raw Jira exports are not transmitted directly to AI providers.
  • Deterministic analytics and forecasting are calculated locally.
  • Only compact, reduced operational summaries are sent for AI-assisted narrative generation.

This architecture is intentionally designed to:

  • Minimise third-party data sharing.
  • Reduce sensitive operational exposure.
  • Avoid unnecessary data persistence.
  • Provide transparent and privacy-conscious AI-assisted reporting.

SprintBrief is not intended to operate as:

  • A Jira backup platform.
  • A document repository.
  • A long-term operational data warehouse.

The platform is designed to generate delivery intelligence and stakeholder reporting while minimising retained customer data wherever practical.

What Data SprintBrief Processes

SprintBrief may process information contained within uploaded Jira CSV exports, including:

Issue summaries
Ticket statuses
Priorities
Dates
Workstream information
Comments
Delivery metrics
Operational metadata
Please Note: Uploaded files may contain business-sensitive information depending on how Jira is used within your organisation.

Local Processing Architecture

SprintBrief is designed to process the majority of analytics locally before narrative generation occurs. This includes:

CSV parsing
Delivery analytics
Risk scoring
Backlog calculations
Forecasting
Workstream grouping
Trend analysis
Dashboard generation

This approach significantly reduces the amount of raw operational data shared externally.

AI Processing

SprintBrief uses external AI providers to generate stakeholder-ready narratives and executive summaries.

Importantly:

  • Raw Jira exports are not transmitted directly to AI providers.
  • Ticket-level detail is aggressively reduced before AI processing.
  • Compact operational summaries and aggregated insights are sent instead.

Examples of information sent to AI providers may include:

  • Delivery health summaries
  • Aggregated risk counts
  • Backlog trends
  • Forecast summaries
  • Workstream metrics

SprintBrief does not intentionally send full Jira exports or complete ticket histories to AI providers.

Data Storage & Retention

SprintBrief is designed to minimise persistent data retention.

Current platform behaviour:

  • Transient ProcessingUploaded CSVs are processed transiently.
  • In-Memory CalculationsAnalytics are generated in-memory where possible.
  • Temporary CachingReports may be temporarily cached to improve user experience and tone switching performance.

SprintBrief is not designed as a long-term Jira data storage platform.

Third-Party Services

SprintBrief may use trusted third-party infrastructure providers for:

AI processingHostingAnalyticsError monitoring

Examples of infrastructure partners may include:

OpenAIAI Summaries
Google GeminiNarrative Generation
VercelHosting & Serverless

These providers may process limited operational summary data required to generate outputs.

Security Principles

SprintBrief is built around the following fundamental security principles:

  • Minimise unnecessary data transfer
  • Reduce AI payload exposure
  • Avoid unnecessary data persistence
  • Process operational analytics locally where practical
  • Use encrypted HTTPS transport

Your Responsibilities

Users should avoid uploading information they are not authorised to process through third-party software or AI-assisted tooling.

Organisations remain responsible for ensuring uploaded Jira exports comply with their internal security and data governance policies.

GDPR & Regulatory Position

SprintBrief aims to follow privacy-conscious engineering practices. However, organisations should independently assess suitability for their own regulatory or compliance requirements.

Contact Us

For questions regarding privacy, data handling, or security practices, please contact our privacy desk.

privacy@sprintbrief.ai