EFFECTIVE 27 AUGUST 2026

Privacy Policy

This policy describes Hourblue's approach to data processed through Hourblue Enterprise products and this website. It will be supplemented by product-specific privacy information before each product is released.

Our approach

We design our products to access and process only the information needed to provide their documented functionality. We do not sell customer or end-user data.

Information we may process

Depending on a product's documented permissions and configuration, we may process account, configuration, support, and technical information, as well as the minimum customer or end-user data needed to provide the product.

Use, storage, and sharing

We use information to operate, secure, support, and improve the product. We use service providers only where necessary to provide those services and do not disclose information except as required by law or to protect the service and its users.

Product disclosures

Before release, each product's Marketplace listing and documentation will identify its requested permissions, whether it stores data outside Atlassian products, and any applicable data-location or security details. If an app's practices change, we will update its public disclosures.

DBML Diagrams for Confluence

What the app reads. When a page contains a DBML diagram macro, the app reads the body of that one page or blog post to find the code block it should draw. It uses a single Confluence permission, read:page:confluence, and reads nothing else in your site.

What the app stores. Nothing on our systems: we operate no servers, database or storage for this app. Two things are stored, neither by us. Which code block a macro draws is saved by Confluence as part of that macro, inside your own page content. Each reader's browser remembers the last height of a diagram, as a single number, so the page does not jump while the diagram loads; that stays on their device.

What leaves your site. Nothing. The diagram is drawn inside the reader's browser, on Atlassian infrastructure. The app makes no requests to us or to any third party, includes no analytics or tracking, and sets no advertising cookies.

Personal data. The app does not collect personal data. The only personal data we receive is what you send us in a support request. If you use the app's “copy details” button when reporting a problem, those details include the DBML source of the diagram, which is why the app tells you so before you send them.

DBML Diagrams for Jira

What the app reads. When an issue has the DBML diagrams panel, the app reads that issue's description and comments to find the code blocks it should draw. It uses a single Jira permission, read:jira-work, and reads only the issue being viewed. Above each diagram from a comment, the app shows the comment's author and date, which the viewer can already see on the issue; it keeps neither.

What the app stores. Nothing on our systems: we operate no servers, database or storage for this app. Two things are kept, neither by us. Jira remembers which issues the panel has been added to, as it does for any app panel. Each viewer's browser remembers the last height of each diagram, as a single number, so the issue does not jump while the diagram loads; that stays on their device.

What leaves your site. Nothing. The diagram is drawn inside the viewer's browser, on Atlassian infrastructure. The app makes no requests to us or to any third party, includes no analytics or tracking, and sets no advertising cookies.

Personal data. The app does not collect personal data. The only personal data we receive is what you send us in a support request. If you use the app's “copy details” button when reporting a problem, those details include the issue's key and, for a diagram that failed to draw, its DBML source. The app tells you when they include the source, before you copy them.

Privacy enquiries