Security overview

Fulscrum connects the signals across GitHub, Jira, and Slack to spot when execution handoffs stall. You can start with GitHub and connect Jira and Slack when you are ready.

• Fulscrum does not access source-code contents.
• Fulscrum does not read unrelated Slack conversations.
• Readiness checks look at active-sprint issues only. Fulscrum does not monitor your backlog for them.
• Each integration asks for the minimum permissions it needs.

The exact permissions are listed on the integration permissions page, and the privacy policy explains what data we collect.

Every outbound message requires explicit approval. Before anything is sent, you review the exact Slack message and either approve it or dismiss the finding. Nothing is sent without that approval.

Approved messages are sent by the Fulscrum bot. Fulscrum never impersonates you or anyone else.

Every finding shows the source data that triggered it, and that evidence is retained with the finding and with the decision you make about it.

A Slack reply adds context. A finding closes only when GitHub or Jira confirms that the underlying situation changed.

Workspace data is isolated. Each workspace’s data is kept separate, so one workspace’s data is never visible to another.

Credentials we store for your connected tools are encrypted.

If you believe you have found a security issue, email us at hi@fulscrum.com with enough detail for us to understand it.