GitHub App Permissions
Minimal read-only access to what we need
Repository AccessRead Only
Read access to issues, metadata, and pull requests
Why: To detect when pull requests are opened, reviewed, merged, or closed, and to read PR metadata like title, description, labels, and assignees for notifications.
Organization AccessRead Only
Read access to organization members
Why: To map GitHub usernames to Slack users and enable team-based notification routing. This helps mention the right people in Slack when they're assigned PRs or requested for reviews.
User AccessMinimal
Read access to email addresses and public profile data
Why: To identify users for notifications and provide personalized settings. Email access is used for billing notifications and important account updates only.
You control repository access. By default, our GitHub app has no access to any repositories. You explicitly choose which repositories to grant access to during installation, and can modify this at any time.
Slack App Permissions
Send-only permissions โ we never read your messages
chat:writeSend Only
Send messages as @PullNotifier
Why: Core functionality โ sending GitHub pull request notifications to your designated Slack channels. We can only send messages, never read them.
chat:write.customizeSend Only
Send messages with customized username and avatar
Why: To make notifications more informative by showing GitHub avatars and usernames in the notification message.
chat:write.publicSend Only
Send messages to channels @PullNotifier isn't a member of
Why: To send notifications to any channel you specify, without requiring the bot to be manually added to each channel first.
incoming-webhookSend Only
Post messages to specific channels
Why: To enable repository-to-channel mapping, allowing you to route different GitHub repositories to different Slack channels automatically.
We cannot read your messages. Our Slack app only has write permissions โ we can send messages but cannot read, edit, or delete any messages in your workspace.
Security Practices
Industry-standard measures protecting your data
HTTPS Everywhere
All data transmission uses TLS 1.3 encryption with perfect forward secrecy
Encryption at Rest
All stored data is encrypted using AES-256 encryption standards
Secure Infrastructure
Enterprise-grade cloud infrastructure with regular security updates
Access Controls
Role-based access with principle of least privilege
Data Minimization
We collect and store only the minimum data necessary for functionality
Zero Trust Architecture
Every request is authenticated and authorized regardless of source
Data Processing & Storage
Data is stored in SOC 2 Type II compliant data centers with 99.9% uptime SLA
Regular automated backups with point-in-time recovery capabilities
Data retention policies ensure information is deleted when no longer needed
Frequently Asked Questions
Have Security Questions?
We're committed to transparency and happy to address any concerns.
security@pullnotifier.com