Privacy

• AAS Archive is responsible for what is kept here.
• Write to admin@ai-assisted-speedruns.org to see what is kept about you, to have it corrected or removed, or to object. You get an answer within a month.

• Reading the site needs no account. The Archive counts visits to know whether anyone is reading it: how many people come, which pages they open, from which country and city, through which network (the provider or company that owns the address), and whether the page's stylesheet was loaded too, which tells a browser from a program. It does not profile you and does not follow you to other sites.
• Your IP address is used for that count and is turned into a code first, with a new key each day. One code is kept permanently, to count how many different visitors there have ever been.
• Failed sign-ins and floods of requests are counted against your address in the same way, to stop them, and those counts are gone within a day.
• The web server keeps an ordinary access log with your address in it, to see attacks.
• A code is not your name, but it is still about you, so you can ask what is held under it and object to it.

• They keep you signed in, make a form safe to send, and remember that you read the note at the foot of the page. None of them follows you, and nobody else reads them.

• An account holds your e-mail address, the name you choose for your runs, and how you sign in. Of a password only a hash is kept, from which the password cannot be read back.
• Signing in through another account tells the Archive who you are there, your confirmed e-mail address and your name. Nothing else, and nothing is written back.
• Your e-mail address is never shown on the site. The Archive writes to it about your submissions and your account, and for nothing else.
• When you sign in and what you change about your account is recorded, and you can read that list on your account page.
• If you sign the tooling in with aas login, the Archive records when that was and when it was last used. Your account page shows it, and signs it out.

• Reading the Archive's data through the API is free and needs an account: you make a token on your account page and send it with every request, or you ask from a browser signed in on the site.
• Of every request the Archive records which account and which token it was (or that it was your signed-in browser), what was asked (the endpoint and its parameters), when, the answer's status, and the code of the network address it came from, the same keyed code as for the visitor count, never the address itself.
• That record is there to know who reads what and to stop abuse of the API; it rests on the account you asked for, and on the Archive's interest in seeing how its data is used. It is kept for 90 days and then deleted; the totals per account stay.
• Your account page shows your tokens and your latest requests, lets you revoke a token, and your data file holds the whole record. Closing your account deletes your tokens and the record with it.

• A run you submit is published as its bundle holds it, under the name you chose. What the model said and did during the run is part of it, and it is public.
• Before a bundle is kept it is searched for things from the machine it was played on, such as names, paths and keys. A bundle carrying those is refused and not kept. The search finds what it knows to look for and no more, so look at what you publish before you send it: what is in the bundle is public.
• Links you add to a run are shown with it once a reviewer has approved them. A link points at someone else's page; what happens there is between you and that site.

• The tooling can ask this Archive to confirm when a run was played, if you are signed in with aas login or answer yes when it asks. It then sends a ticket request before the run, and during the run a hash of its own logs: at the start and end of every segment and once an hour. A hash is a fingerprint of those logs; the logs themselves stay on your machine, and nothing about you or the run goes with it. Without an account the ticket is tied to nobody until you submit the run.
• When you submit such a run, its raw logs are sent along in a private part of the upload. The Archive uses them for one thing only: to check that the published run is what those logs make. They are never published, never in any download and never shown on a page, and they are deleted as soon as a reviewer has decided on the submission, or after 30 days if nobody has.
• If a run is questioned later, the Archive can ask you to send the logs again. They have to match the fingerprints the Archive already signed, so they cannot have been changed in between.

• A comment under a run and a guide on a game are public the moment you post them, with the name on your account beside them. Anyone can read them, signed in or not.
• A comment stays as you wrote it until you change it yourself. A guide keeps every version, with the name of whoever wrote that version, so a change can always be undone; the versions are part of the guide and stay when you change it again.
• A reviewer can hide a comment or a guide, and the reason is shown where it stood. Hidden is not deleted: the Archive keeps it, and only reviewers still read it.
• Closing your account takes your name off what you wrote: the comment and the guide stay, without an author. Ask if you want something you wrote removed as well.

• The forum is part of the Archive: its pages are at /forum/, and it runs on a machine of its own. You are signed in there with your account here; the forum never has a password of yours and there is nothing to register there.
• The Archive tells the forum your account number, the name on your runs, your e-mail address, whether you have answered at it, and your roles here, which decide what you may do there. It tells it again when any of these changes here. Nothing else, and the forum writes nothing back. Your name and address are changed here, not there.
• The forum keeps what you post there and one cookie of its own, on its own address, to keep you signed in. Your address is not shown to other readers.
• The forum sends no mail at all: no notifications, no digest, nothing. What the Archive writes to you about your account comes from the Archive.
• What you post on the forum is public the moment you post it, with the name on your account beside it. Closing your account here closes your forum account too, with everything you wrote there.

• Anyone sees a published run and the name you chose for it.
• A reviewer sees the submission they are reviewing, with the name and e-mail address of whoever sent it.
• An admin sees every account: its address, its name, when it last signed in and what it has made.
• Nobody outside the Archive: no advertiser, no analytics service, no other company.

The Archive keeps to the European Union's data protection rules, the GDPR. It and its mail run on machines in the European Union, kept by the Archive itself, and nothing about you leaves the European Union.

• Your account and your submissions: the Archive holds them to do what you asked it to do.
• A published run: it stays because that is what an archive is, a record that can be checked later.
• Statistics: the Archive keeps visitor statistics to see how the site is used.
• Security: to prevent abuse of the site's forms and the API.
• No decision about you is made here by a machine, and nothing profiles you.

• See what is kept: your account page gives you everything about you in one file.
• Correct it: you change your name and your address there.
• Have it removed: close your account there. For a published run, ask on the run's own page and a reviewer removes it.
• Take it with you: that file is JSON, which any other system can read.
• Object, or ask that its use be limited: write to admin@ai-assisted-speedruns.org.
• Complain: to the data protection authority of the country you live in.

Closing your account deletes it with your sign-in methods, your keys, your submissions and everything you wrote about your runs.