Back to PullPing
SECURITY

Your code stays
in GitHub.

PullPing reads PR activity and posts useful updates to Slack.

PullPing uses read-first access.

PullPing receives signed GitHub webhook events for selected repositories.

PullPing can refresh PR snapshots through read-only GitHub API calls.

PullPing does not approve, comment on, or merge pull requests.

Workspace tokens are protected.

PullPing stores Slack and GitHub credentials for connected workspaces.

PullPing uses these credentials only to provide the service.

Revoke access from Slack or GitHub if you need to disconnect.

PullPing stores operational data.

PullPing stores routes, user mappings, PR snapshots, and Slack message references.

PullPing also stores review plans, reminders, and digest schedules.

Report security concerns.

Use your onboarding contact to report a security concern during early access.

Do not send tokens, private keys, or secrets in the first message.

Read privacy notes