codevii — Legal drafts

DRAFT — pending legal and business approval. These proposed terms are not final and do not replace existing rights from previous purchases.

v0.3

Company & contact · support@codevii.com

# Terms specification — platform and purchases

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

## Existing technical behaviour

Connection and a login signature are not payment. A purchase is confirmed by a separate BNB transaction on BNB Smart Chain. The catalogue displays package prices in USD; the order quotation determines the BNB amount and the wallet displays the network fee. Package pricing is not $VIIX pricing.

The current catalogue contains Basic $7.77, Plus $77.70, Pro $177.70, Elite $377.70 and Ultra $777. Special 7,777 is not purchasable. Existing BNB referral percentages do not determine future Airdrop weights.

After a confirmed purchase, the interface provides package records, referral functions and a personal code. The code does not establish final Airdrop eligibility or any token amount. Eligibility rules: TBD.

## Planned Airdrop

Phase 1 includes a planned $VIIX Airdrop. The pool, eligibility, weights, formula, rounding and remainder handling must be approved before distribution. The token is not issued; its price and the monetary value of distribution are undefined. No fixed token amount, monetary return, redemption or exchange for BNB/USD is promised.

# Privacy Policy specification

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

## Observed data flows

Local code processes wallet addresses, one-time challenges and signatures for login; orders, packages, BNB amounts, exchange rates, hashes and confirmations for purchase records; and referral relationships and rewards. Profiles may contain a nickname and email. Public blockchain data does not establish the absence of personal data.

Production requests to Google Fonts, Reown APIs, Reown fonts and a Pulse WalletConnect beacon were observed before connection. AppKit localStorage keys were also found. See the audit report.

In local code, the challenge cookie lasts 5 minutes and user sessions last 30 days with renewal; other records, logs, backups and archives have TBD retention periods. These technical TTLs are not an approved retention policy.

## Pending approval

TBD: controller/processor roles; purpose-specific legal bases and necessity; required fields; applicable rights and request procedures; age; markets; final retention/deletion periods; providers and agreements; international transfers, regions and safeguards; DPO where needed; incidents and notifications; effective date and final wording.

Administrative archiving is not deletion. Blockchain persistence does not justify indefinite retention of the entire database. Provider names must not be presented as proof of executed agreements or data localisation.

When you contact support by email, your email address and the information you include are used to handle your request.

Policy preparation contact: support@codevii.com. Private keys and seed phrases are not requested. The public site currently contains only a short temporary notice, not a complete Privacy Policy.
# Refund and cancellation specification

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

Proposed refund mechanism — pending legal and business approval. The periods and percentages below are proposals, not approved policy.

A participant may request a refund if CODEVII:

- fails to pay an eligible referral reward within 24 hours after the participant becomes entitled to that payment under the referral programme rules; or
- fails to distribute the participant’s allocated $VIIX tokens within the deadline specified in the project terms following the end of Phase 1.

Referral payments are processed automatically. The maximum payment processing period is 24 hours. If payment has not been made within that period, the participant may submit a refund request.

**Refund Amount**

If the participant has not received any referral rewards or tokens associated with the relevant package, the refund will equal **100% of the amount paid for that package**.

If the participant has already received any such rewards or tokens, the refund will equal **80% of the amount paid for that package**. Previously received rewards or tokens will not be deducted further from this refund amount.

The refund is calculated using the package’s USD value recorded in the confirmed order at the time of payment.

**Refund Currency and Exchange Rate**

Refunds are paid in BNB on BNB Smart Chain.

The amount of BNB is calculated as follows:

**Refund in BNB = package amount paid in USD × applicable refund percentage ÷ USD price of one BNB.**

The exchange rate is obtained from **[exchange-rate source]** and recorded at **[time of exchange-rate determination]**. The amount of BNB refunded may differ from the amount of BNB originally paid.

CODEVII pays the network transaction fee for sending the refund. This fee is not deducted from the calculated refund amount.

**How to Request a Refund and Processing Deadlines**

Refund requests must be sent to **support@codevii.com** and include the order number, payment transaction hash, and details of the unfulfilled obligation.

Requests are reviewed within **30 calendar days of receipt**. The participant will be notified of the outcome by email.

If the participant is eligible for a refund, payment will be made within **30 calendar days of approval of the request**.

The total period for reviewing the request and issuing the refund will not exceed **60 calendar days from receipt of the request**, unless applicable law requires a shorter period.

This policy does not limit any rights the participant has under applicable law.

---
# Referral programme — technical specification

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

Legal admission, markets, age and eligibility: TBD. The table below describes existing BNB code, not legal approval of the offer or Airdrop weights. Phase 2 $VIIX reward parameters require separate approval.

## 1. Participation and invitations

After a confirmed purchase, a participant receives a personal referral link. A purchaser may follow that link or enter the link/code in the invitation field before payment. The server verifies the code and records a permissible relationship. Self-referrals and cycles are prohibited. [TO BE AGREED: the precise point when the relationship becomes final, correction of an incorrect code and competing invitations.]

## 2. Levels and rates

| Recipient’s package | G1 | G2 | G3 | G4 | G5 |
|---|---:|---:|---:|---:|---:|
| Basic $7.77 | 25% | — | — | — | — |
| Plus $77.70 | 25% | 15% | — | — | — |
| Pro $177.70 | 25% | 15% | 10% | — | — |
| Elite $377.70 | 25% | 15% | 10% | 10% | — |
| Ultra $777.00 | 25% | 15% | 10% | 10% | 10% |

G1 is a direct invitee, G2 is someone invited by your invitee, and so on. Depth depends on the recipient’s package; the reward base is the amount of the relevant confirmed purchase in their chain.

Diagram: participant A ← invitee B (G1) ← C (G2) ← D (G3) ← E (G4) ← F (G5). When F purchases, F is E’s G1, D’s G2, C’s G3, B’s G4 and A’s G5. Each receives only the rate for their generation if entitled to that level.

## 3. Calculation and payment

Phase 1 rewards are calculated in BNB: confirmed order amount in wei × rate / 100, rounded down to a whole wei. Example: with a base of 0.01 BNB, the first-generation reward is 0.0025 BNB. USD displayed on screen is a monetary equivalent, not a fixed obligation to pay that dollar amount regardless of exchange-rate changes.

The calculation is made upon purchase confirmation, taking account of the recipient’s status and available depth. In the current code, an unavailable reward is not passed up to another participant; the corresponding amount remains with the project. Before publication, the operator must approve this rule and counsel must review it.

[TO BE AGREED and displayed to participants: reward delay, minimum payout, limits, fees, checks and manual-review deadlines.] Automatic payouts may technically be queued and delayed. The absence of an established maximum delay must not be concealed by a promise of immediate payment.

## 4. Upgrades, Special and refunds

A higher package increases depth for subsequent events. Past rewards are not automatically recalculated. The verified code includes Special 7,777 with seven levels: 25%, 15%, 10%, 10%, 10%, 5%, 5%. It is not a sixth purchasable package. [TO BE AGREED: separate grant and qualification criteria, effects of refunds/archiving and availability of automatic qualification.]

Handling cancelled purchases and commissions already paid requires a separately agreed rule; an undisclosed debt must not be imposed retrospectively on a participant.

## 5. Fair promotion

Participants disclose their interest in earning rewards and accurately describe reward conditions, token status and confirmed project information. Spam, false reviews and concealment of material terms are prohibited. Referral rewards depend on eligible confirmed purchases and programme rules.

## 6. Phase 2

The operator plans to retain referral links and move to rewards in $VIIX. [TO BE AGREED: commencement, exchange rate, formula, token, rounding, vesting, minimums and fees.] Existing BNB obligations are not deemed automatically converted into tokens. The new scheme must be disclosed before purchases governed by it.

## Legal prerequisite to publication

This programme requires review of its economic substance: payouts are actually funded from package purchase proceeds. Documents and a future game do not rule out classification as a prohibited scheme. Until counsel provides an opinion, these rules do not confirm the programme’s permissibility.
# $VIIX Airdrop — mechanism

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

## Status

Phase 1 includes a planned $VIIX Airdrop. The token has not been issued and final tokenomics are unapproved. A predetermined Airdrop Pool is intended to be distributed among participants meeting final eligibility rules. Owning a code or purchasing a package does not establish final eligibility. Eligibility rules remain pending approval.

## Weight / points

Proposed factors include the purchased package, upgrades, invited referrals’ number and/or activity, and other criteria approved before the Airdrop. A higher package and additional activity may increase weight, but coefficients and rules remain undefined. No invented points accrue.

A candidate for future implementation is User Allocation = Airdrop Pool × User Weight / Total Weight of all eligible participants. This is a design principle, not an approved formula or a calculation of current entitlement. No $VIIX amount is currently determined. Token price is unnecessary for this allocation and is not inserted into the formula.

## TBD parameters

Total Supply; token decimals; Community Allocation; Airdrop Pool; Sponsor/Marketing Allocation; Liquidity Allocation; Team Allocation; Treasury Allocation; bucket relationships/overlap; eligibility rules; package weights; referral weights; final formula; upgrades and cancelled purchases; snapshot; rounding; remainder handling; zero Total Weight; delivery, claim, vesting and fees.

Official price P and its approved source: TBD. Token valuation is separate from package prices and referral activity. Exchange, redemption and any BNB/USD refund terms remain pending approval and publication.

## Interface

Actual packages, referral activity and “eligibility rules pending approval” status may be shown. Eligibility, points, tokens and USD value are not replaced with zero or displayed as approved. Points may appear only after the model is approved and implemented.
# $VIIX — status and risk-disclosure preparation

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

$VIIX has not been issued. Network, contract, issuer, supply, allocation structure, price P, administrator powers, transfer restrictions and listings are TBD.

Token allocation, valuation, exchange and redemption terms remain pending final published token documentation. USD/BNB package purchases do not establish a $VIIX price.

Following classification, the final document must disclose actual development, security, wallet-access, liquidity, market-price, holder-rights and third-party risks. Audits, reserves, licences, partnerships or listings must not be claimed without evidence.

Offer classification, required documents, markets and permissible marketing are TBD. Disclaimers do not waive existing mandatory user rights.

# Cookies and browser storage

> Version 0.3, 23 September 2026. DRAFT — pending legal and business approval; not final terms.

Operator: OLTRADING LTD.
Email: support@codevii.com.

## Observed in production

Initial navigation to https://codevii.com and opening the wallet selector were checked in isolated Chromium without connecting, signing or paying. No cookies were found in these scenarios. This does not establish absence of cookies after login or on all devices.

Detailed keys and resources are in sanitised audit JSON; storage values, pairing URIs and tokens were not exported.

Local AppKit sets analytics:false, but the library permits INITIALIZE and CONNECT_SUCCESS independently of that flag. This is consistent with the observed beacon; its full payload was not retained in this audit. “No tracking” cannot be asserted.

## Consent and limitations

Provider locations, retention, international transfers, authenticated flows and  settings were not verified by this browser test.