Privacy Policy

This policy describes how StatusFleet, the operator of the service, handles personal information at statusfleet.app, in the app, and on the status pages the service hosts. It also covers the copy of the app hosted on GitHub Pages. The Terms of Service describe the rules for using the service.

Information StatusFleet collects

Account and sign-in

An account stores the email address you sign up with, the account name, and the authentication data needed to sign in. The password is handled by Supabase Auth. StatusFleet does not keep a separate copy of the password. If the account must confirm its email before sign-in, Supabase Auth sends that message.

Status pages and incidents

The account stores the pages, components, incidents, incident updates, and maintenance windows you enter, plus branding such as colors and a logo or favicon. Logos and favicons are image files (PNG, JPEG, or WebP) stored for that page. A custom domain, when you add one, is stored with the page. A client report is built in the browser from the page’s uptime and history. It is not saved as a separate file.

A private page stores a bcrypt hash of one shared access password. The password itself is not stored. A correct password returns an unlock token once. StatusFleet stores a hash of that token for 12 hours. The browser keeps the token in session storage, under a key that starts with sf-page-access:, until that tab closes.

Subscribers

When someone subscribes to a public status page, StatusFleet stores the email address, whether it is confirmed, and later whether it was unsubscribed or suppressed after a bounce or a complaint. A private page does not accept subscribers. The page owner can read subscriber addresses for that page. Confirmation uses a single-use token. StatusFleet stores a hash of that token, not the token itself. Unsubscribe links are signed. The address is not shown on the page.

Monitor alerts

Monitor alerts are on by default. StatusFleet emails the account address when a monitor is confirmed down or confirmed back up. The owner can turn that off, and can add up to three more addresses. An extra address is stored and is mailed only after it confirms. Confirmation uses a single-use token. StatusFleet stores a hash of that token, not the token itself. This mail is sent from noreply@mail.statusfleet.app. It is separate from subscriber mail, and a bounce of an alert does not suppress a subscriber.

Uptime monitors

A monitor stores the HTTPS URL you enter, the check method, the schedule, and an optional keyword. Each check stores the time, whether it passed, the HTTP status code, the latency, and a short error string. StatusFleet does not store the response body. Check rows older than 90 days are deleted.

Integrations and API keys

Slack incoming-webhook URLs and customer webhook URLs are stored so StatusFleet can deliver the notifications you configured. A webhook signing secret is stored so deliveries can be signed. It is shown when the integration is created and is not returned on later reads. An API key is shown in full once. After that, StatusFleet stores a prefix and a hash of the key, plus the name, when it was last used, and whether it was revoked.

Billing

Payments are handled by Stripe Checkout and the Stripe customer portal. StatusFleet stores the Stripe customer id, the subscription id, the subscription status, the current period end, the price id, whether cancellation is set for the end of the period, and the ids of Stripe events it has already processed. The account email is sent to Stripe when the customer is created. The card number is entered on Stripe’s page. StatusFleet does not receive or store the full card number, and it does not store the card security code.

Logs

The marketing pages are static. They do not load advertising scripts. Cloudflare Web Analytics is used for cookieless aggregate page stats. The Cloudflare Worker that serves statusfleet.app records request logs and traces. Those records can include an IP address, a user agent, and the URL. GitHub Pages, which serves a copy of the app, may keep its own request logs. Subscriber email does not turn on open or click tracking.

The marketing site at statusfleet.app loads Google Analytics 4, a service of Google LLC, for aggregate traffic stats. The tag is on the home page, pricing, comparison and use-case pages, docs, terms, and this policy. It is not loaded on customer status pages, custom-domain pages, private pages, history or uptime reports, or the signed-in app, and it is not included in email. If the browser sends Global Privacy Control or Do Not Track, the marketing site does not load Google Analytics. Blocking it in the browser has the same effect.

Why

StatusFleet uses this information to:

  • Create and secure your account
  • Host status pages and deliver the content you publish
  • Send confirmation, incident, and maintenance email to confirmed subscribers on a public page
  • Send monitor alerts to the account address and to confirmed extra addresses
  • Run the monitors, Slack notifications, webhooks, and API you configured
  • Bill the subscription and show its status in the app
  • Keep the service reliable, debug failures, and prevent abuse

StatusFleet does not sell personal information. It does not use it for advertising, and it does not share it for cross-context behavioral advertising.

Public pages

A published public page is visible to anyone with the link or the custom domain. That includes the page name, component status, incident text, maintenance that has not ended, and Past incidents from the last 90 days. A published private page shows its name before the password is entered. Components, incidents, maintenance, history, and uptime are shown only after a correct password. Put only information you are willing to share with everyone who has the link, or the password, in that text.

Subprocessors

These providers process information so the service can run. The list is limited to providers the service actually uses.

ProviderRole
SupabaseDatabase, authentication, file storage, and edge functions
StripeCheckout, the customer portal, and payment processing
ResendSubscriber email (confirmation, incidents, maintenance, and unsubscribe) and account email (monitor alerts and alert-address confirmation). Account email is sent from noreply@mail.statusfleet.app.
CloudflareHosting, CDN, DNS, and custom hostnames for statusfleet.app, plus request logs, traces, and cookieless Web Analytics
Google LLCGoogle Analytics 4 on the statusfleet.app marketing site, for aggregate traffic stats. Not used on status pages, in the app, or in email.
GitHub PagesHosts a copy of the application and the marketing files. The status-page database is not stored there.

After you cancel

Canceling the subscription does not delete the account or the pages. The data stays until you delete the account. In Settings, a signed-in owner can download a JSON export of that account and can delete it by typing the account email. Deleting the account cancels a Stripe subscription immediately so it does not bill again, removes uploaded logos and favicons, and queues removal of custom hostnames. Email support@mail.statusfleet.app from the account address if you cannot sign in.

Retention

Account information, page content, subscriber addresses, integrations, and API key records stay while the account or the page exists. Monitor check rows are deleted after 90 days. A suppression record for a bounced or complained address can remain so that address is not mailed again on that page.

Stripe keeps payment records under Stripe’s own policy. StatusFleet keeps the Stripe event ids it has already processed, in stripe_events, so a repeated webhook is not applied twice. Those rows are the event id and the event type. They are not deleted with the account. Provider backups and request logs are kept for the period that provider uses. This policy does not set a separate number of days for those copies.

Deletion and export

A signed-in owner can download a JSON export from Settings. The file includes the account, pages, components, incidents, maintenance, monitors, subscribers on those pages, notification settings, and billing status. It does not include other people’s accounts, API key material, webhook secrets, access passwords, or confirmation tokens. The same screen deletes the account after the owner types the account email. Deletion removes the sign-in. An access token that was already copied can still pass a signature check until it expires, and then it finds no rows. Email support@mail.statusfleet.app from the account address if you need a copy or deletion and cannot sign in. StatusFleet still will not delete records it must keep for billing, security, or a legal obligation. Stripe event ids are one of those records.

A subscriber does not need an account to stop mail. Use the unsubscribe link in the message, described below. To ask for the address itself to be deleted, email the same support address.

Subscriber email and unsubscribe

StatusFleet sends a confirmation message before it sends incident or maintenance email. Only a confirmed subscription receives those messages. The sender name on the message is the status page name. Each message includes an unsubscribe link, and incident and maintenance messages include a one-click unsubscribe header. Unsubscribing stops that mail for that page. The address can remain stored so the choice is remembered. A bounce or a complaint suppresses further subscriber mail to that address on that page. The app does not set open or click tracking on these messages.

If you publish a status page, you are responsible for having a lawful reason to email the people who subscribe.

Cookies and local storage

On statusfleet.app, the marketing pages set Google Analytics cookies so Google can recognize a returning browser for those traffic stats. They do not set other cookies. The signed-in app stores the authentication session in the browser’s local storage, under the key statusfleet-auth, so you stay signed in. Signing out clears that session. The same browser also stores a checklist record under statusfleet.checklist.v1. plus the account id. That record is whether a public page was opened and whether a share link was copied. Signing out does not remove it. A status page uses a separate client that does not persist a sign-in session. A private page stores its unlock token in session storage, under sf-page-access: and the page slug, until the tab closes. StatusFleet does not use advertising cookies.

Security

The service is served over HTTPS. Database access is limited so an account reads its own rows, and a public page does not expose subscriber addresses. API keys are stored as hashes. Webhook signing secrets are not returned after they are created. Uptime checks and webhooks refuse private, loopback, link-local, and metadata addresses. These measures reduce risk. They do not make the service impossible to attack.

Children

StatusFleet is not directed at children under 16, and it does not knowingly collect their personal information. If you believe a child has provided personal information, email support@mail.statusfleet.app and StatusFleet will delete it.

International transfers

StatusFleet is operated from the United States. Supabase, Stripe, Resend, Cloudflare, Google, and GitHub may process information in the United States and in other countries where those companies run their services. If you use the service from outside the United States, your information is handled by those providers on that basis.

Your requests

Depending on where you live, you can ask StatusFleet to:

  • Tell you what personal information it holds about you, and give you a copy
  • Correct information that is wrong
  • Delete personal information, as described above
  • Provide an export of the information it holds
  • Stop emailing a subscriber address

StatusFleet does not sell personal information and does not share it for cross-context behavioral advertising. You may still tell StatusFleet not to sell or share it. StatusFleet will record that request and will keep this practice.

StatusFleet will not deny the service because you made a privacy request, except where the service cannot work without the information, such as an account email. StatusFleet may ask you to confirm that a request comes from the account, or from the subscriber address, before it acts. You may also complain to a data protection authority where you live.

Send requests to support@mail.statusfleet.app.

Changes

StatusFleet may update this policy by posting the new version on this page and changing the date above. If a change is material, StatusFleet will send a notice to the account email when that is practical.

Contact

Privacy questions: support@mail.statusfleet.app.