Last updated: February 18, 2026
This Privacy Policy explains what data is collected, how it is used, and how it is protected when you use the BTCT/DOGE DEX platform and BTCT Town.
This platform is a non-custodial, open-source decentralized exchange (DEX) that facilitates peer-to-peer HTLC atomic swaps between BTCT and DOGE. The server acts solely as a bulletin board and message relay.
The server NEVER holds, accesses, controls, or stores private keys or user funds.
| Data Type | Description | Purpose |
|---|---|---|
| BTCT Address | Public blockchain address (not personal information) | Trade coordination, listing identification |
| DOGE Address | Public blockchain address | Trade coordination (DOGE sending) |
| Trade Data | Listing details, trade status, HTLC hashes | Atomic swap coordination |
| Chat Messages | Text messages between trade participants (max 500 chars) | Trade communication, dispute reference |
| Town Position | In-game character coordinates (BTCT Town only) | Multiplayer functionality (not stored in DB) |
The following data is stored only in your browser's localStorage and is never sent to the server:
⚠ If you clear your browser data, you will lose your locally stored wallet keys and trade secrets. Always back up your private keys.
| Data Type | Retention Period |
|---|---|
| Trade listings (ads) | Indefinite (public bulletin board) |
| Trade records | Indefinite (blockchain coordination history) |
| Chat messages | 90 days (automatically deleted) |
| Town player positions | Session only (in-memory, cleared on disconnect) |
Your data is never shared with third parties. The only external service used is:
Since no personal information is collected, traditional data subject rights (access, deletion, portability) apply in a limited way:
The full source code is publicly available at github.com/timessanta/btct-doge-dex (MIT License). You can verify exactly what data is collected and how it is handled.
For questions about this privacy policy, please open an issue on the GitHub repository.
This policy may be updated. Changes will be reflected in the "Last updated" date above and committed to the GitHub repository.