OSCR

Your data and your rights

See what OSCR holds about you, and use your rights under the EU's General Data Protection Regulation (GDPR): access, erasure, objection, rectification, the deletion of your account. You ask signed in, and the answer comes to this page: OSCR has no email address, and asks for none. The privacy page lists everything the registry holds, why, and for how long.

What OSCR may hold about you

Your account, if you signed in
The name your provider gave, your ORCID iD and GitHub login once linked, the identifiers of your linked identities, your sessions (a short description of the browser, never an IP address), your roles. Shown on this page once you are signed in.
Your requests
What you submitted, claimed, corrected, validated or asked to remove, with the decisions; and, on the operator's computer, the moderator's log of those decisions (12 months).
Your contact details, if you are an author of a paper the registry read
What the paper publishes about how to reach you: email address, given and family names, ORCID iD, organisation, postal address and affiliation — kept privately, to cite the authors of the code and to reach you about your own work; never shown, never published, never used for mass email. The registry recognizes them as yours by your ORCID iD only: a name, a GitHub login or a Google account proves nothing.
Your name in the published records
Your name, ORCID iD and affiliations as a paper and its public metadata publish them: that is the public record of the paper, which this page does not change. To have part of a record removed, use its removal request.

How a request is answered

  1. OSCR's machine reads the requests every 10 minutes or so. It answers by itself what it can prove: access (your account's data; and, signed in with your ORCID iD at orcid.org, each contact detail kept under that iD, your email address masked), erasure and objection (signed in with your ORCID iD), the deletion of your account.
  2. What it cannot prove — a rectification, or contact details asked for by an account without an ORCID iD — waits for the operator, who answers on this page within one month, as the GDPR requires (article 12(3)). There is no human moderator on duty at the moment, but a request about your data is never closed unanswered: it stays open until the operator answers it.
  3. An erasure reaches the private copy of the contact details on Hugging Face at the next nightly publication (04:17, the registry's local time), which rewrites that copy's history, so that no earlier version keeps you.
  4. A refusal says why. You may also complain to the data protection authority of the country where you live or work.

What is kept of a request