Privacy Policy

PRBoard helps your team see pull requests, review them, and ship without the usual chaos. To do that, we need some account and repo information, and we never collect more than we need.

We do not sell your data. We do not use your private code to train unrelated AI models. If something here feels unclear, email us at support@prboard.io. We would rather explain it in plain English than hide behind jargon.

Last updated: May 22, 2026.

This policy applies to anyone who visits our website, signs in with GitHub or GitLab, or uses a paid workspace.

If your company invited you to a workspace, your admin may control certain settings. Your personal account data still belongs to you, and you can ask us about it directly.

We only collect what we need to run the product. Here is what that usually looks like:

• Account details from GitHub or GitLab sign-in: name, email, username, and profile image.
• Workspace info you enter: team name, slug, and member invites.
• Pull request metadata: titles, numbers, status, reviewers, labels, timestamps, and comment counts, enough to power the board and reports.
• Review activity inside PRBoard: approvals, change requests, inline comments, and points you earn.
• Billing details if you upgrade (handled by our payment provider; we do not store full card numbers).
• Support messages and optional feedback you send us.
• Basic usage data (which pages you visit, in aggregate) so we can fix bugs and improve the app.

We are not a code host. Your repositories stay on GitHub or GitLab.

• We do not bulk-download or permanently store your full repository.
• Diffs are fetched from your VCS when you open a review, for that session.
• We do not sell personal data to advertisers or data brokers.

We use your data to do the job you signed up for. Nothing sneaky on the side.

• Show PRs on your board and keep columns in sync with GitHub or GitLab.
• Let reviewers comment, approve, or request changes from inside the app.
• Calculate points, badges, leaderboards, and team reports you choose to use.
• Send SLA alerts and in-app notifications you turn on.
• Process payments and manage your subscription.
• Respond when you contact support.
• Keep the service secure and meet legal obligations.

When you connect GitHub or GitLab, their privacy policies apply to data they handle on their side.

We request only the permissions needed to list repos and sync PR activity. You can revoke access anytime from your VCS settings or from PRBoard under Settings → Integrations.

Slack is optional. If you connect it, the sections below describe exactly what we access, why, and how to delete it.

If a workspace admin connects Slack, PRBoard receives data from Slack only to run notifications and review routing you enable. We do not read your full Slack message history.

Data we may access or store includes:

• Slack workspace and team identifiers, and the channel you choose during install.
• Bot and webhook credentials (stored encrypted) so we can post messages on your behalf.
• Slack user IDs and, where permitted by Slack, email addresses. We use these to match teammates to PRBoard accounts and to open direct messages to the right person.
• Display names and profile basics returned by Slack when we look up a user for routing or skip actions.
• Message metadata for PRBoard-sent DMs (for example channel ID and message timestamp) so we can update the same message after a skip or merge.
• Interactive button clicks you send from our Slack messages (for example Snooze or Skip), including which Slack user clicked.

We send direct messages (DMs), not channel spam, when review routing assigns someone to a PR or reroutes after a skip.

Each DM explains why that person was picked (for example open review load and path familiarity), links to the PR on PRBoard and GitHub, and optional actions such as Open review or Snooze / Skip.

We may also post to a channel you select during setup for workspace-level alerts you turn on. You control which notification types are enabled in Settings.

When you install our Slack app, we request only the bot scopes needed for the features above. Each scope and why we need it:

• chat:write. Post review routing messages, SLA alerts, and other notifications you enable.
• im:write. Open direct message channels and send assignment and reroute notifications to individual reviewers.
• users:read. Look up Slack users so we can address messages and match them to teammates on your board.
• users:read.email. Match a Slack user to a PRBoard account by email (required for Skip and personalized DMs).
• channels:read. Let you pick which channel to use during Slack setup.
• incoming-webhook. Post optional messages to the channel you selected when connecting Slack.

While Slack stays connected, we keep integration credentials, your selected channel, cached Slack user IDs linked to workspace members, and message identifiers for DMs we sent so we can update them.

When a workspace admin disconnects Slack under Settings → Integrations, we revoke stored bot and webhook tokens, clear the linked channel, and stop collecting new Slack data immediately.

Cached Slack user IDs on member profiles and historical assignment records (for example that a DM was sent) may remain until you delete the workspace or ask us to erase personal data. We do not keep using disconnected tokens.

Slack's own retention policies apply to messages in your Slack workspace. Messages already delivered in Slack remain in Slack under your team's control.

You can request deletion of Slack-related personal data at any time.

Email support@prboard.io from the address on your PRBoard or Slack account with the subject "Slack data deletion" and your workspace name. We will verify your identity and respond within 30 days.

You can also disconnect Slack yourself (workspace admin → Settings → Integrations → Disconnect Slack), which removes our ability to access Slack and deletes stored tokens on our side.

For full account removal, include that in your email or delete your workspace from Settings. We will delete or anonymize personal identifiers as described in Your rights below.

We do not sell Slack data. We do not share Slack user IDs, emails, workspace details, or message content with advertisers, data brokers, or unrelated third parties.

Slack data is processed only to provide PRBoard to your team, to operate our hosting and security tooling, and when required by law.

Slack, Inc. processes data on their platform when you use Slack; their privacy policy applies to data held in Slack itself.

If you use optional AI review suggestions, we send the relevant diff context to our AI provider to generate feedback. That data is used only to return suggestions to you. We do not train public models on your private code without your consent.

You can skip AI features entirely and use PRBoard without them.

We keep workspace and account data while your subscription or free workspace is active.

If you delete your account or ask us to remove your data, we delete personal identifiers within a reasonable period. Anonymized, aggregated stats may remain so we can understand product usage trends.

Backups roll off on a schedule after deletion requests are processed.

For Slack-specific retention and disconnect behavior, see Slack data retention above.

Our production infrastructure is hosted with reputable cloud providers. Data is encrypted in transit (TLS) and at rest.

If you are in the EU, UK, or another region with data protection laws, you may have additional rights. See the section below.

Depending on where you live, you may have the right to access, correct, export, or delete your personal data.

Email support@prboard.io with your request. We will verify it is really you, then respond within 30 days in most cases.

Slack-related deletion requests are handled the same way; see Slack data deletion above for the recommended wording.

If you are unhappy with our response, you may have the right to complain to your local data protection authority.

PRBoard is built for professional engineering teams. We do not knowingly collect data from anyone under 16.

We may update this page when we launch new features or when laws change. We will post the new date at the top. For big changes, we will try to notify workspace admins by email.

Privacy questions, data requests, or just want to talk it through? Write to support@prboard.io. A real person reads it.