We keep this short, because our use of cookies is short.
We use cookies for one job: signing in
Our websites, including pyroclastic.cloud, this policies site, and the status page, set no cookies at all.
The only place we use cookies is Mayon, our sign-in server at mayon.pyroclastic.cloud, when you sign in. That covers two places:
- the account portal, where you manage your account; and
- the sign-in screen an app sends you to when you connect it to your account.
There, cookies:
- keep you signed in to the account portal during your session; and
- carry your sign-in safely through the steps of connecting an app, and protect those steps against forged requests from other websites.
What we don’t use
We do not use:
- performance or analytics cookies,
- advertising or tracking cookies, or
- third-party cookies of any kind.
Apps keep their own sign-in
Once you’ve connected an app to your account, the app keeps its own record of that sign-in, in your browser or on your device. That storage belongs to the app, and its own policies cover it.
Why there’s no cookie banner
Our sign-in cookies are strictly necessary to provide the service you asked for. Under EU law (Article 5(3) of the ePrivacy Directive, as implemented in each member state) and UK law (regulation 6(4) of the Privacy and Electronic Communications Regulations), strictly necessary cookies don’t require consent. Several European regulators advise against showing a consent banner for cookies like these, because it suggests you have a choice to make when you don’t.
The law still requires us to tell you about these cookies, which is what this page does.
Turning cookies off
You can block or delete cookies in your browser settings. If you do, you won’t be able to sign in to the account portal or connect apps to your account from that browser.
Changes to this policy
We may update this policy. When we do, we’ll change the “Last updated” date. If we ever want to use cookies for anything other than signing in, we’ll update this policy first.