StatusPier

StatusPier Privacy Policy

Solutions Group Unlimited, LLC · Last updated November 17, 2026

This policy explains what information Solutions Group Unlimited, LLC ("SGU", "we", "us") collects when you use StatusPier at statuspier.com, what we use it for, how long we keep it and who else sees it. We do not sell personal information. SGU's website and desktop software are covered by the SGU privacy policy.

StatusPier has four kinds of users:

  • Teams: the company that runs status pages. Its members sign in with a Microsoft work or school account.
  • Readers of a private page: a company's staff, who sign in with their Microsoft work account.
  • Subscribers: people who ask to get a page's updates by email.
  • Visitors of public status pages, who do not sign in.

What we store, and for how long

  • Team members: name and email address from Microsoft sign-in, Microsoft Entra tenant and user IDs, and your role in the account. Changes made in the team area are recorded with your email address. Team members' names and addresses are never shown on a status page.
  • Accounts and pages: the account's name, its pages' names, addresses and settings (colour, support link, time zone, the tenant IDs allowed to see a private page, a page's own address and its setup state), the trial dates and, for a paid plan, the plan, its status and the date it is paid up to. We do not store card or bank details.
  • Page content: the components, incidents, maintenance and updates your team writes, and the history of each component's status (closed entries are kept for 365 days; the page shows 90). What a public page shows can be read by anyone.
  • Subscribers: your email address, the page, the components you chose, whether the subscription is waiting for confirmation, active, ended or refused by the mail service, when you asked, confirmed or unsubscribed, how many confirmation emails were sent to you in the last day, and how often the mail service refused your address. Subscribing is double opt-in: we send a confirmation link (good for 7 days) and mail you updates only after you click it. A subscription never confirmed is deleted 7 days after its last confirmation email; one you ended is deleted 30 days after you unsubscribed. An address the mail service refused for good (3 times) is kept so that we never mail it again, until you ask us to delete it. Your address is shown only to the team of the page you subscribed to.
  • Sent mail: for each email, the address, the page, the incident, what kind of mail it was, when it was queued and sent and the result. These records are deleted 30 days after the mail was queued, whether it was sent, refused or not sent. Mail not sent within 24 hours is not sent late.
  • Readers of a private page: we keep no record of you in our database. Your Microsoft sign-in (name, email address, tenant and user IDs) is kept only in a cookie in your browser. If you subscribe, you are a subscriber as above.
  • Abuse protection: to limit how often an address can be subscribed, the IP address of a subscribe request is held in our server's memory for up to an hour. It is not written to our database.

Account and page records are kept while the account exists. To close an account and have its records deleted, write to support@solutionsgroupunlimited.com; we then delete them, except what we must keep for legal, tax, accounting or security reasons.

Team notifications

On the Team plan, a page's Owners and Admins can have StatusPier post its incidents and maintenance to their own Microsoft Teams, Slack, Discord or Google Chat channel, or to a web address (webhook) of their own. Each post carries only what the team wrote on the page: the page's name, the incident's title and status, a maintenance's planned time (and the time it was planned for before, when it moves), the first 300 characters of the update and the affected components, with a link to the incident on the status page. It never carries a subscriber's address, a team member (not even who added the destination) or anything about the page's readers. For a private page the post goes to the destination as written, so everyone who can read that channel sees it. Posts go only to the destinations the page's team adds, and stop when the team turns them off or deletes them. A post about a vendor the page watches (see "Vendor watch") carries the vendor's name, its incident's title and status, the first 300 characters of the vendor's own update, the vendor's components it names and a link to the vendor's status page.

They are sent by NotificationCentral, SGU's own notification service on SGU's servers. It keeps each destination's web address stored encrypted, the posts waiting to be sent (for at most 24 hours), and a record of each delivery (its time and result, kept for 30 days). Once delivered, a post is held by the service the team chose, under the team's own agreement with that service.

Vendor watch

A team can show on its pages the status of the cloud services it uses ("vendors", such as Microsoft 365, Slack or AWS). Our servers read each vendor's public status page every few minutes, once for all our customers. Nothing about you or the team is sent to the vendor: only our servers' request for its public status. We store what the vendors publish: each vendor's status, its components, the history of their status (closed entries are kept for 365 days; a page shows 90), and its incidents and maintenance with their updates (kept for 120 days after they end). We also store which vendors a page shows and its vendor settings. A vendor's text is shown as the vendor wrote it; we do not check it.

  • Vendor incident emails are off unless a page's team turns them on. Then subscribers of that page who chose all components also get an email when a vendor the page shows posts an incident, an update or its end (with the vendor's own text). They are sent and kept like the page's other emails (see "Sent mail").
  • Request a vendor: the vendor's name, its status page address and the note the team member writes are stored with that member's email address and the account, for SGU to read, and deleted after 365 days.
  • Your own Microsoft 365 service health (Team plan): only when an Owner connects it and an administrator of your organization grants StatusPier's app the permission "Read service health" (ServiceHealth.Read.All) in your Microsoft Entra ID. We then read, every few minutes, your tenant's service health: the status of each Microsoft 365 service and the open advisories and incidents, as the Microsoft 365 admin center shows them. We read nothing else from your tenant: no users, mail, files or other content. We store the latest read (the services, their status and the open issues with Microsoft's text), your tenant ID, and when and by whom it was connected. It is shown only to your team and, if your team chooses, on your PRIVATE page; never on a public page. Disconnecting deletes what we read; the permission itself is removed by your administrator in your tenant (Enterprise applications).

Cookies

StatusPier uses only the cookies it needs to work:

  • sp_team keeps a team member signed in, for up to 8 hours after the last visit.
  • sp_view keeps a reader of a private page signed in, for up to 8 hours after the last visit.
  • A security cookie protects forms (such as the subscribe form) against cross-site requests, and short-lived cookies are used while you sign in with Microsoft.

Public status pages, their feeds and status.json set no cookie of their own. We use no analytics or advertising cookies.

No tracking

We do not use analytics, tracking pixels or advertising networks on the status pages or in emails, and links in our emails are plain links (no click tracking).

Server logs

Our servers record technical details of requests and errors, such as IP addresses and the addresses requested. The service's own log never contains subscribers' addresses or the tokens in confirmation and unsubscribe links. Logs are kept for about 30 days.

Who else sees information

  • Microsoft: team members and readers of private pages sign in with Microsoft Entra ID. Emails are sent through Microsoft's Azure Communication Services, which receives each recipient's address and the email's text to deliver it. When a team connects its Microsoft 365 service health, our servers sign in to Microsoft Graph as StatusPier's app for that tenant to read it (see "Vendor watch").
  • Vendors: our servers request the public status pages of the vendors in our list. The vendors see those requests from our servers only, never who watches them.
  • Stripe processes payments for paid plans through Solutions Group Unlimited's billing service. Card details go straight to Stripe and are never seen or stored by us. To start a subscription we pass the account's ID and name, the chosen plan and the email address of the owner who subscribes (for the receipt).
  • The team's own chat tools: when a page's team adds a destination (Microsoft Teams, Slack, Discord, Google Chat or a webhook of their own), the posts described under "Team notifications" are sent there.
  • Cloudflare: a public page shown at a team's own address (such as status.yourcompany.com) is delivered through Cloudflare, which issues that address's certificate and passes each request to our servers. Cloudflare therefore handles the requests to that address (such as the visitor's IP address and the address requested) and knows the address itself. Pages at statuspier.com addresses do not pass through Cloudflare.

We do not share information with anyone else, unless the law requires it. StatusPier runs on servers operated by SGU in the United States.

Your choices

  • Every email has a link to unsubscribe; no sign-in is needed.
  • A page's team can remove a subscriber at any time.
  • You can ask us to see, correct or delete your information at support@solutionsgroupunlimited.com.

Changes

When this policy changes we update the date at the top.

Contact

Solutions Group Unlimited, LLC
Email: support@solutionsgroupunlimited.com