CHATTrace is not a service. It is a session.
When the terminal closes, the chat disappears — completely.
CHATTrace was born after multiple failed attempts to build a traditional anonymous chat service.
Those failures revealed an important truth:
Long‑running services attract traceability.
Short‑lived tools disappear naturally.
Instead of fighting platforms or forcing persistence, CHATTrace embraces ephemerality as a design principle.
The result is a chat system that exists only while the operator is present — inspired by the lifecycle philosophy of tools like LENSTrace and NEXUSTrace.
- 🕒 Session‑based lifecycle (operator‑controlled)
- 🧠 Memory‑only chat (no DB, no disk storage)
- 👤 No accounts, no authentication
- 🌍 Temporary public URL
- 🧹 Clean shutdown with optional log deletion
- 🖥️ Terminal‑first tool UX
- ⚙️ Fully automated setup (no manual installs)
CHATTrace provides application‑layer anonymity, not network‑layer anonymity.
- No persistent identities
- No message history after shutdown
- No cookies / localStorage
- No database
- No background daemons
- No auto‑restart
- Operator‑controlled exposure
- ❌ Tor‑level anonymity
- ❌ IP address hiding
- ❌ Traffic obfuscation
- ❌ End‑to‑end encryption (yet)
CHATTrace minimizes data existence, not network visibility.
User Browser
↓
Flask Web Server (Local)
↓
In‑Memory Chat State
↓
Temporary Tunnel (Session‑Scoped)
- Backend: Python (Flask)
- Frontend: HTML + CSS (Jinja templates)
- Control: Bash scripts
- Exposure: Temporary tunnel
- Storage: RAM only
CHATTrace/
├── venv/ # Auto‑created virtual environment
│
├── assets/
│ ├── ascii.txt # ASCII banner
│ └── style.css # UI styles
│
├── bin/
│ └── cloudflared # Local tunnel binary
│
├── server/
│ ├── app.py # Flask backend (memory‑only)
│ ├── logs/ # Runtime logs (optional)
│ └── templates/
│ └── index.html # Chat UI
│
├── config.json # Runtime configuration
├── chattrace.sh # Main launcher (does everything)
└── cleanup.sh # Safe cleanup script
- Linux
- Python 3
- Bash
- curl
- Internet connection
- Python virtual environment
- pip dependency installation
- Flask installation
- Tunnel setup
- Session cleanup
You do not need to install pip or create a venv manually.
git clone https://github.com/chriz-3656/CHATTrace.gitcd CHATTracechmod +x chattrace.sh cleanup.sh./chattrace.shThat’s it.
The script handles everything else.
- ASCII banner is displayed
- System & dependency checks
- Virtual environment is created (if missing)
- Dependencies are installed automatically
- Old sessions are cleaned
- Flask server starts locally
- Temporary public URL is generated
- URL is printed in terminal
- Chat exists only while the terminal is open
Press:
CTRL + C
On shutdown:
- Server stops
- Tunnel closes
- Memory is wiped
- You are prompted to save or delete logs
No background processes remain.
- Minimal HTML (Jinja template)
- Terminal‑style CSS
- No heavy frameworks
- No background workers
- No persistent browser storage
The UI is intentionally simple to avoid fingerprinting and reduce complexity.
- Stored in:
server/logs/ - Session‑scoped only
- Never persisted unless you choose to keep them
To force cleanup:
./cleanup.shCHATTrace is intended for:
- Temporary chat sessions
- Demos & testing
- Educational use
- Tool‑style communication
It is not intended to be:
- A permanent chat service
- A public anonymous platform
- A secure messenger replacement
If a system must live forever, it becomes traceable.
If a system exists only when needed, it becomes forgettable.
CHATTrace treats ephemerality as a feature, not a limitation.
Chris (chriz‑3656)
GitHub: https://github.com/chriz-3656
CHATTrace is a tool, not a service.
If you run it like a tool, it behaves like one.
