Educator-Only Policy

1. Why educator-only

A plagiarism checker that students can use stops being a checker. It becomes a way to test work against detection and change it until it passes. Every student who can run a check weakens the result for the instructor who relies on it.

So we made a choice: Codequiry serves the people who assess code, not the people whose code is assessed. That is what educator-first means. Educator-only is how we hold the line: we refuse accounts we cannot tie to a real member of teaching or academic staff, and we close any account that turns out to be used by a student.

2. Who may hold an account

An account belongs to the person who opened it and the institution they opened it for. Credentials are personal and may not be shared, including with colleagues (Terms, Section 2).

3. How we verify

Verification happens at the start of sign-up, before an email code is sent and before any payment step. An applicant who does not pass never sees a price.

1. A faculty email on the institution's own domain. Personal addresses are refused, and so are addresses that look like student, alumni or alias mailboxes.
2. A faculty or staff page on the same domain. The page must name you with a teaching or staff role and belong to the address you signed up with. Self-written homepages do not count.
3. A professional profile. A LinkedIn profile is required, and it has to agree with the rest.
4. A one-time code and a signed statement. You confirm the emailed code, then certify that you are faculty or staff opening the account for your institution and that everything you entered is accurate.
5. Payment from the institution. Plans are annual and paid by bank transfer from the institution. The account stays locked until the transfer clears.

Verification does not end at sign-up. We may ask for proof of your role or your institution at any time, and we may treat an account as student use on reasonable grounds, such as the email address, the code uploaded or the way the account is used (Terms, Section 1.3). An account that does not answer a verification request is suspended until it does.

4. Students and Codequiry

A student's only contact with Codequiry is handing in coursework through a submission link their instructor provides. Submitting through that link does not create an account and gives the student no access to the platform, to checks or to results.

The instructor decides what a result means. Codequiry reports similarity and where it came from. A person reviews that evidence under their own institution's policy, gives the student a fair chance to respond, and makes the decision. A result is never the only basis for a penalty (Terms, Section 7).

Student work is handled as an education record. We use it only to provide the service to the institution that submitted it and never to advertise to anyone (Terms, Section 14.3).

5. Acceptable use

A verified account may use Codequiry to:

• check submissions for similarity within a class, across past terms and against public sources such as GitHub, Stack Overflow and the web;
• identify AI-generated code in programming coursework;
• review a match with a student, a colleague or an academic integrity panel;
• connect the institution's learning platform, or the API, to automate checks for its own courses;
• keep records of checks the institution has run, under its own retention rules.

6. What is not allowed

Each of these is a breach of this policy and of the Terms (Section 4):

• opening, buying or using an account as a student, or for yourself as an individual;
• checking your own work, or work that will be handed in for a grade, credit or assessment;
• giving a student access to an account, a result, a report or an API key;
• using Codequiry to help any work get past a plagiarism or AI check, or to test whether it will be flagged;
• misstating your name, role or institution, or signing up with someone else's details;
• sharing credentials, reselling access, or opening extra accounts to get around a limit or a block;
• reverse engineering, scraping or probing the detection methods;
• uploading code you have no right to submit.

7. Enforcement

We monitor accounts to keep this policy true. When we find a breach we act without waiting for a complaint, and we do not need to warn first.

The account

Closed immediately, with every key and integration revoked.

The person

Blocked permanently. Email addresses, IP addresses, devices and payment details linked to the account are refused at every future sign-up (Terms, Section 12).

The money

Nothing paid on the account is refunded, whether or not a check was ever run (Refund Policy).

False statements

The certification at sign-up is a statement of fact. Giving false information is fraud, and we may report it to the institution named and to the authorities.

Getting around a block

A new email, device, VPN or payment method used to return is a further breach and is treated as fraud.

8. Organizations outside education

New accounts are open only to verified university and college faculty and staff. Organizations outside education that already hold an account keep it under the Terms. Commercial use, such as hiring, contracting or paid training, is allowed only on an active Defense plan (Terms, Section 3). The rest of this policy applies to them in full: no student may use their account, and no one may use it to check their own work.

9. Reporting misuse

If you believe a student, or anyone else not allowed here, is using Codequiry, tell us through the contact page. Include the name or address you suspect and why. We look at every report, and we do not tell the account holder who sent it.

10. Changes to this policy

We may tighten this policy as we learn how people try to get around it. The date at the top shows the latest version. Continuing to use Codequiry after a change means you accept it. Where a change affects active subscribers materially, we tell them by email first.