Privacy Policy

Last updated: August 30, 2026

Sullins Labs builds apps for the Atlassian Marketplace. This page explains what data those apps collect, how it is used, and where it lives. It covers PIER, our Mermaid diagram rendering app for Confluence and Jira; SOUNDING, our Confluence permissions-inventory app; and DRYDOCK, our Confluence stale-page finder. It will be updated as further apps ship. A short section at the end covers the sullinslabs.com website itself, which is a separate thing from the apps.

What data we collect

PIER collects only the diagram content you create: the Mermaid diagram source text you type into the editor.

SOUNDING reads what it needs from your Confluence site to build its permissions-inventory dashboard: your spaces and their permission grants, your pages' view/edit restrictions, and the accountIds and display names of the users, groups, and access-classes those grants and restrictions reference. It does not use the content of your pages, only the structural and permissions metadata described above. Its dashboard is also gated behind a Confluence-admin capability check, so only admins can run it.

DRYDOCK collects only non-personal operational data needed to run and resume a scan: page-level metadata (pageId, spaceId, ageDays, staleness band, view signal, view count), plus scan-run bookkeeping such as thresholds, progress, and timestamps. Drydock stores no personal data at any point. The only identity value it ever handles is the accountId of the administrator running a scan, used solely for an in-memory space-admin check and never retained. Starting a scan and archiving a page each independently confirm the requesting user is a space admin. On that basis, Sullins Labs does not act as a data processor for Drydock. All data Drydock stores lives in Atlassian's Forge-hosted storage and inherits Atlassian's data residency handling.

None of the three apps collects your email address, IP address, browsing activity, or any information beyond what is described above. We do not run analytics, and we do not track how you use any of them.

How we use it

PIER's diagram source is used for exactly one thing: rendering your diagram back to you. SOUNDING's scan results are used for exactly one thing: displaying the permissions-inventory dashboard back to the admin who ran it, so a re-scan isn't needed on every page load. DRYDOCK's page-level metadata is used for exactly one thing too: showing the staleness-band results table back to the admin who ran the scan, and confirming a page's status after an archive action. In every case, the data is never read, analyzed, or used for any other purpose by us or by anyone else.

Where it is stored

All three apps store data using Atlassian's own Forge platform storage, inside your own Atlassian site:

• PIER's diagram source, on a Confluence page, is stored in the macro's configuration, alongside the page itself. In a Jira issue, it is stored in Forge's built-in key-value storage (KVS), keyed to that issue.
• SOUNDING's scan results are stored in Forge KVS, in the app's own storage namespace within your Atlassian site.
• DRYDOCK's scan data (the page-level metadata and scan-run bookkeeping described above) is stored in Forge KVS, in the app's own storage namespace within your Atlassian site.

In every case, the data stays inside Atlassian's infrastructure, in your own instance. Sullins Labs does not operate any servers or databases of our own that any of these apps talk to. There is nowhere for your data to be sent, because all three apps run entirely on Atlassian's Forge platform ("Runs on Atlassian"). We never receive, see, or store your data on any infrastructure we control.

Third parties and network connections

PIER, SOUNDING, and DRYDOCK make no network connections outside Atlassian's own infrastructure. SOUNDING calls Confluence's own REST API to build its permissions-inventory dashboard, and DRYDOCK calls Confluence's own REST API and Confluence Analytics to build its staleness scan, but none of the three apps talks to any third-party service, analytics provider, CDN, or external API. Nothing you create or scan is ever sent to servers outside Atlassian.

Cookies and tracking

None of the three apps sets cookies, runs analytics, or tracks usage in any form.

Data retention and deletion

PIER's diagram source persists for as long as the Confluence page or Jira issue it is attached to exists, or until you edit or delete it yourself. SOUNDING's scan results persist in Forge KVS for as long as the app stays installed on your site, and a new scan overwrites the previous result. DRYDOCK's scan data persists in Forge KVS for as long as the app stays installed; unlike SOUNDING, Drydock keeps the current scan run and the run immediately before it, and cleans up older runs as later scans complete, rather than overwriting on every scan. For all three apps, uninstalling removes the data it stored, according to Atlassian Forge's standard app-storage cleanup behavior. This is customer-controlled: it happens because you uninstall the app, not on any schedule we set.

This website

Separately from the apps above: this section covers sullinslabs.com's own pages, not the embedded WhereToLive app at /whereto, which is a separate product with its own data practices. Those pages run no analytics or tracking scripts of any kind; there is nothing added to watch what visitors do. The only thing stored in your browser is a light/dark theme preference, kept in localStorage and never sent anywhere. The site is hosted on Netlify; like most hosting providers, Netlify may keep basic server access logs as part of operating its infrastructure, but Sullins Labs does not layer any analytics or tracking on top of that, and does not use hosting logs to track individual visitors.

Children's privacy

Our apps are workplace productivity tools distributed through the Atlassian Marketplace and are not directed at children. They do not knowingly collect data from children.

Changes to this policy

If this policy changes, the "last updated" date at the top of this page will be updated. Material changes will also be reflected in the relevant app's Marketplace listing.

Contact

Questions about this policy or how our apps handle data can be sent to support@sullinslabs.com. To report a suspected security vulnerability, see the security page.