Fulscrum Privacy Policy

Fulscrum connects to GitHub, Jira, and Slack to help engineering teams catch stalled work early. This policy explains what data we collect, why, and how to control it.

Fulscrum is currently operated directly by its founders, not yet as an incorporated company. You can reach us at hi@fulscrum.com for any privacy question or request.

Fulscrum is currently operated directly by its founders, not through an incorporated company. If you need to identify the operating party for a legal matter, contact hi@fulscrum.com.

Pull request and review metadata, including:

• GitHub organization and repository identifiers
• PR number, title, URL, and state (open, closed, merged, draft)
• PR author and requested reviewers
• Review-request, review, and merge timestamps
• Review state (approved, changes requested, commented)
• GitHub user IDs and available public profile information
• GitHub App installation details (which repositories are connected)

We do not request or process the contents of your source code.

Jira site and project identifiers; issue key, title, status, and status category; sprint membership; assignee email (when your Jira account makes it available); creation, update, and status-change timestamps; issue links and the status of linked issues; and, for projects an administrator selects, configured readiness fields such as estimate and acceptance-criteria fields. Administrators choose which Jira sites, projects, and fields Fulscrum monitors. We do not access issue descriptions or comments.

Workspace and messaging metadata needed to deliver and track approved messages, including:

• Slack workspace and user IDs
• The email address used to match you to your Slack account
• DM channel and message identifiers
• The content of messages Fulscrum sends once approved
• Replies to those specific messages, and their timestamps
• Approval and delivery status for each message

We do not read your other Slack conversations or channel history.

Separately from integration data, we also collect:

• Your account name and email
• Your workspace membership and role
• Your integration configuration (which repositories, projects, and channels are connected)
• Records of approvals, dismissals, and other activity within Fulscrum
• Basic technical data such as IP address and browser information, for security and troubleshooting

We do not currently use third-party analytics or advertising cookies. If that changes, we'll update this policy.

Solely to detect stalled reviews, blocked dependencies, stale tickets, sprint readiness gaps, and mismatches between GitHub and Jira; to draft and deliver the messages you approve; and to operate and secure the Fulscrum service itself.

Fulscrum uses a third-party AI service to draft these messages from the structured evidence behind a finding; the AI does not make detection decisions itself. Data sent to this service is not used to train the provider's models. The message is not sent until an authorized user reviews and approves it.

We do not sell your data or use it for targeted advertising. We share it only with service providers who help us run Fulscrum, including categories such as:

• Hosting and cloud infrastructure
• Database and storage
• Authentication
• Error monitoring and security logging
• Email delivery
• An AI model provider, for message drafting

We may also disclose information where required by law, to protect the security of Fulscrum or its users, or in connection with a merger, acquisition, or transfer of the product.

Fulscrum is hosted and operated in the United States.

We use technical and organizational safeguards designed to protect your data, including encryption of stored credentials, tenant-scoped access controls so one workspace's data is never visible to another, and integration permissions limited to what each feature needs. No system can guarantee complete security, but protecting your data is a design priority, not an afterthought.

Disconnecting an integration stops new data collection from it immediately. You can request deletion of all your workspace's data at any time by contacting us, and we will act on that request promptly.

If your employer or organization connects its GitHub, Jira, or Slack workspace to Fulscrum, that organization controls what data it makes available to us, and its own privacy policies may also apply to you. If you have questions about data collected through a workspace you don't administer, we may direct you to that workspace's administrator.

You can email hi@fulscrum.com to ask questions, or to request access to, correction of, or deletion of information associated with you. We may need to verify your identity, or coordinate with the administrator of the workspace through which your information was provided, before acting on a request.

• Cookies: we do not currently use third-party analytics or advertising cookies. If that changes, we'll update this policy.
• Children: Fulscrum is not directed to anyone under 18, and we do not knowingly collect information from them.
• Disconnecting: workspace administrators can disconnect any integration at any time from Fulscrum's settings.

We'll update this page as the product changes and note the date above. If a change materially affects how we use your data, we will provide additional notice through the product or by email where appropriate.