Legal
Cookie Policy
Published by: [rechtsvorm en naam exploitant] — qoinomics.com. Questions: [contact e-mail].
Read this first — short
- Cookies are small files that a website places on your device. We also use similar techniques such as local storage in your browser.
- In the draft phase, Qoinomics only uses techniques that are needed to make the service work, plus the language preference. There are no advertising cookies and no tracking pixels from social media.
- For techniques that are not necessary, we ask for consent — and refusing must be as easy as accepting.
- You can always delete cookies via your browser; some settings may be lost as a result.
1. What are cookies and similar techniques?
A cookie is a small text file that a website places on your computer, phone or tablet, so that the site can recognise you (again). There are also similar techniques, such as local storage in your browser (localStorage) and tokens that the service temporarily keeps in memory. In this policy, "cookies" refers to all these techniques together.
2. Which cookies and techniques does Qoinomics use?
In the draft phase, Qoinomics uses the following techniques. (This overview will be checked against the actual website before publication. Names in brackets will be filled in after that check.)
| Technique | Name | Purpose | Needed for the service? | Retention period on your device |
|---|---|---|---|---|
| Session cookie | [cookie name to be verified] | keeping you logged in while you use the world | Yes | [to be verified: e.g. until you close your browser] |
| Security token | [to be verified whether this is a cookie; it may only be sent along with requests] | protection against attacks (CSRF) | Yes | [per session, to be verified] |
| Language preference | qn_lang | remembering which language you want to use the world in | To be assessed for necessity — see section 4 | [duration to be verified] |
| Realtime token (Ably) | [to be verified: memory or local storage] | temporary access to the realtime channels (positions, chat, presence) | Yes | Short-lived token (valid for max. 1 hour; storage time on your device [to be verified]) |
| Voice connection (WebRTC) | no cookie | direct voice between players | Yes (if you use voice) | Per conversation |
What we do not use (draft phase): advertising cookies, retargeting pixels from social media (Facebook, Instagram, LinkedIn, YouTube), third-party marketing SDKs and third-party payment tracking. (To be confirmed: this is the set-up for launch; as soon as marketing pixels are added, this policy will be updated first and consent will be requested.)
3. Necessary cookies
The session cookie, the security token and the realtime token are necessary to make the service work: without them you cannot stay logged in and the world does not work. We do not need consent for these techniques, but we do tell you what we do (this policy). Do you want to block them? You can, via your browser — but then you cannot use the service (properly).
4. Functional techniques: the language preference
The language preference (qn_lang) remembers which language you use the world in. We do not assess this technique only by the label "functional", but by purpose (remembering your language choice), necessity and duration; the only thing stored is your language choice. [To be confirmed: whether we rely on the Dutch rule that allows comparable, privacy-friendly storage without consent after informing you (Article 11.7a of the Dutch Telecommunications Act; supervisor: ACM), or ask for consent after all.]
5. Analytics (statistics)
We want to know how the world is used, so that we can improve it. Our starting point is a privacy-friendly, self-hosted solution without cross-site tracking and without selling data. In the draft phase, no active analytics policy has yet been adopted. [To be confirmed: which tool, which settings, and whether it falls under the Dutch exception for techniques with minor privacy impact (Article 11.7a of the Dutch Telecommunications Act) or whether consent is needed. If consent is needed: we block the technique before consent, offer an equally easy refuse button, and you can always withdraw consent. "Cookieless" is not in itself an automatic exemption.]
6. Logging in via Google
You can log in with your Google account. Please note: depending on how the login library is built in, the login button may already send requests to Google before you actually click "log in". For Google's own privacy policy — what Google does with that data — we refer to Google's privacy policy. We will check how our own login button works technically before publication.
7. Third parties and the CDN
The 3D world is loaded quickly via a Content Delivery Network (jsDelivr). [To be checked: whether this network places cookies on your device; in any case it processes IP addresses to make the connection possible.] This is also stated in the privacy statement. Insofar as we use external services (Ably, Metered, OpenAI, Stripe/Mollie), their own terms apply; the privacy statement explains their role.
8. Consent: how we ask and how you withdraw
Insofar as we ask for consent (for example for analytics or, later, marketing):
- we ask before the technique is used, and block the technique until you have made your choice;
- refusing is as easy as accepting (no small grey button next to a big green one);
- you can choose per category (necessary techniques are always on);
- you can always withdraw your consent, via the cookie settings at the bottom of the site or via [contact e-mail].
9. Managing it yourself in your browser
You can block or delete cookies via your browser settings (Chrome, Safari, Firefox and Edge each have their own menus for this; search for "cookies"). As a result, some things may no longer work, such as staying logged in or your language preference. "Incognito/private browsing" also limits cookies per session.
10. Questions and complaints
Questions about cookies? E-mail [contact e-mail]. In the Netherlands, the Netherlands Authority for Consumers and Markets (ACM) supervises the rules on cookies and similar techniques; if it concerns the personal data collected with them, you can also contact the Dutch Data Protection Authority.
11. Changes
When functions change, we update this policy and publish the new version with a date. When we add techniques that require consent, we will ask for your consent again.
