Privacy

We process account identifiers, profile and workspace names, workspace membership, monitor targets, check results, SSL metadata, alert channel configuration, backup result payloads, status page content, support requests, and billing state.

The mobile apps process installation and push-notification identifiers, workspace notification preferences, and account-linked product interactions such as acknowledging or resolving alerts so that responder features and requested notifications work across devices.

Secrets such as backup ingest tokens, webhook URLs, OAuth data, and payment data are minimized, masked in diagnostics where possible, and never intentionally exposed in customer-facing logs.

Stripe is the billing provider for checkout, subscription, invoice, portal, and payment method workflows. Email providers and notification providers deliver account, support and contact intake, invite, alert, and backup notifications.

Firebase Cloud Messaging is used as functional infrastructure for mobile push delivery and processes installation, app, device, and unlinked SDK-performance metadata needed to deliver and maintain notifications.

Where a provider acts as our subprocessor, our agreements require it to process personal data only on our documented instructions, apply appropriate security and confidentiality measures, assist with applicable data-subject and deletion obligations, and maintain contractual protections equivalent to those that apply to the same processing under our customer commitments, subject to applicable law.

Optional Firebase Analytics and Crashlytics collection, analytics cookies, and related browser storage remain disabled until the corresponding consent is granted. Consent can be withdrawn at any time from mobile Settings or the web Cookie Preferences page, depending on where it was granted. Withdrawal stops future optional collection but does not affect processing that lawfully occurred before withdrawal.

Authentication, account security, fraud prevention, and functional Firebase Cloud Messaging delivery are not controlled by analytics or crash-reporting consent. Notification permission and per-workspace failure and recovery subscriptions can be managed separately in the mobile app and operating-system settings.

You can start account deletion while signed in from account Settings in the web portal or mobile app. If you cannot sign in, use the public account-deletion page linked below to submit a request using the registered email address; we verify ownership before processing it. Owned workspaces must first be transferred or deleted, and active billing or ownership blockers must be resolved.

When account deletion completes, active sessions and refresh credentials are revoked, and account-linked mobile device registrations and notification subscriptions are removed. Workspace and product data within the deletion scope is deleted unless a limited record must be retained for an applicable legal exception.

We retain each category of data only for as long as reasonably necessary to operate and secure the service, provide support, maintain billing and accounting records, resolve disputes, prevent abuse or fraud, and meet legal obligations. The period therefore varies by data category and circumstances. Data is deleted or anonymized when those purposes end, except where applicable law, a legal hold, the establishment or defence of legal claims, or another lawful requirement permits or requires limited retention.

Depending on applicable law, you may request access, correction, export, restriction, objection, or deletion of personal data and may withdraw consent without affecting earlier lawful processing. Contact us using the details below to exercise these rights or ask about the retention that applies to a specific record.