Privacy policy

The Capasight:Lite app

Nothing leaves your Atlassian site

The app makes no external calls. It has no servers of its own, uses no third-party services, and therefore engages no subprocessors. All computation and storage happens on Atlassian's infrastructure, within your own site. The app is built on Atlassian Forge and is eligible for Atlassian's Runs on Atlassian programme, which recognises apps that run entirely on Atlassian's platform with no data leaving it.

Franklin, the app's assistant in Rovo, keeps to the same rule. Rovo is Atlassian's own AI: when you ask Franklin a question, Rovo calls the app inside your site, the app works out the answer with the same logic as the screens, and Rovo words the reply under Atlassian's terms. The app runs no AI model of its own and sends nothing to any AI service.

What the app reads

The app holds no write permission of any kind and cannot change your Jira data. It reads:

• Your work items — initiatives, features, epics and the work items beneath them, with the fields that carry size estimates, story points, the team, start and due dates, status, rank and sprint.
• How your teams are organised — where your site uses Atlassian Teams, the names of your teams and which are parents or sub-teams of which, so setup can offer that structure instead of asking you to type it.
• Whether you may change its configuration — each time you open the app, and again when you save a change, it asks Jira whether you administer it and which groups you are in. The answer decides which controls you are offered and whether a change is accepted, and is not stored.

You only ever see work Jira would show you. Spaces you cannot browse are left out of every figure, and so are work items that work item security hides from you — the page says how many were held back. Two people on the same screen see two different portfolios if that is what their Jira permissions say.

Franklin, the assistant in Rovo

Franklin answers planning questions in Rovo — capacity, late work, when an item will be delivered, what to fix first, room in the coming sprints, velocities — in Capasight's own figures and words. It reads nothing the screens do not: it answers from the same snapshot, as you, with your Jira permissions, so it never tells you about work you could not see in the app. It only reads; it changes nothing in Jira. It needs Rovo switched on for your site; the conversation, and the Rovo credits it uses, are Atlassian's and your site's.

What the app stores

Everything the app stores is held in Atlassian's own storage inside your site. There are four kinds of record.

Configuration — what an administrator or a nominated planner entered: the names of your teams, ARTs and value streams, and the Atlassian team each is linked to; team velocities; the estimate scales and thresholds; the sprint cadence; any spaces left out; Jira field identifiers; the words your organisation uses for its groups; and the names of the Jira groups nominated as planners. After a reset, the previous configuration is kept so it can be restored. Saved views — named sets of filters that anyone on your site can save and use; the name is whatever the person saving it typed.

A snapshot of your portfolio — a large portfolio cannot be read in the seconds a page load allows, so it is read in the background and every screen is served from the result. For each work item in scope, the snapshot holds its work item and space key, its summary, its work type and level, its parent, its start, due and created dates and the earliest and latest dates beneath it, its t-shirt size, the story points rolled up beneath it (in total and by team) and how many are accepted, its status, its rank, the Jira team on it and the teams on the work beneath it with their Atlassian team identifiers, and the identifier of any work item security level on it. It holds no descriptions, no comments, no attachments, and no assignee, reporter or any other user identity. It is replaced by each refresh, only the two most recent are kept, and it never leaves your Atlassian site.

Working records — what the app has measured and needs to remember between reads: each team's measured velocity and the dates of the Jira sprints its stories sit in, Jira's icons for your work types, which spaces the last read covered and when, and a record of teams renamed or moved in Jira so Configuration can tell you what changed.

What you last had open — so Franklin can answer about the page in front of you, the app keeps one short record per person, under their Atlassian account ID: the page, the level, the value stream or ART, the saved view and the item open or last opened (as identifiers, not names), the browser's time zone and language, and when. It counts for 30 minutes; every hour the app deletes any record older than that.

Because all of this is Forge hosted storage, Atlassian pins it to the same region as your Jira site and moves it automatically if you move your data residency location.

Personal data

The app keeps one piece of personal data: the record above — an Atlassian account ID with what that person last had open in the app, kept for 30 minutes and then deleted. It exists only so Franklin answers about the screen you are looking at. The app erases each record itself, within the hour after its 30 minutes are up, so no record lasts longer than about an hour and a half; that is why it does not need to report accounts to Atlassian's personal data reporting service. It records no names, no email addresses and no other user activity — not in its storage, and not in its logs. Planners are nominated by Jira group name rather than by naming individuals. It never asks for or stores an Atlassian API token.

The one thing worth stating plainly: the snapshot holds the summaries of your work items, because they are what the app puts on screen beside each figure, and the names you give your teams, groups and saved views are stored as you wrote them. Summaries and names are free text your own people wrote, so they could contain anything they chose to put there. That is your content, it is treated as your content throughout, and it never leaves your Atlassian site — but it is stored, and you should know that rather than read that nothing is.

Logs

Atlassian's platform records application logs which we can read for support and diagnosis. We deliberately record only counts, statuses and the kind of action refused. We do not log work item keys, work item summaries, field names or values, team names, the names of saved views, user identities, or the contents of Jira's responses — a failed call to Jira is logged by its HTTP status alone.

For Franklin, the app logs which question was asked, which of its inputs were filled (by name, never the value), counts and timings — never the question's wording, an account ID or the answer.

Deletion

When the app is uninstalled, Atlassian deletes everything it stored — configuration, saved views, working records, the snapshot, and the records of what each person last had open (which are deleted within the hour of going stale anyway). The data is soft-deleted at once, so the app can no longer read it, and is destroyed at the end of Atlassian's retention period of 28 days. Within 21 days of uninstalling it can be relinked to a new installation, and only at your request. Because nothing is ever copied outside your site, there is no second copy anywhere for us to delete — we hold none of it and have no way to.

Capasight for Azure DevOps

Nothing leaves your Azure DevOps organisation

Capasight for Azure DevOps is an Azure DevOps extension. It runs in your browser, inside Azure DevOps, and talks only to Azure DevOps itself. It has no servers of its own, uses no third-party services, and therefore engages no subprocessors. Its files are served by Microsoft from the Visual Studio Marketplace, and everything it stores is held by Azure DevOps, in your organisation.

What the extension reads

It reads Azure DevOps as you, with your own permissions, and holds no permission to change a work item. It reads:

• Your work items — those on your backlogs (initiatives, epics, features, user stories and bugs, or your process's own types), with their type, title, state, area path, iteration, parent, created and closed dates, story points, backlog order, t-shirt size, start date and target date.
• How your project is set up — its work item types and their states, its backlog levels, its fields, its area and iteration trees, and its teams with the areas they own and how each team works with bugs, so setup can offer your structure instead of asking you to type it.
• Whether you may change its configuration — each time you open it, it asks Azure DevOps whether you may edit the project's information and manage its properties. The answer decides which controls you are offered, and is not stored.

You only ever see work Azure DevOps would show you: work in an area you may not view is left out of every figure. Two people on the same screen see two different portfolios if that is what their permissions say.

What the extension stores and writes

It writes nothing to your work items. Everything it stores is held by Azure DevOps inside your organisation. There are three kinds of record.

Configuration — what a Project Administrator or a nominated planner entered: your value streams, ARTs and the teams in them, and the Azure DevOps team each stands for; team velocities; the estimate scales and thresholds; the sprint cadence; field identifiers; the words your organisation uses for its groups; and the Azure DevOps teams nominated as planners. It is kept in the project's properties, where Azure DevOps' own “Manage project properties” permission decides who may change it. After a reset, the previous configuration is kept so it can be restored. Saved views — named sets of filters that anyone in the project can save and use; the name is whatever the person saving it typed.

Your snapshot of the portfolio — the figures every screen is served from, built in your browser from what you may read and kept in the extension's storage for you alone: nobody else can read it. For each work item in scope it holds its ID, title, work item type and level, its parent, its start, target and created dates and the earliest and latest dates beneath it, its t-shirt size, the story points rolled up beneath it (in total and by team) and how many are done, its state, its backlog order, and the team that owns it and the teams on the work beneath it; for each team, its name, its measured velocity and its sprints' dates and completed points. It holds no descriptions, no comments, no attachments, and no assignee or any other user identity. Each refresh replaces it.

Personal data

The extension collects no personal data of its own. It records no user identifiers, no names of people, no email addresses and no user activity. Planners are nominated as an Azure DevOps team rather than by naming individuals, so no list of people is ever kept. It never asks for or stores a personal access token: Azure DevOps gives it a short-lived token for each read.

As with the Jira app: the snapshot holds the titles of your work items, because they are what the extension puts on screen beside each figure, and the names you give your groups and saved views are stored as you wrote them. That is your content, treated as your content throughout, and it never leaves your organisation — but it is stored, and you should know that rather than read that nothing is.

Logs, and what Microsoft tells us

The extension keeps no logs and sends no telemetry: it has nowhere to send them. As the publisher, the Visual Studio Marketplace gives us its own reports — how many organisations installed or uninstalled the extension, any feedback someone chooses to write when uninstalling, and ratings and reviews. Microsoft provides those under its own terms.

Deletion

Uninstalling the extension does not, by itself, delete what it stored. We tested this on 14 October 2026: once the extension was uninstalled its saved views and snapshots could no longer be read, and when it was installed again they were all still there. Microsoft does not document how long Azure DevOps keeps an uninstalled extension's storage after that. So the extension removes it itself, before you uninstall: on its Configuration page, Remove what Capasight stored lets anyone delete their own snapshot (only they can), and a Project Administrator delete the configuration, its backup and the saved views. Questions: contact@capasight.co.uk. The configuration is kept in the project's properties, so it stays until a Project Administrator removes it (the properties are named Capasight.Config and Capasight.ConfigBackup). Because nothing is ever copied outside your organisation, there is no second copy anywhere for us to delete — we hold none of it and have no way to.

Buying a licence

Licences for Capasight for Azure DevOps are sold by Capasight directly, by invoice. To issue one we collect your organisation's name, billing address and VAT number; the name and email address of the person who receives the invoice and the licence key; and your Azure DevOps organisation's ID, which the key is tied to. We use them only to invoice you, to issue and renew your licence, and to keep the accounts the law requires, under our contract with you. We do not use them for marketing.

Our accounts are kept in FreeAgent (FreeAgent Central Ltd, UK), and licence keys are issued from Amazon Web Services in London; both act only on our instructions. Invoices are kept for six years, as UK law requires; the contact's email address is removed from our licence records twelve months after a licence ends. Checking a licence key happens inside the extension, in your browser, and sends nothing to us. To see, correct or remove what we hold, email contact@capasight.co.uk.

Capasight for Azure DevOps is not affiliated with or endorsed by Microsoft.

Capasight for monday.com

Nothing leaves monday.com

Capasight for monday.com is a monday.com app. Its screens run in your browser, inside monday.com, and talk only to monday.com itself. Franklin, its assistant in monday sidekick, runs on monday code — monday.com's own hosting for apps — and talks only to monday.com too. It uses no third-party services, so it engages no subprocessors beyond monday.com. Everything it stores is held by monday.com, in your account, or in your own browser.

What the app reads

It reads monday.com as you, with your own permissions, through monday.com's own sign-in for apps; it holds no token of its own, and it has no permission to change a board. It asks monday.com for five read-only permissions:

• Boards (read) — your monday dev boards: each team's Epics, Tasks and Sprints boards, with the columns that carry status, dates, t-shirt size, story points, and which epic and sprint a task belongs to.
• Workspaces (read) — the names of the folders your boards sit in, because a monday dev team is a folder of boards.
• Me (read) — which monday.com teams you belong to, to decide whether you may change its planning settings. The answer is not stored.
• Teams (read) — your account's teams, so an admin can nominate one to do the planning.
• Account (read) — your account's ID, which keeps its storage separate.

You only ever see work monday.com would show you: boards you cannot open are left out of every figure. Two people on the same screen see two different portfolios if that is what their monday.com permissions say.

Franklin, the assistant in monday sidekick

When you ask Franklin a question in monday sidekick, sidekick asks you to approve it, and monday.com then sends Franklin's server a request signed for your account, carrying a short-lived permission that acts as you. Franklin reads your monday dev boards with it — only what you can see — works out the answer with the same logic as the screens, and returns it to sidekick, which words the reply. Franklin uses no AI model of its own and sends nothing to any AI service; the conversation is monday sidekick's, under monday.com's terms. Franklin only reads: it changes nothing in monday.com.

To answer from the same figures, Franklin's server keeps your snapshot of the portfolio in memory while you use it, and drops it after 12 hours unused. It is never written to disk, and it is gone whenever the server restarts. Franklin's server runs in monday code's United States region, whatever region your monday.com account is in.

What the app stores and writes

It writes nothing to your boards. There are three kinds of record.

Configuration — what an account admin or a nominated planner entered: your value streams, ARTs and the teams in them, and the monday dev team each stands for; team velocities; the estimate scales and thresholds; the sprint cadence; the columns it reads; the words your organisation uses for its groups; and the monday.com teams nominated as planners. It is kept in monday.com's storage for apps, for your account. After a reset, the previous configuration is kept so it can be restored. Saved views — named sets of filters that members can save and everyone can apply; the name is whatever the person saving it typed. Viewers and guests apply saved views but cannot save one.

Your snapshot of the portfolio — the figures every screen is served from, built in your browser from what you may read, and kept in your browser's own storage for this app: nobody else can read it, and it is not sent to monday.com or to us. For each item in scope it holds its ID, name, level, the epic it belongs to, its dates and the earliest and latest dates beneath it, its t-shirt size, the story points rolled up beneath it (in total and by team) and how many are done, its status, its position on its board, and the team that owns it and the teams on the work beneath it; for each team, its name, its measured velocity and its sprints' dates and completed points. It holds no updates, no files, and no people column or any other user identity. Each refresh replaces it.

What you last had open — so Franklin can answer about what you are looking at, the app records which page you have open in Capasight, the level, the value stream or ART, any saved view and the item you have open, as IDs only, with the time. It is kept in monday.com's storage for apps, under your monday.com user ID, and Franklin uses it for 30 minutes after you last used Capasight. It holds no names, titles or figures.

Personal data

The app collects no names of people and no email addresses. It uses two monday.com identifiers: your user ID, under which the record of what you last had open is stored, and your account and user IDs, which monday.com sends with each Franklin request and which Franklin's server uses to keep your snapshot apart from everyone else's. Planners are nominated as a monday.com team rather than by naming individuals, so no list of people is ever kept.

As with our other apps: the snapshot holds the names of your items, because they are what the app puts on screen beside each figure, and the names you give your groups and saved views are stored as you wrote them. That is your content, treated as your content throughout, and it never leaves monday.com and your browser — but it is stored, and you should know that rather than read that nothing is.

Logs, and what monday.com tells us

The screens keep no logs and send no telemetry to us: if a request to monday.com fails, the reason is written to your browser's own console, which only you can see. Franklin's server writes a line to monday code's logs for each answer — which kind of question it answered, your account's ID, and how long it took — and the error message when an answer fails. It never logs your question's words, board data, names or tokens. Those logs are kept by monday code under monday.com's terms. The app tells monday.com when it has shown you real figures (monday.com's “value created” signal for marketplace apps). As the developer, monday.com gives us its own reports: installs and uninstalls, plans and billing for our app, and any feedback, ratings or reviews you choose to give. monday.com provides those under its own terms.

Deletion

Uninstalling the app does not, by itself, delete its configuration. We tested this on 16 October 2026: monday.com keeps an app's storage for your account through an uninstall, and installing the app again found the configuration and saved views where they were. So the app removes it itself, before you uninstall: on its Configuration page, Remove what Capasight stored lets anyone delete their own snapshot and their record of what they last had open, and an account admin delete the configuration, its backup and the saved views. Franklin's server keeps nothing on disk; its in-memory copies go after 12 hours unused. Your snapshot is also removed when you clear this site's data in your browser. Because nothing is ever copied outside monday.com and your browser, there is no copy anywhere for us to delete — we hold none of it and have no way to. Questions: contact@capasight.co.uk.

Paying for it

Capasight for monday.com is sold and billed by monday.com, through its marketplace, on monday.com's terms. We receive no card or bank details. monday.com tells us which plan your account is on, so the app can check it, and the app reads that from monday.com in your browser.

Capasight for monday.com is not affiliated with or endorsed by monday.com.

Hosted Capasight (Asana, and Smartsheet with Jira)

Where your data is

Hosted Capasight runs on Amazon Web Services in the United States (us-east-1, Northern Virginia). Licensing runs separately in London (eu-west-2). Your organisation controls the work data it connects; Capasight processes it to run the service.

What Capasight reads

Read-only, through the access you allow at sign-in: workspaces, users, portfolios, projects, tasks, custom fields and teams. It never changes anything in Asana.

What Capasight keeps

• Your work: each item's name, T-shirt size, points, dates, completion, team and place in the hierarchy. It keeps no descriptions, comments or attachments.
• Your account: your name, organisation and work email; your password, stored only as a scrypt hash; your two-step secret, sealed with AWS KMS; your sign-in sessions; and, if you choose, a trusted-browser record.
• The access Asana issues: sealed with AWS KMS and never shown again.
• An audit trail: sign-ins and admin changes, with who acted, from which IP address and when. It is kept for one year, and pseudonymised when a workspace is deleted.
• Logs: the service's logs, which include IP addresses, kept for 30 days.
• Backups: encrypted, kept for 30 days.

Who else handles it

• Amazon Web Services: hosting, encryption keys, logs and backups.
• Microsoft 365: sends the service's emails (welcome, sign-in links, password resets).
• Have I Been Pwned: checks a new password against known breaches using the first 5 characters of its hash only; the password itself never leaves Capasight.
• Asana: the source of your work, under your own agreement with Asana.

How long it is kept

• Removing the Asana connection deletes everything read from Asana.
• A workspace that never connects a tracker is deleted with its contact details 30 days after sign-up.
• After a licence lapses, a workspace's data is deleted 30 days after the licence gate, unless it is renewed.
• Deleting a workspace removes its data, sessions, two-step secrets and trusted-browser records.

To see, correct or remove what we hold, email contact@capasight.co.uk.

Capasight for Asana is not affiliated with or endorsed by Asana.

The capasight.co.uk website

Registration form

If you register for a session, we collect the details you enter and your consent choices. They are stored encrypted in the United Kingdom (London), retained for 12 months, and used to run the session you registered for. Attendance and marketing consent are recorded separately: you receive the joining details either way, and marketing email only if you opted in.

Analytics

With your consent, this website uses Google Analytics to see how visitors use it — which pages are viewed and how, including how a visitor arrived. A cookie-consent banner is shown on first visit; analytics only runs if you accept it. Declining, or leaving the banner unanswered, means nothing is sent to Google, on any page. Where it runs, IP addresses are anonymised. Google processes this data on our behalf under its own terms and privacy policy (policies.google.com/privacy), which covers how it is handled, including transfers outside the UK. You can withdraw consent at any time by declining when the banner is next shown, or by clearing this site's data in your browser.

What we do not do

We do not sell or share your details. We do not use advertising trackers, and analytics only runs with your consent, as described above.

Your rights

You can ask us for a copy of what we hold, ask us to correct it, or ask us to delete it. Email contact@capasight.co.uk and we will action it.

Contact

contact@capasight.co.uk