Termbook Privacy Policy
Effective date: October 1, 2026
This policy explains what information the Termbook: Glossary and Acronyms for Confluence app ("Termbook", "the app") handles and how. Termbook is made by Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA ("Great Work", "we", "us"). Questions: hello@greatwork.company.
Summary
Termbook runs entirely on Atlassian's Forge platform. Everything the app stores lives in your Atlassian site's Forge storage, hosted by Atlassian in the same data residency location as your Confluence site. Great Work does not run servers for Termbook, does not receive your glossary or page content, does not use analytics or tracking, does not sell data, and does not send data to any AI model or other third party.
What the app processes
| Data | Where it comes from | Why | Where it is kept |
|---|---|---|---|
| Glossary terms, definitions, acronyms, synonyms, tags, related terms | Entered or imported by your users | The core feature | Forge SQL storage for your site |
| Atlassian account IDs of term owners, editors and the people who created, changed, suggested or reviewed a term | Your users' actions and settings | Ownership, permissions and change history | Forge SQL and Forge key-value storage for your site |
| App settings (editor groups, editor account IDs, options) | Your Confluence admins | Permissions and behaviour | Forge key-value storage for your site |
| A cached copy of whether a user is a Confluence admin and which groups they belong to | Confluence REST API, read when the user uses the app | Permission checks; refreshed at least every 10 minutes | Forge key-value storage for your site |
| Import files and pasted rows | Uploaded by editors | Import preview and commit | Parsed in the Forge function; the validated rows are held in Forge key-value storage until the import finishes and for at most 24 hours |
| Page content | Read through the Confluence REST API, as the signed-in user, when someone opens the Glossary byline, the "terms on this page" macro, the Mark glossary terms action or exports a page | Finding glossary terms on the page and, when asked, adding term macros to the page | Not stored. Processed in memory during the request only |
The app does not collect names, email addresses, IP addresses, passwords or API tokens, and it does not set cookies.
Where data is stored and who can access it
Forge storage is provisioned per installation and is only accessible to Termbook on your site (Atlassian's Forge platform enforces this isolation). Data is encrypted at rest and in transit by Atlassian. Data residency follows your Confluence site, as provided by Atlassian's Forge data residency support.
Great Work staff cannot browse your glossary. Atlassian gives app developers operational logs and metrics; Termbook logs contain error messages and technical identifiers only, never term text or page content. If you contact support and choose to share a glossary export or screenshots, we use them only to answer your request and delete them when the request is closed.
Subprocessors
Atlassian (hosting through the Forge platform). No others.
Retention and deletion
Data stays in your site's Forge storage while the app is installed. When you uninstall Termbook, Atlassian deletes the app's hosted storage for your site according to the Forge hosted storage data lifecycle. Export your glossary to CSV first if you want to keep it. Within the app, editors can delete individual terms at any time.
Your rights
Because your data is stored in your own Atlassian site, your Confluence admins can view, export (CSV) and delete it directly. For any data subject request we can help with, write to hello@greatwork.company and we will respond within 30 days.
Children
Termbook is a business tool and is not directed at children.
Changes
We will post changes to this policy at this URL and update the effective date. Material changes will also be announced in the app's release notes.
Contact
Great Work LLC, 651 N Broad St Suite 206, Middletown, DE 19709, USA. hello@greatwork.company