Chrome extension
Privacy policy
This extension sends nothing anywhere. There is no server, no analytics, no telemetry and no account. The only host it ever communicates with is the Confluence site you are already reading, using the session you are already signed in with.
Glossary — Live Highlight for Confluence
While you have a Confluence page open, and only on sites you have granted:
– The text of the page, in your browser, to find which glossary terms appear in it.
– Your Confluence glossary, by calling your own Confluence’s REST API from the page itself.
– The glossary’s display settings (the names, colours and icons of statuses, domains and languages) from a Confluence space
property published by the Glossary app.
Every one of these requests runs in the page’s own origin with your own session cookie.
Confluence applies your permissions to them exactly as it does when you browse. A term in a space you cannot open is never
in the response, so the extension cannot show it to you. No permission logic exists anywhere in the extension.
What it stores, and where
|
What
|
Where
|
Lifetime
|
|
The list of glossary terms you can see
|
`chrome.storage.session` — browser memory
|
Cleared when you close the browser. Never written to disk. Refetched after 30 minutes.
|
|
Which sites you switched highlighting off for
|
`chrome.storage.sync`
|
Until you switch them back on. Synced by Chrome to your own signed-in browsers.
|
The cached term list is kept separately for each Confluence site, keyed by the site the content script was actually running on. One site’s glossary can never be served on another’s pages.
Nothing is stored anywhere else. Nothing leaves your browser except requests to your own Confluence.
What it never does
Changes to this policy
Any change is published in this file and in the extension’s Chrome Web Store listing before the version it applies to is released.
Questions about this policy, or about what the extension does with anything it reads: support@wknowledge.com