Whitepaper
2.0 ENG
2.0 ENG
  • Welcome To dKargo
    • Vision
    • dKargo 2.0: Transitioning to a New Environment
      • dKargo 1.0 vs dKargo 2.0
      • Suitability for Logistics
  • dKargo Platform
    • dKargo Protocol
    • dKargo Network
      • Rollup
      • Node Operation
    • Ecosystem
      • dOptim: Maximizing Logistics Efficiency and Productivity
      • Data Lab: Enhancing Logistics Data and Creating Added Value
      • dHub : DAO and Community
    • Governance
      • Governance Committee
      • Process
      • Implementation and Monitoring
  • tokenomics
    • DKA Token
    • Token Distribution
    • Circulation Plan
  • dkargo's horizon
    • Expectations
    • Roadmap
  • about us
    • Community
    • Brand Kit
    • FAQ
  • Disclosure
    • Compliance
    • Disclaimer
Powered by GitBook
On this page
  • Data Protection and Privacy Policy
  • Anti-Money Laundering (AML) and Know Your Customer (KYC)
  1. Disclosure

Compliance

Data Protection and Privacy Policy

While the decentralized and transparent nature of blockchain technology inherently records all transactions publicly, dKargo is committed to enhancing privacy protection. Personal information or sensitive data is not recorded directly on the blockchain; instead, it is stored in the form of hashed values or encrypted data for protection. Additionally, dKargo implements regular network audits and has a monitoring system in place to identify and resolve data protection issues, ensuring the ongoing safeguarding of privacy.

Anti-Money Laundering (AML) and Know Your Customer (KYC)

To foster a secure and trustworthy ecosystem, dKargo follows a series of legal and regulatory measures. The platform monitors transactions on the blockchain network to prevent the laundering of illicitly obtained funds, identifying and reporting abnormal or suspicious activities. Furthermore, to prevent malicious actions by users, dKargo conducts identity verification using documents such as identification cards, passports, driver’s licenses, and utility bills when necessary.

PreviousFAQNextDisclaimer

Last updated 8 months ago