Communication and Language
Section 14 Communication and Language
14.1. Communication Standard
DeltaGrid adopts a technical and transparent communication standard, with standardized terminology to ensure clarity and consistency:
| Principle | Description |
|---|---|
| Standardized language | All official communication follows approved technical terminology. |
| Prohibition of promises | Any promise of results, gains or profitability is expressly prohibited. |
| Consistency | All communications — official, from partners and from ambassadors — follow the same standards. |
| Technical UX | Interface presents technical language, not emotional. No APY, no expected gains. |
14.2. Nature of the Operation
DeltaGrid performs a swap of assets. The user swaps USDT for dgUSD and proceeds to use a decentralized software protocol that executes technical market operations. There is no credit relationship or obligation of return.
14.3. Correct Operational Flow
The operational flow of the protocol must be described exclusively as follows:
- The participant allocates USDT in the smart contract and receives dgUSD 1:1 as a tokenized receipt in their wallet.
- The participant selects the operational profile (Conservative, Moderate or Aggressive).
- Upon approval, an individual smart contract automatically executes the technical mechanisms according to the chosen profile.
- Market fees may or may not be generated, depending on market conditions. Results may be positive, negative or zero.
- The participant may stop the contract at any time. At the end of the period, they swap dgUSD for USDT ± operational result, subject to fees, liquidity and market conditions.
IMPORTANT NOTICE
There is no obligation of return. There is no promise of equivalence. There is no credit relationship between the user and the protocol.
14.4. Mandatory Language
All official communication must exclusively use the approved terminology:
| Approved Term | Usage Context |
|---|---|
| swap | Description of the USDT ↔ dgUSD operation |
| participation | User's relationship with the protocol |
| liquidity provision | Technical function of the protocol: provision of liquidity in markets |
| operational allocation | Positioning of assets in the technical mechanisms |
| position in the system | User's state within the protocol |
| protocol usage | Interaction with the system's functionalities |
| software credit | dgUSD's function as an access unit |
| technical operations | Automated mechanisms of the protocol |
| market fees | Revenue source of the protocol |
14.5. Language Not Used by the Protocol
The protocol does not use the following terms in any official communication, as they do not reflect the nature of the operation:
| Term Not Used | Reason |
|---|---|
| lend / loan | The protocol does not perform credit operations |
| borrow | There is no debt relationship |
| return / refund | There is no contractual obligation of return |
| interest / yield | The protocol does not generate guaranteed or expected results |
| creditor / debtor | There is no credit relationship |
| guaranteed results | The protocol does not make financial promises |
| fixed income / passive income | The protocol is not a financial product |
| X% per month / guaranteed profit | Results are variable and without guarantee |
| safe / risk-free | All participation involves risks |
| financial application | The protocol is software infrastructure |
| multiply your money | No results are guaranteed |