Cookies
Cookies
Version: 2026-09-22
This document is a translation of the original Czech version. In the event of any discrepancy between language versions, the Czech version shall prevail.
This document describes what cookies and similar technologies the duelgo Platform (operated by duelgo s.r.o., IČO 23846356) uses and why.
1. What Cookies Are
Cookies are small text files that websites store in your browser. They serve to make the website remember your login, preferences and the state of your interaction (e.g. a game in progress). Without cookies, some functions could not be offered at all.
2. Why We Do Not Have a Cookie Banner
Many websites display a cookie banner on the first visit asking "do you agree to our cookies?". We do not display a banner, because:
- We use only technically necessary cookies, which do not require consent to function (Article 5(3) of the ePrivacy Directive 2002/58/EC).
- We do not use third-party tracking cookies (Google Analytics, Meta Pixel, Hotjar, advertising networks).
- For anonymous traffic statistics we use the cookieless tool Plausible Analytics, which sets no cookies and does not identify individual visitors across websites — it therefore does not require consent.
- We process the statistical traffic data necessary for the functioning of the Platform anonymously/in aggregate, or as a legitimate interest under GDPR.
If in the future we ever wished to add cookies requiring consent, we would of course display a banner before such a cookie is set.
3. List of Cookies Used
3.1 Necessary cookies (always active)
| Cookie | Domain | Duration | Purpose |
|---|---|---|---|
dgsid |
duelgo.fun | 12 months | Identification of an anonymous Player — matches one Player's responses together and prevents duplicates. HttpOnly, not readable from the page |
dgsid_js |
duelgo.fun | 12 months | A copy of dgsid readable from the page. In-app browsers (Facebook, Instagram) and older iOS Safari lose the original cookie mid-game; without this copy the Player would lose the responses already given |
dgsid_hdr |
duelgo.fun | 12 months | A marker that the session identifier was restored from the copy above. It ensures that an identifier restored this way can never log anyone into an account |
connect.sid |
duelgo.fun | 12 months | Login of a registered User to the studio. Set only after logging in |
3.2 Server-side storage (not classic cookies, but an associated technology)
| Key | Storage | Duration | Purpose |
|---|---|---|---|
sessions table |
PostgreSQL | 12 months | Session data of a logged-in registered User, including the anti-CSRF token |
game:sess-resp:{sessionId}:{quizId} |
Redis | 30 days | Copy of the Player's responses for resuming a Duelgo in progress and for the betting slip |
game:submit-count:{quizId}:{contentId}:{identity} |
Redis | 30 days | Limiting the number of attempts to submit one response |
game:user-link:{sessionId} |
Redis | 30 days | Mapping the session to an account after the Player registers |
game:anon:{sessionId} |
Redis | 1 hour | Temporary cache of the anonymous Player's profile (nickname, avatar) |
live:* |
Redis | 24 hours | State of a live game in progress (connected players, answers, ranking) |
3.3 Local storage (localStorage/sessionStorage)
| Key | Duration | Purpose |
|---|---|---|
dg_sid |
Persistent until cleared | Backup of the session identifier in case the browser loses the dgsid cookie |
dg_ref |
7 days | Referral code, if the visitor arrived via a link with ?ref= |
dg_replay_{quizId}, dg_replay_max_{quizId} |
Per tab / persistent | The pass number for Duelgos that may be played repeatedly |
duelgo_quiz_{quizId} |
Persistent until cleared | Game progress, so the game can be finished after the page is refreshed |
duelgo-admin-language |
Persistent | The chosen interface language |
userProfile, currentTeamId |
Persistent | Nickname, avatar and team, to pre-fill them in the next Duelgo |
4. Third-Party Cookies — None
The duelgo Platform uses no third-party cookies. For anonymous traffic statistics we use Plausible Analytics — a tool that is cookieless (it sets no cookies or other identifiers on your device) and processes data in aggregate, without tracking individuals across websites. The service is hosted in the EU. We therefore do not need a cookie banner. If in the future we add cookies requiring consent, we will update this document and display a cookie banner with a consent request before they are set.
5. How to Manage Cookies in Your Browser
Most browsers accept cookies automatically, but you can block or delete them in the browser settings:
- Chrome: Settings → Privacy and security → Cookies and other site data
- Firefox: Preferences → Privacy & Security → Cookies and Site Data
- Safari: Preferences → Privacy
- Edge: Settings → Cookies and site permissions
⚠️ If you block necessary cookies, the Platform will not function correctly (you will not be able to log in or play a duelgo).
6. Your Rights
Cookies contain technical identifiers that may be considered personal data under GDPR. Your rights towards the Operator are governed by the Privacy Policy, § 7.
7. Contact
Send questions about cookies to info@duelgo.fun.
8. Changes
We may update this document when the Platform's technologies change. We communicate material changes to registered Users by e-mail.