Terms of Service

1. Acceptance of These Terms

By using the Coder in 90 website, by subscribing to Coder in 90 Classroom, or by joining a class that runs on it, you agree to these Terms of Service. If you do not agree, do not use the site or the product.

These terms cover two different people, and most sections say which one they bind. An instructor is the person or institution who subscribes and runs classes. A student is someone who joins one of those classes. Section 3 sets out the difference and Section 15 covers the separate case of a self-paced course bought before this version took effect.

2. What Coder in 90 Sells

The paid product is Coder in 90 Classroom, a per-instructor monthly subscription to software that runs coding assignments on GitHub. It creates a repository from your starter repository for each student, or for each team on a team assignment, installs an autograding GitHub Actions workflow, reads each run's test results into a gradebook, and writes plain-language explanations of failures.

Plans are sold by class size. There are three sizes: up to 50 active students a month, up to 150, and up to 400. Current prices are on the pricing page. Larger classes and multi-instructor departments are arranged by email.

Each plan is available in two forms: one where we supply the AI capacity, and one where you supply your own AI provider key. The second is set up on request rather than bought from the site; email us if you want it.

Students never pay. The instructor's subscription covers everyone in their classes.

3. Instructors and Students

The instructor is the paying customer. They choose the plan, hold the billing relationship with us, decide who is on the roster, own the GitHub organization the class runs in, and set the class settings that decide what is collected from students and for how long. Sections 4 to 8 bind the instructor and nobody else.

A student is a user, not a customer. Joining a class, accepting an assignment, pushing work, reading feedback and using the Coder in 90 CLI involve no payment of any kind, and a student is never asked for a payment method. Sections 9 to 14 bind a student: GitHub, AI-generated feedback, the handling of their work, acceptable use, intellectual property and limitation of liability.

A student's relationship over their coursework is with their instructor and their institution. We provide the software that instructor uses.

4. Your Subscription

A Classroom plan is a monthly subscription that renews automatically until you cancel it. Checkout starts a 14-day free trial. We collect a payment method when the trial starts and charge nothing until the trial ends; if no payment method is given, the subscription is cancelled at the end of the trial rather than converted.

You may cancel at any time by emailing hello@coderin90.com. Cancelling stops the next renewal. Your class keeps working until the end of the period you have already paid for, and we do not interrupt a term you have paid for because a card was declined; a failed payment is retried before anything changes.

When a subscription ends, the repositories the product created stay where they are. They live in your own GitHub organization, they belong to you and your students, and we do not delete, archive or transfer them. What ends is your right to use the software around them: the gradebook, assignment provisioning, autograde ingest and AI-generated feedback. Export anything you want to keep, such as the gradebook CSV, before you cancel, and remove the GitHub App from your organization when you are done.

5. Plan Size and AI Usage

Your plan size follows the peak number of active students in a calendar month, counted across every class on the subscription rather than per class. Where several instructors share one subscription, it is counted across all of their classes together. A student is active in a month if they submitted work in it, so last term's roster stops counting on its own. If you cross the cap of your plan, we will move you up to the next plan size for the following month; nothing is cut off at the cap and no student is turned away mid-term.

Plans where we supply the AI include a monthly allowance of AI explanations. What counts against it is a graded run that called for one: a run where every test passed spends none of it, and neither does an assignment carrying no points. If you go past the allowance, feedback keeps working and the extra runs are metered and added to your next invoice, at the rate stated on the pricing page. We do not cap or throttle grading runs themselves; the only limits on those are the resubmission limit you set yourself on an assignment, and your own GitHub Actions allowance, since the grading workflow runs in your organization.

One feature is an exception on every plan: an assignment marked by an AI judge against a rubric you wrote runs on your own AI provider key, whichever plan you are on, because judging a whole working session costs many times what explaining a failed test does. Without a working key of your own, those assignments report an error instead of a mark. Nothing else works that way.

6. Payments, Pricing and Tax

Prices are listed in US Dollars (USD). Payments are processed by Stripe as our Merchant of Record. Stripe Tax adds the destination-country VAT or sales tax on top of the listed price at checkout and remits it to the appropriate authority. Stripe may present the price in your local currency; settlement is in USD. By subscribing, you authorize Stripe and us to charge the payment method you provided, on each renewal, for the plan price plus any metered usage under Section 5.

7. Refunds and Cancellations

The 14-day free trial is how you evaluate Classroom before paying for it, so a subscription is not refunded pro rata for a partial month. Cancelling ends the renewal and leaves your access in place for the rest of the period you have paid for.

If we get something wrong on our side, write to us. We would rather sort out a billing mistake than stand behind a paragraph.

If we discontinue Classroom outright, we will tell you by email and refund the unused part of the period you have paid for. The separate Refund Policy applies to the self-paced courses in Section 15 and not to a subscription.

8. EU Consumers and the Right of Withdrawal

If you are a consumer resident in the European Union, you have a 14-day right of withdrawal after concluding a distance contract, under the EU Consumer Rights Directive (Directive 2011/83/EU). A school, university, bootcamp or company subscribing for its teaching staff is not a consumer, and this section does not apply to it.

We do not ask you to waive that right, and there is no waiver checkbox at Classroom checkout. A Classroom subscription is a continuing service rather than a one-off supply of digital content, and its free trial is 14 days, which is the same length as the withdrawal period. So the practical effect is that you may withdraw inside the first 14 days and owe nothing, because nothing has been charged yet.

To withdraw, email hello@coderin90.com within 14 days of subscribing. Withdrawing after a charge has been taken is treated as a cancellation under Section 7. Nothing in these terms limits a mandatory consumer right you hold in your own country.

9. GitHub, and the Access You Grant Us

Classroom runs on GitHub and does not host code itself. To use it, an instructor installs the Coder in 90 Classroom GitHub App on the GitHub organization the class will run in. GitHub asks the instructor to approve the App's permissions, and that approval is the sole authority under which the App acts. An instructor who does not own or administer the organization must not install it there.

The App is granted the ability to create repositories, read and write repository contents, install and update the autograding workflow, read Actions runs and check runs, and open and comment on pull requests and issues. It uses that access to create a repository per student, add students and teaching assistants as collaborators, commit the grading workflow, read results, and post feedback. It writes only to the repositories it created for your classes, with two exceptions, both on your own starter repository and both of which you ask for explicitly: if the starter is not marked as a template, the assignment page offers to tick that box for you, and the same page offers to replace an out-of-date grading workflow inside it. Neither happens without your confirmation.

Students are added as repository collaborators. They are not added to your GitHub organization.

Instructors and students each need their own GitHub account and are bound by GitHub's Terms of Service as well as by these terms. GitHub's availability, its Actions allowances and its handling of your repositories are matters between you and GitHub. An instructor may remove the App from their organization at any time, which stops all of the access described above.

10. AI-Generated Feedback Is Not a Grade

Two things the product writes are produced by a language model: the explanation of why a test failed, and the review of the changes on a branch where every test passed. Both are AI-generated, and both can be wrong. They can misread code, miss a real defect, describe one that is not there, or comment on a line the student did not write.

This material is teaching commentary. It is not a grade of record. The instructor is the grader: they set the assignment, decide what a submission is worth, review what the autograder recorded, and issue the mark that counts. Instructors may hold AI-generated feedback for review before students see it. Students who think a piece of feedback is wrong should raise it with their instructor.

We make no warranty that AI-generated feedback is accurate, complete or fit for assessment, and we do not offer it as a substitute for the instructor's own judgement.

11. Student Work, Submissions and CLI Transcripts

Students keep ownership of the code and written work they produce. We claim no ownership of it. We process it to run the product: to grade a submission, to write the feedback described in Section 10, and to show the instructor what was handed in.

The Coder in 90 CLI can record a transcript of a student's AI-tool sessions and the commands run inside its session shell, and upload it to the instructor when work is pushed. To find secrets worth removing it also reads project config files such as .env and replaces the values it finds there. The CLI asks for the student's agreement before any of that happens, and states what is collected and how it is redacted. Secrets and personal data are removed before the record is readable.

Transcript content is deleted 30 days after it is uploaded. A class may extend that period, to a maximum of 730 days, and a class cannot shorten it below 30 days. When content is deleted, the record that a session existed is kept, so an instructor can tell a student who used no AI from a record that has aged out.

How we collect, use, share and delete personal data, and how to opt out of analytics and session recording, is set out in the Privacy Policy. Where an instructor runs a class for a school or other institution, that institution decides what is collected from its students and why, and we handle student coursework data on its instructions; the Data Processing Agreement forms part of these terms and governs that handling. Instructors: a student who asks us to access or delete their class data will be referred to you.

12. Acceptable Use

Instructors and students alike agree not to:

• Use the service for any unlawful purpose.
• Attempt to gain unauthorized access to our systems, to another class, or to another student's work.
• Interfere with the operation of the website, the grading pipeline or the CLI.
• Submit content that infringes someone else's rights, or that is malicious, or that is designed to attack the grading infrastructure.
• Redistribute or resell access to the product.

Instructors are responsible for the roster they build and for having the right to enrol the students on it. We may suspend an account that breaks this section, and we will say why.

The autograder is not an anti-cheat system, and we do not present it as one. It reports what the tests in a repository produced.

13. Intellectual Property

The Coder in 90 software, website, documentation, brand and course materials are our intellectual property. A subscription grants a non-exclusive, non-transferable right to use the product for the duration of the subscription, and nothing more.

Assignment briefs and starter repositories written by an instructor stay the instructor's. Work written by a student stays the student's.

14. Limitation of Liability

Coder in 90 is provided on an "as is" basis. We do not guarantee uninterrupted availability, and much of the pipeline depends on GitHub and on third-party AI providers whose outages we do not control. We do not guarantee specific outcomes, employment or income for any student.

To the maximum extent permitted by law, our total liability arising from or relating to the service is limited to the amount the instructor paid us in the twelve months before the claim. For a student, who pays us nothing, liability is limited to the maximum extent the law permits. Nothing here excludes liability that cannot be excluded by law.

15. Purchases Made Before September 9, 2026

Coder in 90 used to sell self-paced courses as digital products: pre-recorded, on-demand video lessons with downloadable worksheets and written reference material, delivered as instant access to the purchased modules the moment payment was confirmed. They carried no service-level deliverables: no scheduled sessions, no instructor time and no human-delivered services were bundled into the price. Those courses were withdrawn on July 8, 2026 and are no longer sold. Checkout refuses every course and workshop product, and no page offers one.

If you bought one before then, your enrollment stands and this section governs it. Your access to the modules you purchased continues, the Refund Policy continues to apply to that purchase, and the right-of-withdrawal waiver, where you accepted one at checkout, continues to apply to it exactly as it did on the day you bought. That waiver rested on Art. 16(m) of the Consumer Rights Directive: it gave up the 14-day right of withdrawal an EU consumer would otherwise have held, and it took effect when you first accessed a paid module, for example when you began streaming a lesson or opened a worksheet. Where no waiver was given, the 14-day right stood as the law provides. Nothing in the sections above narrows a right you already held.

The previous version of these terms, effective May 12, 2026, governed those purchases and remains the version they were made under. Email us if you need a copy.

16. Changes to These Terms

We may update these terms. Material changes will be announced by email to instructors, or by a notice on the website, before they take effect. Continued use after a change takes effect is acceptance of the revised terms. Each version carries the effective date at the top of this page.

17. Governing Law

Coder in 90 is operated from Spain as a sole trader (autónomo). These terms are governed by the laws of the Kingdom of Spain. Any disputes arising from or relating to these terms shall be submitted to the courts of Barcelona, unless mandatory consumer-protection rules in your country of residence provide otherwise.

18. Contact Us

Questions about these terms? Email hello@coderin90.com.