← Back to LivingDocs
Privacy Policy
Last updated: May 18, 2026 · Novaders LLP
1. Overview
LivingDocs is a Confluence Forge app developed by Novaders LLP. This policy explains what data we access and how we handle it.
2. Data We Access
- Confluence page ID — used as a key to store your repo/file configuration against a specific page. We do not read page content.
- GitHub repository URL and file path — entered by you, stored per page in Forge's built-in key-value storage scoped to your Confluence site.
- GitHub Commits API — queried on demand when you click "Check Staleness" to retrieve the last commit date for the configured file. We do not store commit data.
3. Data We Do Not Collect
- We do not collect personal data (names, emails, IP addresses).
- We do not use analytics or tracking cookies.
- We do not share data with third parties except GitHub (to check commit history).
- We do not store data outside of Atlassian's Forge infrastructure.
4. Data Storage
Configuration data is stored using Atlassian Forge's built-in key-value storage, hosted and managed by Atlassian within their secure infrastructure, scoped to your Confluence site installation.
5. Third-Party Services
LivingDocs queries the GitHub REST API (api.github.com) to retrieve commit history for files you configure. Only public repository data is accessed. No authentication tokens are stored.
6. Data Deletion
Uninstalling LivingDocs from your Confluence site removes all associated configuration data from Forge storage. You may also clear settings per page using the "Reconfigure" button.
7. Contact
For privacy questions: dinesh@novaders.com