Security

Parlance for Confluence - last updated 6 October 2026

Where the app runs

Parlance is an Atlassian Forge app. Its code runs on Atlassian's own hosted platform, inside Atlassian's cloud, and its data is stored in Atlassian's Forge storage attached to your site. There is no Coreyard server in the path: we operate no backend, no database and no proxy for this app.

A consequence worth stating plainly: we cannot read your data even if we wanted to. Your glossary and your pages never reach us. We see no content, no page titles, no user names.

Egress

The app declares no external domain in its manifest, so the Forge runtime refuses any outbound call it might attempt. Nothing leaves Atlassian's network.

The Draft a definition feature uses Atlassian's Forge LLMs API, which runs on Atlassian infrastructure. The request does not leave Atlassian, and no third party receives it or trains on it.

Permissions, and why each one

storage:appStores the glossary itself, its history and its trash, in Forge storage on your site.
read:page:confluenceReads the page being viewed so terms can be found in it.
read:space:confluenceLists spaces so a term can be scoped to one.
search:confluenceFinds pages that mention a term, to source a drafted definition.
read:confluence-userAttributes each change to its author in the term history.
read:confluence-groupsChecks whether a user belongs to the group allowed to edit.

There is no write scope on Confluence content. Parlance cannot create, modify or delete a page, a comment or an attachment. Uninstalling it leaves your content exactly as it was.

Permission checks

Every read of your content runs as the signed-in user, so Confluence's own permissions apply unchanged. A user who cannot open a page cannot see its content through Parlance, and a drafted definition can only be sourced from pages that person could already read.

Writes to the glossary go through a single server-side check. Restricting editing to a group is enforced in the backend, not hidden in the interface.

Availability and recovery

Availability, backups and disaster recovery for Forge apps are Atlassian's, and follow the platform's own commitments for your Confluence site. Because the glossary lives in Forge storage next to your instance, it is covered by the same guarantees as the rest of your site. You can also export the whole glossary to CSV at any time, from Settings, and keep your own copy.

Reporting a vulnerability

Write to security@bycoreyard.com. Please include what you found, how to reproduce it, and how we can reach you.

Please do not run automated scanners or load tests against a customer's Confluence site. If you need an instance to test against, ask us and we will arrange one.

Incident response

A security incident is any confirmed or suspected access to customer data that should not have happened, or any flaw that lets the app be used against your site. When one occurs, we follow these steps, in this order.

  1. Contain. Stop the harm first: deploy the previous version of the app, or disable the affected feature, before investigating further.
  2. Assess. Establish which sites, which data and which period are affected, and keep a written timeline of what we find.
  3. Notify Atlassian within 24 hours of confirming the incident, through a P1 ticket on the Atlassian ecosystem support portal, as Atlassian's incident guidelines for Marketplace partners require.
  4. Notify affected customers without undue delay, and within 72 hours when personal data is involved, with what happened, what was affected and what you should do.
  5. Fix within Atlassian's Security Bug Fix Policy timeframes: 10 days for a critical vulnerability, 4 weeks for high, 12 weeks for medium.
  6. Review. Once fixed, we write down the cause and the change that prevents it from happening again, and share the summary with affected customers on request.

Related

What data the app handles, and for how long, is in the privacy policy. How to use the app is in the documentation.