Data Processing

StatusCloud is committed to ensuring that our customers' data is always handled appropriately, and we are transparent on where we store and how we process this information.

Broadly, we handle three types of data:

• Our data, such as our source code.
• User data, such as monitor configurations and product usage.
• Personal data, such as names and contact details of real human beings.

We process this in three main areas:

• Central data processing in the UK and EU - this is where most of our business logic takes place and is the only place that stores personal data.
• Our global network of monitoring servers - these servers perform the uptime checks and access relevant user data as required.
• Service partners, such as Cloudflare - they handle some of our data and some user data to help us perform our services.

You can always reach out to us if you have any questions and we'll be happy to discuss this in more detail.

Locality

At Rest

All user data that we store is located on servers in the UK and EU, and operates in strict accordance with GDPR and other data protection standards. At present, most of our data processing occurs in London.

The only information stored at rest on servers in our global network is source code and other technical data required to operate the service - our data, not that of a user.

Our service partners store some user data, such as status page configurations, but never any personal data. All personal data is only stored by us, in the UK and EU.

In Use

When an uptime check is run, the monitor configuration is sent to a server in each specified region. After the check is performed, the server sends the results back to the central location. Neither the monitor configuration nor the check result are stored on the server beyond this point.

This user data on the monitoring server typically only exists in memory, although it is possible that it could be temporarily written to disk if the underlying operating system pages out that location.

In Transit

To reach the relevant server in our global network, data naturally has to traverse the internet. While the route taken between any two locations is usually fairly direct, StatusCloud has no control over this and the data could theoretically travel through any country.

This also applies when using the console. Any data sent to or from your computer must travel across the internet to reach our servers.

In all cases, we fully encrypt data in transit. We use standard libraries and encryption implementations, and our servers are kept up-to-date with the latest patches.

Personal Information

Like other MattCorp services, we use MattCorp Identity for authentication and this forms the single source of truth for user account details. Some Enterprise customers may alternatively use their own corporate single-sign-on platform.

In either case, StatusCloud caches account details such as name and contact information when logging in to the console. We need these details to send the downtime notifications and other alerts for which our monitoring service is designed. As with all other data, we never sell it to advertisers or use it for purposes other than providing our service.

You can request for your details to be removed from all MattCorp systems at any time by contacting data@mattcorp.com.

Service Partners

We use a few third-parties to help us run our services. In all cases, we require that they operate under privacy policies compatible with ours and that they implement all necessary safeguards (both technical and procedural) to ensure that any data we give them is stored securely.

We share some of our data (for example, certain pieces of source code and error logs) with these third-parties, and they store some of our user's data on our behalf (for example, status page configurations). We do not transfer any personal data to them.

Our service partners are listed below, with a link to their respective privacy policies.

• Cloudflare
• Sentry