Moodhuggers home

Privacy policy

Last updated: 18 November 2026

This policy explains what the game Moodhuggers and this website use, who receives it, and why. It is written so that players and parents can follow it.

Who is responsible

Moodhuggers is made by Koray Oksuztepe, in Turkey, who is responsible for the information described here. For any question or request, write to contact@moodhuggers.com.

In short

The services the game uses on phones

RevenueCat (the purchase)

The game sells one thing, the full Chapter 1. RevenueCat checks the purchase with Apple or Google. It receives:

  • an anonymous ID made for this install of the game;
  • on iPhones, Apple's vendor identifier, an ID that is the same for all of one app maker's apps on that phone. RevenueCat's library sends it with every request, and has no switch to turn that off. It is not the advertising ID;
  • the record of your purchases in this game, from the App Store or Google Play;
  • basic device and app details, such as the device model, the system version and the phone's languages, and the device's IP address, which any request carries.

It is used to know whether the full Chapter 1 is owned, and to restore it, for example on a new phone. RevenueCat's privacy policy

Google AdMob (ads)

Ads keep the game free to try. They come from Google AdMob.

  • Every ad request is marked as directed to children and under the age of consent. It asks for family ads only (rated G), and for ads that are not personalized, so they are not based on what you have done before.
  • The game never uses the advertising ID (see below).
  • Google receives what any ad request needs to show an ad and to prevent fraud: the device's IP address, and device and app details.
  • Google's ads library also collects some things by itself, as Google's own pages for developers list them. The game doesn't switch this collection off, and for most of it Google's pages describe no way to:
    • a device identifier tied to the app or its maker. On iPhones, Google says this can be the advertising identifier or other identifiers bounded to the app or its developer, such as Apple's vendor identifier; on Android, Google lists its app set ID. The game never uses the advertising ID, and on Android it removes the permission to read it, but this library's own device identifiers are beyond the game's control;
    • the device's approximate location, worked out from its IP address;
    • the ads shown and the taps on them, and other interactions such as an app launch;
    • app performance data, such as how long the app takes to open, and crash and diagnostic information about the app and the library.
  • Where the law asks for consent, such as in the European Economic Area, the UK and Switzerland, Google's consent form asks you first, and ads start only once Google's consent check allows them. You can open the form again at any time in the game, from Settings > Privacy options.
  • Buying the full Chapter 1 ends the ads: a buyer sees no ads between rooms, and a buyer's hints are always on, with no video. The ad service still starts with the game on a buyer's phone, and may get an ad ready, but a buyer is never shown one.

Google's privacy policy

Firebase Analytics (play statistics)

Firebase Analytics, from Google, counts how the game is played. It receives:

  • an app-instance ID, a random ID that Firebase makes for this install;
  • the game's events: rooms started, finished and restarted, with their moves, blooms and glimmers; hints and undos; when the game offered the full Chapter 1, and when that offer was opened; ads offered, shown, skipped or watched; purchases and restores; reaching the end of the free part; whether Google's consent form and the phone's rating prompt were asked; whether the full Chapter 1 is owned; and a random group number from 0 to 99, which decides where the free part of the game ends, so that different choices can be compared;
  • the events Firebase records by itself, including: when the game is first opened; each play session, and how long the game is in use; updates of the game and of the phone's system; on Android, when the game is removed; and in-app purchases;
  • the device model, system version and language, and the country or region, worked out from the IP address, which Firebase collects itself;
  • never the advertising ID, and on iPhones Firebase is told not to collect Apple's vendor identifier either.

Where the law asks for consent, the play statistics follow your answer to Google's consent form. They are used to see where players get stuck, and to improve the game and its difficulty. Firebase's privacy information

Firebase Crashlytics (crash reports)

If the game crashes, Firebase Crashlytics, from Google, receives a crash report: what the game's code was doing, device and app details, an ID made for this install, the random group number, and whether the full Chapter 1 is owned. It is used to find and fix bugs. Firebase's privacy information

The settings file (moodhuggers.com, served by Cloudflare)

When the game starts on a phone, it asks this website, moodhuggers.com, for its current settings, such as how often ads may show. The website is served by Cloudflare. As with any web request, Cloudflare sees the device's IP address. Besides that, the request carries only the name and version of the game's engine and the phone's system (iOS or Android). We don't log these requests. Cloudflare's privacy policy

The rating prompt

At most twice, after room 9 is first won and when Chapter 1 is finished, the game asks the phone to show its own rating prompt, Apple's or Google's. The phone decides whether it shows. The game never learns whether or how you rated. Apple's privacy policy · Google's privacy policy

No advertising ID

Phones have an advertising ID that apps can use to follow you from app to app. Moodhuggers never uses it:

On the iPhone, Firebase Analytics is also told not to collect Apple's vendor identifier, an ID that is the same only across one app maker's apps. RevenueCat's library does send it with every request, and Google's ads library may read identifiers of that kind by itself (see RevenueCat and Google AdMob above).

Children

Moodhuggers is made for everyone, children included. The game never asks anyone, children included, for a name, an email address or an age. The only identifiers involved are IDs tied to the app on that device: the random install IDs described above, the device identifiers bound to the app or its maker that RevenueCat's and Google's libraries read by themselves (never the advertising ID), and the IP address that any request carries. We use them only to run the purchase, show family ads, count play and fix crashes, never to build a profile of anyone or to target ads, and every ad request asks Google for family ads that are not personalized. Parents can write to contact@moodhuggers.com with any question or request.

On a computer

The computer version of the game (for the Mac) uses none of the services above. It has no purchases, ads, play statistics or crash reports, and it doesn't fetch the settings file. Your progress stays on your computer.

This website

This website uses no cookies, no analytics and no scripts, and loads nothing from other websites. It is served by Cloudflare, which, as with any website, sees your IP address when you visit.

Keeping information safe

Legal grounds

This information is used on these grounds:

Transfers abroad

Google, RevenueCat and Cloudflare handle this information on servers outside Turkey and the European Economic Area, mainly in the United States, under their own safeguards for such transfers, described in their policies linked above.

Your choices and rights

How long information is kept

Changes to this policy

If this policy changes, the new version is posted on this page with a new date at the top.