Legal
Terms of use
The terms under which you may use the CASRAI website, the Dictionary content, the GraphQL and REST endpoints, and any contributions you submit. We’ve tried to keep them short and reasonable; the content licence (CC-BY 4.0) is the load-bearing part.
These terms govern your use of casrai.org and the services it offers — the Dictionary, CRediT vocabulary, GraphQL endpoint, REST feeds, machine-readable distributions, the Ask CASRAI assistant, and editorial publishing. The substantive outputs are licensed CC-BY 4.0; that licence is the load-bearing part of the relationship. These terms cover the bits CC-BY doesn’t speak to: rate limits, contributor licensing, brand use, and the boring-but-necessary disclaimers. For the trademark policy specifically see /legal/trademark; for privacy and data handling see /legal/privacy; for the imprint / responsible-person disclosure see /legal/imprint.
Section 1
Content licensing
The CASRAI Dictionary, the CRediT-adjacent editorial outputs published on this site, the per-release datasets, the JSON-LD / Turtle / JSON / CSV distributions, and any prose authored by the editorial board are licensed Creative Commons Attribution 4.0 International (CC-BY 4.0). You can copy, redistribute, adapt, translate, and build upon them — including commercially — so long as you credit CASRAI as the source and indicate any changes.
Three exceptions: (a) the CASRAI name and logo are trademarks, not CC-BY assets — see /legal/trademark; (b) individual photographs of people on the site are licensed individually with attribution as marked; (c) third-party content embedded with permission (e.g., quotations from peer-reviewed papers, partner logos under partnership notices) follows the original source’s licence terms. The CRediT taxonomy specifically is stewarded by NISO under ANSI/NISO Z39.104-2022 and is also CC-BY 4.0 — cite NISO as the steward; see /credit/standardization.
Section 2
API and machine-readable distributions
We expose the Dictionary through a public GraphQL endpoint at /implement/graphql, REST feeds at /feed.xml and /feed.json, and LLM-targeted bundles at /dictionary/for-llms and /credit/for-llms. Public read access is unauthenticated. Rate limits apply: 60 requests per minute per IP unauthenticated, 300 requests per minute authenticated. The limits are protective of shared infrastructure, not an artificial scarcity — if your institutional or integration workload needs more, email [email protected] and we’ll lift the cap for legitimate use.
Prefer the machine-readable distributions over scraping the HTML pages; they’re quicker for you and cheaper for us, and they let us cache aggressively at the edge. For bulk mirroring (e.g., a CRIS pulling a monthly snapshot), pin to the dated release version URL rather than the live one — see /standards/versioning for the version-pinning pattern.
Section 3
Contributions
By submitting a term proposal at /dictionary/contribute, a translation at /get-involved/translate, a comment during a public-review window at /get-involved/comment, an editorial submission, or any other contribution to CASRAI, you grant CASRAI a perpetual, irrevocable, royalty-free, sublicensable, non-exclusive licence to use, modify, publish, translate, and redistribute your contribution under CC-BY 4.0. You retain copyright in the original work; the licence permits us to publish and the community to reuse.
We attribute substantive contributors on the published entry using the CRediT vocabulary — the same vocabulary the site develops. The pattern is documented at /credit/for-authors. If you would prefer your contribution be attributed under a pseudonym, or anonymously, say so when you submit.
Section 4
Disclaimers
The Dictionary, CRediT vocabulary, editorial guidance, and implementation playbooks are provided as is, without warranty of any kind, express or implied. The CASRAI editorial board reviews each release before sign-off and entries link to the authoritative external sources (NISO, ISO, ICMJE, COPE, NIH, FDA, EMA, ROR, ORCID, and others) but errors and omissions are possible.
For life-safety, regulatory, or compliance-critical use — clinical-trial reporting, regulatory submissions, formal grant applications, audit evidence — defer to the authoritative external source linked from the entry, not to our restatement of it. Where you find an error that matters, tell us at [email protected] and we’ll fix it within the next release window, out-of-cycle for safety-critical cases.
To the maximum extent permitted by applicable law, CASRAI is not liable for indirect, incidental, consequential, or special damages arising from use of the site or its content. The CC-BY 4.0 licence itself includes a no-warranty clause; this paragraph restates that clause in plainer terms.
Section 5
Acceptable use
Don’t do the obvious bad things: probe for vulnerabilities outside our published security-response process; attempt to access non-public parts of the editorial CMS; circumvent the rate limits via distributed scraping; impersonate CASRAI editorial staff; or use the GraphQL endpoint as a backbone for malware command-and-control, spam, or denial-of-service against third parties. We reserve the right to block traffic and pursue any other remedies available to us where this happens.
For coordinated security disclosure, email [email protected]; we treat good-faith disclosures favourably and don’t pursue legal action against researchers acting under a clear vulnerability-disclosure policy.
Section 6
Ask CASRAI (the AI assistant)
Ask CASRAI answers questions using only CASRAI’s own published pages, and cites them. It is offered as is and as available, free of charge, with no warranty of any kind and no service-level commitment. Answers are drafted by a language model and may be incomplete, out of date, or simply wrong; the disclaimers in Section 4 apply to them in full, and with more force. For anything compliance-critical — a regulatory submission, a grant application, a research-integrity determination — rely on the primary source we link, not on our restatement of it, and not on a generated answer. Answers on /ask/a/… permalinks have had no editorial review; only published /ask/… pages carry a named reviewer.
Fair use. The assistant is provided for people researching a question. Per-session, per-account and per-network limits apply and are enforced; they exist because each answer costs us real compute, and they are set so that ordinary research use never notices them. Please don’t automate queries against it, distribute them across addresses or sessions to evade the limits, use it as a general-purpose language-model proxy, or attempt to extract its instructions or the underlying corpus through it. If you want the content in bulk, take it — properly and for free — from the machine-readable distributions in Section 2, which are faster for you and cheaper for us.
Your questions. What we keep, for how long, why, and how to have it deleted is set out in the privacy policy. In short: questions are logged so we can see what our documentation is missing and write it; they are scrubbed of anything resembling personal data before storage; they are never sold; and they are never used to train a third-party model, which is enforced on every request we send rather than merely asserted here. Don’t paste confidential or unpublished material into it. If a question of yours becomes the basis of a published answer page, it is rewritten and reviewed by an editor first — a raw submitted question is never shown to another user.
Availability. We may rate-limit, degrade, suspend or withdraw the assistant at any time, for any user or for everyone, without notice — including automatically, when our own cost or abuse limits are reached. Nothing else on casrai.org depends on it: the Dictionary, the CRediT documentation, the guides and every API in Section 2 remain fully usable, and the underlying content stays CC-BY 4.0 regardless.
Section 7
Governing law and updates
These terms are governed by the laws of England and Wales, and disputes arising from them are subject to the exclusive jurisdiction of the English courts. The choice reflects where the operating entity is being incorporated in 2026; the editorial board itself is internationally distributed — see /legal/imprint.
We may update these terms with 30 days’ notice via the editorial newsletter and a prominent banner on this page. Material changes (those that meaningfully shift what you can or cannot do, or that change the licensing posture) trigger a full editorial-board sign-off; cosmetic changes do not. The current revision is dated at the foot of this page.
FAQ
Frequently asked
- Do I need to accept these terms to read the site?
- Reading the public pages doesn't require accepting anything beyond the implicit norms of fair use. The terms govern more active uses — API consumption, term proposals, translations, and any reuse of the Dictionary content under the CC-BY 4.0 licence.
- I want to scrape the dictionary into my private system. Is that allowed?
- Yes, with two practical conditions. Use the GraphQL endpoint or the JSON / RDF / CSV distributions rather than scraping the HTML — it's faster for both of us. And stay inside the rate limits (60 req/min per IP unauthenticated, 300/min authenticated). The content is CC-BY 4.0; reuse is the explicit default.
- I run a CRIS at my institution and want to mirror the dictionary monthly. What do I need to do?
- Use the dictionary release dataset (each release is dated, versioned, and citable) rather than scraping live. Cache the JSON or Turtle distribution locally; refresh against the canonical version URL when the next release ships in March or September. No registration is needed. If your traffic exceeds 300 req/min authenticated, email [email protected] and we'll lift the cap.
- A term proposal I submitted was changed materially by the editorial board. Did I lose control of my contribution?
- You retain copyright in the original submission; the licence you grant is non-exclusive and irrevocable, so the board can publish, modify, and translate it under CC-BY 4.0. Editorial modification is the norm — proposals are starting points for a community review, not finished entries. We attribute substantive contributors per the CRediT vocabulary on the published entry.
- Can I build a product on top of Ask CASRAI, or query it programmatically?
- Not through the assistant. It is rate-limited per session, per account and per network, and those limits are enforced — scripted querying, distributing queries across addresses to evade them, or using it as a general-purpose language-model proxy will get the traffic blocked. Build on the machine-readable distributions instead: the GraphQL endpoint, the JSON / RDF / CSV releases, and the REST feeds in Section 2 are unauthenticated, generously rate-limited, CC-BY 4.0, and give you the same underlying content in a form you can actually depend on. A stable public /api/v1/ask is on the roadmap; until it exists, the assistant is for people, not programs.
- The assistant gave me an answer that turned out to be wrong. Where does that leave me?
- Answers are drafted by a language model over CASRAI's own published pages, and they are offered as is, with no warranty — the same disclaimer that covers the rest of the site, and it applies here with more force. That is exactly why every answer cites the pages it drew on and why we link the funder's or publisher's own policy: for anything compliance-critical, the primary source governs, not our restatement of it and certainly not a generated summary. Answers at /ask/a/… permalinks have had no editorial review at all; only published /ask/… pages carry a named reviewer with a resolvable ORCID iD and a review date. Tell us where it went wrong — the thumbs-down on the answer, or [email protected] — because a wrong answer usually means a page of ours is wrong or unclear, and that is worth fixing.
- Which jurisdiction governs disputes?
- England & Wales. The editorial board is internationally distributed but the operating entity is being incorporated under English law in 2026; English courts have exclusive jurisdiction over disputes arising from the terms.
- If the dictionary contains an error that affects my regulatory filing, can I sue CASRAI?
- The terms include the standard "no warranty" disclaimer common to open-licence content, so a contract claim for editorial error is unlikely to succeed. But: every entry links to authoritative external sources (NISO, ISO, NIH, FDA, EMA, etc.) and we expect implementers to defer to those for compliance-critical use. Tell us where the error is — [email protected] or [email protected] — and we'll fix it within the next release window or out-of-cycle for safety-critical errors.
Related legal pages
Licensing (CC-BY 4.0) · Privacy · Cookies · Imprint · Trademark · Accessibility · Citation policy · Verified Contributor Directory terms
Last reviewed by the CASRAI Editorial Board: July 2026 (Section 6, Ask CASRAI, added 31 July 2026).







