Engineering Reporting is designed so that your code and PR data never leave GitHub.
What we do not store
We do not store your source code, PR contents, commit messages, or any raw GitHub data. Reporting metrics are computed live from the GitHub API each time a macro renders on a page.
What is cached
To keep pages fast, we cache the computed aggregate result briefly after each render - for example, the median cycle time for a given repository and date range. The cache holds only that aggregate number, not the underlying PR data used to compute it.
Computed aggregates are cached for 12 minutes. The accessible-repository list used by the macro configuration picker is cached separately for 5 minutes.
Where configuration is stored
Macro parameters - repositories, branches, date range, display mode - are stored as standard Confluence macro parameters on the page. No configuration data is stored outside Confluence.
GitHub connection
Engineering Reporting reuses the existing GitHub App connection configured by your Confluence administrator. No new GitHub scopes or permissions are required to start using the reporting macros. See Managing GitHub App permissions and organisation access if you need to review or update your connection.
Summary
|
What |
Stored? |
|---|---|
|
Source code |
No |
|
PR contents / commit messages |
No |
|
Raw GitHub API data |
No |
|
Computed aggregates (e.g. median cycle time) |
Cached for 12 minutes only |
|
Accessible-repository list |
Cached for 5 minutes only |
|
Macro configuration (repos, date range, etc.) |
Yes - as Confluence macro parameters |
Metrics are always team-level - never per-developer.
Related pages
-
How metrics are calculated - metric definitions, period handling, and v1 limitations
-
Security & Privacy - EULA, Privacy Policy, and security practices for the full app
Updated: