Beta

Data processing agreement

The terms under which we process personal data on your company's behalf, as Article 28 of the GDPR asks of a processor.

In force from TODO: date

TODO This is a draft for legal review. Remove this notice once the text is approved.

In short

  • YoursWhat we collect for your company is your company's. We use it only to draw its reports.
  • IrelandIt is stored in AWS's Europe (Ireland) region, or in your own AWS account if your company chooses.
  • 30 daysafter your company is deleted, its data is gone.

Who it is between

This agreement is between your company, which uses qloudpulse's hosted service and is the controller of the personal data in it, and TODO: legal entity name, TODO: registered address, which runs qloudpulse and is your company's processor. It is part of TODO: link to the terms of service, and applies from when your company is created in qloudpulse until its data is purged.

It covers the hosted service only. A self-hosted install runs in your own cluster and keeps what it collects in your own database, so we process none of it, and this agreement does not apply to it.

What we keep to give a person a login and to run the service, such as their name and email address, the sign-in itself and the audit trail, we keep as controller. The privacy policy covers that.

What we process

Why

To collect what your company's AWS accounts and Kubernetes clusters run and cost, and to draw its reports, findings, alerts and recommendations from it. And to count what the changes made on our advice save, added up across every company, which we publish on qloudpulse.com as one total. The total holds no account, resource, name or tag, never shows one company's figure, appears only once at least three companies have saved something, and is rounded down to whole hundreds. Nothing else: we do not sell it, use it for advertising, or use it to train anything.

What, and about whom

  • Infrastructure, not people: resource ids, names and tags, account names, cluster, namespace and workload names, sizes, usage and cost. A name or tag can hold a person's name or email address, such as an owner tag or an IAM user's name, so we treat all of it as personal data.
  • The bill, if your company connects it: AWS's Cost and Usage Report, whose line items carry the same names and tags.
  • Flow log samples, if your company turns them on: the addresses that talk to each other inside the VPCs it chooses. An address can belong to a person's device.
  • What your company's people write in qloudpulse: feature requests and their images, problem reports and their screenshots.

If your company chooses to keep its data in its own AWS account, the collected data, the archive and the uploaded bills are stored there, in the region it picked, under its own KMS key. We read and write them through a role your company creates and can delete. We still process them, in Ireland, to collect them and draw the reports. That account is your company's: AWS hosts it under your company's own agreement with AWS, not as our sub-processor.

The people concerned are your company's staff and contractors, and anyone named in your infrastructure. We do not ask for special categories of personal data, and the product has nowhere meant to hold them.

How long

As long as your company exists in qloudpulse, and gone within 30 days after it is deleted, as below.

What we do, and do not

  • Your instructions only. We process the data as this agreement says and as your company's admins set it up in qloudpulse, such as which accounts are connected and which options are on, and for no other purpose. If we believe an instruction breaks the GDPR, we tell you.
  • Unless the law says otherwise. If a law makes us process it otherwise, we tell you first, unless that law forbids it.
  • Confidentiality. Only our staff who need it to run and support the service can reach the data, and each of them is bound to keep it confidential. Each time our staff open a company's pages, the audit trail records it.
  • Security. We keep the measures listed below, and keep them up to date.
  • Helping you. We help you answer requests from the people concerned, for access, correction or deletion, as far as the product does not already let your admins do it themselves. We help you with security, breach notices, impact assessments and consultations with a supervisory authority, as far as they concern what we process.
  • Proof. We give you what you need to show that this agreement is kept, and allow audits as below.

Sub-processors

You allow us to use these sub-processors. Each is bound by a written agreement with the same data protection duties as this one, and we answer to you for them.

  • Amazon Web Services: hosts qloudpulse, its databases and its storage in AWS's Europe (Ireland) region, eu-west-1, and sends the service's emails through Amazon SES in the same region.
  • GitHub, United States: holds an issue for each problem report, without its screenshots, and for each error a page of the reports hits, in a repository only our engineers can open. TODO: the safeguard for the transfer to the US, for legal review
  • Google: our support mailbox in Gmail, where mail to support@qloudpulse.com arrives. Only what someone writes to support. TODO: a personal Gmail account comes with no processor terms; move support to a mailbox at qloudpulse.com (ADR 0043) before this agreement is signed

Before we add or replace a sub-processor, we change this list and email your company's admins at least 30 days ahead. If your company objects on reasonable grounds and we cannot meet them, it may end its use of qloudpulse and have its data deleted, as below.

Outside the EU

Your company's data is stored in the EU, in Ireland. If your company keeps it in its own AWS account in a region outside the EU, that is its choice and its instruction to us, and we read it there for as long as it stays. Otherwise it leaves the EU only for GitHub and Google as above, and only under the European Commission's standard contractual clauses or another safeguard the GDPR accepts.

How we keep it safe

TODO Check each measure against the running service before this agreement is signed.

  • Everything is served over HTTPS only, and the cluster pods send their figures over outbound HTTPS with a token per cluster.
  • Data is encrypted at rest in AWS.
  • Each company has a database of its own, and every request is checked against the company of the person signed in.
  • We read AWS accounts through read-only roles your company creates itself, which deny access to what is stored in them: files, rows, secret values and log events. Deleting the roles ends our access.
  • Data kept in your company's own AWS account is reached through one role that trusts only your company, with a session cut down to each use. The database answers our addresses only, over TLS, and everything there is encrypted with your company's own KMS key. Deleting that role or disabling the key ends our access.
  • Our staff sign in through our own Keycloak, with roles that hold only what each job needs.
  • Every change to a company's users and settings, and every time our staff open its pages, is recorded in an audit trail that nobody can change.
  • Our logs hold no personal data: job keys, run ids, counts and outcomes, never names, email addresses or request bodies.

We are working towards SOC 2. We do not have a SOC 2 report yet.

If something goes wrong

If we find a breach of the personal data we process for your company, we tell your company's admins without undue delay, and within 48 hours of finding it. We say what happened, what data and how many people it may concern, what it may lead to, and what we have done and will do about it, and we send what we learn later as we learn it. We help you with your own notice to the supervisory authority and to the people concerned.

Audits

We answer your company's written questions about how we keep this agreement. If the answers are not enough, your company, or an auditor it chooses who is bound to confidentiality, may audit us once a year, on 30 days' notice and in working hours, or at any time after a breach. Each side pays its own costs. TODO: audit terms, for legal review

At the end

When your company stops using qloudpulse, an admin deletes the company on its page in qloudpulse, or asks us to. Before that, an admin can ask us for a copy of the company's data.

  • At once: nobody can sign in to the company any more.
  • Within 30 days: its database, with everything collected for it, its feature requests, its problem reports and its settings are deleted. A deleted company's savings leave the total with the rest of its data.
  • Backups of what was deleted age out 35 days after that.
  • In your own AWS account: if your company keeps its data there, the purge ends our access, and the bucket and database stay your company's to keep or delete. Our own copy was deleted 7 days after the data moved.

We keep nothing of your company's data after that, apart from a line saying that the company existed, with its id and the dates it was deleted and purged, and what the law makes us keep. The audit trail is ours, kept as the privacy policy says.

The rest

Liability under this agreement is as in the terms of service. Where this agreement and the terms of service disagree about personal data, this agreement wins. TODO: governing law and courts, for legal review

When this agreement changes, this page changes with it, and so does the date at the top. A change that lowers your company's protection takes effect only after we have emailed its admins 30 days ahead.

For a signed copy, or anything about this agreement, write to TODO: privacy contact email.