Security

Cuelight runs on Atlassian Forge. Here's what it stores, where data goes, and how presses are authorized.

Where it runs

On Atlassian Forge, inside Atlassian's cloud. Cuelight has no servers of its own.

What it stores

DataWhereWhy
Action definitions, project mappingsForge storageConfiguration
Run history: who, when, inputs, resultForge storage, 180 daysAudit
Current next stepsForge storage, mirrored to an issue propertyShowing the panel
GitHub token, signing secret, install keyForge storage, encrypted secretsAuthentication

Run history older than 180 days is deleted every day. Next steps are dropped when they expire. When an Atlassian account is closed, its name in run history is replaced with "Former user".

Where data goes

Only to api.github.com. When someone presses a button, Cuelight sends the repository, workflow, ref, the inputs you defined, the callback URL and the run token. Nothing else leaves Atlassian. jira_update actions don't leave Atlassian at all.

Reports and offers come in through a Forge web trigger. Cuelight doesn't call out to them.

How presses are authorized

Jira groups are checked on the server at the moment of the press, not only when the panel loads. Reports and offers can only point at actions an admin defined, and they can't grant permission to run one. Settings can only be changed by Jira admins.

Tokens and keys

  • The GitHub token is stored encrypted and never shown again after you save it.
  • Each run gets its own run token, signed with a per-installation secret. It only works for that run and expires after 24 hours.
  • The install key only lets tools leave next steps. An admin can replace it at any time, and the old key stops working at once.
  • No Jira credentials go into GitHub.

App logs

Cuelight's logs contain ids and outcomes, never work item content, tokens or input values.

Reporting a vulnerability

Email cuelight@ryzaworks.com. We'll confirm we got it within two business days.