D-Wallet Document Center

1. Understanding D-Wallet

D-Wallet is a self-custodial wallet tool that provides four account-management models in one app. Each model uses different signing or approval rules.

2. Before You Begin

• Use only an official trusted download or website, and verify the domain, HTTPS status, and installation source.
• Prepare independent wallet addresses, devices, and backup locations. Do not keep multiple signing credentials together.
• Confirm the network, asset contract address, and sufficient funds for Gas fees.
• Record the account address, signers, M/N threshold, protocol version, and compatible-tool information offline.
• Never give a private key, seed phrase, or guardian passphrase to a website, app, or support representative.

3. Creating an Account

1. Choose the account mode and connect the wallets you intend to use.
2. Verify the network and every wallet address.
3. Configure signers, the M/N threshold, roles, limits, and approval rules as required.
4. Review the complete account rules and receiving address before confirming creation.
5. Transfer only low-value assets first and test proposal creation, signing, execution, and compatible access.

4. Transactions

1. The proposer enters the network, asset, amount, receiving address, and any contract action.
2. Each signer independently verifies the token contract, approval scope, recipient, amount, Gas, and signature progress.
3. Execute only after the required threshold or approval conditions are satisfied. Completed signatures do not necessarily mean the transaction is on-chain.
4. Save the transaction hash and verify the final status in a trusted block explorer.

5. Continued Access

Multisig accounts remain on-chain if the D-Wallet app or website stops operating. Continued access may be possible when users hold valid credentials, satisfy the original threshold, the network is available, and a compatible tool supports the same protocol, configuration, and contract version.

6. Routine Checklist

• Confirm transaction hashes and on-chain status, and review signers, thresholds, roles, and limits.
• Keep devices, backups, and recovery information separate, and check for unknown approvals or proposals.
• Perform periodic low-value recovery exercises for important accounts.

7. Fees

Blockchain Gas fees are charged by the underlying network. Product subscriptions, account limits, and export charges are governed by the latest version published on the official website.

1. Components

• Guardian Sign account: the on-chain multisig account that holds the assets.
• Signer wallets: independently held wallets that confirm multisig transactions.
• Administrator wallet: the wallet connected during creation, which may act under the confirmed guardian-passphrase rules.
• Guardian passphrase: created and stored by the user. D-Wallet does not collect, hold, or reset it.

2. Independent Recovery Paths

3. Common Configurations

A personal 2/3 setup can use one administrator wallet for daily activity and two independent signer wallets. A family setup can choose M/N according to membership, independent custody ability, and its management process.

4. Creation and Testing

1. Add signer wallets, choose 2/2 or a higher M/N configuration, and verify every address.
2. Set the guardian passphrase and confirm the receiving address and execution conditions.
3. Record the account address, signers, threshold, protocol version, and compatible tools.
4. Test both passphrase recovery and multisig execution with low-value assets.

5. Compatible Tools

Another tool may identify and operate an account only when it supports the same protocol, account configuration, and contract version. Access still requires valid credentials, enough signatures, and an available network.

6. Troubleshooting

1. Verify the network, account address, compatible-tool version, signer credentials, and original threshold.
2. Check whether signing is complete but the transaction has not been broadcast.
3. Check Gas, Nonce, congestion, node status, and third-party services.
4. Never submit a seed phrase, private key, or guardian passphrase while seeking help.

7. Security Boundaries

• Guardian Sign does not replace credential and device backups.
• Keeping signer wallets on one device or cloud backup weakens distributed control.
• The two recovery paths follow separate rules and cannot bypass one another.
• Smart contracts, networks, compatible tools, and user configuration can all introduce risk.

Frequently Asked Questions

Does D-Wallet hold my assets?

No. Assets remain in on-chain accounts controlled by user-held credentials, signers, M/N thresholds, and permission rules.

Does D-Wallet collect or reset private credentials?

No. Users create and store their own private keys, seed phrases, and guardian passphrases. D-Wallet does not hold or reset them.

Is Guardian Sign a 1/2 multisig setup?

No. Guardian Sign uses at least 2/2 multisig. Guardian-passphrase recovery is a separate execution path, not a reduced multisig threshold.

What does M/N mean?

N is the total number of signers and M is the number of valid confirmations required for execution. A 2/3 account requires at least two of three signers.

Why is a transaction still pending?

Possible causes include insufficient signatures, no broadcast, low Gas, a Nonce conflict, congestion, or node problems. Signing and on-chain execution are separate stages.

Can I access an account without D-Wallet?

Potentially, when you hold valid credentials, satisfy the original rules, and use a compatible tool supporting the same protocol, configuration, and contract version.

Is multisig absolutely secure?

No. It reduces single-point risk, but misconfiguration, simultaneous compromise, or collective approval of an incorrect transaction can still cause losses.

Can one person hold multiple signer wallets?

Technically yes, but it weakens distributed control. Signer accounts, devices, and backups should remain independent.

How is Enterprise Sign different from Multisig?

Enterprise Sign adds roles, membership changes, approvals, budgets, limits, freezes, and activity records to fixed-signer M/N multisig.

Who charges Gas fees?

Gas is charged by the underlying blockchain network, not by D-Wallet as a custody fee.

What if a balance appears incorrect?

Verify the network, wallet address, token contract, and a trusted block explorer. Interface data may be delayed.

What if a device or credential may be compromised?

Stop signing and connecting new DApps. On a trusted device, inspect proposals and approvals, then move remaining assets through a verified safe path.

Can support recover my seed phrase?

No. A self-custodial wallet cannot recover a lost credential for the user. Anyone claiming otherwise and asking for credentials is not trustworthy.

Before Contacting Support

• Prepare the public wallet address, network, transaction hash, time, app version, device version, screenshots, and reproduction steps.
• Never send a private key, seed phrase, guardian passphrase, or unredacted sensitive information.

1. Credential Protection

• Keep private keys, seed phrases, and guardian passphrases offline. Never upload them to cloud storage, chats, or online forms.
• Each signer should use an independent account, device, and backup location.
• Do not save seed phrases as screenshots or enter complete credentials on an unfamiliar device.

2. Device and Network Security

• Keep operating systems, wallets, and browsers updated from trusted sources.
• Use dedicated devices for important signatures and avoid untrusted apps, extensions, and public Wi-Fi.
• Enable device locks and disk encryption, but do not treat a device password as a seed-phrase backup.

3. Before Signing

• Verify the network, chain ID, asset, token contract, recipient, amount, Gas, and approval scope.
• Check for contract calls, unlimited approvals, membership changes, threshold changes, and the final executing wallet.

4. Configuration Security

• A threshold that is too low weakens protection; one that is too high may block transactions when signers are unavailable.
• High-privilege roles should not be concentrated in one person or device.
• Review membership, thresholds, roles, allowlists, budgets, and limits more strictly than routine payments.

5. Emergency Response

1. Stop signing and connecting new DApps, and ask other signers to pause approvals.
2. On a clean trusted device, inspect public addresses, pending proposals, recent transactions, and token approvals.
3. If a safe signing path remains, move assets to a newly created and verified account under the established rules.
4. Revoke suspicious approvals, activate any established enterprise freeze, and suspend high-risk roles or workflows.
5. Preserve transaction hashes, addresses, domains, screenshots, and timestamps, and report the incident where appropriate.

6. Incident Guidance

7. Routine Reviews

• Review signers, roles, thresholds, budgets, limits, and backups at least quarterly.
• Periodically test proposal, signing, execution, and compatible access with low-value assets.
• Remove former members, unused devices, and unnecessary token approvals promptly.

1. Acceptance

By visiting the website, downloading or using D-Wallet, connecting a wallet, proposing a transaction, signing, or using another feature, you acknowledge these Terms and the referenced Privacy Policy, Cookie Policy, and Risk Disclosure. If you do not agree, stop using the service.

2. Product Nature

D-Wallet is a self-custodial wallet and on-chain account-management tool. It is not a bank, custodian, broker, exchange, investment adviser, or fiduciary asset manager. D-Wallet does not hold user assets or guarantee investment returns, preservation of value, or transaction success.

3. Eligibility

You must have legal capacity to enter a binding agreement and use the service in compliance with applicable law. Persons prohibited by sanctions, embargoes, jurisdictional restrictions, or other law may not use it.

4. Self-Custody and Responsibility

Users create and safeguard their own private keys, seed phrases, guardian passphrases, device passwords, and signing credentials. Users are responsible for verifying networks, assets, recipients, amounts, approvals, contract actions, signers, thresholds, and account rules.

5. Transactions and Fees

Digital-asset transactions are generally irreversible. D-Wallet cannot cancel a broadcast transaction or guarantee confirmation time. Gas and other on-chain costs are charged by the underlying network or third parties.

6. Public Protocols and Third Parties

Third-party wallets, block explorers, nodes, DApps, tokens, smart contracts, and compatible tools are independently provided. Mention of a third-party tool is not an endorsement or security guarantee.

7. Service Changes

D-Wallet may modify, suspend, or discontinue interface features for maintenance, security, legal, or product reasons. This does not automatically delete on-chain accounts or change existing signing rules.

8. Prohibited Conduct

Do not use the service for unlawful transactions, fraud, money laundering, sanctions evasion, terrorist financing, attacks, malicious code, infringement, impersonation, disruption, unauthorized access, or assistance with such conduct.

9. Intellectual Property

Rights in D-Wallet trademarks, interface, documentation, code, and content belong to their respective owners. Open-source components remain subject to their licenses. Do not copy, sell, impersonate, or misleadingly use the brand without permission.

10. Risks and Disclaimers

Digital assets, self-custody, multisig, smart contracts, and blockchain networks involve inherent risks. The service is provided “as is” and “as available.” D-Wallet does not provide investment, legal, tax, or accounting advice.

11. Liability

To the maximum extent permitted by law, the service provider is not liable for indirect, incidental, special, or punitive damages, loss of data, expected profits, market losses, or third-party conduct. Nothing excludes liability that cannot legally be excluded.

12. Suspension, Termination, and Updates

Users may stop using the service at any time. Hosted features may be limited in response to unlawful activity, attacks, security threats, or serious violations. These Terms may be updated as the product, law, or operations change.

1. Scope

Asia DAO Alliance Limited ("D-Wallet," "we," "us") respects your privacy. This Policy explains how we process personal data when you use the D-Wallet Android application, website, and related online services.

D-Wallet is a self-custodial wallet and does not create a conventional server-side user account for ordinary wallet users. During normal wallet creation, import, and transaction signing, seed phrases and private keys are generated and encrypted on your device. We do not ask you to upload seed phrases, private keys, keystore files, wallet passwords, or recovery secrets to our servers, and we do not store them in readable plaintext. Never disclose those credentials to anyone, including anyone claiming to represent D-Wallet.

This Policy covers processing for which we determine the purposes and means. Public blockchains, DApps, WalletConnect peers, RPC nodes, swap or bridge providers, and other services you choose may process data independently under their own policies.

2. Data We Process

We process the categories below only as relevant to the features you use.

2.1 Data processed locally on your device

• Seed phrases, private keys, wallet-password verification values, and local key material;
• Wallet names, address labels, derivation paths, network settings, token lists, DApp sessions, and preferences;
• Local caches of transactions, swaps, multisig activity, budgets, permissions, guardians, and audit records;
• The result of Android biometric authentication. D-Wallet does not receive or store your biometric template;
• Camera frames used to recognize QR codes on-device. D-Wallet does not upload complete camera frames merely because you use QR scanning.

This data is generally stored in the operating-system application sandbox, encrypted database, or Android Keystore. It may leave the device when you choose to export, back up, paste, capture, connect to a third party, or send it to support.

2.2 Wallet and blockchain data

• Wallet and account addresses, chains, assets, tokens, NFTs, balances, and public contract information;
• Transaction hashes, amounts, sender and recipient addresses, gas, timestamps, status, approvals, and contract interactions;

We do not provide server-side synchronization of ordinary wallet records and do not store your wallet name, seed phrase, private key, or local wallet database on our servers. When you query balances, obtain quotes, connect to a DApp, or broadcast a transaction, RPC, market-data, swap, bridge, or public blockchain services process the wallet addresses, chains, tokens, amounts, transaction parameters, and IP addresses needed to complete the request.

Wallet addresses and blockchain data are often public or pseudonymous, but may still be linked to a person when combined with other information.

2.3 Multisig, guardian, and organization data

When you use relevant connected features, we may process multisig IDs, signer addresses, roles, permissions, thresholds, invitations, proposal titles and descriptions, creator and target addresses, amounts, chains, confirmations, rejections and reasons, deadlines, transaction hashes, guardian and recovery status, budgets, approval workflows, membership, security audit events, and subscription or service-order details such as plan, billing period, payment chain, token, amount, status, and transaction hash.

Multisig audit records may be retained by our Hong Kong backend for three years to support collaboration traceability, security investigations, and dispute resolution. At the end of that period, we delete or anonymize them unless law requires continued retention or the record has been written to a public blockchain. Organizations providing member data to D-Wallet are responsible for having an appropriate lawful basis and providing required notices.

2.4 Device, network, and region data

• IP address and an approximate country or region inferred from it;
• Device model, operating system and version, app version, language, time zone, and network status;
• Access timestamps, request status, app version, operating system, network status, security events, and anti-abuse signals.

Region-check providers may receive your IP address and basic request information to determine service availability or apply regional restrictions.

The production version does not enable Firebase Analytics, Firebase Crashlytics, push notifications, advertising, or advertising attribution, and does not collect Firebase installation IDs, advertising IDs, app-interaction analytics, or crash reports for those purposes. If we enable any such function in the future, we will update this Policy first and provide any notice or consent choice required by law.

2.5 Data you provide

If you contact support or submit feedback, a complaint, or a security report, we may process your email address, messages, screenshots, wallet address, transaction hash, and diagnostic material you choose to provide. Never send a seed phrase, private key, wallet password, or recovery secret.

3. Device Permissions

D-Wallet does not currently request precise location, contacts, SMS, or microphone permission.

4. Purposes and Legal Bases

We process data to create, import, display, and manage wallets; query assets and construct, sign, simulate, or broadcast transactions; provide multisig, guardian, invitation, approval, budget, and audit features; provide swaps, bridges, prices, DApps, or WalletConnect connections; assess region eligibility and prevent fraud, attacks, abuse, and unauthorized access; respond to support and disputes; and comply with law and lawful requests.

Depending on applicable law, our legal bases may include performance of a contract, steps you request before a contract, compliance with legal obligations, protection of vital interests, our legitimate interests, and your consent. Withdrawal of consent does not affect prior lawful processing.

5. Disclosure and Sharing

We do not sell seed phrases or private keys, and selling personal data is not our primary business model. We may disclose necessary data to:

• Infrastructure and security providers: Hosting, content-delivery, and security providers supporting our Hong Kong backend;
• Region providers: Cloudflare, ipwho.is, FreeIPAPI, or similar providers that may receive IP address and request data;
• Blockchain infrastructure: Ankr, dRPC, other RPC nodes, block explorers, and public blockchain networks that may receive IP addresses, wallet addresses, and blockchain requests;
• Price, swap, and bridge providers: CoinGecko, ParaSwap, and providers you select, which may receive token, chain, amount, wallet-address, and transaction parameters;
• Connections you initiate: DApps, WalletConnect peers, contracts, or other third parties;
• Collaborators: Administrators, proposers, signers, approvers, guardians, and auditors in your multisig or organization;
• Advisers and authorities: Lawyers, auditors, regulators, courts, or law-enforcement bodies where legally required or necessary to protect users, the service, or legal rights;
• Corporate-transaction recipients: A buyer, investor, or successor in a merger, acquisition, financing, reorganization, or asset transfer, subject to appropriate safeguards.

Some providers act on our instructions; others determine their own processing purposes. Their terms and privacy policies apply to their independent processing.

6. Public Blockchains

When you broadcast a transaction or interact with a smart contract, wallet addresses, recipient addresses, amounts, transaction hashes, and contract parameters may become permanently public. Anyone may copy or analyze them and attempt to link them to a real-world identity. D-Wallet does not control public blockchains and generally cannot correct, erase, or hide confirmed on-chain records. Do not put personal information you wish to keep private into transaction notes, NFT metadata, or contract parameters.

7. Retention and Deletion

• Local wallet data remains until you delete the wallet in the app, clear app data, or uninstall. Securely back up required recovery material before deletion;
• We do not retain ordinary wallet-synchronization data;
• Multisig audit records are retained for three years and then deleted or anonymized, unless law requires continued retention or the record is on a public blockchain;
• Access and security logs are retained for three years and then deleted or anonymized, unless a security incident, dispute, or law requires continued retention;
• Support communications are retained as needed to resolve the request and satisfy legal or dispute requirements;
• Public blockchain data is retained by the relevant network and is outside D-Wallet's control.

You can delete a local wallet in the app, or delete other local data by clearing app data or uninstalling the app. D-Wallet does not create a conventional server-side user account, so there is no separate web account-deletion page. To exercise rights concerning multisig audit records or access and security logs, contact us at dwalletsafe@gmail.com. We may ask you to demonstrate the relevant wallet or collaboration relationship and will apply the three-year periods above and applicable law. Public blockchain records cannot be deleted by us.

8. Security

We use measures appropriate to risk, including application sandboxing, encrypted databases, Android Keystore, transport encryption, access controls, logging, and backup restrictions. Android performs biometric matching. No system can be completely secure; download D-Wallet only from official channels, keep your device updated, use a device lock, and safeguard seed phrases and private keys independently.

Where required by law, we will notify affected users and regulators of a personal-data incident.

9. International Processing

We, our infrastructure providers, RPC nodes, and blockchain participants may be located outside your country. Where required, we use contractual clauses, adequacy decisions, risk assessments, consent, or other lawful safeguards. Public blockchain data propagates to independent nodes worldwide, whose locations and further processing we do not control.

10. Your Rights and Choices

Depending on your location, you may have rights to access, correct, delete, restrict or object to processing, obtain a copy, portability, withdraw consent, and complain to a regulator. You may also disable camera or biometric access in system settings; disconnect DApps, WalletConnect, or custom RPCs; delete a wallet or clear local data; and contact dwalletsafe@gmail.com about multisig audit records or access and security logs we control.

We may require a wallet signature or other reasonable verification to prevent unauthorized requests. Rights may be limited by blockchain immutability, other people's rights, and legal-retention duties.

11. Children

D-Wallet is not directed to anyone under 18 or below the age of legal majority where they live. We do not knowingly collect children's personal data. If we learn that such data was collected, we will delete or restrict it where legally and technically feasible.

12. Changes

We may update this Policy when our product, technology, providers, or legal obligations change. We will provide notice of material changes through the app, website, or another reasonable method and obtain consent again where required. The date above identifies the latest version.

13. Contact

Data controller: Asia DAO Alliance Limited
Registered address: Level 24, The Lee Garden One, 33 Hysan Avenue, Causeway Bay, Hong Kong, China
Privacy email: dwalletsafe@gmail.com

We will respond within the period required by applicable law. You may also complain to the competent data-protection authority where you live.

14. Key Third-Party Privacy Information

• Google Privacy Policy: https://policies.google.com/privacy
• Cloudflare Privacy Policy: https://www.cloudflare.com/privacypolicy/
• Ankr Privacy Policy: https://www.ankr.com/docs/privacy/

For any RPC, DApp, swap, bridge, or blockchain service you select, review the policy presented by that provider or on its official website.

1. Self-Custody and Transaction Risk

Loss, exposure, or damage involving a private key, seed phrase, guardian passphrase, or device may allow assets to be transferred or make them inaccessible. An incorrect network, address, token contract, amount, approval, or contract call can cause irreversible losses.

2. Multisig and Guardian Sign Risk

A low threshold weakens distributed control; a high threshold may block transactions. Concentrating credentials recreates a single point of failure. Passphrase exposure, incorrect addresses, insufficient signers, or untested conditions can affect Guardian Sign safety and access.

3. Enterprise Governance Risk

Incorrect roles, thresholds, budgets, limits, freezes, or approval flows may permit insufficiently authorized transactions or prevent valid ones. Technology cannot replace organizational judgment.

4. Smart-Contract and Compatibility Risk

Contracts may contain defects, vulnerabilities, upgrade risks, compatibility issues, or dependencies. Another tool may work only if it supports the same protocol, account configuration, and contract version, and may itself contain errors or malicious code.

5. Network, Device, and Phishing Risk

Congestion, forks, node failures, Nonce conflicts, insufficient Gas, and outages may affect transactions. Malicious sites, counterfeit apps, extensions, remote-control software, clipboard replacement, and social engineering may cause credential loss or malicious signatures.

6. Asset, Market, Legal, and Tax Risk

Digital assets may fluctuate sharply or fall to zero and may carry liquidity, issuer, de-pegging, freeze, blacklist, upgrade, or fraud risk. Rules vary by region and may change; users are responsible for applicable sanctions, reporting, and tax obligations.

7. Third-Party and Continuity Risk

Outages or attacks involving nodes, RPC services, block explorers, download channels, operating systems, app stores, or other services may affect use. D-Wallet discontinuation does not delete on-chain accounts, but continued access is not guaranteed under every condition.

8. Displayed Information and No Guarantee

Balances, prices, signature status, and transaction status may be delayed or inaccurate. D-Wallet does not provide investment advice or promise returns, capital protection, absolute security, continuous availability, or fitness for a particular purpose.

Risk-Reduction Measures

• Use trusted software and independent devices for signer credentials.
• Test every execution and recovery path with low-value assets first.
• Verify networks, addresses, amounts, contract actions, permissions, signers, and thresholds before signing.
• Regularly review signers, roles, limits, backups, and compatible tools.
• Never submit a private key, seed phrase, or guardian passphrase to a website, app, or support representative.

1. Cookies and Similar Technologies

Cookies are small data files stored by a website in a browser. Local storage, session storage, and similar technologies may remember preferences, maintain security state, or measure website use after consent.

2. Categories

3. Website Storage

4. Information Not Collected

D-Wallet does not use Cookies or analytics tools to collect private keys, seed phrases, or guardian passphrases.

5. User Choices

• Users may allow anonymous analytics or enable only necessary functionality when a choice is presented.
• Users may update Cookie choices through available settings or delete and block Cookies in the browser.
• Blocking Cookies may prevent some preferences or basic functions from being saved.

6. Third Parties and Retention

Hosting, CDN, analytics, or security providers may process identifiers under their own terms. Session technologies expire with the browser session; persistent technologies remain until expiration or deletion.

7. Updates

This Policy will be updated if new analytics, advertising tools, third-party SDKs, or purposes are introduced. Consent will be requested again where required.