IQ Mogged — Privacy Policy

Last updated: 2026-11-03
App: IQ Mogged (iOS / Android)

1. Who is responsible (Controller)

The controller for your data under the GDPR is:

• The Lucas Agency GmbH
• Am Kabellager 11, 51063 Köln, Germany
• Represented by: Maxim David Dambietz
• Register: Amtsgericht Köln, HRB 127141
• Contact: iqmogged@lucasagency.de

If you have questions about this policy or your data, contact us at iqmogged@lucasagency.de.

2. Summary

IQ Mogged is a daily logic-puzzle game. You can play offline without giving us any personal details. If you use the online features (daily leaderboards, friends), we store a minimal profile and your daily solve times so you can compete with friends. The game is free to play; there are three optional one-time in-app purchases and never a subscription — one unlocks every level, one removes the ads, and one is both together. Only the last two remove the ads. We never ask for your real name or email address to play — they are only involved if you choose to use Sign in with Apple, either to create your account or to secure an existing one (§3(h)).

Since version 2.0 the free game is funded by advertising: a full-screen ad appears after every third level you finish. The daily puzzles stay ad-free. Separately from that, you can choose to watch a short ad in exchange for a hint (in version 3.1: an extra life) — that one only ever appears when you tap it, and it stays available even if you have paid to remove the ads. On iOS we ask, through Apple's tracking prompt, whether ads may be matched to your interests: if you decline, or before you answer, the ads are non-personalised and nothing else changes. Android has no such prompt — there the decision rests on Google's consent dialog and is applied by Google's advertising SDK. Details in §3(j). We do not sell your data, and your puzzle results, times and friends are never shared with advertisers.

From version 3.2.2 we use AppsFlyer to measure which of our own ads (for example on TikTok) lead to installs and purchases — in the EU, EEA, UK and Switzerland only with your consent (§3(k)).

3. What we collect and why

a) Account / identity data

When you first open the app we create an anonymous account (a random user ID) via our backend provider (Supabase). To use the social features you choose:

• a username (a unique handle, e.g. @lucas),
• optionally a display name (shown to friends),
• a system-generated friend code.

We store these plus the account creation date. Playing does not require an email address, a phone number, or your real name, and we never ask for them here (please don't type sensitive information into your display name either). If you choose to secure your account with Sign in with Apple, an email address and optionally your Apple name are involved — see §3(h).

Purpose: to give you an identity others can add and compete with. Legal basis (GDPR Art. 6(1)(b)): performance of the service you requested.

b) Social / friends data

If you add friends: your friendship connections and pending friend requests (who sent/received, status, timestamps).

Purpose: to run the friends and request features. Legal basis: Art. 6(1)(b) (service), and for others adding you, our legitimate interest in providing a social game (Art. 6(1)(f)).

Invitations (from version 3.2). If you say who invited you when you sign up, we store that link (your account, the inviting account, the time) and make you friends straight away — this is the one case in which a friendship is created without a request being accepted (from version 3.2; the named player can remove or block that friend at any time). To decide whether the invitation counts towards a reward, we check on how many days you solved a daily puzzle in your first 14 days. The inviting player sees your name and on how many of those days (at most 3) you played in their "Invited friends" list. We also store which rewards a player has claimed — for extra levels, the game and the level up to which it is unlocked. This data is deleted with the account.

Weekly events (from version 3.2). If you claim an event reward, we store which event, what you chose (extra levels in which game and up to which level, or the badge) and when. To check whether you completed the event, we use the daily results described in (c). Deleted with your account.

Showcase (from version 3.2.2). We store which badges you put in the showcase on your profile (up to seven, including event badges) and in which order, linked to your account. Your friends see the showcase when they open your profile; if public ranking is on, so does anyone who opens your public profile (see (c)). Along with it, they learn which weekly events you completed — not what you chose as the reward. If you have not picked anything, the app shows your highest badges and your event badges there. Deleted with your account.

Purpose: to run the "invite friends" feature and to prevent abuse. Legal basis: Art. 6(1)(b) (service).

c) Gameplay data (online)

Two kinds of solve time are stored on our servers, each linked to your account:

• Daily puzzles: your solve time for that day and game, which powers the per-game daily leaderboard shown to you and your friends. For Words (from version 3.2) we store the number of guesses instead of a time, and if you did not find the word, that you played that day's Words without solving it; your friends see both. The words you typed stay on your device.
• Level packs: when you solve a level, we store which game and level number it was and how long you took, so you and your friends can compare times on the same level. We keep one row per level and, in it, your best time: replaying a level updates that row if you were faster and changes nothing if you were not. We also store the major version of the app that uploaded the result (e.g. 2) — no more than that single number. When a level pack is rebuilt, a level number stops referring to the same puzzle, so this is what lets us keep results uploaded by outdated app versions out of the leaderboards instead of ranking them against times set on a different board.
• Levels you did not complete (from version 3.2): if you fail a level in Words or Categories for good, we store the game, level number, the level's language, the version of the level pack and the time. That keeps the level locked after a reinstall or on another device. Only you can see this; it never counts as solved.

Public leaderboards (on by default from version 3.2, can be switched off at any time). The leaderboards above show you and your confirmed friends. Beyond that there is public ranking; while it is on, any signed-in player can see the following.

• Up to version 3.1, public ranking is off until you switch it on in the app.
• From version 3.2 it is on by default. After the update or after sign-up, the app shows you a one-time notice with exactly this list and a switch set to "on". The setting is only turned on for your account once you confirm or close that notice — you do not appear before that. If you switch it off in the notice, it stays off. You can change it at any time in your profile under "Appear in the leaderboards".

In the public leaderboards:

• your username (in app version 3.1 and later; players still on an older version see your display name instead, if you had switched public ranking on there),
• your solve time for a given daily puzzle,
• your number of solved levels per game, together with the moment you last solved one in that game,
• your total number of solved levels across all games, together with the number of games you have solved anything in,
• from version 3.2, the colour of your name (silver or gold) if you have made a purchase — see (g).

In your public profile, which any of those players can open by tapping your row:

• your username again,
• your number of solved levels per game,
• the days on which you solved a daily puzzle (from version 3.2, for Words also the days on which you played it without solving it) — one date-and-game entry per day, for your whole history. The app turns that list into the streaks and the badges it shows on the profile; it contains no times.

Your display name, your friend list, your e-mail address and your individual level times are not part of any of it. Because your username is shown, other players can use it to send you a friend request; it only becomes a friendship if you accept it — except that a new player may name you as the person who invited them, which makes you friends straight away (see "Invitations" in (b)). Switching public ranking off removes you from the public leaderboards and from the public profile. If you switched public ranking on before app version 3.1, that consent covered your display name only: it does not carry over to your username. In version 3.1 you appear only once you agree to the new text in the app; from version 3.2 the notice above applies.

"Friends only" view (from version 3.2). In the leaderboards you can show only your friends. There, your friends see your place in the public leaderboard — but only while your public ranking is on. If it is off, your friends see only your time or your solved levels there, as before, without a place.

Purpose: leaderboards and streaks; with public ranking on, comparison beyond your friend circle. Legal basis (GDPR Art. 6(1)(b)): performance of the service you requested. For public ranking up to version 3.1, your consent (Art. 6(1)(a)), which you can withdraw at any time via the same setting. From version 3.2, our legitimate interest (Art. 6(1)(f)): comparing results with other players is the core of the app, and only a username you chose yourself and your game results are shown — nothing about you as a person. You can object at any time (Art. 21) by switching the setting off, without giving a reason and with immediate effect.

d) Data stored only on your device

Your in-progress puzzle state, streaks, app settings, and which levels you have unlocked are stored locally on your device and are not sent to us — except for levels you received as a reward for invitations or weekly events: those are stored on our server (see (b)) so they come back after a reinstall. (Your solve times are uploaded — see (c).) Your login session token is stored securely on your device (iOS Keychain / Android Keystore). Uninstalling the app removes this local data.

e) Notifications (from version 2.0)

Notifications are optional. We ask inside the app first, whether you would like to be reminded at all; the system dialog of iOS (and of Android 13 or later) only appears if you agree there or, from version 3.4, tap "Turn on" under Profile → Settings → Reminders. Android 7 to 12 has no such system dialog; there, from version 3.4, we rely on our own question alone: no reminder is scheduled and no push identifier is stored until you agree there or tap "Turn on". Installations on Android 7 to 12 that had reminders on without having been asked are switched off once by version 3.4 and their push identifier is deleted from our server; after that we ask our question at the next occasion. If you decline, we store no push identifier and send you no notifications. From version 3.4 we do, however, learn that you saw our dialog and how you answered — see "Measurement" at the end of this section.

If you agree, three things are involved:

• Your reminders — for your streak and, from version 3.4, after a few days without opening the app — scheduled and shown by your device. The reminder itself never travels to us; from version 3.4 we learn whether you tapped it (see "Measurement"). One detail does reach us, together with the push identifier below: which puzzle days your device has a reminder planned for (up to version 3.3 one day, from version 3.4 all planned days). We need it so we do not send you a server game notification on a day your phone is already going to remind you — one a day, not two through different channels. It is stored against your account id and overwritten whenever the plan changes.
• The device's push identifier — an identifier issued by the operating system and Expo (a push token), linked to your account id. Stored alongside it: the platform (iOS/Android), your device language, the reminder days described above, when the entry was last updated and, from version 3.4, your device's time zone, the installed app version and whether notification permission was granted at that point. The identifier is what allows a notification to reach your device at all — for example, the note that a friend has overtaken you on a daily, or that someone has sent you a friend request or accepted yours. The time zone lets us keep quiet hours by your local time: no game notification between 10 pm and 8 am, and friend notifications wait until the morning (without a time zone we use German time). We need the app version so that a notification only names games your app knows; the permission status is used for the measurement below. Which open game a notification names is chosen from your stored daily results (the game you solved most often in the last 30 days). Delivery runs through Expo's push service and from there through Apple or Google.
• The notification queue — when someone overtakes you on a daily, or sends you a friend request or accepts yours, we write one entry recording who triggered it, which kind of notification it is, for dailies the game and puzzle day, and what happened to the notification afterwards (sent, held back, or skipped and why). For every notification sent we also store, per device, Expo's delivery receipt: the ticket id Expo issued, the push identifier it went to, and whether Apple or Google accepted it. If Expo reports that a device can no longer be reached (for example because the app was deleted), we remove its push identifier. This is what makes the caps possible — at most one game notification a day, at most three friend notifications in 24 hours — and it is how we can tell a delivery problem from a silent one. We delete these entries after 90 days, or earlier with your account.

The legal basis is your consent (Art. 6(1)(a) GDPR). You can withdraw it at any time by turning Profile → Reminders off (from version 3.2: Profile → Settings → Reminders). That deletes the scheduled reminder on the device and removes the stored push identifier from our server, so nothing is sent to it any more; the entries for notifications already sent (queue and delivery receipts) still record it for up to 90 days. Deleting your account removes it everywhere. We never send advertising through this channel.

Measurement (from version 3.4). Whether or not you agree, we record with your account id when our notification dialog is shown to you, whether you choose "Yes, remind me" or "Later", whether the operating system grants or denies permission, whether you open the system settings from your profile, and whether you open a notification. With each of these events we store the time, the platform (iOS/Android) and the app version, plus the occasion on which the dialog appeared (for example after solving a daily) and, when a notification is opened, its kind and text variant. At most 50 entries in 24 hours; no game content, no names, no push identifier. This does not tell us whether a notification was delivered, only whether it was opened. The entries are kept only in our database (Supabase), cannot be seen by other players, are not passed to any analytics or advertising service and are not used for advertising. Purpose: finding out whether our dialog and our notifications work and which wording works better. Legal basis: our legitimate interest in improving our app (Art. 6(1)(f) GDPR). You can object at any time (Art. 21) by emailing iqmogged@lucasagency.de. We delete the entries after 13 months, or earlier with your account.

f) Technical data

Our backend provider processes technical data needed to deliver the service (e.g. IP address at the moment of a request, for security and rate-limiting). We do not build advertising or tracking profiles from it.

App updates (from version 3.4). Every time the app starts, it asks the update service of our provider Expo (EAS Update) whether there is newer program code for the installed app version. We use this only to deliver bug fixes to the app version you have installed, never to add new features. Each request carries your IP address, the platform (iOS/Android), the installed app version, the update channel, the identifiers of the update versions currently running, built in or recently failed, and an installation ID that the update component creates once and stores on your device; if the app crashed with a fatal error during start-up, also a technical error message (at most 1,024 characters). Like any connection, it also carries ordinary connection data (on iOS, for example, the system version and app build in the User-Agent). We do not link the installation ID to your account, and it is not your push identifier. These requests happen whether or not you have turned notifications on.

Purpose: keeping the installed app working and secure by delivering bug fixes. Legal basis: Art. 6(1)(b) GDPR (performance of the service you use) and Art. 6(1)(f) GDPR (our legitimate interest in an error-free, secure app).

g) Purchase data

The app offers three one-time purchases: unlocking every level, removing the ads, and a bundle of both. All three are non-consumable and none is a subscription, and they are independent of one another — unlocking the levels does not remove the ads, and removing the ads does not unlock the levels. The payment itself is handled by Apple or Google; we never see your card details. Our purchases provider (RevenueCat) records that a purchase was made and the resulting entitlements (levels unlocked: yes/no; ad-free: yes/no), linked to your account's user ID so that a payment can be matched to an account if you contact us about it. RevenueCat does not receive your username, display name, email address, or friends data. On your device we store only a local flag for what you own.

Christmas pass 2026 (from version 3.4). This additional one-time purchase unlocks seasonal bonuses. RevenueCat also records views of the pass purchase page to measure purchase conversion, linked to its existing customer identifier. Our server stores the pass entitlement, its initial grant, claimed doors, earned cosmetics and assigned puzzle completions under your account ID. Refunds end further pass access; already earned rewards remain. The initial-grant record prevents duplicate purchase gifts after a refund and repurchase.

Name colour (from version 3.2). We store on our server whether your name is shown in silver (all levels unlocked) or gold (all levels unlocked and ads removed). We take this from RevenueCat; no price, receipt or transaction data is stored. Other players see the colour wherever your name appears to them: your friends, open friend requests and, if public ranking is on, the public leaderboards and your public profile. This also applies to purchases made before version 3.2: the colour appears the first time you open version 3.2. A levels unlock you earned by inviting friends colours your name the same way. The entry is updated when your purchases change and deleted with your account.

Purpose: to unlock the paid content and restore your purchase after a reinstall. Legal basis (GDPR Art. 6(1)(b)): performance of the purchase contract.

h) Sign in with Apple or Google (optional)

Your account is anonymous by default, which means it lives on that one device: reinstall the app or switch phones and your streaks and friends are gone. Sign in with Apple prevents that, and you can use it in two ways:

• to create your account, offered as the first action on the very first screen, and
• to secure an account you already started ("Save progress"), or to restore it later on a new device with the same provider account.

Exactly one provider is offered per platform: Sign in with Apple on iOS, Sign in with Google on Android. You are never asked to choose between them.

This is entirely optional in both cases — the first screen also offers a plain form, and everything in the app works without ever signing in.

When you do, Apple sends us:

• a stable user identifier for your Apple ID (specific to this app),
• your email address — if you choose Hide My Email, this is an Apple relay address (…@privaterelay.appleid.com) and we never see your real one,
• optionally your name, which we use as your display name unless you change it. Apple only provides this on the very first sign-in.

On Android, Google takes Apple's place and sends us the same three things: a stable user identifier for your Google account, your email address, and optionally your name. Google offers no relay-address equivalent, so the address is your real Google address. Unlike Apple, Google provides the name and email on every sign-in, not only the first.

We store the identifier and email with your account at our backend provider (Supabase) purely so we can recognise you again. We do not use your email address for marketing and we never send you email. This is the same data either way — only the provider differs.

Purpose: creating your account, and recovering it after a reinstall or device change. Legal basis (GDPR Art. 6(1)(b)): performance of the service you requested. Withdrawal: you can stop the linkage at any time — in your Apple ID settings, or under Third-party apps with account access in your Google account — and you can delete the account entirely in the app (Profile → Delete account; from version 3.2 Profile → Settings → Delete account, or the menu at the top right), or via our account deletion page.

i) Reports and blocks

If you block another player, we store who blocked whom. If you report someone, we store the reported account, the reason you selected, and the time — plus a copy of the username and display name as they were at that moment, so the report still makes sense if the account is later renamed or deleted. Only we can read this; it is never shown to other players.

Purpose: to keep blocks working and to act on abuse (Apple requires both for apps with user-generated content). Legal basis: Art. 6(1)(b) (service) and Art. 6(1)(f) (our legitimate interest in a safe service and in documenting abuse reports).

j) Advertising (from version 2.0)

There are two ad formats, and the difference matters for your data.

Full-screen ads, shown to you. If you have not bought "remove ads" or the bundle, the app shows a full-screen ad after every third level you finish. Buying "unlock every level" on its own does not stop these. The daily puzzles are always ad-free, and no ad ever interrupts a puzzle you are solving. If you own ad-freedom, none of these is ever requested or shown, and nothing to do with advertising is started for you unprompted — no ad request leaves your device unless you ask for one, as described next.

Rewarded ads, only when you ask for one. Where the app offers you a hint (in version 3.1: an extra life), you may tap to watch a short ad in exchange for it. It is never shown on its own, it never interrupts anything, and nothing is credited unless the ad was watched through to the end. It is available to every player, including those who bought "remove ads" or the bundle: paying removes the ads we would put in front of you, not the ones you choose to watch. If you do tap it, the advertising SDK is started at that moment and the consent dialog described below is shown first — this is the one case in which an ad request leaves the device of a paying player. If you never tap it, nothing is started.

The ads are delivered through Google AdMob. To deliver them, Google's SDK processes a device identifier and technical data about your device and about the ad itself (which ad was shown, whether you tapped or dismissed it, error and performance data). It uses this to deliver ads, to limit how often you see the same one, and to detect invalid traffic and fraud.

AdMob is the mediation platform, not the only source of ads. For each ad slot it collects bids from other ad networks and lets the highest one serve. Besides Google, one further network is currently integrated: Unity Ads (Unity Technologies). When Unity wins a bid, its SDK also processes a device identifier and technical data about your device and the ad in order to deliver it, for the same purposes. If another network is added, it will be named here before the app version carrying it is released.

The limits below apply to every one of these sources alike, whichever network ends up serving a given ad: how a request is marked follows the rules set out next, and if you own ad-freedom no advertising SDK starts at all unless you tap a rewarded ad yourself — not Google's and none of the mediated ones.

The limits we set in the app:

• On iOS we ask before anything is personalised. The app shows Apple's App Tracking Transparency prompt. Only if you allow it may the advertising identifier (IDFA) be used, and only then are ads selected on the basis of your interests.
• On iOS, if you decline, the ads stay non-personalised. The request is then marked "non-personalised ads only", iOS withholds the advertising identifier from the SDK, and nothing about the game changes. The same applies before you have answered.
• **On Android there is no tracking prompt, and personalisation follows the consent dialog instead.** Android has no App Tracking Transparency, so the app marks the request neither way; whether an ad is personalised is decided by Google's advertising SDK itself, on the basis of the consent you gave or refused in Google's consent dialog described below. Refuse there and no ad is requested at all.
• Nothing depends on your answer. No feature, no content and no price changes either way, and we offer you nothing in return for allowing it.
• You can change your mind at any time in iOS Settings → Privacy & Security → Tracking.

Your choice (EEA/UK): before the first ad request we show you Google's consent dialog (Google User Messaging Platform). If you decline, or if the dialog cannot be shown, the app requests no ads at all. You can change your decision later via the privacy options in the dialog where offered. You can also remove the full-screen ads permanently with the one-time "remove ads" purchase or the bundle; the voluntary rewarded ad stays available to you afterwards if you want it.

Purpose: to fund the free version of the game. Legal basis: your consent (GDPR Art. 6(1)(a)) where consent is collected via the dialog above; storage on your device is based on your consent under §25(1) TTDSG.

k) Measuring our ad campaigns (AppsFlyer, from version 3.2.2)

We advertise IQ Mogged, for example on TikTok. To learn which ads lead to installs and purchases we use AppsFlyer Ltd. (Israel). AppsFlyer receives:

• Device identifiers: on iOS the identifier for vendor (IDFV) and — only if you allowed tracking in Apple's prompt — the advertising identifier (IDFA); on Android Google's advertising ID (unless you deleted it in Android settings) and the Android device/app-set ID,
• IP address, device type, OS and app version, time of install and app launches, and on Android the Google Play install referrer,
• In-app events: completed purchases (product, amount, currency — never payment details) and the first time you solve a level (game and level number). From version 3.4 this also includes opening the Christmas pass page and its entry point, displayed offers, purchase attempts and outcomes, and design previews and selections. These events include the season, platform, level-ownership status and relevant design or game identifier.

AppsFlyer does not receive your username, display name, email address, friends or times. It attributes the install to the ad you came from and passes that result to the ad platform we ran the ad on (for example TikTok, later possibly Meta or Google). On iOS AppsFlyer additionally receives anonymous, aggregated install reports from Apple via SKAdNetwork.

When: measurement starts only after Google's consent dialog and — on iOS — Apple's tracking prompt. In the EU, EEA, UK and Switzerland it starts only if you consented in the consent dialog to storing information on your device and to personalised advertising; otherwise AppsFlyer does not start at all. Without consent in Apple's tracking prompt no advertising identifier is sent on iOS. Once you own ad-freedom, measurement no longer starts.

Purpose: measuring and billing our own ad campaigns and understanding purchase conversion. Legal basis: your consent (Art. 6(1)(a) GDPR, § 25(1) TDDDG); outside the EU, EEA, UK and Switzerland our legitimate interest in measuring our advertising (Art. 6(1)(f) GDPR). You can withdraw consent at any time through the privacy options in the consent dialog, where offered.

4. What we do NOT do

• No personalised advertising unless you allowed it. On iOS the permission is Apple's App Tracking Transparency prompt: decline it, or leave it unanswered, and the ads are non-personalised. On Android there is no such prompt — the decision rests on Google's consent dialog and is applied by Google's advertising SDK. See §3(j).
• No selling of your data, and no sharing of your puzzle results, times or friends list with any advertiser. What the ad SDK receives is the advertising identifier and ad-interaction data, never your game content.
• No third-party analytics or crash-reporting SDK — except AppsFlyer for measuring our ad campaigns and purchase conversion (§3(k)). RevenueCat records views of the Christmas pass purchase page (§3(g)); the error message in the update check (§3(f)) serves only to fix bugs.
• No sale or sharing of personal data for others' marketing.
• No collection of special-category data.

5. Who we share data with (processors)

We use trusted service providers who process data on our behalf under data-processing agreements:

• Supabase — backend hosting, database, and authentication. Region: EU (Ireland), AWS eu-west-1. See Supabase's privacy terms.
• Apple / Google — app distribution and payment processing for in-app purchases. Your payment details go to the store, never to us. If you use Sign in with Apple, Apple also acts as the identity provider and passes us the data listed in §3(h).
• RevenueCat — manages the in-app purchases and your resulting entitlements (levels unlocked, ad-free). It processes your account's user ID (see §3(g)), your purchase/receipt data, from version 3.4 views of the Christmas pass purchase page (§3(g)), and basic device/technical data needed to validate and restore purchases. It receives that user ID but not your username, display name, email address, or friends data. US-based; safeguarded by Standard Contractual Clauses and a data-processing agreement.
• Expo (Expo Push Service) — delivers notifications, if you have turned them on (§3(e)). It processes only your device's push identifier and the content of the notification itself (text, kind and, where relevant, game and text variant), passes both on to Apple or Google, and reports back to us whether Apple or Google accepted the notification. Your username, display name and friends data are not sent — though another player's name may appear inside the text of a notification: a friend's display name, or the username of someone who sent you a friend request. US-based; transfers are safeguarded by Standard Contractual Clauses.
• Expo (EAS Update, from version 3.4) — delivers bug fixes to the installed app (§3(f)). On every app start it receives the data listed there: your IP address, platform, app version, update channel, update identifiers and the installation ID, after a fatal start-up error also the error message. This happens whether or not you have turned notifications on. It does not receive your account ID, username, display name, friends or game data. US-based; transfers are safeguarded by Standard Contractual Clauses.
• Google (AdMob) — serves the ads described in §3(j) and receives the data listed there. Unlike the providers above, Google also uses that data for its own purposes (ad delivery across its network, fraud prevention, reporting), so it is not simply acting on our behalf. Google is US-based; transfers are safeguarded by Standard Contractual Clauses. If you own ad-freedom, no data reaches Google unless you tap a rewarded ad yourself: nothing to do with advertising is started for you unprompted (§3(j)).
• Unity Technologies (Unity Ads) — an ad network integrated through AdMob's mediation (§3(j)). It receives the data listed there only when it wins the bid for a given ad slot and its ad is actually shown. Like Google, Unity also uses that data for its own purposes (delivery across its network, fraud prevention, reporting), so it is not simply acting on our behalf. US-based; transfers are safeguarded by Standard Contractual Clauses. The same applies here: if you own ad-freedom, no data reaches Unity unless you tap a rewarded ad yourself.

• AppsFlyer Ltd. — measures our ad campaigns (§3(k)) and processes the data listed there on our behalf. Based in Israel (EU adequacy decision); processing among others in the EU and the US, safeguarded by Standard Contractual Clauses.
• Ad platforms we advertise on (for example TikTok) — receive from AppsFlyer whether an install or purchase came through their ad.

We disclose data only if required by law.

6. International transfers

Your account, social, and gameplay data is stored inside the EEA, in the EU (Ireland) region. Purchase and entitlement data handled by RevenueCat and Apple is processed on US infrastructure. Expo processes push and update requests on US infrastructure. Some of our providers are US-based companies whose staff may access data from outside the EEA for support or maintenance; such access is safeguarded by Standard Contractual Clauses and the providers' data-processing agreements. AppsFlyer is based in Israel, for which the European Commission has issued an adequacy decision.

7. How long we keep it

• Account, social, and gameplay data: for as long as your account exists.
• Notification data (§3(e)): the push identifier until you turn reminders off, delete your account, or Expo reports the device as no longer reachable; the queue and delivery receipts for 90 days, measurement events for 13 months, in each case no longer than your account exists.
• When you delete your account in the app (Profile → Delete account; from version 3.2 Profile → Settings → Delete account), your account and all associated rows are permanently deleted from our database — among them your profile, username, friendships, friend requests, daily results, level results, from version 3.2 your unsolved Words dailies, invitations and claimed invitation and event rewards and your name colour, from version 3.2.2 your showcase, any push identifiers, the notification-queue entries and delivery receipts described in §3(e), from version 3.4 the notification measurement events described there, and the blocks and reports described in §3(i). This cannot be undone.
• Local device data is removed when you uninstall the app.
• Measurement data at AppsFlyer: per AppsFlyer's retention policy; we delete it on request to iqmogged@lucasagency.de.
• Update requests at Expo (§3(f)): per Expo's retention policy; the installation ID stays on your device until you uninstall the app.
• A step-by-step description, including what is kept and for how long, is on our account deletion page.

8. Your rights (GDPR)

You have the right to access, rectify, erase, restrict, and port your data, and to object to processing. Specifically:

• Access / portability: request a copy of your data at iqmogged@lucasagency.de.
• Rectification: change your username and display name in the app at any time.
• Erasure: delete your account in-app (Profile → Delete account; from version 3.2 Profile → Settings → Delete account), or ask us at iqmogged@lucasagency.de.
• Complaint: you may lodge a complaint with your data protection authority (in Germany, your state's Datenschutzbehörde).

9. Not yet active (update this section when they launch)

The following are not used in this version and this policy must be updated before they go live:

• Crash reporting (Sentry): would process crash and diagnostic data.
• Analytics: no general analytics service, and no analytics SDK apart from AppsFlyer (§4). We measure only what is described above: from version 3.4, how our notification dialog and the notifications are used (§3(e)) and views of the Christmas pass purchase page, which RevenueCat records to measure purchase conversion (§3(g)); AppsFlyer measures our ad campaigns and purchase conversion (§3(k)).

(In-app purchases and Sign in with Apple are both live — see §3(g), §3(h) and §5. There are no subscriptions.)

10. Children

IQ Mogged is not directed at children under 16. We do not knowingly collect data from children under that age. If you believe a child has provided us with data, contact us at iqmogged@lucasagency.de and we will delete it.

(16 is the GDPR "digital consent" age unless a member state lowers it; Germany does not.)

11. Security

Access to your data is restricted by database Row-Level Security so only you and your confirmed friends can see the relevant rows — except for the data published while public ranking is on (section 3c), which is then visible to any signed-in player; session tokens are stored in the device's secure enclave; leaderboard submissions are validated server-side. No system is perfectly secure, but we take reasonable measures to protect your data.

12. Changes to this policy

We may update this policy; the "Last updated" date reflects the latest version. Material changes will be surfaced in the app or on the store listing.

13. Contact

The Lucas Agency GmbH — iqmogged@lucasagency.de — Am Kabellager 11, 51063 Köln, Germany

Eine deutschsprachige Fassung dieser Erklärung finden Sie unter Datenschutzerklärung.