Who we are
BLOOMLOGIC LTD, registered in England and Wales, company number 11173973, registered office 82a, James Carter Road, Mildenhall, Bury St. Edmunds, England, IP28 7DE. Contact: privacy@bloomlogic.co.uk.
Effective 23 September 2026 · Last updated 23 September 2026.
How this policy is arranged
Part one is about the company and is true of everything we do. Part two covers each product we make, because what a product reads and stores depends on what it is. Today there is one: Canopy, an app for Jira.
Part one — The company
The short version
We hold very little about anybody. We use no analytics, no advertising and no tracking of any kind, and we set no cookies on our website beyond what it needs to work. We do not sell, rent or share personal information with anyone.
Two different roles
When you use one of our products inside your own systems, your organisation decides what is held there and why. Your organisation is the controller; we act on its instructions as a processor. What that means for each product is set out in part two.
For our own records — people who email us for support, report a security issue, or correspond with us about a product — we are the controller. That is the only personal data we decide the purposes of.
What we hold about you directly
If you write to us, we hold your message, your email address, and whatever you chose to tell us, for as long as it takes to deal with the matter and for two years afterwards. We use it to answer you and for nothing else.
Who else is involved
We use no analytics provider, no error-reporting service, no advertising network and no artificial intelligence service of our own. Where a product depends on a supplier, that product's section names it.
Your rights
You can ask us for a copy of what we hold about you, ask us to correct or delete it, or object to our holding it. Write to privacy@bloomlogic.co.uk and we will answer within one month. Where the information is inside your own organisation's systems, your organisation is the right first contact, because it decides what is held there — we will help it answer you promptly. You can also complain to the Information Commissioner's Office at ico.org.uk.
Children
Our products are tools for workplaces. They are not directed at children and we do not knowingly hold information about them.
Changes to this policy
If this policy changes we will update this page and the date at the top. Where a change matters to how your data is handled, we will say so on the page rather than change it quietly.
Part two — Our products
Canopy, for Jira
Canopy is an app installed into your own Atlassian site. It runs entirely inside Atlassian: there are no servers of ours, no database of ours, and no connection to any other company. We cannot see your issues.
What it reads
When somebody opens Canopy, it reads from Jira using that person's own permissions and nothing more:
-
Issues and their fields: key, summary, type, status, priority, dates, estimates
-
The links between issues, which is how Canopy knows the shape of the plan
-
Who work is assigned to, so a card can show it
-
Project, board and sprint details
-
The name and avatar of the signed-in person and of assignees
This is read when needed and shown on screen. It is not copied to us and does not leave Atlassian.
What it stores
Canopy keeps a small amount of its own information in Atlassian's Forge storage, inside your site, each person's entries labelled with their Jira account identifier:
-
Saved Views and Branches — the filters and focus points a person has saved
-
Display preferences — palettes, visible columns and fields, folded parts of the tree, pinned cards, text size, chosen theme
-
Keyboard learning counters — how often each shortcut has been used, so the app stops offering a hint someone no longer needs
-
Baselines — a dated snapshot of the plan's dates, estimates and statuses, saved deliberately so later changes can be compared against it
-
A short-lived change journal — that a card was reordered or deleted, so other people's screens update. These expire automatically and are not a history of your project
-
An archive record — which items were archived, by whom, when
-
The site's subscription state, as Atlassian reports it
Sibling order is stored on the issue itself, as a Jira property, not with us.
What is kept on your own device
For speed, Canopy keeps a copy of what it last displayed in your browser's own storage: issue data already fetched, your display preferences, and a local record of any error it hit. This never leaves your browser. Clearing the site's data removes it.
Artificial intelligence
If your site has Rovo enabled and someone uses the Canopy branch digest, the issues in that branch are passed to Atlassian's Rovo AI to be summarised — issue keys, summaries, statuses, due dates, priorities, and the names of the people work is assigned to.
That happens inside Atlassian, under Atlassian's terms, using your organisation's Rovo credits. Nothing goes to an AI service of ours or anyone else's, and nothing is used to train a model by us. If your organisation does not want this, do not enable Rovo, or do not use the feature.
Who else is involved
Atlassian, and nobody else. Typefaces and every other resource ship inside the app rather than being fetched from elsewhere.
Where it is held, and for how long
Everything Canopy stores is held by Atlassian within your own site. Where that sits geographically, and any data residency option, is governed by Atlassian's arrangements with your organisation, not by us. The change journal expires automatically after a short period; everything else is kept until deleted in the app, or until the app is uninstalled.
What happens if you uninstall
Saved Views, Branches, palettes, preferences, baselines, archive record and journal are deleted with the app and cannot be recovered. Your Jira work is untouched — the hierarchy lives in Jira's own issue links and properties, so every issue and the structure connecting them remains exactly as it was.