Home/Trust centre
Trust centre
Documents, governance and compliance
Every controlled document carries a version, a language, a publication date and a status. A document that has been superseded stays visible and is marked as superseded rather than quietly replaced.
Document centre
Controlled documents
| Document | Type | Version | Status |
|---|---|---|---|
| White paper | Token | — | In legal review |
| Litepaper | Token | — | Drafting |
| Smart-contract audit report | Assurance | — | Not commissioned |
| Offering terms | Legal | — | Not drafted |
| Revenue-share package terms | Legal | — | Not drafted |
| Holding plan terms | Legal | — | Not drafted |
| Privacy policy | Legal | Draft | Published as draft |
| Terms of use | Legal | Draft | Published as draft |
| Risk disclosure | Legal | Draft | Published as draft |
Governance
Who decides what
High-risk changes require more than one pair of eyes. Price, supply, sale activation, allocations, contract addresses, administrative keys and production feature flags all need separation of duties or dual approval.
| Decision | Control |
|---|---|
| Sale price, supply, dates and caps | Dual approval before publication |
| Enabling a regulated feature | Audited administrator action, written approval on file |
| Identity decisions | Reason code, reviewer, timestamp and evidence version recorded |
| Refunds above threshold | Separation of duties |
| Contract address publication | After deployment, audit and verification only |
| Content publication | Factual owner, legal approver, version and publish date |
Compliance
The approach, stated plainly
Security and compliance are treated as product requirements rather than a launch-week checklist. These are the commitments the platform is being built against.
Risk-based, per market
One global identity rule is not sufficient. Requirements are set market by market and screened against sanctions and politically-exposed-person lists where required.
Data minimisation
Only necessary personal data is collected, the reason is explained at collection, and retention and deletion obligations are defined.
No credential storage
Payment credentials, private keys and seed phrases are never stored in the platform, and are never requested by it.
Independent audit
Any token, vesting, sale, treasury or claim contract is independently audited before deployment, with the report published alongside the address.
Tamper-evident audit trail
Identity decisions, offering changes, transactions and administrative actions produce audit events that cannot be edited after the fact.
Disabled by default
Regulated functions ship switched off. Turning one on requires recorded approval and cannot be done through ordinary content editing.
Scope boundaries
What this website is not
Five limits the platform is built against. They are published rather than kept internal, because most of them are the reason something a visitor might expect to find is deliberately absent.
The public site can launch on its own
The marketing website may go live independently of any token-sale functionality. It does not wait on the offering, and the offering does not ride on it.
No fabricated live metrics
A countdown, an amount raised, a participant count or a token price must be driven by approved live data. None of them may ever be invented for visual effect.
An interface is not an authorisation
A website does not replace legal authorisation, regulated custody, payment licensing, an audited token contract or a compliant identity and anti-money-laundering programme.
Regulated features stay off until the gates are cleared
Investment, revenue-sharing and real-asset features remain disabled by configuration until the legal and operational launch gates are complete.
Controlled sources only
The white paper, token contract address, audit report and corporate data must come from versioned, approval-controlled sources.
System states
Every record has a state, and every state is auditable
A thing is never simply “done”. Each entity below moves through a defined set of states, so that a record’s position can be evidenced rather than asserted.
| Entity | Required states |
|---|---|
| Content | Draft, factual review, legal review, approved, scheduled, published, archived |
| Identity | Not started, submitted, pending, information required, approved, rejected, expired |
| Offering | Draft, review, scheduled, open, paused, closed, cancelled |
| Payment | Created, pending, authorised, settled, failed, expired, refunded, chargeback |
| Allocation | Pending, approved, allocated, locked, claimable, transferred, reversed |
| Plan or package | Draft, offered, accepted, active, matured, closed, cancelled |
| Support | Open, assigned, waiting on user, waiting internally, resolved, closed |
Standardised assumptions
Corrections carried into this build
The source material contained figures that contradicted each other. Rather than pick silently, each correction is recorded here with the page where the standardised figure now appears.
| Item | Standardised position | Where it appears |
|---|---|---|
| Scope | Standardised as a proposed 65-page responsive platform, including dedicated photo and video galleries. | See the 65-page inventory |
| ICO allocation | 100,000,000 AKT, equal to 20% of the proposed maximum supply of 500,000,000 AKT. The remaining 400,000,000 AKT is the ecosystem reserve. | See tokenomics |
| Round 4 price | Standardised at USD 5 per AKT. At the stated quantities, the maximum capital across all four fully subscribed rounds is USD 390,000,000. | See the rounds |
| Monthly releases | Growth-plan releases are calculated from the original token purchase and remain subject to approved programme terms; they are not cash returns or guarantees of market value. | See the growth plans |
| Open decisions | Blockchain, jurisdiction, token classification, vesting schedules, accepted payment methods, refund rules and restricted territories are marked for approval rather than invented. | See what is undecided |
| Prohibited claims | “World’s first”, “exclusive”, “asset-backed” and “guaranteed” are not published unless legally cleared and factually substantiated. | — |
| Distribution chart | A dynamic chart is required. This build renders it from the accessible data table in the page, so the figures cannot drift apart, and adds no charting dependency. | See the chart |
Press
Press kit
Brand assets, verified facts and the media contact will be published as a single downloadable kit once the corporate record is confirmed.
Press kit not yet available
[Approved brand assets and fact sheet required.] Journalists can request specific facts directly in the meantime, and every figure supplied will carry its source and as-of date.