LEGAL
Privacy Policy
Updated: August 27, 2026
This policy explains what data Haggle collects, why we process it, where it is stored, and what rights you have. We process only the data necessary to operate the browser-based negotiation training game.
1. Who we are
Haggle is a text-based negotiation RPG: you duel AI bosses and receive breakdowns from an AI judge. oleksii@conversai.xyz.
2. What data we process
- Account data — email, player name, password in hashed form (or Google login identifier).
- Game data — selected bosses, duel moves, results, rating, badges, and duel limits.
- Technical data — visited pages, UI actions, IP address, browser type, and logs for security and debugging.
3. Why we process data
- Providing and maintaining the game (contract performance);
- Saving progress, rating, and duel limits;
- Generating boss lines and judge breakdowns through AI providers;
- Security, abuse prevention, and legal obligations.
4. Where data is stored and processed
- Database (PostgreSQL) — account and game progress;
- Application hosting — web application delivery;
- AI providers — processing duel text for lines and analysis; we send only the text required for the task, without passwords.
5. Cookies
We use cookies for session management and authentication to keep you logged in. You can delete cookies in your browser settings; without session cookies, logging into the game is not possible.
6. Data retention
We retain account and game data while the account is active, and as long as required for legal obligations. You may request data deletion — see section 8.
7. Security
Data is transmitted over encrypted connections. Passwords are stored in hashed form; server secrets never reach the browser.
8. Your rights
- access to the data we hold about you;
- correction or deletion of data;
- objection to processing or its restriction;
- data portability in a machine-readable format;
- withdrawal of consent at any time.
To exercise your rights, email oleksii@conversai.xyz. We respond within 30 days.
9. Policy changes
We may update this policy as the service evolves. The current version is always on this page, with the last update date above.