Terms & Conditions Permanent Unique Cryptographic ID Acceptance TrustDAG Technologies Foundation #1811582-6 Canadian Not-for-Profit organization Version 1.1 Effective date for review: July 31, 2026
1. Purpose of this section
This Terms & Conditions section explains the condition attached to verified access in the TrustDAG ecosystem: TrustDAG creates and maintains one permanent unique cryptographic ID for each approved participant. The ID supports verified ecosystem access, the Fair Trust System, wallet binding, DAO eligibility, DDRS eligibility, staking eligibility, operator eligibility, launchpad activity, faucet abuse prevention, and other safety rules.
This section is written in plain language. It does not replace the full Terms & Conditions of the website or any agreement signed by operators, developers, partners, donors, or service providers. It defines the acceptance needed before a participant receives verified ecosystem access.
2. What the cryptographic ID is
The permanent unique cryptographic ID is an ecosystem reference created for TrustDAG safety and accountability. It is not a legal identity document, not a public profile, not a passport record, not a government ID record, and not a biometric record.
The ID links verified access, wallet-binding status, ecosystem eligibility, and behavior-based trust events to one persistent TrustDAG reference. It helps prevent repeated account resets, disposable identities, abuse cycles, trust-score farming, coordinated manipulation, and attempts to escape prior harmful conduct.
The ID is permanent because TrustDAG cannot protect verified participants if harmful activity can be erased by abandoning one identity and returning through another clean identity.
3. What the cryptographic ID is not
The cryptographic ID does not contain raw personal information. It does not contain a legal name, home address, date of birth, government ID number, identity document, biometric file, KYC file, KYB file, AML file, PEP screening file, or private contact record.
TrustDAG does not place personal verification data on-chain, in the backend ecosystem, in the Explorer, in the Fair Trust System, in DAO records, in DDRS records, in staking records, in operator records, in launchpad records, or in faucet records.
Selected third-party verification providers handle personal verification information, including KYC, KYB, AML, restricted-region screening, and PEP screening where applicable. TrustDAG receives limited verification outcomes and provider-authenticated references needed for verified access. The raw personal file remains with the selected provider.
4. Acceptance for verified ecosystem access
By completing the verified ecosystem access procedure, the participant accepts that TrustDAG creates, uses, and keeps a permanent unique cryptographic ID for ecosystem safety. The ID supports access control, Fair Trust System scoring, score and sub-score history, wallet binding, abuse prevention, eligibility checks, sanctions, suspensions, bans, and public aggregate reporting where applicable.
The participant also accepts that the ID cannot be reset, erased, replaced, or recreated simply to remove prior ecosystem behavior. A request to stop participating disables or restricts access instead of rewriting historical protocol records.
This acceptance applies to ecosystem features that require verified access. Public website reading does not require this ID.
5. Right to refuse and effect of refusal
A person or organization can refuse the creation of the permanent unique cryptographic ID by not entering the verified ecosystem access process or by stopping before acceptance is completed.
Refusal has a direct consequence. TrustDAG Technologies Foundation will automatically decline access to the TrustDAG ecosystem for anyone who refuses the cryptographic ID requirement, no exception. This includes access to features that depend on verified participation, including the purchase of the native coin on verified CEX, wallet binding, Fair Trust System eligibility, DAO eligibility, DDRS eligibility, staking eligibility, operator eligibility, launchpad eligibility, faucet access, and any other verified ecosystem feature.
TrustDAG applies this rule because verified access and the Fair Trust System cannot function if participants can avoid a permanent accountable reference.
6. PEP screening and compliance outcomes
PEP screening is part of the selected third-party verification process where applicable. PEP screening can include screening for politically exposed persons, heads of international organizations, and related or closely associated persons according to the provider process and applicable law.
A PEP status by itself is not a statement of wrongdoing. It is a compliance-screening category that can require additional review, risk treatment, or eligibility decisioning.
TrustDAG does not receive raw PEP reports, source databases, identity documents, biometric records, KYC files, KYB files, or raw AML files. TrustDAG receives limited provider-authenticated compliance outcomes or eligibility results needed for verified ecosystem access.
7. Privacy and worldwide compliance position
The cryptographic ID is designed to support accountability without collecting or exposing personal information. TrustDAG does not need raw personal information to create or use the ID. The ID is derived from verification outcomes, provider-authenticated references, wallet-binding status, and ecosystem behavior signals.
This structure supports the privacy principle of data minimization. TrustDAG keeps raw personal verification files outside the chain and outside the backend ecosystem. The selected third-party verification provider manages those files under its own verification process and privacy notice.
TrustDAG uses the minimum derived information needed to decide whether verified access is allowed, whether a wallet can be bound, whether an account remains eligible, and whether a trust or compliance event affects ecosystem access.
8. Fair Trust System connection
FTS means Fair Trust System. It is composed of a main score and sub-scores. The Fair Trust System uses the permanent cryptographic ID to connect behavior-based trust events to one stable ecosystem reference.
The Fair Trust System does not require public personal information. It works from verified-access status, cryptographic reference, wallet-binding status, ecosystem actions, dispute outcomes, staking eligibility, operator behavior, and other permitted protocol events.
The ID makes trust portable inside the TrustDAG ecosystem while keeping raw personal identity information outside public views and outside the hardcoded protocol features.
9. Post-quantum security design
TrustDAG is designed to align critical security paths with NIST-standardized post-quantum cryptography where those controls are implemented.
ML-KEM-1024 protects communication paths that require post-quantum key establishment. ML-DSA-87 protects high-value signing workflows, including DAO voting and Treasury multisig voting where post-quantum digital signatures are required. SLH-DSA acts as a stateless hash-based fallback signing family.
This security design protects communication and signing paths. It does not place personal information on-chain and does not convert raw personal information into ecosystem data.
10. Limits, restrictions, and forbidden uses
Participants agree not to create or attempt to create duplicate verified identities, evade a prior trust record, farm scores, manipulate sub-scores, bypass wallet-binding rules, use another person or organization as a false front, or interfere with third-party verification.
TrustDAG can deny access, suspend access, restrict access, or permanently remove access when abuse, fraud, evasion, manipulation, false information, restricted-region access, sanctioned activity, criminal activity, security abuse, or harmful conduct is detected or confirmed.
No DAO vote, private agreement, operator action, developer action, website feature, or support request can override the permanent cryptographic ID rule where verified ecosystem access is required.
11. No investment advice and digital-asset risk
TrustDAG content is informational only and is not investment, financial, legal, tax, or trading advice. Digital assets involve risk. No profit, yield, liquidity, exchange listing, resale value, or future access is guaranteed.
Access to TrustDAG ecosystem features can be staged, limited, paused, restricted by jurisdiction, restricted by compliance status, restricted by security events, or unavailable during testing and development. Participation decisions remain the responsibility of the participant.
12. Contact
General contact: contact@trustdag.com Support: support@trustdag.com Security reports: security@trustdag.com