OpsBrief

Description Permissions Security & Compliance

OpsBrief consolidates incidents, releases, deployments, and infrastructure changes from Slack, PagerDuty, Datadog, GitHub, Microsoft Teams, Discord, and more into one intelligent daily brief and a searchable events calendar.WHAT YOU GET
✓ Faster incident response (MTTR ~40 → ~7 min typical)
✓ Full context in 30 seconds — no more Slack scroll-back
✓ Daily digest via Slack, email, or calendar
✓ Searchable event history across every connected tool
✓ Fewer status meetingsHOW OPSBRIEF WORKS INSIDE SLACKOpsBrief installs once as a single workspace bot - no user scopes, no per-member authorization. Every behavior maps to a scope and a user action:1) Reads messages only from channels you choose
You pick monitored channels in the OpsBrief web app under Channels.
• Public channels: channels:history + channels:read - read recent messages and resolve channel names.
• Private channels: groups:history + groups:read are used only after you run /invite @OpsBrief in that channel. The bot cannot read any private channel it has not been invited to.
• users:read attributes messages to the right author in your digest.
• channels:join lets the bot auto-join newly selected public channels.2) Extracts events with AI in our cloud — never inside Slack
Messages are sent to OpsBrief's backend, classified into typed events (incident, release, deployment, alert, decision, launch), and written to your private events calendar. Slack itself is not modified — no replies, reactions, or threads.3) Posts your digest into ONE channel you pick — and nowhere else
This is the only time OpsBrief writes to Slack and requires two explicit actions:
a) Turn on "Enable Slack digests" in Settings → Digest Preferences.
b) Pick one destination channel. Only channels where the bot is already a member appear in the picker.
Once configured, OpsBrief uses chat:write to post a single summary message at the cadence you choose (hourly, daily, or weekly, in your timezone). The message contains a header, the date range, an event-count summary by severity, and up to ten extracted events with platform/channel attribution and a permalink back to the original Slack message.4) What OpsBrief does NOT do in Slack
• No slash commands.
• No event subscriptions (no app_mention, no message.channels, no reactions).
• No user scopes — does not act on behalf of individual users.
• The bot does not reply, react, DM users, or open modals.
• The bot never posts in any channel other than the single digest channel you selected.5) Turning it off
• Toggle "Enable Slack digests" off in Settings → Digest Preferences — posts stop immediately.
• Disconnect from Connections — revokes the bot token and removes chat:write access.
• Remove the bot from a channel (/remove @OpsBrief) to stop reading that channel.GETTING STARTED
1. Click "Add to Slack" and authorize the bot scopes: channels:history, channels:read, channels:join, groups:history, groups:read, users:read, chat:write.
2. In OpsBrief, open Channels and select Slack channels to monitor. For private channels, run /invite @OpsBrief first.
3. (Optional) Open Settings → Digest Preferences, enable Slack digests, pick a destination channel, and set your schedule. Until then, chat:write stays dormant.BUILT FOR
→ Engineering: releases, incidents, deployments
→ Product: launches, experiments, feedback
→ Operations: infrastructure changes in real time
→ Leadership: visibility without manual updatesDEPLOYMENT
Cloud or on-premise. SSO, SAML, and dedicated support on Team and Enterprise.PRIVACY
Bot tokens are encrypted at rest. Message content is processed to extract events and retained for your subscription term. Disconnecting deletes all Slack-derived data. Details: https://opsbrief.io/docs/securityNOTE: AI summaries may occasionally be inaccurate. Every extracted event links back to the original Slack message - verify important items against the source.

OpsBrief will be able to view:

OpsBrief will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

DATA RETENTION POLICY OpsBrief — Effective Date: November 2025 OVERVIEW OpsBrief retains operational event data for 12 months to enable users to view and analyze their operational history. EVENT DATA RETENTION • Default retention period: 12 months • Retention begins: from the date the event is ingested into OpsBrief • Access: users can access events throughout the entire 12-month window via calendar, timeline, and search DATA TYPES RETAINED OpsBrief retains the following operational events: • Incident events (PagerDuty, Opsgenie): alerts, escalations, resolutions, severity, responders • Deployment events (GitHub, GitLab, Bitbucket): status, user, commits, files changed, outcome • Communication events (Slack, Teams, Discord): messages from monitoring/ops channels with timestamps • Infrastructure alerts (Datadog, New Relic, Prometheus, CloudWatch): alerts, severity, metric snapshots • System metadata: timestamps, source information, user/service identifiers, event relationships Note: users cannot delete individual events. Events are automatically deleted after 12 months. AUTOMATIC RETENTION ENFORCEMENT • Events older than 12 months are automatically removed nightly • Removal is permanent and irreversible • No manual action required from users • No data recovery possible after deletion BULK DATA REMOVAL Workspace administrators can contact OpsBrief support to request complete workspace data removal. All workspace data will be deleted within 7 business days. DATA SUBJECT RIGHTS OpsBrief honors: • Right to access — users can access all their operational event data • Right to deletion — workspace admins can request workspace data deletion • Right to data portability — users can request data export in standard format CONTACT Email: hello@opsbrief.io Support: https://opsbrief.io/contact Document Version: 1.0 | Last Updated: November 10, 2025

Data archiving and removal policy

DATA ARCHIVAL AND REMOVAL POLICY OpsBrief — Effective Date: November 2025 AUTOMATIC DATA REMOVAL • Events reach end-of-life after 12 months • An automated process removes expired events nightly • Removal is permanent and irreversible • All associated metadata and relationships are removed • Deletion is logged in system audit trails MANUAL DATA REMOVAL BY WORKSPACE ADMINISTRATORS Only workspace administrators can request manual data removal. Individual users cannot delete events. Workspace data removal request: 1. Workspace administrator contacts OpsBrief support at hello@opsbrief.io 2. OpsBrief sends a verification email to confirm 3. Administrator confirms the removal request 4. All workspace data is deleted within 7 business days 5. Deletion confirmation is provided Removal includes: • All operational events from the workspace • All event metadata and relationships • Associated analytics and correlations • All workspace configurations and settings Removal does NOT include: • Original source system data (Slack, PagerDuty, GitHub) — remains in source systems • OpsBrief system logs and audit trails • Anonymized usage analytics DATA REMOVAL UPON ACCOUNT DELETION When a user deletes their OpsBrief account: • All personal workspace data is deleted within 7 business days • Deletion is permanent and cannot be reversed • User preferences and settings are removed • Audit logs may retain deletion records for 90 days for compliance When a workspace is deleted: • All operational events and user data associated with that workspace are deleted • Deletion occurs within 7 business days • Original source system data remains unaffected DATA RECOVERY • Users can request recovery of accidentally deleted data from backup • Recovery requests must be submitted to hello@opsbrief.io • OpsBrief will recover data from the most recent backup • Recovery available for backups up to 30 days old • Recovery provided at no additional cost AUDIT AND LOGGING • All manual deletion requests are logged with user, timestamp, and data deleted • Audit logs retained for 12 months • Workspace administrators can access audit logs through the admin panel CONTACT Email: hello@opsbrief.io Support: https://opsbrief.io/contact Document Version: 1.0 | Last Updated: November 10, 2025

Data storage policy

DATA STORAGE POLICY OpsBrief — Effective Date: November 2025 STORAGE INFRASTRUCTURE • Primary platform: Railway (cloud hosting and data storage) • Geographic location: United States • Data residency: all operational data remains within the United States • Automated backups: daily backups with automatic failover procedures • High availability: automated monitoring and recovery systems in place DATA ENCRYPTION In-transit encryption: • All data transmitted to and from OpsBrief is encrypted using TLS 1.2 or higher • Applies to API calls, webhook data, browser traffic, and internal communication At-rest encryption: • All operational event data is encrypted using AES-256 at the database level • Encryption is transparent to users — no user action required Encryption key management: • Encryption keys are securely managed and stored • Keys are not accessible to the customer support team • Keys are rotated annually • Keys are managed according to industry security best practices DATA ISOLATION AND ACCESS CONTROLS • Workspace isolation: each workspace's data is logically isolated from others • User access controls: users can only access data for workspaces they're granted access to • Role-based access: members and admins have defined permissions • Row-level security: users cannot query other workspaces' data • API access: API tokens grant access only to a specific workspace BACKUP AND DISASTER RECOVERY • Daily backups: full daily backups of all operational data • Backup retention: backups are retained for 30 days • Backup encryption: all backups are encrypted with AES-256 • Recovery time: data is available within 1 hour of request • Quarterly testing: backup and recovery procedures are tested quarterly THIRD-PARTY SERVICES OpsBrief uses: • Railway — infrastructure, hosting, and data storage • Auth0 — authentication (does not store operational data) • Stripe — payment processing (payment data is NOT stored by OpsBrief) All processors comply with security standards and data protection requirements. SECURITY MEASURES • Authentication: multi-factor authentication available for all users • Session management: secure session handling with automatic timeouts • Network security: firewalls and intrusion detection systems in place • DDoS protection: DDoS protection mechanisms enabled • Data validation: prevents injection attacks and data corruption COMPLIANCE • Current: CCPA (California Consumer Privacy Act) compliant • Planned: GDPR compliance (Q2 2026) • In progress: SOC 2 Type II certification • Data rights: OpsBrief honors the right to access, deletion, and data portability MONITORING AND TESTING • 24/7 monitoring: infrastructure and security monitoring is continuous • Annual testing: penetration testing and vulnerability assessments • Disaster recovery: quarterly DR testing • Compliance: regular audits to ensure policy compliance CONTACT Email: hello@opsbrief.io Support: https://opsbrief.io/contact Document Version: 1.0 | Last Updated: December 10, 2025

Data center location(s)

United States

Data hosting details

Data is hosted on the cloud in the US

Data hosting company

Railway

App/service has sub-processors

App/service uses large language models (LLM)

yes

LLM model(s) used

gpt-4o-mini

LLM retention settings

OpenAI's API does not retain API inputs or outputs for model training (zero data retention policy). OpsBrief retains ONLY processed message summaries in our database for the duration of the customer's subscription. Original message content is not stored.

LLM data tenancy policy

OpsBrief uses OpenAI's API which operates on a multi-tenant infrastructure. We do not host or fine-tune our own LLM models. All AI processing is handled through OpenAI's standard API endpoints with no custom model training on customer data.

LLM data residency policy

Data is processed through OpenAI's API infrastructure located in the United States. OpsBrief's own application data is hosted on Railway (US region). We do not transfer Slack data to any other geographic regions for AI processing.

Certifications & compliance

Security