MDCAndroid DEMODEMO / TEST ONLY
Privacy policy
An offline interface demo, with clear limits on what it does and how information is handled.
This policy covers the Android DEMO and its download and privacy pages.
- Responsible team
- Dapp developer team
- Privacy contact
- contact@mdctoken.org
- App / package
- MDC Wallet DEMO
com.mdc.wallet.demo.internaldemo - Covered version
- 0.1.0-demo / versionCode 1
- Last updated
- November 2, 2026
- Effective date
- November 2, 2026
1. What this policy covers
This policy covers the reviewed MDC Wallet Android DEMO candidate and the MDC Android download and privacy pages. Dapp developer team is the responsible team and the contact for these practices.
It does not describe a future production wallet, native security laboratory builds, the web wallet, faucet, swaps or other blockchain services. Those services need their own review and disclosures.
The DEMO uses mock data. It cannot create, import or recover a real wallet, store private keys, hold assets, sign transactions or broadcast them. Never enter a real recovery phrase or private key, or send funds to demo information.
2. Information in the offline app
The app displays preset fictional balances, history and an intentionally invalid demo receive identifier. Amount and recipient edits, navigation, theme selection and security-preview switches are used locally for interface simulation. Real recipient addresses are rejected by the simulated send flow.
These interactions use runtime state in the reviewed code. No developer server account or real wallet database is configured. We do not promise that interface state will persist after the app restarts.
The inspected APK requests no Android permissions, including INTERNET, storage, camera, microphone or biometric permissions. No developer-controlled advertising, analytics or remote crash-reporting service is configured in the reviewed DEMO. It does not connect to a public blockchain.
The app, its React Native / Expo components and Android may create caches, compiled files and ordinary runtime records. The absence of requested permissions does not mean zero local storage. Android, device vendors, keyboards and system diagnostics may process information under their own settings and policies.
4. Download pages and hosting services
The reviewed download and privacy pages contain no analytics scripts, advertising, forms, third-party fonts or page code that sets cookies or browser storage. Clicking an email link opens your chosen email application; it does not silently send an email.
The MDC website is served through GitHub Pages. GitHub logs visitors' IP addresses for security purposes, including visits without a GitHub account. When you follow a GitHub source or Release link, GitHub processes information under its own privacy policy.
Website and service providers may process browser, connection and access-log information. Their infrastructure practices are separate from this offline APK. An offline app is not a promise of anonymous web browsing.
See GitHub Pages data collection and the GitHub Privacy Statement.
5. Support email
If you email contact@mdctoken.org, your email address, message, attachments and normal email metadata are processed to respond to your request and handle related privacy or security issues. Send only what is needed. Never send recovery phrases, private keys, signing keys or passwords.
Support correspondence is handled by Dapp developer team and its email service providers. Inbound mail is routed through Namecheap Private Email. Email providers and any services used to handle a request process information under their own policies.
We restrict mailbox access to team members who need to handle support and privacy requests. We do not use support emails for advertising or marketing.
See the Namecheap Privacy Policy. Provider retention, backups and service locations follow their policies and available controls. We do not promise deletion from provider backups on a fixed schedule.
6. Retention and deletion
Support email retention. We delete support correspondence within 90 days after a request is closed and process verified deletion requests within 30 days, subject to the limited exceptions described below.
| Information | Retention and deletion |
|---|---|
| Demo interface state | Used in runtime memory for simulation; not promised to survive restart. No real wallet or server account is created. |
| App caches and system records | Managed by Android and the relevant components. Android app backup is disabled for the reviewed candidate. Uninstalling normally removes app-specific local data; copied text, shared content and third-party records may remain. |
| Support messages and attachments | We remove these from active support mailboxes, including relevant sent, archive and trash folders, within 90 days after the request is closed. For a verified deletion request, we process deletion within 30 days unless a specific legal obligation or documented security need requires limited retention. We explain any exception, limit access and retain only what is needed for as long as necessary. |
| Provider logs and backups | Handled under provider policies and available controls. The team's active-mailbox deletion target does not promise immediate deletion from provider backups or records outside its control. |
7. Privacy questions and requests
Contact contact@mdctoken.org to ask about your support correspondence or request correction or deletion. Identify the email thread if possible; do not send secrets or identity documents unless a necessary, proportionate verification process has first been agreed.
We use a reply from the original email address where practical to verify a request. Any rights and exceptions depend on applicable law; this policy does not determine your jurisdiction or promise rights beyond it.
8. Security and policy updates
This DEMO has not completed an independent production security audit and makes no real-asset protection promise. Its security-preview switches are not active wallet protection.
Before a new build or service changes how information is processed, the team must review the behavior and update this policy as needed. The published policy will show its effective date. A future production wallet requires a separate review.