Sprint Verdict foooverse

Privacy policy

Last updated: 5 September 2026


The short version

This app does not store your data on any server we control. It has no database, no analytics, and no external services. Everything it reads and writes stays inside your own Atlassian Cloud site.


Who we are

Foooverse is an independent software project, built and maintained by a single developer.

Contact: support@foooverse.com

Foooverse is the Marketplace Partner responsible for this app. For the data in your Jira site, you are the data controller and Foooverse acts as a processor — see Personal data below.

The developer behind it is identified and verified with Atlassian under the Marketplace Partner programme; full legal and contact details are available on request to the address above, and will be provided to any customer, regulator or authority that asks.

Foooverse is not a registered company. If it becomes one, this section will name the registration.


What the app reads

Only what it needs to calculate capacity, and never more than the person using it could already see. Jira is read by the app rather than as the individual, so the app enforces the check itself: before returning anything it asks Jira which projects that viewer may browse, and drops every board they may not. A board it cannot match to a project is hidden rather than shown.

DataWhy
Boards, sprints, and the issues in themThe work being measured
Issue fields — summary, type, status, assignee, estimate, dates, labels, parentCapacity and completion maths
Issue change historyAccurate burndown, based on when work actually finished
Display names and account IDs of assigneesShowing who is on the team
Field definitions on your siteLetting an admin pick the estimation field
Projects and assignable usersThe leave-project picker and team roster
Issues matching your leave JQL, if configuredReading leave you already track in Jira

The app does not read issue descriptions or comments except to check whether a description exists at all (a backlog-readiness rule). The content is never stored or transmitted.

What the app writes

One thing, and only when someone with project admin permission saves it on the Team page:

It holds one team per board in that project. For each board: the roster (display name and Atlassian account ID), per-person availability settings, the leave-source configuration, any leave typed in by hand, and the public holiday calendar.

Holidays can be added in bulk by pasting a list. That is still one write to the same property — a year of holidays is a single save, not one per date.

The app never creates, edits, transitions, comments on or deletes an issue, sprint, board or project.

Leave read from Jira issues is never copied into this property. It stays where it is.

Where data is stored

WhatWhereWho controls it
Team roster and settingsA project property in your Jira Cloud siteYou
Leave, when read from issuesYour Jira issues, untouchedYou
Display preferences (metric mode, chart settings)Forge storage, on Atlassian's infrastructureAtlassian, per your install
Light/dark preference and themeYour own browser's local storageYou

The last row is the only thing the app stores outside Jira, and it is two strings — which theme you picked and whether you prefer light, dark or automatic. It never leaves your browser, is never sent to Jira or to us, and two people looking at the same board can have different settings. Clearing your browser data resets it and loses nothing else.

Nothing is stored on infrastructure operated by Foooverse. The app runs entirely inside Atlassian's Forge platform.

What we do not do

Personal data

The only personal data the app handles is what Jira already holds: display names and Atlassian account IDs of people on a board, plus their leave dates if you configure leave tracking.

Leave dates can imply sensitive information — a long absence recorded as sick leave, for example. The app reads leave you have already chosen to record in Jira, applies your own project permissions to it, and stores none of it. If that inference concerns you, use a generic leave type or keep leave in a project with restricted permissions.

We are a data processor; you remain the data controller.

Retention and deletion

Sub-processors

None. The app has no external network access. Atlassian hosts the runtime and the data.

Data residency

The app stores no data of its own, so residency is entirely determined by your Atlassian Cloud site's region. Forge respects Atlassian's data residency commitments.

Your rights

Because we hold none of your data, requests for access, correction, export or deletion are served directly from your Jira using the REST calls above. Contact us at support@foooverse.com if you need help.

Security

See our security statement. Report a vulnerability to support@foooverse.com — we aim to acknowledge within 2 business days.

Changes

Material changes will be announced on the Marketplace listing before taking effect.

Contact

support@foooverse.com