StatusBoltStatusBolt home
PricingDemoChangelogRoadmapBadgesHelpSign InGet Started
StatusBolt

Status pages that update themselves. Built by an indie maker, for indie makers.

Product

  • Features
  • Pricing
  • Changelog
  • Roadmap
  • Demo

Help

  • FAQ
  • Documentation
  • Support
  • API Status

Company

  • Contact
  • Built in public
  • Sign in

Legal

  • Privacy
  • Terms

Built with care for indie makers · © 2026 StatusBolt

    Privacy Policy

    Last updated: August 2, 2026

    Written for an indie UK SaaS in plain language. This is not a substitute for solicitor review — please get legal advice before relying on it for regulated use.

    Who we are

    StatusBolt is operated by an independent maker in the United Kingdom (controller for account data). Contact: [email protected].

    Controller vs processor

    For your StatusBolt account (login, billing, support), we are the data controller. For emails and details of people who subscribe to your public status page, you are typically the controller and we act as your processor — we send notifications you trigger and store subscriber records on your behalf.

    Information we collect

    • Account details: email, name, hashed password
    • Status page content: components, incidents, subscribers
    • Billing metadata via Stripe (we do not store full card numbers)
    • Usage data: page views, monitor checks, support tickets
    • Technical logs: IP address, user agent (for security and rate limiting)
    • Session cookies for sign-in (NextAuth). We do not use advertising trackers on the product by default.

    How we use data

    • Operate and improve the StatusBolt service
    • Send incident and subscription emails you configure
    • Process payments and enforce plan limits
    • Provide support and prevent abuse

    Processors

    • Stripe — payment processing for paid plans.
    • AuthSMTP — transactional email delivery (confirmations, incident notifications, support).
    • OpenAI — when AI features are enabled, rough notes may be sent to draft incident updates. Do not include secrets in AI prompts.

    We do not sell personal data. Hosting providers may process data as needed to run the service.

    Retention

    Account data is kept while your account is active. Incident history retention follows your plan (e.g. Free ~7 days on the public page history setting; paid plans keep longer). Subscriber emails stay until they unsubscribe or you delete the page/account. After account deletion we aim to remove or anonymise personal data within a reasonable period unless law requires longer retention (e.g. billing records).

    Your rights

    Depending on your location (including UK GDPR), you may request access, correction, or deletion of personal data. Email [email protected] or open a support ticket.

    Contact

    Privacy questions: [email protected].