ERD Studio for Confluence

Security

Last updated 21 September 2026

This page explains how ERD Studio for Confluence (the "app") is built to keep your GitHub repositories and your Confluence site safe. The app is made by Liam Wynne, a sole trader in Australia (ABN 94 885 368 933). For what data the app reads and stores, see the privacy policy.

In short: the app runs entirely on Atlassian Forge. It reads GitHub through a GitHub App your organisation installs on the repositories it chooses, with read-only access. Each GitHub token is narrowed to one repository, lasts under an hour and never reaches the browser. Every backend function that reads repository data or changes settings checks the caller's permissions itself.

Architecture

Access to GitHub

Access goes through the "ERD Studio for Confluence" GitHub App. A GitHub organisation owner installs it and picks which repositories it can see. Nobody shares a personal access token.

GitHub App permissionWhy
Contents: readTo read the diagram files in .erd-studio/ folders.
Metadata: readTo list repository and branch names in the macro settings.

Connecting GitHub to your site

Permission checks

Forge doesn't limit who can call an app's backend functions, so each function checks for itself instead of trusting which screen the request came from.

FunctionChecks
Showing a diagram on a page Active licence. The repository, branch and file are read only from the macro settings saved in the page, which only page editors can change. Anything else the browser sends is ignored.
Previewing a diagram, and listing repositories, branches and files in the macro settings Active licence, and the caller must be able to edit the page the macro is on.
Connecting, disconnecting and checking the GitHub connection The caller must be a Confluence site admin.

The macro settings panel can also ask which GitHub account the site is connected to. That returns only the account name and whether the site is licensed.

Anyone who can view a Confluence page can see the diagram on it, even without access to the GitHub repository. Choose which pages show which diagrams with that in mind.

Handling repository content

Macro settings are written by page editors and repository files by anyone with push access, so the app treats both as untrusted.

Network access and Forge scopes

Forge only lets the app contact the addresses declared in its manifest:

AddressUsed for
api.github.comBackend: reading repository files and metadata, and checking installations
github.comBackend: completing the admin's GitHub sign-in
avatars.githubusercontent.comBrowser: the connected GitHub account's avatar image on the admin page

The app asks Atlassian for three scopes:

ScopeWhy
storage:appTo store the GitHub connection, cached tokens and cached diagrams in Forge storage.
read:confluence-userTo check whether the caller is a site admin.
read:confluence-content.permissionTo check whether the caller can edit the page the macro is on.

The app can't read Confluence page content, attachments or comments.

Data retention and deletion

Logging

The app logs only unexpected errors, to Atlassian's Forge logs. An error message can include a repository or file name. We use these logs only to run and support the app, and we don't share them.

Reporting a vulnerability

If you think you've found a security issue, email digest@w2solutions.ai with "Security" in the subject. Include what you found and how to reproduce it.

Incidents

If a security incident affects your data, we'll notify affected customers without undue delay, tell you what happened and what we're doing about it.

Changes

If we change how the app handles security, we'll update this page and the date at the top.