Terms of Service

1. Acceptance of These Terms

By using the Coder in 90 website, subscribing to Coder in 90 Classroom, or 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 roles. An instructor is the person or institution who subscribes and runs classes. A student is someone who joins one of those classes. Section 3 says which sections bind whom.

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. For each student, or each team on a team assignment, it creates a repository from your starter repository and installs an autograding GitHub Actions workflow. It then reads each run's test results into a gradebook and explains failures in plain language.

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

Each plan comes 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 choose the class settings that decide what is collected from students and for how long. Sections 4 to 8 bind only the instructor.

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, and a student is never asked for a payment method. Sections 9 to 14 bind a student as well as the instructor. They cover GitHub, AI-generated feedback, student 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 the 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, and your class keeps working until the end of the period you have paid for. A declined card does not interrupt a period you have paid for: we retry a failed payment before anything changes.

When a subscription ends, the repositories the product created stay 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. 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. It is counted across every class on the subscription, including the classes of every instructor who shares it. 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 go over your plan's cap, we move you 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. Only a graded run that calls for an explanation counts against it: a run where every test passed does not, and neither does an assignment worth no points. Past the allowance, feedback keeps working and the extra runs are metered and added to your next invoice, at the rate on the pricing page. We do not cap or throttle grading runs. The only limits on them are any resubmission limit you set on an assignment, and your own GitHub Actions allowance, since the grading workflow runs in your organization.

One exception applies 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 more than explaining a failed test. Without a working key of your own, those assignments report an error instead of a mark.

6. Payments, Pricing and Tax

Prices are listed in US dollars (USD). Payments are processed by Stripe as our Merchant of Record. At checkout, Stripe Tax adds the VAT or sales tax of your country to the listed price, and pays it to the tax authority. Stripe may show the price in your local currency; settlement is in USD. By subscribing, you authorize Stripe and us to charge your payment method 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 keeps your access until the end of the period you have paid for.

If we get something wrong on our side, write to us. We would rather fix a billing mistake than point to this section.

If we discontinue Classroom, we will tell you by email and refund the unused part of the period you have paid for. The separate Refund Policy covers only the self-paced courses sold before July 8, 2026. It does not apply 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 from 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, not a one-off supply of digital content. Its free trial also lasts 14 days, so if you withdraw within that time you owe nothing, because nothing has been charged.

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. Do not install it on an organization you do not own or administer.

The App is granted permission 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 for each student, add students and teaching assistants as collaborators, commit the grading workflow, read results and post feedback.

The App writes only to the repositories it created for your classes, with two exceptions, both on your own starter repository. If the starter is not marked as a template, the assignment page offers to mark it for you. The same page offers to replace an out-of-date grading workflow in 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 these terms. GitHub's availability, its Actions allowances and its handling of your repositories are between you and GitHub. An instructor may remove the App from their organization at any time, which ends all of the access described above.

10. AI-Generated Feedback Is Not a Grade

Some of what the product writes is produced by a language model, for example the explanation of why a test failed and the review of the changes on a branch where every test passed. All of it is AI-generated, and all of it can be wrong. It 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 give the mark that counts. Instructors may hold AI-generated feedback for review before students see it. A student who thinks 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. It is not 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 none 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 in its session shell, and upload it to the instructor when work is pushed. To find secrets to remove, it also reads project config files such as .env and replaces the values it finds there. The CLI asks for the student's agreement first, and says what it collects and how it is redacted. Secrets and personal data are removed before anyone can read the record.

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

The Privacy Policy sets out how we collect, use, share and delete personal data, and how to opt out of analytics and session recording. 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: if a student asks us to access or delete their class data, we will refer them to you.

12. Acceptable Use

Instructors and students alike agree not to:

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

Instructors are responsible for their roster 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 other content are our intellectual property. A subscription grants a non-exclusive, non-transferable right to use the product while the subscription lasts, 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 "as is". 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 any outcome, 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. Changes to These Terms

We may update these terms. We will announce material changes to instructors by email, or with a notice on the website, before they take effect. Using the service after a change takes effect means you accept the revised terms. Each version shows its effective date at the top of this page. Email us if you need a copy of an earlier version.

16. Governing Law

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

17. Contact Us

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