Quorin Technologies · Archon
Acceptable Use Policy
A short list, because you run Archon on your own hardware and we are not in a position to police what you do with it — nor do we wish to be.
- Effective
- 9 August 2026
- Last updated
- 9 August 2026
Draft — not yet in force
This document is missing details that only Quorin Technologies can supply, and it has not been reviewed by a qualified lawyer in Zimbabwe. Do not rely on it, and do not present it to a customer, until both are done.
Outstanding
- · Full registered company name
- · Company registration number
- · Registered office address
Edit src/lib/legal/company.ts. This banner disappears by itself once nothing is outstanding.
1. What this policy is for
We cannot see inside your deployment, and this policy does not pretend otherwise. It is not a content moderation regime. It sets out the small number of things that would breach your licence, almost all of which concern the integrity of the licensing and audit mechanisms rather than what you record.
2. Licence integrity
You must not:
- Modify, patch, disable or work around licence verification or entitlement checks in order to use capabilities you have not licensed.
- Forge or alter a licence key, or attempt to.
- Use a licence key issued to a different organisation, or share your key outside the organisation it names.
- Redeem a pilot code on behalf of an organisation other than your own, or attempt to redeem more than one pilot code for the same laboratory.
Where a licence covers a stated number of sites, running additional sites on it is a breach.
3. Record integrity
Archon’s central claim is that its records are tamper-evident. That claim is worth something only if it is not undermined deliberately. You must not:
- Alter, delete or reorder audit trail entries directly in the database, or otherwise bypass the audit hash chain.
- Apply an electronic signature as, or on behalf of, another person, or share credentials so that signatures cannot be attributed to an individual.
- Backdate, alter or reconstruct finalised records outside the amendment mechanisms Archon provides.
- Represent records to an accreditation body, regulator, funder or customer as having been produced under controls that were in fact disabled or bypassed.
The last of these is the one that matters most. If a laboratory does this, the damage lands on the credibility of every laboratory that did not.
4. Misuse of the software
You must not use Archon to:
- Break the law that applies to you, or to help someone else do so.
- Infringe intellectual property or breach confidentiality obligations you owe to a third party.
- Store or process personal data without a lawful basis, or in breach of your obligations to the people concerned.
- Attack, probe or gain unauthorised access to systems that are not yours, including by configuring outbound webhooks or integrations to do so.
- Distribute malware, or use an Archon deployment as infrastructure for unrelated activity.
5. Resale and hosting for others
You may run Archon for your own laboratory or group of laboratories under your licence. You may not offer it to third parties as a hosted, managed or white-labelled service without a written agreement with us. Multi-site and network arrangements are what the Network tier exists for — talk to quorinstartup@proton.me.
6. Security research
We welcome vulnerability reports. Test against your own deployment, not against ours or anyone else’s, and report what you find to quorinstartup@proton.me. We will not pursue anyone who acts in good faith, gives us reasonable time to fix an issue, and does not access or destroy data belonging to others. See our Security Statement.
7. Enforcement
Where we become aware of a breach, our remedies are the ones available to a software licensor: we may suspend support, decline to renew, revoke a licence key, or terminate under the Terms of Service. We will normally raise the issue with you first and give you a chance to put it right.
We will not disable your deployment or take away your records. We have no remote kill switch and will not build one. A revoked licence returns the laboratory to the Free tier; the records stay where they are, fully readable, on your server.
8. Contact
Questions about this policy: quorinstartup@proton.me.