Security you can explain to your CTO

PRBoard is a PR workflow layer, not a code host. Your repos stay on GitHub or GitLab. We sync metadata, load diffs on demand, and encrypt everything that crosses our systems.

Full repos stored

Code stays on GitHub/GitLab

TLS 1.2+

In transit

Browser, API, and VCS

AES

At rest

DB, backups, attachments

MFA

Staff access

Limited, logged production

We do not store your source code

0 repos

PRBoard syncs PR metadata (title, status, reviewers, comments). Your repository files stay on GitHub or GitLab.

Encrypted in transit and at rest

TLS 1.2+

TLS 1.2+ for every connection. Database and backups use encryption at rest with managed keys.

Minimal Git permissions

Scoped

PR metadata and reviews only, not your full repo. You pick which repositories to connect. Revoke access anytime.

AI sees only what you open

On-demand

On the AI plan, suggestions use the diff you are actively reviewing in the panel. We do not bulk-ingest repos for training.

Git permissions we request (and what we never take)

PRBoard connects through the official GitHub App or GitLab OAuth. We only ask for permissions that power the PR board, reviews, and status sync.

We do not clone, mirror, or store your full repository. We do not take admin control of your org or delete repos. You choose which repositories to connect during install or in Settings.

GitHub App permissions

Permission	Access	Why we need it
Repository metadata	Read	List repos you selected and show names on the board
Pull requests	Read & write	Sync PR status, post reviews and merge when you approve in PRBoard
Contents	Read	Load the diff for a PR only when you open the review panel (not bulk download)
Pull request webhooks	Receive events	Keep the board updated when PRs open, update, or merge on GitHub

We never request on GitHub

Write or push commits to your default branch
Delete repositories or change repo settings
Organization admin or billing access
Access to every private repo without you selecting them in the GitHub App install
Storing a full copy of your repository in our database

GitLab OAuth scopes

Permission	Access	Why we need it
read_api	Read	Read merge requests, labels, and project metadata for connected projects
read_repository	Read	Load diffs on demand when you review (session only, not warehoused)
api	Write (scoped)	Post review comments and update MR status when you act in PRBoard

We never request on GitLab

Full mirror or clone of your GitLab project
Owner or admin rights on your GitLab group
Access to projects you did not connect
Storing source files outside an active review session

Your source code stays on GitHub or GitLab. We only read PR and review data for repos you connect, plus diffs on demand when you review.

What we store vs what stays on your VCS

Clear boundaries so security reviewers and leads know exactly what crosses our boundary.

We store (encrypted)

PR title, number, status, and column on your board
Reviewer names, labels, and timestamps from your VCS
Comments and approvals you submit inside PRBoard
Workspace settings, permissions, and billing metadata
OAuth tokens (encrypted) to keep repos in sync

We do not store

Your full repository or branch history (we only use Git permissions for PRs, not repo cloning)
Bulk copies of files for search or analytics
Private code for unrelated AI model training
Passwords (you sign in with GitHub or GitLab OAuth)
Payment card numbers (handled by our payment provider)

01.How we secure PRBoard

Teams trust PRBoard with PR metadata and review activity. Security is built into the product, not bolted on later.

We are a PR workflow layer, not a code host. Your repositories stay on GitHub or GitLab.

PR metadata encrypted in transit and at rest
Diffs loaded on demand when you open a review
Revoke GitHub or GitLab access anytime from your VCS or Settings
Workspace admins control per-repo roles (viewer, reviewer, merge)

02.We do not take or warehouse your code

PRBoard does not copy your full repository into our database.

We store PR metadata: titles, numbers, status, reviewers, timestamps, and comments you leave in the app.

When you open a review, the diff is fetched from your VCS over HTTPS for that session. We do not bulk-download repos for analytics or model training.

You own your code. Disconnecting GitHub or GitLab stops new syncs. You can request workspace deletion anytime.

03.GitHub and GitLab permissions (what we ask for)

PRBoard connects through the official GitHub App or GitLab OAuth. We only ask for permissions that power the PR board, reviews, and status sync.

We do not clone, mirror, or store your full repository. We do not take admin control of your org or delete repos. You choose which repositories to connect during install or in Settings.

GitHub: metadata and pull requests on repos you connect, not your entire account
GitLab: read and scoped API access on projects you connect only
No permission to push code, delete repos, or read unrelated private projects
Revoke anytime from GitHub/GitLab settings or PRBoard Integrations

04.Encryption

All traffic between your browser, our API, and GitHub or GitLab uses TLS 1.2 or newer.

Database rows, backups, and file attachments are encrypted at rest with industry-standard AES.

OAuth tokens and API secrets are stored in a managed secret store, never in application logs or source control.

05.Infrastructure

Production runs on isolated networks with regular patching and monitoring.

Secrets like OAuth keys live in managed secret stores, not in our repo.

07.Access

Workspace data stays inside your organization. Admins and members have different permissions for SLAs, repos, and billing.

Our staff access to production is limited, logged, and protected with MFA.

08.Report a problem

Found a vulnerability? Email support@prboard.io with details. We try to respond within two business days.

Please give us time to fix issues before public disclosure.

Ready to try the board with your team?

Start free