Student code of conduct

You are paying for guidance, and you should expect to get it. This code is about the other half of that — what makes the guidance work, and the few things that will cost you your account.

It sits alongside our community guidelines, which apply to everyone, and our terms of service.

1. The work has to be yours

Your mentor will teach you, review what you build and tell you where it breaks. They will not build it for you, and asking them to is the one thing that ends an account fastest.

• Do not ask a mentor to write your project, code, report or dissertation.
• Do not ask a mentor to attend an examination, viva or interview in your place.
• Do not submit anything you could not explain, line by line, if you were asked.
• Check your own institution's academic integrity rules before you start. They vary, and only you can check them.

Getting help and getting someone else to do it are different things, and every institution knows the difference. So does every examiner.

2. Engage in good faith

• Describe your project honestly in the brief — your real deadline, your real budget, and what you can actually already do.
• Turn up to sessions you have booked, or cancel with reasonable notice.
• Do the work between sessions. A mentor cannot review what does not exist.
• Reply within a reasonable time. A project stalls when one side goes quiet.
• Raise problems early. Something wrong in week one is fixable; the same thing in week three often is not.

3. Treat your mentor as a professional

• Your mentor is a working professional giving you their time, not a service that owes you availability at any hour.
• Keep it respectful, particularly when you disagree about the work.
• No romantic or sexual advances, comments or content. This is a professional relationship.
• Do not ask your mentor for their personal contact details, or to continue off-platform.

4. Scope changes

Projects grow. That is normal, and your mentor will usually accommodate a reasonable amount of it. What is not reasonable is expanding the brief substantially after the price is agreed and expecting the same fee to cover it. Agree the change in the workspace and adjust the scope properly.

5. Payment and approval

• Pay through the platform. A mentor who suggests otherwise is breaching their own code — tell us.
• Review delivered work within the window shown in your workspace and either approve it or raise a dispute. Approval releases payment.
• Do not withhold approval as leverage for extra work outside the agreed scope.
• Do not raise a dispute over work that was delivered as agreed. Disputes are for genuine failures of delivery.

6. Reviews

• Review the mentorship you actually received. An honest three-star review is more useful to everyone than a polite five.
• Do not threaten a bad review to extract extra work, a discount or a refund.
• Do not review your own project through another account, or ask anyone else to.
• Grades and marks are awarded by your institution, not your mentor. Do not rate a mentor on an outcome they do not control.

7. Confidentiality and content

• Do not record or publish a session without your mentor's consent.
• Do not redistribute teaching material your mentor produced for you.
• Only upload material you have the right to share. Do not upload someone else's code, dataset or documents without permission.

8. If you breach this code

Depending on severity and history: a warning, suspension, or permanent removal. Asking a mentor to produce work for you to submit as your own, and any form of harassment, lead to immediate permanent removal — and where the work was submitted, we will respond truthfully if your institution asks us about it.

Money genuinely owed back to you is still refunded. We do not use this code as a reason to keep it.

9. Questions and appeals

Unsure whether something is allowed? Ask first: contactmentorbuild@gmail.com. To appeal a decision, email contactnavatrix@gmail.com within 30 days.