Terms of Service

1. Acceptance of These Terms

By using the Coder in 90 website, setting up an institution on Coder in 90 Classroom, teaching on it, 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 three roles. An institution is the school, university, bootcamp, company or other organization that pays for its students' places. An instructor is someone who runs classes, including a teaching assistant or coach. A student is someone who joins one of those classes. Section 3 says which sections bind whom.

2. What Coder in 90 Sells

The product is Coder in 90 Classroom, software that runs coding assignments on GitHub. For each student, or each team on a team assignment, it creates a repository from the instructor's 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.

Instructors use Classroom free. Creating classes, publishing assignments and seeing results cost nothing.

The institution pays per student. It pays a fee for each student it gives an active place in its classes, by the month or by the year. Current prices are on the pricing page. Other terms, such as a price per semester, are arranged by email and confirmed in writing.

Students never pay. A student is never asked for a payment method.

3. Institutions, Instructors and Students

The institution is the paying customer. Its admins hold the billing relationship with us, decide which students get a place, invite its instructors and choose the classes it runs. Sections 4 to 8 bind only the institution. A person who sets up an institution accepts these terms on its behalf and confirms they may do so.

An instructor is a user, not a customer. They decide who is on a class roster, own or administer the GitHub organization the class runs in, and choose the class settings that decide what is collected from students and for how long.

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. Sections 9 to 14 bind every role. 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 they use.

4. Places and Billing Periods

An institution pays for active places only. A place is active from the moment an admin gives it to a student until the admin takes it back. Only a student with an active place can reach a class the institution pays for.

The institution chooses a monthly or yearly billing period, which renews automatically until it ends it. A place given part way through a period is charged for the rest of that period. A place taken back stays usable until the end of the period already paid for, and is not refunded.

We check each institution that sets itself up before its places open, usually within one working day. Nothing is charged before then.

To end a subscription, take back every place or email hello@coderin90.com. When places end, the repositories the product created stay in the class's own GitHub organization. They belong to the institution, its instructors and its students, and we do not delete, archive or transfer them. What ends is the use of 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, first.

Anyone who subscribed to a per-instructor plan before November 7, 2026 keeps it on the terms they agreed to until they cancel it.

5. AI Usage

A place includes AI-generated feedback on the student's graded runs. We do not cap or throttle grading runs. The only limits on them are any resubmission limit an instructor sets on an assignment, and the GitHub Actions allowance of the organization the class runs in, since the grading workflow runs there.

One exception applies. An assignment marked by an AI judge against a rubric the instructor wrote runs on the instructor's or institution's own AI provider key, because judging a whole working session costs many times more than explaining a failed test. Without a working key, those assignments report an error instead of a mark.

6. Payments, Pricing and Tax

Prices are listed in euros, or in US dollars for institutions in the United States, and VAT or sales tax is added where it applies. Payments are processed by Stripe. An institution pays by card or SEPA direct debit, charged at the start of each period, or by invoice and bank transfer. By choosing card or direct debit, the institution authorizes Stripe and us to charge that payment method each period for its active places.

An invoice is due by the date it shows. If it stays unpaid 14 days past that date, the institution's students lose access to its classes until it is paid. Their work and repositories are not affected.

7. Refunds

A period that has started is not refunded pro rata, including for a place taken back part way through it.

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 every institution by email and refund the unused part of the period it has paid for. The separate Refund Policy covers only the self-paced courses sold before July 8, 2026. It does not apply to Classroom.

8. EU Consumers and the Right of Withdrawal

Classroom is sold to institutions, which are businesses and not consumers, so this section does not apply to them. If you buy places as a consumer resident in the European Union, you have a 14-day right of withdrawal under the EU Consumer Rights Directive (Directive 2011/83/EU), and we do not ask you to waive it.

To withdraw, email hello@coderin90.com within 14 days of your first purchase. We refund what you paid, less a fair share for the days the places were already in use at your request. 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. Using Classroom, free as an instructor or on a paid place as a student, grants a non-exclusive, non-transferable right to use the product while that use 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 institution paid us in the twelve months before the claim. For an instructor or 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 institutions and 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.