Cookies and browser storage
Last updated: 26 October 2026
In brief
- Rikiki sets no cookies for tracking, advertising or statistics.
- The game stores small pieces of necessary data in your browser (who you are, your current game) and your settings (sound, language, card deck, large text…). They are never sent to advertising networks.
- Two items load only after your agreement: Google reCAPTCHA and KLIPY GIFs.
1. Why we do not ask for consent for everything
In Belgium (article 129 of the law of 13 June 2005 on electronic communications) and in the European Union, your agreement is not needed to store information that is strictly necessary for a service you asked for, such as keeping you signed in or remembering a setting you chose (language, sound…). It is needed for everything else. That is why the two outside services listed below only load after a click from you.
2. What is stored in your browser
Rikiki uses the browser's storage space ("localStorage"), not cookies. Here is the complete list.
| Name | Purpose | Type |
|---|---|---|
| rikiki_profile | Your signed-in profile (nickname, player identifier), so we do not ask for your code at every visit. | Necessary |
| rikiki_fb_uid, rikiki_fb_name, rikiki_fb_color | Your player identifier, first name and colour when you play without a profile. | Necessary |
| rikiki_last, rikiki_resume | The code of your current game (or one you left less than 6 hours ago), to give it back to you if you reload the page or to resume it from the home screen. | Necessary |
| rikiki_recent_names | The last first names you wrote in the score sheet, offered as suggestions next time. | Setting |
| rikiki_ptok | A secret token that proves it is really you if you need to get your hand back. | Necessary |
| rikiki_attest_todo_…, rikiki_claim_… | League results to confirm and an ongoing code-recovery request. | Necessary |
| rikiki_sfx, rikiki_music, rikiki_led_help, rikiki_autoplay, rikiki_big_text, rikiki_lang, rikiki_deck, rikiki_coach | Your settings: sound effects, music, help, large text, language, card deck, coach. | Setting you chose |
| rikiki_tuto_seen, rikiki_news_seen | Remember that you have already seen the tutorial and the news. | Setting |
| rikiki_consent, rikiki_gif_ok | Your choice about reCAPTCHA and GIFs. | Necessary (proof of your choice) |
| rikiki_last_backup, rikiki_lobby_clean_at | Date of the last backup and of the last automatic clean-up (publisher only). | Setting |
| firebaseLocalStorageDb (IndexedDB) | The Google Firebase sign-in token: it keeps you signed in. | Necessary |
You can erase everything at any time in your browser settings ("clear site data"). You will then have to sign in again.
3. What loads only after your agreement
| Service | What it does | What it receives | If you refuse |
|---|---|---|---|
| Google reCAPTCHA (through Firebase App Check) | Checks that connections come from the real game. | Your IP address and information about your browser. Google may set its own cookies on its domain. | The game works exactly the same. |
| KLIPY (chat GIFs) | Searches for and displays GIFs. | Your IP address and your search words. GIFs are displayed from KLIPY's server. | GIFs stay hidden (a button offers to show them). The rest of the chat works normally. |
You can change these two choices at any time: ⚙️ Settings in the game. Withdrawing an agreement prevents later loading; it does not delete what Google or KLIPY already received.
4. What is loaded from outside anyway
The Google Firebase programs are loaded from Google's server (gstatic.com): this is essential for the online game. The pages of the site come from GitHub Pages. These two companies see your IP address like any website. More details in the privacy policy. Fonts are hosted by Rikiki itself.