Terms
IsotopeAI is MIT-licensed software you run yourself. There is no service, no account with us, and no contract for us to breach — but a few things are still worth stating plainly.
Last updated 2026-08-28
Not legal adviceThis page describes the practical position in plain language. It is not drafted by a lawyer. If you need enforceable terms for a deployment serving other people, have a solicitor review them against your jurisdiction.
What you are agreeing to #
By using, copying or modifying IsotopeAI you accept the MIT License. That is the operative legal document — everything below is explanation, not additional terms.
The MIT License grants you, free of charge, the right to use, copy, modify, merge, publish, distribute, sublicense and sell copies, on one condition: the copyright notice and licence text must travel with any substantial portion of the software.
There is no service #
This is the part that makes most conventional terms inapplicable. IsotopeAI has no hosted backend. The software runs on your hardware and connects to a Supabase project you create and pay for, if anything.
| Consequence | Detail |
|---|---|
| No uptime commitment | There is nothing for us to keep online. Availability is a property of your machine and your Supabase project. |
| No account with us | You never register with the project. Authentication is between you and Supabase. |
| No data processing by us | We never receive your data, so we are not a processor or controller of it. |
| No support obligation | Issues and pull requests are welcome and answered when possible, on a best-effort basis. |
| No termination | We cannot revoke your access. You have the source. |
No warranty #
The MIT License states this in capitals, and it is meant literally: the software is provided as is, without warranty of any kind — express or implied — including merchantability, fitness for a particular purpose and non-infringement.
In practice that means you are responsible for your own backups. The software includes a verified backup tool and conflict-resolution designed so real data cannot be overwritten by an empty snapshot, but no software is defect-free. Keep independent copies of anything you cannot afford to lose.
Take a backup before anything irreversible./backup.sh backup produces a checksummed tarball that is verified against the source project. Do this before a restore, a migration or a schema change.
Limitation of liability #
To the extent permitted by applicable law, the authors and copyright holders are not liable for any claim, damages or other liability arising from the software or its use — including lost data, lost study progress, or loss of any kind.
Some jurisdictions do not allow the exclusion of certain warranties or liabilities. Where that is the case, the exclusions above apply only to the extent permitted, and your statutory rights are unaffected.
Your responsibilities as operator #
Running your own install makes you the operator. That carries obligations we cannot discharge for you.
- Credentials. Keep
SUPABASE_SERVICE_ROLE_KEY,SUPABASE_ACCESS_TOKENandADMIN_SECRETprivate. The service key bypasses row-level security entirely. - Exposure. The server binds
0.0.0.0so other devices on your network can reach it. If you expose it further, securing it is your responsibility. See Security. - Other people’s data. If you invite others to your install, you become responsible for their data under whatever law applies to you.
- Third-party terms. Your use of Supabase is governed by your agreement with Supabase. The same applies to any AI provider whose key you supply.
- Applicable law. Comply with the law where you are. We cannot advise on that.
Acceptable use #
Because the MIT License imposes no use restrictions, we have no mechanism to enforce a policy — and inventing one we cannot enforce would be dishonest. What follows is a request, not a term.
- Do not present a modified copy as the official project.
- Do not use the name or mark in a way that implies endorsement.
- If you invite others to an install you operate, tell them who holds their data.
Contributions #
Contributions submitted for inclusion are licensed under the same MIT terms as the project, without additional conditions. There is no separate contributor licence agreement. See Contributing.
Name and mark #
The MIT License covers the code, not the name. You may state that your work is based on or derived from IsotopeAI. Please do not use the name or logo in a way that suggests the project endorses or maintains your fork.
Changes #
This page lives in the repository beside the code, so its history is the git history. There is no mailing list and no account, therefore no notification mechanism — check the changelog if it matters to you.
Contact #
Questions, corrections and disputes: open an issue at github.com/Suydev/isotope-code/issues. For a suspected vulnerability, use GitHub’s private reporting rather than a public issue.