terms
Experimental, and provided as is.
CopperOS is a hobby operating system. It has no warranty of any kind, express or implied, including fitness for a particular purpose. It can crash, hang, and write to whatever disk you point it at. The authors are not liable for data loss, hardware damage, or anything else that follows from running it.
Run it in a virtual machine. If you install it on physical hardware, you are accepting that a kernel with no filesystem safeguards has been given control of a real disk, and that this is entirely your decision.
Open source.
The source is public and licensed under the terms in the repository's LICENSE file, which is the authoritative version. Nothing on this page overrides it.
What the site keeps.
- Your cookie answer. Whether you accepted or declined, which optional categories you allowed, and when — so the choice can be honoured and counted. Every cookie is listed here.
- Discussion accounts. A username, a hashed passcode, and the country the sign-up came from. Posts are public to anyone who opens the page.
- Support messages. What you typed, your name and email, plus your account name if you were signed in.
- Salted one-way hashes of address and browser, used only to rate-limit failed admin logins and to bind an admin session to one browser. The address itself is not stored against your consent record.
No advertising, no third-party trackers, nothing sold or shared. You can delete your discussion account and its posts yourself from Manage my account.
Conduct.
The discussion board is lightly moderated and posts are automatically screened. A post that trips the filter is flagged and the account is suspended for fifteen minutes. Administrators can remove posts and accounts. Keep it civil, keep it about CopperOS, and do not post anything you would not want attached to a public page indefinitely.
If your post did not publish and you do not know why, that case is explained here.
These terms can change.
CopperOS is a moving project, so this page will occasionally move with it. Material changes will be noted on the roadmap rather than made quietly.