Legal Document
These terms cover membership of the Revision Genie developer programme and use of the Revision Genie developer API. They are an agreement between you and Revision Genie Ltd, a company registered in England and Wales (company number 16212210, registered office 45 Fitzroy Street, London W1T 6EB).
They are written for the person or organisation building a product on top of our API. If you are a student, parent, teacher or school using Revision Genie itself, our Terms and Conditions are the document you want.
We have kept these terms short and readable. Where something matters commercially or legally we have said it plainly rather than burying it, including the parts that are less generous than you might hope.
1.1 These terms apply to every developer registered for the programme, and to every call made with a developer API key issued to them.
1.2 "You" means the individual or organisation named on the developer registration. If you are registering on behalf of a company or other organisation, you confirm that you are allowed to accept these terms for it.
1.3 You must be at least 18 years old to join the developer programme.
1.4 Your ordinary Revision Genie account is still governed by our Terms and Conditions, Privacy Policy and Acceptable Use Policy. Where any of those conflict with these terms in relation to the developer API, these terms take priority.
1.5 You accept these terms when you complete developer registration, and we record the date you accepted them.
2.1 Your API keys are secrets. Treat them the way you would treat a password.
2.2 You are responsible for everything done with your keys, whether by you, by your colleagues, or by anyone else who obtains them.
2.3 Never place a secret key in a mobile app, a web page, a public code repository, or anywhere else a user could read it. Calls should be made from a server you control.
2.4 If a key is exposed, revoke it immediately in your developer dashboard and tell us at support@revisiongenie.com.
2.5 Do not share your keys with another organisation, and do not use them to give API access to anyone who is not a user of your own product.
3.1 We grant you a non-exclusive, non-transferable, revocable licence to call the API and to use the data and outputs it returns inside your own product, for as long as your developer account is active and in good standing.
3.2 You may store and cache API responses as far as you need to in order to run your product, and you may display them to your users.
3.3 You may not redistribute, resell, publish or otherwise hand on the raw data the API returns, in bulk or as a feed of your own, whether free or paid.
3.4 You may not use the API to assemble a copy of our catalogue, or any dataset or index that would stand in for calling the API. Systematic downloading for that purpose is a breach of these terms.
3.5 You may not sublicense your access, or let a third party call the API through you as though it were their own service.
3.6 You may not reverse engineer the API, work around its authentication or its limits, or probe it for weaknesses except where we have invited you to in writing.
3.7 We keep all rights in the API, in our curriculum structures and content, and in our brand. Nothing in these terms transfers ownership of anything to you.
4.1 Any surface in your product powered by our genie chat API must show the words "Powered by Revision Genie" on or beside that surface, where the user can see it.
4.2 The attribution must be legible and reachable. Hiding it behind a menu, a tooltip, or an about page nobody visits does not count.
4.3 You may use our name and logo for that attribution, and to state truthfully that your product uses the Revision Genie API. Any other use of our brand needs our written agreement.
4.4 You must not say or imply that we endorse, approve, check or are partners in your product, beyond the fact that you are a member of the developer programme.
5.1 Revision Genie is an independent product and is not affiliated with or endorsed by AQA, Pearson Edexcel, OCR, WJEC or Eduqas. Those names belong to their owners and we use them only to describe which qualification our content relates to.
5.2 The API does not supply exam board specification text, past papers or mark schemes. It will not do so unless the board concerned grants us a written licence, and we would tell you before anything of that kind appeared in a response.
5.3 Where the API returns a specification reference, such as a unit or point code, it is a factual signpost to the board's own published document, and we include a link to that document so you can show your users the real wording from the source. The reference and the mapping to our subtopics are our own work. The board's wording is not included and is not ours to give you.
5.4 If you want to show exam board material in your product, whether specification text, past papers, mark schemes or a board's branding, getting permission for it is your responsibility and not ours.
5.5 You must not present anything the API returns as a board's official material, or as approved, checked or endorsed by a board.
5.6 Where your product shows specification references taken from our API, it should carry a non-affiliation statement of its own, saying in substance what clause 5.1 says.
6.1 We may add, change or withdraw any endpoint, field or dataset at any time.
6.2 Where a change would break working integrations we will give reasonable notice wherever that is practicable, normally at least 30 days, through our developer changelog and by email to registered developers.
6.3 We may make a change immediately and without notice where we need to for legal or safety reasons. That includes a complaint or demand from a rights holder, a change to a licence we rely on, a court or regulatory order, a security problem, or a risk to users.
6.4 Acting under clause 6.3 is not a breach of these terms by us. Being able to withdraw something quickly is part of what lets us offer any of this data in the first place.
6.5 If we permanently withdraw an endpoint and that leaves you holding a balance you can no longer spend, section 10 sets out what happens to it.
7.1 We build our subject, topic and subtopic structures ourselves, we name them ourselves, and we believe we are entitled to share them along with the specification references that go with them.
7.2 What we cannot do is guarantee that no exam board or other rights holder will ever take a different view.
7.3 So, plainly: we give no indemnity for third party intellectual property claims relating to curriculum data, specification references, mappings, names, or anything derived from them. In that respect you use the data at your own risk, and how you present it in your product is your responsibility.
7.4 If a rights holder raises a complaint with us, we may withdraw the affected data under section 6. Neither the complaint nor the withdrawal is a breach of these terms by us.
7.5 This section does not affect section 13, and nothing in these terms limits any liability that cannot be limited by law.
8.1 Your users are yours, not ours. You are responsible for them and for what your product does.
8.2 If children can use your product, meeting the duties that come with that is your responsibility. This includes age appropriate design under the ICO's Children's Code, your safeguarding duties, and any obligations you have under online safety law. We cannot meet them for you and we do not check them for you.
8.3 You are the controller of your users' personal data. We do not process personal data about your users through the API, and we are not your processor for them.
8.4 Do not send us personal data about your users. Names, contact details, school details, or anything else that identifies a person must not appear in prompts, in message history, or in any other field you send us. The chat API is stateless: we store no conversation, and we neither read nor write any learner profile.
8.5 If you send us personal data in breach of clause 8.4, that is your breach, and we may delete it without notice.
8.6 The chat API runs our safeguarding detection. Where a message suggests a user may be at risk, the API returns a refusal event with a reason instead of an answer, and we do not charge you for that call.
8.7 Your product must handle a refusal event responsibly. Show the user something appropriate, give them a route to real help, and do not hide the event, strip it out, or retry the request to get past it.
8.8 Do not present the API as counselling, crisis support, or any kind of clinical or emergency service, and do not build a product that invites users to rely on it in that way.
8.9 Our Safeguarding Policy and Children's Code Compliance pages set out how we approach this on our own platform. They are a fair guide to the standard we expect from products built on our API.
9.1 Questions, answers, explanations and other AI output can be wrong, out of date, or pitched at the wrong level. Nothing the API generates is checked by a person before it reaches you.
9.2 You must satisfy yourself that anything you show your users is accurate and suitable for them, particularly where those users are children. That review is yours to do.
9.3 We make no promise about grades, exam outcomes, or complete coverage of any specification, and you must not make a promise of that kind to your users on our behalf.
9.4 Tell your users when content is AI generated. It is the honest thing to do, and in some settings you may be required to.
9.5 Our AI Ethics and Usage Policy explains how we build and monitor these features.
10.1 There is one prepaid balance, which you top up in pounds sterling. Access to the data endpoints is included once you have made your first top-up, of any amount we offer, and stays included for as long as your developer account is active, whatever your balance is afterwards. The endpoints marked as paid in our developer documentation are charged per call against that balance. There is no separate data plan and no separate periodic fee for data access.
10.2 Your balance is money held on account. The amount you pay is the amount added to your balance: there is no separate unit, no conversion and no bulk discount. It cannot be transferred between accounts, and it does not expire while your developer account is active.
10.3 Each AI call costs the price published in our developer documentation. Those published prices are the prices we charge. We may change them on at least 30 days' notice, and a change never applies to a call you have already made.
10.4 A call that fails because of a fault on our side is not charged. Where a charge has already been taken for such a call, we return it to your balance.
10.5 You can top up by hand, set up a monthly top-up, or switch on automatic top-up, where we charge your saved payment method when your balance falls below a threshold you choose. You can change or switch off any of these at any time in your developer dashboard.
10.6 Within 14 days of a top-up you may ask us to refund any of that top-up you have not spent. The Consumer Contracts Regulations 2013 protect consumers rather than businesses, but we apply the same 14 day position to developers as a matter of policy.
10.7 If your access to the programme ends, we refund your unspent balance. We will not do this where we ended your access because you broke these terms.
10.8 If we permanently withdraw an endpoint and that leaves you with a balance you cannot use, clause 10.7 applies as though your access had ended.
10.9 Payments are handled by Stripe. Our Refund Policy covers consumer purchases on the main platform. For the developer programme, this section is the one that applies.
10.10 Prices are exclusive of VAT unless we say otherwise, and VAT is added where it applies.
11.1 Every key carries per-minute rate limits, published in our developer documentation. Calls beyond a limit are refused rather than queued.
11.2 Do not work around a limit by spreading traffic across several keys or several accounts, or by any other method.
11.3 We may apply a temporary limit, or refuse traffic, to protect the service or other developers. Where we do this to your account for anything other than a brief automatic throttle, we will tell you.
11.4 If you are expecting unusual volume, such as a launch or a start-of-term peak, tell us in advance and we will do what we can to accommodate it.
12.1 You can stop at any time. Revoke your keys in the dashboard and tell us you are closing your developer account.
12.2 We may suspend or end your access if you break these terms, if money you owe us is unpaid, if there is a security problem, if the law requires it, or if your use is harming users or the service.
12.3 Where it is safe and practical, we will contact you first and give you a chance to put things right. In serious cases, and particularly where users may be at risk, we may act immediately.
12.4 When your access ends you must stop calling the API, stop using our name and logo, and delete data you have stored from the API within 30 days, apart from anything you have to keep for legal or accounting reasons.
12.5 Sections 5, 7, 12.4, 13 and 15 continue to apply after this agreement ends.
13.1 The API is provided as it is. We do not promise uninterrupted or error free service, and current service state is published on our status page.
13.2 We are not liable for loss of profit, loss of business, loss of data, or any indirect or consequential loss arising from your use of the API.
13.3 Our total liability to you in any twelve month period is limited to the amount you paid us for the developer programme in that period.
13.4 Nothing in these terms limits our liability for death or personal injury caused by our negligence, for fraud or fraudulent misrepresentation, or for anything else that cannot be limited by law.
13.5 You will cover us against claims brought by your users or by any third party arising from your product, from your use of the API, or from your breach of these terms.
14.1 We may update these terms. The date at the top of this page always shows the current version.
14.2 For material changes we will email registered developers at least 30 days before they take effect, unless a change is needed sooner for legal or safety reasons.
14.3 Continuing to call the API after a change takes effect means you accept the updated terms. If you do not accept them, close your developer account and section 10 covers your unspent balance.
15.1 These terms, and any dispute or claim arising out of them, are governed by the law of England and Wales.
15.2 The courts of England and Wales have exclusive jurisdiction over any such dispute or claim.
For anything about the developer programme, your keys, billing or your balance, email support@revisiongenie.com.
For data protection questions, contact our Data Protection Officer, Joel Martin, at joel@revisiongenie.com.
Our developer documentation is the technical reference these terms point to, including the published prices, rate limits and changelog.