Outage App Privacy Policy
Effective November 13, 2026
This Privacy Policy explains how Outage App (“we,” “us,” or “our”) collects, uses, shares, and protects personal data when organizations and their users use outageapp.com and the Outage App web application (the “Service”).
Outage App is a business-to-business incident management and automation service. Our customers are organizations (“Customers”) that report outages, alert their company, track status, send updates, and manage calendars and change requests. See also our Terms of Service.
1. Our two roles
We handle personal data in two roles:
- We are the controller (we decide how and why data is used) for account data: people who sign up or log in, billing contacts, and people who contact us. This policy fully applies to that data.
- We are a processor or service provider for Customer data: recipient contact details the Customer provides, and incident content the Customer enters or sends to the Service. The Customer is the controller of that data and decides who receives alerts and what they say. We process it only on the Customer’s instructions to provide the Service. If you received an alert and have a question about your data, contact the organization that sent it. We will help that organization respond.
2. Personal data we collect
| Category | Examples | Source |
|---|---|---|
| Account data | Name, work email, organization name, role, and login credentials (passwords are stored only as a salted hash or held by our authentication provider) | You, when you sign up or are invited |
| Billing data | Stripe customer ID, plan, subscription status, and the billing period. Card details are held by Stripe. We do not store card numbers. | You, through Stripe checkout |
| Recipient data (Customer data) | Names, email addresses, and group membership the Customer provides | The Customer, from lists, a file import, or a synced directory such as Microsoft Entra |
| Incident and workspace data (Customer data) | Incident details, status, messages, calendar entries, change requests and approvals, webhook payloads, workflows, policies, and branding | The Customer, its users, or systems it connects |
| Integration credentials | Channel addresses and routing keys (Slack, Teams, PagerDuty) and stored workflow secrets, kept encrypted. Webhook tokens are used to check incoming events. | The Customer, when it sets up an integration |
| Logs and usage data | IP address, timestamps, browser or client information, email delivery results, an activity (audit) log of changes, and monthly usage counts | Automatically, when the Service is used |
| Website visit data | On our public website pages only: pages viewed, the site you came from, device and browser type, and approximate location (country or region), collected in aggregate with Vercel Web Analytics. It uses no cookies and does not follow you across other sites. | Automatically, when you visit those pages |
| Support communications | The content of emails you send us and of Help requests you submit in the app (your message, severity, name, email, organization and role) | You |
3. How we use personal data
We use personal data to provide the Service, including accounts, alerts, integrations the Customer configures, and workspace features such as audit exports; to bill for subscriptions and trials; to keep the Service secure; to support you and send account, billing, security, and policy notices; to maintain and improve the Service; and to comply with law and our Terms of Service.
We do not sell personal data, and we do not “share” it for cross-context behavioral advertising. We do not use Customer incident content for advertising or to train artificial intelligence models. We do not use advertising trackers. We use Vercel Web Analytics to count visits to our public website pages (the home page, user guide, terms, and this policy) so we can see which pages are useful. We do not use it inside the signed-in application or on the sign-in and sign-up forms.
For people in the European Economic Area, the United Kingdom, or similar jurisdictions, our legal bases for processing account data are performing our contract with you or your organization, our legitimate interests in running and securing a business service, complying with legal obligations, and consent where we ask for it.
6. Our subprocessors
We use the following providers to operate the Service. This list may change, and we will update it when it does.
| Provider | Purpose |
|---|---|
| Vercel | Hosts the Outage App user interface, and provides cookie-free website analytics (Vercel Web Analytics) on our public pages |
| Supabase | Database and user authentication |
| Amazon Web Services (AWS) | API, alert processing, secrets storage, and server logs |
| Mailjet | Email delivery |
| Stripe | Payment processing |
| Sentry | Error monitoring. Reports are stripped of request contents, cookies, and email addresses before they leave our servers. |
| Slack, Microsoft Teams, PagerDuty | Alert delivery, only when the Customer configures a channel |
| Microsoft Entra | Directory sync, only when the Customer enables it |
Slack, Microsoft Teams, PagerDuty, and Microsoft Entra are used only at the Customer’s direction. They are listed here so you can see where data may go when those features are turned on. Customers who need advance notice of subprocessor changes can request it through a Data Processing Addendum.
7. How long we keep data
Customers can export their data (including audit exports), delete an organization, and individual users can delete their own account.
| Data | Retention |
|---|---|
| Account data and Customer data | While the account is active. When an owner deletes an organization it is frozen and can be restored for 14 days; after that we permanently delete it. |
| A user’s own account | Deleted when the user deletes it: name, email, and credentials are removed. The history their actions created stays in the organization’s records without their details. |
| Activity (audit) log and delivery logs | Kept with the organization’s data for as long as the organization exists, and deleted with it. The activity log cannot be edited or deleted while the organization is active. |
| Server logs | Kept for a limited period for security and troubleshooting. |
| Backups | Held by our database provider and expire automatically on its backup schedule. |
| Billing and transaction records | As long as needed for tax, accounting, and legal requirements |
Customers can request an export or deletion at any time by emailing privacy@outageapp.com. We may keep limited data longer when the law requires it or to resolve disputes and enforce our agreements.
8. Security
We use reasonable technical and organizational measures designed to protect personal data, including encryption in transit and at rest, access controls, logical isolation of each Customer’s data inside the database, encrypted storage of channel credentials and workflow secrets, an optional emailed sign-in code, and a separate, audited console for our own support staff. We do not claim any particular security certification. No system is perfectly secure, and we cannot guarantee the security of data. If we become aware of a breach that affects your personal data or Customer data, we will notify affected Customers without undue delay and as required by law.
9. Your rights and choices
Depending on where you live, you may have the right to know what personal data we hold about you and get a copy of it, correct it, delete it, receive it in a portable format, object to or restrict certain processing, withdraw consent where we rely on it, and complain to your local data protection authority.
California residents. Under the California Consumer Privacy Act, as amended by the California Privacy Rights Act, you have the rights to know, delete, and correct personal information, and to opt out of sale or sharing. We do not sell or share personal information as those terms are defined. Categories, sources, purposes, and disclosures are described in Sections 2, 3, 5, and 6. We will not discriminate against you for exercising your rights. You may use an authorized agent to make a request on your behalf.
How to make a request. You can delete your own account in the app under Account. For anything else, email privacy@outageapp.com. We will verify your request and respond within the time the law requires. If your request is about Customer data (for example, an alert you received from an organization that uses Outage App), we will refer you to that organization, or help it respond, because it controls that data.
10. International transfers, children, and changes
Outage App is operated in the United States, and personal data is processed in the United States. Our service providers may also process data in the United States and other countries. Where the law requires, we rely on appropriate safeguards for international transfers, such as standard contractual clauses.
The Service is for businesses and is not directed to children. No one under 16 may use the Service, and we do not knowingly collect personal data from children under 16. If you believe a child has given us personal data, contact us and we will delete it.
We may update this Privacy Policy from time to time. If we make a material change, we will notify account administrators by email or in the app before it takes effect, and we will update the effective date above. We will also update this policy when our list of subprocessors changes.
11. Contact us
- Email: privacy@outageapp.com
- Website: outageapp.com

