How this server handles your data

This server keeps as little about the people using it as the job allows, and forgets it on a schedule. This page says what it keeps, why, for how long, and what you can do about it.

What is kept

• Your account: your name, your email address and when it was confirmed, a one-way hash of your password, when the account was made and what it may do. While a confirmation link waits to be followed, the address it was mailed to is kept with it.
• Your API tokens and signed-in browsers: a one-way hash of each, the name you gave a token, and when each was made, last used and expires.
• A record of each request: when it was made, which model and which machine answered it, how many tokens it used, how long it took and whether it succeeded.
• If you lend a machine: the name you gave it, the type you say it is, the hostname, system and version it reports, when it was last seen and the models it offers.
• If you count a machine in the pool, anybody who opens this server's front page sees one more machine of its type. Nobody is shown which machine is yours, and until you count it, it is shown only as undisclosed.
• If your machine reports power: how many watts it draws and, where it can tell, the energy it has used, sampled while it is online.

What is not kept

• What you ask and what comes back. This server passes both through and neither stores nor logs them.
• Your IP address. This server does not record it.
• Analytics, advertising and third-party scripts: there are none. The only cookie is the one that keeps you signed in.

Who else sees your requests

• Each request is answered by a machine that a member of this server lends. Its owner's software sees what you asked and what it answered, and may keep logs of its own, which this server can neither see nor erase. The X-Rozalia-Proxy response header names the machine that answered.
• The web server in front of this one may log the address and page of each request it forwards, as its operator has set it up.

For how long

• The record of each request is kept for 90 days, then erased.
• A revoked or expired API token is kept for 90 days, then erased.
• Power readings are kept for 14 days, then erased.
• Your account, tokens and machines are kept until you delete them or close your account. An expired sign-in, and a confirmation link that has lapsed, are removed within the hour.
• What is erased leaves the database file within the hour. Backups the operator keeps may hold it until they are replaced.

Why

To run the service you signed up for and, for the record of requests, to share the machines fairly and to show you and the operator what was used. Under the GDPR that is the agreement you entered by signing up (Art. 6(1)(b)) and the legitimate interest in running a shared service fairly (Art. 6(1)(f)).

To have an account you must give a name, an email address and a password; without them there is no account. Nothing else is asked of you: the record of requests is made as you use the service.

Your right to object

You may object at any time, on grounds relating to your particular situation, to the record of your requests being kept for the legitimate interest above. Write to the contact above. It must then no longer be kept, unless whoever runs this server shows compelling legitimate grounds that override your interests, rights and freedoms, or needs it for legal claims.

What you can do

From your account page you can correct your details, download everything this server holds about you, and close your account to have it erased. To have the use of your data restricted, so that it is kept but not used, or for anything else, write to the contact above. You may also complain to your data protection authority.