Acceptable use
What you may do on this public site, and what you must not do.
Last updated: 2026-10-21.
Scope
This page applies to a-rex.pages.dev and to early-access requests. It is not a customer contract. The steward named in the standard is the A-REX Foundation, a name in the governance, not a registered legal entity. See Terms.
The site sets no cookies and runs no analytics. The colour theme and the language stay in the browser. The privacy policy states what the site collects when you request early access. This page adds no processor, no residency rule, and no data-processing agreement.
What you may do
You may read the published pages.
You may use published specification text under CC0-1.0.
You may use a published reference implementation under the MIT licence.
You may send an early-access request for evaluation, implementation, and feedback, using your own details.
You may report a vulnerability in the specification or the reference implementation by the path in Terms.
Early access
Request early access for evaluation, implementation, and feedback. The programme is for companies and professionals. The privacy policy states that the site does not knowingly collect data from people under 18.
Give accurate contact details. Do not send another person's details as if they were yours. Do not present a request as an order, a purchase, or the acceptance of a service.
Material from the private repositories stays confidential until that material is published. Do not publish it. Early access grants no exclusivity and no conformance status.
What you must not do
Do not use this site to:
- break, overload, or bypass the site, the early-access form, or a private repository you were not given;
- take access you were not given, other than a vulnerability report sent as Terms describe;
- send malware, or send unsolicited bulk messages through the form;
- collect other people's requests or contact details from the site;
- impersonate the Foundation, a maintainer, or another reader;
- publish material from a private repository;
- claim an affiliation with the standard or with a maintainer that you do not have.
The maintainers may decline an early-access request that breaks these rules. This page states no indemnity and no damages amount.
Prohibited statements
Do not describe A-REX Core as an ERC. It is draft 2.1.0-alpha.2. It is not yet an ERC.
Do not describe the specification, the reference implementation, or the documented platform as audited. An external audit is not done. The platform security model states that no mainnet release can be marked audited until that audit exists.
Do not say that mainnet is offered. Mainnet is not offered.
Do not describe the token, the standard, or the documented platform as a financial instrument, a security, a means of payment, an investment, or a product that pays yield.
Do not write "1 token = 1 tonne", or "1 token = 1 t", as a statement of title. Do not write that the token is backed by the goods, that it can be redeemed for the goods, or that it is collateral.
The phrase "A-REX Core conformant" follows the standard's implementer criteria. This site does not sell a certification. Do not sell one in the name of the Foundation.
Do not present the legal research as a lawyer's opinion or as a regulator's decision. Terms mark inferences as inferences.
The token in your own materials
If you implement the draft, or if you describe it, keep the token a traceability record. Terms states the words the research says a future contract must use. Those words are not yet a contract.
Do not describe the token as title, as a pledge, as a warehouse receipt, or as a Brazilian rural product note (CPR), certificate of agricultural deposit (CDA), or agricultural warrant. Do not describe it as the official register of any of those instruments.
Sanctions screening
The specification publishes no sanctions list. This site publishes none.
An eligibility check or a sanctions check in an implementation is that implementer's list. Do not call it an A-REX list, an A-REX screen, or a decision of the Foundation.
The legal research mentions screening of future tenants against public sanctions lists as a recommended practice, in the case where a later operator is not a VASP. That sentence is an inference. It is not a list, not a screening service, and not a contract.
Personal data
Do not place personal data in a field the specification keeps off the chain. Do not ask this site to publish a person's name, tax identifier, or precise location as a public ledger record.
Contact
Questions about these pages: seanluis47@gmail.com.